When I switched my system to Evaporative cooling - thermo mode, the plugin would crash with a traceback error indicate a Key error "fanSpeed" on line 230 of hub.py. Inspecting the log revealed that when in thermo my climate uses a setpoint in the range of 1 - 8 for the fan speed. The XML key for this is setPoint.
I have added support so that if the unit is in evap - thermo mode it will use the key value SetPoint instead of fanSpeed and will construct the correct send command with the mode as thermo and fanSpeed sent as set point.
I have tested this over the last few days on my unit and it has been working perfectly. The HA climate integration still treats it is as changing the fan speed - this is similar to how the Bonaire Navigator controller works when in this mode.
I haven't thought of a better way to do this as the HA climate integrations isn't designed for a thermo mode that targets a fan speed like the bonaire units do.
When I switched my system to Evaporative cooling - thermo mode, the plugin would crash with a traceback error indicate a Key error "fanSpeed" on line 230 of hub.py. Inspecting the log revealed that when in thermo my climate uses a setpoint in the range of 1 - 8 for the fan speed. The XML key for this is setPoint.
I have added support so that if the unit is in evap - thermo mode it will use the key value SetPoint instead of fanSpeed and will construct the correct send command with the mode as thermo and fanSpeed sent as set point.
I have tested this over the last few days on my unit and it has been working perfectly. The HA climate integration still treats it is as changing the fan speed - this is similar to how the Bonaire Navigator controller works when in this mode.
I haven't thought of a better way to do this as the HA climate integrations isn't designed for a thermo mode that targets a fan speed like the bonaire units do.