Heating program

Benoit G shared this problem 6 years ago
Known

Hello Zipato team,


Since a few days, my heating program is setting on "until next" alone...When I set it on "run program", it stays like this for a few mn or hours (depends, but I don't know on what) and is going again on "until next".

I use a Horstmann HRT4-ZW and my firmware is the last one (0.9.999.8A).


Thanks for your help!

Benoit

Replies (13)

photo
1

Hello,

Zipato team decided to modify the management of HRT4-ZW. They round the heating setting value to an interger (see https://community.zipato.com/topic/question-to-horstmann-hrt4-users-how-do-you-use-it)

I've already asked not to do it ... but no answer from the team ...

photo
1

Hi Christophe,


Are you sure that this is the same pb? As you can see on pic1, I have 17.4 and 18.7 values.


The thing is, after a few mn, the program is going alone to "until next" and set the value I trigged on the wall thermostat control...


Thanks,

benoit

Files: Pic1.JPG
photo
1

Hi Benoit,

I had the same strange behaviour recently and I have already open a ticket for that. It was impossible to keep the program running and was always switching to "until next" value.

How is configured the HRT4 in your virtual climate device? For myself, it was setup as input and output device. To fix temporary the problem, I have removed the HRT4 as input device from the climate device. Thus, I can see the target temperature on the HRT4 but I am not able to assign a different one directly from the HRT4.

It is not perfect but at least, the program is running smoothly (which was my priority) and I am still able to select a different temperature directly from the web app if necessary.

Concerning the rounding issue, could you have a look not to the climate but to the HRT4 and to SETPOINT_HEATING endpoint. You can see hereafter a table with my data. I refresh the HRT4 every 5mns. What is strange to me is there is always to have two values every 5min and not one with one rounded (and to be precise truncated) and one not. The value not truncated is not precisely the one set in the climate device (19.799999237060547 instead of 19.8).

I think when the HRT4 is used as input, it checks if the new value received from the HRT4 is identical or not to the current one defined in the climate device. And because 19.0 (or 19.799999237060547 I don't know) is not identical to what is set-up by the climate calendar, it takes this as a new instruction and goes to "until next".

It is just a guess and I am waiting the feedback from zipato team on this.


t

v

2015-11-03T15:52:34Z

19.0

2015-11-03T15:47:35Z

19.799999237060547

2015-11-03T15:47:34Z

19.0

2015-11-03T15:42:35Z

19.799999237060547

2015-11-03T15:42:34Z

19.0

2015-11-03T15:37:35Z

19.799999237060547

2015-11-03T15:37:34Z

19.0

2015-11-03T15:32:35Z

19.799999237060547

2015-11-03T15:32:34Z

19.0

2015-11-03T15:27:35Z

19.799999237060547

2015-11-03T15:27:34Z

19.0

2015-11-03T15:22:35Z

19.799999237060547

2015-11-03T15:22:34Z

19.0

2015-11-03T15:17:34Z

19.799999237060547

2015-11-03T15:12:34Z

19.799999237060547

2015-11-03T15:07:34Z

19.799999237060547

2015-11-03T15:07:33Z

19.0

2015-11-03T15:02:34Z

19.799999237060547

2015-11-03T15:02:33Z

19.0

2015-11-03T14:57:32Z

19.799999237060547

2015-11-03T14:57:31Z

19.0

2015-11-03T14:52:32Z

19.799999237060547

2015-11-03T14:52:31Z

19.0

2015-11-03T14:47:32Z

19.799999237060547

2015-11-03T14:47:31Z

19.0

2015-11-03T14:42:32Z

19.799999237060547

2015-11-03T14:42:31Z

19.0

2015-11-03T14:37:32Z

19.799999237060547

2015-11-03T14:37:31Z

19.0

2015-11-03T14:32:32Z

19.799999237060547

2015-11-03T14:32:31Z

19.0

2015-11-03T14:27:32Z

19.799999237060547

2015-11-03T14:27:31Z

19.0

2015-11-03T14:22:32Z

19.799999237060547

2015-11-03T14:22:31Z

19.0

2015-11-03T14:17:32Z

19.799999237060547

2015-11-03T14:17:31Z

19.0

2015-11-03T14:12:32Z

19.799999237060547

2015-11-03T14:12:31Z

19.0

2015-11-03T14:07:32Z

19.799999237060547

2015-11-03T14:07:31Z

19.0

2015-11-03T14:02:32Z

19.799999237060547

2015-11-03T14:02:31Z

19.0

2015-11-03T13:57:32Z

19.799999237060547

2015-11-03T13:57:31Z

19.0

2015-11-03T13:52:32Z

19.799999237060547

2015-11-03T13:52:31Z

19.0

2015-11-03T13:47:32Z

19.799999237060547

2015-11-03T13:47:31Z

19.0

2015-11-03T13:42:32Z

19.799999237060547

2015-11-03T13:42:31Z

19.0

2015-11-03T13:37:32Z

19.799999237060547

2015-11-03T13:37:31Z

19.0

2015-11-03T13:32:32Z

19.799999237060547

2015-11-03T13:32:31Z

19.0

2015-11-03T13:27:32Z

19.799999237060547

2015-11-03T13:27:31Z

19.0

2015-11-03T13:22:32Z

19.799999237060547

2015-11-03T13:22:31Z

19.0

2015-11-03T13:17:32Z

19.799999237060547

2015-11-03T13:17:31Z

19.0

2015-11-03T13:12:32Z

19.799999237060547

2015-11-03T13:12:31Z

19.0

2015-11-03T13:07:32Z

19.799999237060547

2015-11-03T13:07:31Z

19.0

2015-11-03T13:02:32Z

19.799999237060547

2015-11-03T13:02:31Z

19.0

2015-11-03T12:57:32Z

19.799999237060547

2015-11-03T12:57:31Z

19.0

2015-11-03T12:47:32Z

19.799999237060547

2015-11-03T12:47:31Z

19.0

2015-11-03T12:42:32Z

19.799999237060547

2015-11-03T12:42:31Z

19.0

2015-11-03T12:37:32Z

19.799999237060547

2015-11-03T12:37:31Z

19.0

2015-11-03T12:32:32Z

19.799999237060547

2015-11-03T12:32:31Z

19.0

2015-11-03T12:27:32Z

19.799999237060547

2015-11-03T12:27:31Z

19.0

2015-11-03T12:22:32Z

19.799999237060547

2015-11-03T12:22:31Z

19.0

2015-11-03T12:17:32Z

19.799999237060547

2015-11-03T12:17:31Z

19.0

2015-11-03T12:12:32Z

19.799999237060547

2015-11-03T12:12:31Z

19.0

2015-11-03T12:07:32Z

19.799999237060547

2015-11-03T12:07:31Z

19.0

2015-11-03T12:02:32Z

19.799999237060547

2015-11-03T12:02:31Z

19.0

2015-11-03T11:57:32Z

19.799999237060547

2015-11-03T11:57:31Z

19.0

2015-11-03T11:52:32Z

19.799999237060547

2015-11-03T11:52:31Z

19.0

2015-11-03T11:47:32Z

19.799999237060547

2015-11-03T11:47:31Z

19.0

2015-11-03T11:42:32Z

19.799999237060547

2015-11-03T11:42:31Z

19.0

2015-11-03T11:37:31Z

19.0

2015-11-03T11:37:30Z

19.799999237060547

2015-11-03T11:32:30Z

19.799999237060547

2015-11-03T11:32:29Z

19.0

2015-11-03T11:27:30Z

19.799999237060547

2015-11-03T11:27:29Z

19.0

2015-11-03T11:22:30Z

19.799999237060547

2015-11-03T11:22:29Z

19.0

2015-11-03T11:17:30Z

19.799999237060547

2015-11-03T11:17:29Z

19.0

2015-11-03T11:12:30Z

19.799999237060547

2015-11-03T11:12:29Z

19.0

2015-11-03T11:07:30Z

19.799999237060547

2015-11-03T11:07:29Z

19.0

2015-11-03T11:02:30Z

19.799999237060547

2015-11-03T11:02:29Z

19.0

2015-11-03T10:57:30Z

19.799999237060547

2015-11-03T10:57:29Z

19.0

2015-11-03T10:52:30Z

19.799999237060547

2015-11-03T10:52:29Z

19.0

2015-11-03T10:47:30Z

19.799999237060547

2015-11-03T10:47:29Z

19.0

2015-11-03T10:42:30Z

19.799999237060547

2015-11-03T10:42:29Z

19.0

2015-11-03T10:37:30Z

19.799999237060547

2015-11-03T10:37:29Z

19.0

2015-11-03T10:32:30Z

19.799999237060547

2015-11-03T10:32:29Z

19.0

2015-11-03T10:27:30Z

19.799999237060547

2015-11-03T10:27:29Z

19.0

2015-11-03T10:22:30Z

19.799999237060547

2015-11-03T10:22:29Z

19.0

2015-11-03T10:17:30Z

19.799999237060547

2015-11-03T10:17:29Z

19.0

2015-11-03T10:12:28Z

19.799999237060547

2015-11-03T10:12:27Z

19.0

2015-11-03T10:07:28Z

19.799999237060547

2015-11-03T10:07:27Z

19.0

2015-11-03T10:02:27Z

19.799999237060547

2015-11-03T10:00:07Z

19.799999237060547

2015-11-03T09:57:27Z

21.0

2015-11-03T09:52:27Z

21.0

2015-11-03T09:52:26Z

21.0

2015-11-03T09:47:27Z

21.0

2015-11-03T09:47:26Z

21.0

2015-11-03T09:42:27Z

21.0

2015-11-03T09:42:26Z

21.0

2015-11-03T09:37:27Z

21.0

2015-11-03T09:37:26Z

21.0

2015-11-03T09:32:25Z

21.0

2015-11-03T09:32:24Z

21.0

2015-11-03T09:27:25Z

21.0

2015-11-03T09:27:24Z

21.0

photo
1

Hi Cédric,


I removed the HRT4 as input device from the climate device and it works... It not clearly the best solution but my heating program is now working!


How can I get the table?


Merci ;)

Benoit

photo
1

Hi Cédric,


I removed the HRT4 as input device from the climate device and it works... It not clearly the best solution but my heating program is now working!


How can I get the table?


Merci ;)

Benoit

photo
1

Hi Benoit,


De rien. To view the table of SETPOINT_HEATING endpoint, you go on Device manager, select Zwave->Hortsmann HT4-ZW->Thermostat->Thermostat setpoint -> SETPOINT_HEATING and click on SETTINGS. The second tab "EVENTS" lists your data.

To extract your data, you copy the UUID on the first tab and you replace {UUID} by your data in the following link:


https://my.zipato.com:443/zipato-web/v2/log/attribute/{UUID}?count=100&order=desc

photo
1

Hello,

I have the same conclusion as Cedric

I've already opened a ticket on support site and i have received the following answer :

If the value will be 20.5 or above then it will be rounded to the 21,

it will be up rounded not down rounded as before.


This will be active with the new firmware version.


Best regards,


Milan


For my point of view, we, HT4-ZW owners, have to all ask the zipato team to stop to round the set_point value !

What do you mind ?

photo
1

I agree. I don't understand what was the need of forcing the rouding for the hrt4. In the meanwhile I don't understand neither why a temperature target has been stored by the virtual climate with more than one digit. The initial bug was this one according to me.

photo
1

Yes I agree! It was working well before... I also send an email to the team.


Benoit

photo
1

Yes you are right "IT WAS WORKING WELL BEFORE"


Zipato team ? Do you listen to customer voice ?

photo
1

New user, I totally agree with that and aim in consequence to send back the Zipabox......what a pity.......I had bought it as an alternative to a Nest.....big big big deception

photo
1

New user, I totally agree with that and aim in consequence to send back the Zipabox......what a pity.......I had bought it as an alternative to a Nest.....big big big deception

photo
1

New user, I totally agree with that and aim in consequence to send back the Zipabox......what a pity.......I had bought it as an alternative to a Nest.....big big big deception

Leave a Comment
 
Attach a file