You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The value returned by the warmup climate entity when an override is set is misspelt.
overide
should have a double r as per all the object's property names and, er, the dictionary.
The value returned by the API appears to be an int, so to rectify this issue should be as simple as modifying the string value against the key in the dictionary declaration RUN_MODE = { at the start of warmup_cc/warmup4ie/warmup4ie.py. Therefore I'll leave this here for now in case anyone fancies having a crack at this as their first issue to PR and fix.
NB: for users this would be a Breaking Change, IF they rely on a text match with the mispelled text in the sensor template or automation logic, so we need to declare this on release
The text was updated successfully, but these errors were encountered:
I don't know if it related to this typo/misspelling:
When the thermostat is set to override (boost) outside of Home Assistant, it does not show the mode change correctly in Home Assistant. For me the mode changes to auto during override and back to heat when the override is complete.
@rct if you have this good, definitive test case, would you consider forking the project and making the change suggested in the first post above? If that fixes it then we can PR your change into the main project. Any contributions are very welcome, thanks
The value returned by the warmup climate entity when an override is set is misspelt.
should have a double
r
as per all the object's property names and, er, the dictionary.The value returned by the API appears to be an int, so to rectify this issue should be as simple as modifying the string value against the key in the dictionary declaration
RUN_MODE = {
at the start ofwarmup_cc/warmup4ie/warmup4ie.py
. Therefore I'll leave this here for now in case anyone fancies having a crack at this as their first issue to PR and fix.NB: for users this would be a Breaking Change, IF they rely on a text match with the mispelled text in the sensor template or automation logic, so we need to declare this on release
The text was updated successfully, but these errors were encountered: