Set temperature on Danfoss with a scene

[stevie 0]

Hi,

 

I am new to HC2 and creating scene's.

 

I want to set a temperature on a Danfoss via a Scene in my HC2 but nothing seems to happen, I guess the reason is that the device is sleeping?

 

How should I wake up the device?

 

Thanks for your answer.

 

Kind regards

Steven

[petergebruers 1,268]

All battery powered devices wake up at regular intervals. The default for danfoss is 15 minutes.

You can wake up a Danfoss thermostat manually (for testing) by pushing (short) the middle button.

This is the code to set a thermostat:

Please login or register to see this code.

Run it, press the middle button and watch the display change to 24.

[stevie 0]

Thanks for the quick reply, does work.

[djtonsil 0]

What exactly is the impact of "setTime" to tonumber(os.time(t)) + 120*60)? What does it change for the danfoss device or, respectively for the HC2?

 

Also without setting the time directly, I recognize that my HC2 often shows the new target temp (e.g. from the heating schedule) plus the 2h clock (decreasing afterwards) when a danfoss woke up and got the update value.

 

So far I thought that I only use setTime to override the heating schedule in HC2 (e.g. keep 22 degress for 2h independent of the heating schedule).

 

Does anyone have more insights what exactly setTime does?

 

Thanks

-djtonsil

[petergebruers 1,268]

setTime is indeed the countdown timer below the temperature in the web UI or mobile UI. The lua code works exactly like the temp & time buttons in the UI. Two burrons, two calls in lua. If you set temp, but no time, the timer defaults to 2 hours. And, as you say, it's an override for the heating panel. When time reaches 0 it reverts back to the schedule from the heating panel. But what if you don't have a schedule? I don't know and I can't try at the moment. If you can find the time, please share with us 

Please login or register to see this image.

/emoticons/default_icon_smile.gif" alt=":-)" />

 

If you start experimenting, I need you know that another user has reported anomalies with the heating panel (confirmed by me) 

Please login or register to see this link.

[djtonsil 0]

Ok, great, it looks like we're dealing with the same stuff. Thanks for the pointer to the bug which I read through.

 

FYI, I'm using 5 danfoss LC 13 with two heating panels and the vacation mode (for which I created a virtual device and scenes for the mobile remote access).

 

For me it seems that the heating panel works ok apart from the 2h setting. All danfoss receive the new target temp within wake-up intervals. But as you describe, the HC2 shows a thermostat timer of 2h after the device is updated and it looks like it wouldn't adapt to new values of the heating panel schedule until the 2h expired again. Because there are always more than 2h (plus wake-up interval time) between different temp settings in my heating panels that doesn't seem to be a problem but it's certainly confusing.

 

I could imagine that the danfoss is confirming the new temp back to the HC2 which is then interpreting this to be set manually by pressing the danfoss button which would lead to a temp being set for 2h and overriding the heating panel. I haven't technically verified this, though.

 

When I'm setting the vacation mode for all heating panels I set the thermostat timer to

tonumber(os.time()) + 0)

for all danfoss to make sure that they get the reduced temp the next time they wake up.

 

If my assumption above is right, you could potentially try to reset the danfoss timers back to 0 using a regularly run scene (e.g. run 10 min after heating schedule changes) or a virtual device. I don't think that we can catch the heating schedule changes as a trigger somehow. Maybe it's possible to catch when a danfoss is waking up and being update? I'd need to investigate this more myself but this could be an interesting trigger to set time back to 0.

 

I'm still not 100% sure what the thermostat "setTime" instruction would translate to if you need to describe in plain English. Since it takes an absolute timestamp, I suppose it's expected to be "keep the set target temperatur in HC2 for this device until timestamp X independent of heating panel schedule" (where timestamp X would be the absolute time compared to os.time()).

 

I hope this all somewhat makes sense

Please login or register to see this image.

/emoticons/default_icon_wink.gif" alt=";-)" /> happy to brainstorm more...

[djtonsil 0]

Just added a comment to the bug entry as well to confirm my experience.

 

I see that the bug reporter has the danfoss changes logged in the event panel but I don't see them in my HC2 event panel. Is there anything I need to activate to see this?