Unable to include HeatIt Z-Temp2 in Secure mode

[erik.simonson 4]

Hello all,

 

I am trying to setup a heating system. I have included the Heatit Z-water in secure mode successfully. Now I am trying add the thermostats (Z-temp2) in secure mode. Since I want to control the z-water relays directly by association from the thermostats, I believe that if this is to work, both Z-temp2's as well as z-water need to be included in secure mode (or all of them in non-secure mode). Since I started with z-water and have now configured it I would like to avoid to re-install it from start (just because the thermostats can not be included in secure mode). Btw, I have tried to install the thermostats in non-secure mode and it works like a charm, with the issue that I can not associate directly to the z-water (since it is included in secure mode).

 

Now to my questions

- Is there anyone else having any issue including any other device (thermostat, switch, dimmer etc) in secure mode?

- I understand that z-temp2 shall be possible to add to HC2 in secure mode. Anyone else having the same experience? (Yes, I have tried multiple times, I have placed the thermostat literally less than a meter from the HC2 during paring, also including it in non-secure mode is working OK).

- During inclusion the following happens:

  o The home center logs the following when adding in secure mode:

[11:34:56] Home Center in learning mode
[11:35:09] Device added
[11:35:10] Requesting neighbours, please wait...
[11:35:13] Requesting neighbours done.
[11:35:13] Add node status protocol done
[11:35:13] Adding devices complete
[11:35:13] Adding devices complete

 

The Z-Temp2 display the "Inc" after that. No transfer of parameters and/or association group data.

 

Compare with adding the z-temp2 in non-secure mode:

[11:39:14] Home Center in learning mode
[11:39:19] Device added
[11:39:19] Requesting neighbours, please wait...
[11:39:23] Requesting neighbours done.
[11:39:23] Add node status protocol done
[11:39:23] Adding devices complete
[11:39:23] Adding devices complete
[11:39:25] ID 426: Received parameter 1 report, value = 900
[11:39:25] ID 426: Received parameter 2 report, value = 10
[11:39:25] ID 426: Received parameter 3 report, value = 10
[11:39:25] ID 426: Received parameter 4 report, value = 0
[11:39:26] ID 426: Received parameter 5 report, value = 0
[11:39:26] ID 426: Received parameter 6 report, value = 10
[11:39:26] ID 426: Received parameter 7 report, value = 1
[11:39:26] ID 426: Received parameter 8 report, value = 50
[11:39:26] ID 426: Received parameter 9 report, value = 3
[11:39:26] ID 426: Received parameter 10 report, value = 5
[11:39:26] ID 426: Received parameter 11 report, value = 50
[11:39:26] ID 426: Received parameter 12 report, value = 400
[11:39:26] ID 426: Received parameter 13 report, value = 0
[11:39:27] ID 426: Received parameter 14 report, value = 0
[11:39:27] ID 426: Received association report from group 1
[11:39:27] ID 426: Received association report from group 2
[11:39:27] ID 426: Received association report from group 3
[11:39:28] ID 426: Received association report from group 1
[11:39:28] ID 426: Received association report from group 2
[11:39:28] ID 426: Received association report from group 3
[11:39:37] ID 426: Device configuration finished
[11:39:37] ID 426: Device configuration finished

 

 Any help/support/solution is appreciated.

 

BR,

Erik

 

 

[erik.simonson 4]

Hello all, 

 

I got an answer from Fibaro.  They are aware of the problem and I am asked to have patience,  since it will be solved in future updates.  They hope it will be soon,  without providing any sort of time frame. 

 

All software products is bound to have some issues,  that I do accept.  But what usually matters is how you deal with the customer when they have an issue due to product quality defects.

Fibaro "hoping" it will be solved is from my view not a particular convincing way to address my issue. 

[cwil 0]

On 1/19/2022 at 9:02 PM, erik.simonson said:

Hello all, 

 

I got an answer from Fibaro.  They are aware of the problem and I am asked to have patience,  since it will be solved in future updates.  They hope it will be soon,  without providing any sort of time frame. 

 

All software products is bound to have some issues,  that I do accept.  But what usually matters is how you deal with the customer when they have an issue due to product quality defects.

Fibaro "hoping" it will be solved is from my view not a particular convincing way to address my issue. 

I am using Heat-it thermostats and very pleased how this works at all. But I does not did investigate in the secure mode issue.

Referring your expectations of issues solving and updates by Fibaro is'nt satisfied so far. This one of the most challenging weaknesses of this SH environement so far. But this is just my personal opinion due to not solved request Tempkates and other full sensor integration likewise Heat-it, Sensative-Sticks, Aeotec.   

[erik.simonson 4]

On 3/30/2022 at 9:58 PM, cwil said:

I am using Heat-it thermostats and very pleased how this works at all. But I does not did investigate in the secure mode issue.

Referring your expectations of issues solving and updates by Fibaro is'nt satisfied so far. This one of the most challenging weaknesses of this SH environement so far. But this is just my personal opinion due to not solved request Tempkates and other full sensor integration likewise Heat-it, Sensative-Sticks, Aeotec.   

Thanks for high- lighting that Heatit works fine in non- secure mode.  It might be the way forward for me as well since Fibaro has hinted at a January update and it is now April....