I have a heat pump that integrates via an MQTT-derived climate entity. The entity is configured via the standard MQTT discovery topic (published by the underlying controller, mitsubishi2mqtt). Although this is working well, there is one quirk that I am not sure is a defect or expected behavior. If the “settings” topic is changed (republished) externally - in this case, changing the setpoint via the HP units remote - the HA entity does not update. Is this expected/intended behavior, or is it an omission in the handling of these entities?
My mitsubishi2mqtt code was built to be bi-directional, specifically so that occasional changes in settings on the HP unit via the remote flow back to MQTT so the status could be accurately reflected in HA.
Based on a quick look at the code, it would appear that this situation should be handled by the handle_target_temperature_received callback -
log reveals
2022-12-05 09:45:58.107 ERROR (MainThread) [homeassistant.components.mqtt.climate] Could not parse temperature from
In interesting timing, it seems this was a defect in the controller firmware which causes the problem if the temperature setpoint is equal to the configured minimum. A change was committed to fix this a couple of days ago, which was after I did my original build.