Closed mvillarejo closed 3 years ago
I think I managed to get some extra details. Looks like the main issue is related to the fact that the climate that is created to control all the zones, does not contain the 'mode' information and seems that when there's an update on the climate zone devices, it also tries to update the virtual climate from the system.
In my case I have 4 zones so as soon as I modify one of them, zone P1 fails and start throwing all the errors above.
Hope that helps
Only thing I can think of is that the KeyError exception is caused because originally the 'mode_raw' variable is a string and then for some reason it's kind of 'presented' as an integer and therefore the MODES_CONVERTER stop working for the common System climate.
I don't use it that much so I wouldn't mind excluding it if it is possible.
Hi, sorry for the delay, I lack free time.
Indeed it's strange, API seems to suddenly returning the mode as an integer instead of string.
Just fix it in the last version.
Max
Hello, First of all, thank you for making this plugin is an amazing implementation (I started my own but not good at all compared to this one).
Just wanted to report an issue that has started since a few weeks back. My climates are detected properly but after a while, they throw an error and stopped working (having to restart the instance to get them back online).
This is the error I'm getting (note that climate.p1 is the global climate of the floor):
after that, any subsequent update of params or function call stopped working, any idea of what's happening?
Cheers, Manuel