[SOLVED] HeatIt Z-Water not updating HC3 when valve changes status

[erik.simonson 4]

Hello all,

 

I have recently migrated from Homecenter 2 which had the equivalent setup as below, but without the issue described below.

 

I have the following

- HC3 running 5.172.23 with Z-wave engine version 3

- HeatIt Z-water (the legacy version) included with S2 securit

- HeatIt Thermostat included with S2 security

 

Current status

- The thermostat controls through direct association the valve on Z-water (turning on when too cold, and off when too hot)

- I can manipulate the thermostat setpoint from HC3 (web and app) with no problems

- I can manipulate the valve from HC3 (web and app) with no problems

 

My problem: When the thermostat is controlling the valve, the status of the valve is not updated on the HC3.

Example: So let us say that the valve is turned off and the thermostat turns it on, it will still show as off in the web/app of HC3. If I then in the web/app turn on the vale after that, nothing happens since the valve is already on. But if then turn it off after that in the web/app then the valve is turning off. So the problem is in my view a pure update issue from Z-water to HC3 (a problem I did not have on HC2).

 

I have taken care to double check all association settings since it is important to have that configuration correctly. The strange thing is that it seems correct from first inclusion of z-water but at the same time it does not look exactly as in HC2 so it is hard to say if this is properly done. Also, HC3 does not accept any other association than the default one which seems correct. It is a bit fishy....

 

I have also double checked towards the clip below since it seems to work.

 

Anyone having any experience or idea?

 

 

Edited April 27, 2025 by erik.simonson
Solved

[Brors94 115]

If I remember right the z-water first edition is included with singelchannel on the endpoint 0(controller). 
Think this have to be changed to multichannel, if you want it to behave like you describe 

[erik.simonson 4]

22 minutes ago, Brors94 said:

If I remember right the z-water first edition is included with singelchannel on the endpoint 0(controller). 
Think this have to be changed to multichannel, if you want it to behave like you describe 

Thanks for confirming, that was my recollection (from HC2) as well. However when I look into HC3 it looks like the picture below, and it does not seem to include what you mentioned above. Or have you yourself included z-water into HC3?

 

Please login or register to see this attachment.

[Brors94 115]

6 minutes ago, erik.simonson said:

Thanks for confirming, that was my recollection (from HC2) as well. However when I look into HC3 it looks like the picture below, and it does not seem to include what you mentioned above. Or have you yourself included z-water into HC3?

 

Please login or register to see this attachment.

 

I do have it on my hc3 engine 2, so dont know how it looks on engine 3. 

But it is a long time ago since I included a z-water v1. 

Please login or register to see this attachment.

 

 

But it also looks like yours is in multichannel? 🤔

 

What type of thermostat heatit v1 with the 1.92 update? 🤔

[erik.simonson 4]

12 minutes ago, Brors94 said:

 

I do have it on my hc3 engine 2, so dont know how it looks on engine 3. 

But it is a long time ago since I included a z-water v1. 

Please login or register to see this attachment.

 

 

But it also looks like yours is in multichannel? 🤔

 

What type of thermostat heatit v1 with the 1.92 update? 🤔

Yes, I would like to believe that my is with multichannel (but it was never single channel from the start either, either the HC3 z-wave engine 3 handles the z-water differently than HC2 OR the problem is still there but not visible to me).

 

The thermostats are HeatIt Z-TEMP2 

My problem is that I want to "excercise" the valves when they are not used for longer duration, it becomes difficult when the status is not correctly reported. I can work around it by comparing the thermostat setpoint to the actual temperature in the room and based on that decide whether I need to excercise the valve, but it is far from optimal.

[Brors94 115]

The z-temp 2 got the update relay parameter, So why not just make it go on and off once every monday night?  

[erik.simonson 4]

If you are referring to parameter 13, my understanding is the following: It causes the thermostat to update the gateway on a specified frequency whether it is in idle/heating mode. This in addition to informing in a push approach when it changes between idle/heating mode. And since that is working well as it is right now I do not understand how that will improve valve->z-water communication issue?

 

Can you please elaborate on you idea, I am not sure I understand you?

[GanzConrad 7]

 

[Brors94 115]

10 hours ago, erik.simonson said:

If you are referring to parameter 13, my understanding is the following: It causes the thermostat to update the gateway on a specified frequency whether it is in idle/heating mode. This in addition to informing in a push approach when it changes between idle/heating mode. And since that is working well as it is right now I do not understand how that will improve valve->z-water communication issue?

 

Can you please elaborate on you idea, I am not sure I understand you?

 

My idea with parameter 13 dosent fix the problem that you dont get the updated status of the "Relay" on the z-water.

But it do get that valve excersise once a week. 

If the parameter 13 is set to 60 minutes, and you make a scene that turns the valve on and off for 10min each monday night.
the termostat will take control again over that valve within the next 60min because of this "update relay status".    
 

 

 

 

[erik.simonson 4]

12 hours ago, GanzConrad said:

 

As I posted in the above linked thread, I do not experience that problem but I still do have my original problem above.

[erik.simonson 4]

12 hours ago, Brors94 said:

 

My idea with parameter 13 dosent fix the problem that you dont get the updated status of the "Relay" on the z-water.

But it do get that valve excersise once a week. 

If the parameter 13 is set to 60 minutes, and you make a scene that turns the valve on and off for 10min each monday night.
the termostat will take control again over that valve within the next 60min because of this "update relay status".    
 

 

 

 

I am with you, thanks for the idea. I will consider it as yet another workaround, right now I have already initiated a different workaround:

Create another linked Other/(Virtual)Thermostat within HC3. I have used the temperature from the Z-TEMP2 and the heating being the Z-water corresponding valve. I have ensured to have the same temperature hysterises.

 

It is for sure redundant control and also double control traffic when the valve shall change open/closed, however the status of each valve will be consistent with reality on the HC3 (the later being fairly important for me).

 

I will keep you posted (Otherwise no news is good news.)

 

 

[erik.simonson 4]

On 4/21/2025 at 11:31 PM, erik.simonson said:

I am with you, thanks for the idea. I will consider it as yet another workaround, right now I have already initiated a different workaround:

Create another linked Other/(Virtual)Thermostat within HC3. I have used the temperature from the Z-TEMP2 and the heating being the Z-water corresponding valve. I have ensured to have the same temperature hysterises.

 

It is for sure redundant control and also double control traffic when the valve shall change open/closed, however the status of each valve will be consistent with reality on the HC3 (the later being fairly important for me).

 

I will keep you posted (Otherwise no news is good news.)

 

 

Hopefully last post on this topic: The strangest thing, a few days later it all of suddenly works as intended (without above workaround applied anymore), I have not changed _any_ associations and/or parameters to the heating. 

I will keep my eye on this, If the issue re-appears I have identified the best workaround, I would use the following trigger to have a scene update the vale status::

 

{

  conditions = { {

      id = 251,

      isTrigger = true,

      operator = "==",

      property = "thermostatOperatingState",

      type = "device",

      value = "Heating"

    },

    {

      id = 251,

      isTrigger = true,

      operator = "==",

      property = "thermostatOperatingState",

      type = "device",

      value = "Idle"

    } },

    operator = "any"

}