Closed luc-ass closed 8 years ago
Nop, I haven't noticed. I have tested by setting a new temperature through Siri and then checking in the Evohome App on my iPhone and everything seemed correct. There could be some issues related to the server datetime. Right now, it tries to understand the timezone and adds 10 minutes, so if the time on the server is not correct or the timezone calculation is wrong, it could tell the Honeywell webservice to set the new temperature untill a date/time in the past.
Good idea. I'll check. Perhaps we can change it to "until next change"
Am 18.04.2016 um 19:43 schrieb Andrea notifications@github.com:
Nop, I haven't noticed. I have tested by setting a new temperature through Siri and then checking in the Evohome App on my iPhone and everything seemed correct. There could be some issues related to the server datetime. Right now, it tries to understand the timezone and adds 10 minutes, so if the time on the server is not correct or the timezone calculation is wrong, it could tell the Honeywell webservice to set the new temperature untill a date/time in the past.
— You are receiving this because you authored the thread. Reply to this email directly or view it on GitHub
Okay, I updated the system time of my raspi (productive system) and rebooted. Now it works perfectly! Thanks again!
Next up: Change 10 minutes to "until next change"
Hey @zizzex,
just saw, that the plugin doesn't cause a problem when setting the temperature (the base station even reflects that the phone changed something - which is then persistent) but the temperature is not changed. Have you noticed something similar?