-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The heater doesn't return to schedule temp after calendar event #79
Comments
so it is locked then will keep the custom user temp as target. If is not locked then user target temp will be changed by calendar when the new change in calendar is comes up |
Hi Sergiu thanks for reply, I made another quick test but still working in that strange mode: tell me where I can find some logs to help you (I solved by reset every hour by send a msg.payload={"isLocked":false,"isUserCustom":false}) but not a nice solution |
Hi, i have the exact same Problem. Look at the video. 2022-01-20.09-37-10.mp4Here's my test flow: Pls help, thats a really bad situation. |
Hello, same here. Reinstalled my nodered on new machine, updated to newest heater node, and i'm seeing same behavior as described above. If i hit "refresh" or "reload" button (the one with crooked arrow), only then it jumps back to scheduled temp. |
Thanks for that issue, i thought that i made something wrong. But looks like i'm not the only one having that problem. Thanks |
Same behavior here as @sniicker - since updating my system to the latest, I'm seeing the same "change for a few seconds, then revert" behavior. |
condition:
1-user set temp to x
2 - calendar event set heater to y
3 at next room temperature sensor reading (topic.currentTemp) the temperature return to value x
the is locked is undefined but I tried also to set to false: same result
The text was updated successfully, but these errors were encountered: