Heating Panel and Heat-it thermostats

[xirilius 0]

Hello,

 

I'm lost.... can i use linked devices (or something else) to combine Heating Panel (HP) with Heat-it Thermostats (HT)?

I want to use the time and temp settings in HP and send them to my thermostats.

 

Can HC2 do this for me or do i have to write a LUA scene,

i know how to write that scene, so that is not the problem.

 

I need to know if this is a standard HC2 option or not.

 

Example:

 

at 7:00 HP-1 sends 20 degrees to HT-1 in the livingroom, HT-1 shows the temperature in the display and controls the heating

at 09:00 HP-1 sends 15 degrees to HT-1 in the livingroom, HT-1 now shows the low 15 temperature.

 

at 8:00 HP-2 sends 20 degrees to HT-2 in the office, HT-2 shows the temperature in the display and controls the heating

at 17:00 HP-2 sends 15 degrees to HT-2 in the livingroom

 

and so on with the other thermostats and Heating Panels.

Edited September 6, 2018 by xirilius

[drboss 107]

Yes the HP work with Thermostat (I use TKB). You only need select good thermostat for room in rooms view as default. You don't need create any link/connection, it work direct with HP panel.

 

[10der 832]

On 9/8/2018 at 1:15 PM, drboss said:

Yes the HP work with Thermostat (I use TKB). You only need select good TKB for room in rooms view as default. You don't need create any link/connection, it work direct with HP panel.

 

5

Hi!

as I can see you also have TKB Thermostat. I have a question for you 

can you see updates here whenThermostat change state from ON to OFF and vice versa?  

 

Please login or register to see this image.

 

Thank you!

[drboss 107]

Yes, the status is changed after on/off thermostat remotely or locally.

Association in group 1 - HC2, parameters 1 = 0, 2=1, 3=0, 4=1

Please login or register to see this image.

/monthly_2018_10/image.png.6706b6969168ad7a042ebb760f6618a7.png" alt="image.png.6706b6969168ad7a042ebb760f6618a7.png" />

[10der 832]

15 minutes ago, drboss said:

Association in group 1 - HC2, parameters 1 = 0, 2=1, 3=0, 4=1

opps!

 

can you provide details for manual params (with types)?

association already has done

Please login or register to see this image.

 

 

thank you so much!

is it right?

 

unfortunately, 2 cannot be 1. after assign it always returned as 0 

 

[16:06:26] ID 1101: Set parameter 2, value = 1
[16:06:26] ID 1101: Received parameter 2 report, value = 0
[16:06:44] ID 1101: Set parameter 2, value = 1
[16:06:44] ID 1101: Received parameter 2 report, value = 0

 

Edited October 30, 2018 by 10der

[drboss 107]

yes, i not sure the role of parameters but I do this experimentally , but I have possibility only set single association:

 

Please login or register to see this image.

/monthly_2018_10/image.png.08d9b55cf4c7f135753c46a5502a1ad2.png" alt="image.png.08d9b55cf4c7f135753c46a5502a1ad2.png" />

my version is:

for parameters the fist one I things is for "on" offset. 1 is +1 degrees plus for default between on and off. I tested one time, but for verification I haven't yet time.

Please login or register to see this attachment.

[10der 832]

Device kind:com.fibaro.operatingMode
Producer:TKB Home
Version:1.3

Z-Wave protocol type:3
Z-Wave protocol ver.:4.38

[petergebruers 1,268]

Something weird... @drboss your "version" reads as "0.13" (printscreen from HC device page) but @10der's version reads "1.3" (extract from device json API response) - that looks a similar but still I think if these devices are the same, both should display "1.3". In fact, the "0.13" looks weirder to me than the "1.3"...

 

To identify the devices correctly, you have to compare this property:

 

"productInfo": "1,24,2,1,5,1,1,3"

 

That's from 10der's device, and the 1,3 as you might have guessed are upper and lower byte of FW version (in Z-Wave parlance: APP_FIRMWARE_ID). The manufacturer can assign any number, so both 0.13 and 1.3 are equally valid (hex: 0x0D or 0x13)

 

If they are identical... what HC/HCL firmware are you guys running?

 

 

[10der 832]

4.510

[drboss 107]

I use to 4.510, but I see one difference in association group 1. In my case I possibility only check for controller , but on screen @10der I see checked [M].

 

Please login or register to see this image.

/monthly_2018_10/image.png.091f43ca833d0a9a11140cf7628a181d.png" />

for my TKB version is: 

"productInfo": "1,24,2,1,5,1,0,13",

"zwaveInfo": "3,4,38",

"zwaveVersion": "0.13"

 

Edited October 31, 2018 by drboss

[10der 832]

so, you have the previous version thermostat

[petergebruers 1,268]

I'm not sure what the difference is, because the manufacturer can use that firmware field as he likes. It might be older, or it might be different hardware revision, or a different model (e.g. other type of relay output but same functionality). It might be the same and the manufacturer accidentally wrote 0.13 to that field. I don't think this manufacturer offers OTA updates, or do they?

 

For example... As a rule of thumb... Fibaro devices with 2.x cannot be upgraded to 3.x because they have different hardware. They usually have different parameters and functionality as well.

 

I asked 10der to select M instead of S but I do not think the device has multiple endpoints, so that does not matter and does not help.

 

@drboss Thanks for the feedback. Now we know your thermostat is likely to be similar, but not identical!