Scheduled temperature not sent to device (SRT321) in climat widget

Same problem for me, please could you fix this issue ? Thanks !

Yes, big problem with this device.

I add a SRT one month ago and no problem with it

I add others one week ago and i can't change value of thermostat with SRT.

I don't understand, the configurtion is the same in SRT device and in Thermostat.

I have the same issue with a second SRT. The target temperature is not send to that SRT but the probe sent the temperature to Zipabox.

It is taged like Solve. There is any solution ?

thanks.

This issue is tagged as solved, I upgraded my box firmware yesterday and still doens't work: what is the solution?

I include a Secure SRT321 (HRT4) in my Zipa system and added the thermostat.

I can control everything but when I change the setpoint of thermostat this change is not vissible on the SRT321.

please advice

I set it to 300 in Zipato and did a syncronisation.

I hope that that will send the wakeuptime to the SRT321

Hello,

300 minutes = 5 hours so if you change the setpoint of the thermostat, the SRT321 could be updated 5 hours later (depending of the last wakeup)

I have a SRT321 and i've set the wakeup time to 5 minutes... then if I modify the setpoint the SRT321 will be upadted in the next 5 minutes

Hi,

A wake up of 5 minutes is a bit short, the battery will discharge very fast.

about 20/30 minutes is for us a better compromise.

Regards

domotique-store.fr team

5 or 300 minutes doesn't matter. It doesn't work any more for 2 weeks :-/

10 of 15 min for low slowness radiator is fine, 15 to 30 for high slowness radiator is enough

Regards,

chilglord

@Chilglord : it's strange, because it works fine at home ...

@domotique-store.fr : for me 20 minutes is too long.

I have at 6:00 AM an new setpoint

With 20 min as wakeup time, this new setpoint will be updated (in the SRT321) between 6:00 an 6:20

I inderstand,

@Christohe : It's a compromise. If battery are empty after 3 month, it's not an optimal solution.

You can set hour of the setpoint change at 5:40 and it be updated between 5:40 and 6:00.

We hope futur product with "FLIRS" Z-Wave function that permit immediate communication with low power consumption. ZXT120 (Z-Wave to IR themostat for air-conditioner) use it but no conventionnal thermostat at this time.

@Chilglord : Can you check that "native association" function is not checked on SRT321 Zipabox configuration.

You can too, exclude then re-include SRT321 and associate it with the actuator (by the SRT321 menu, not the Zipabox associate function).

On climat, you must have only SRT321 in input, output and thermometer function (no actuator selected in this case because it's the SRT321 that drive the actuator by Z-Wave association).

Regards

domotique-store.fr team

Hi

I am pleased to tell that it works fine now

Set the wake-up value to 5 (I was in the impression that is ware seconds but they are minutes)

SRT321 sw 1 up en in LI mode

syncronise zipato on website

I am planning to add a mains supply to the SRT321 (3V)

Did you really get the virtual thermostat to send "set_temperature" to SRT321?

Here are the settings i used, works fine now.

When a change the virtual thermostat value, within 5 minutes the SRT321 updates and shoes the new setpoint in the display.

Be shure that you update the SRT321 to a wakeupvalue of 5 minutes

SRT321 switch 1 in up position and then in LI mode

then syncronise zipato on website

Excellent. I was missing the checkbox in associaties (sic?). After putting that in I could choose and save the theromstat as output in the virtual thermostat, and it sticks! And it sends "set_temp" to the SRT321. Before having the checkbox I could choose and save, but the boiler would turn up as output again.

Since I had already included the SRT321 in my system I did not need to do the switch 1 and LI mode. I just had to wait fo the next wakeup.

Now I will have a very stable temperature.

Thank you!