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
Hi, I'm very new here.
I'm indirectly using the HeatPump library as part of Mitsubishi2MQTT, that I integrated in my house's Home Assistance in 4 instances, one per (Mitsubishi) heat pump that I got installed in the past.
Despite having no issues with the Home Assistant (and HeatPump library) integration when using those heat pumps for cooling, I have as issue when using them for heating: in facts, it looks to me that the Mitsubishi heat pumps, when in heating mode, deliberately set the internal version of the target temperature between 2 and 4 degrees (Celsius) higher than what is commanded by means of the remote or by the CN105 connector (and the HeatPump library therefore).
While I do see some rationale in this choice (hot air floats up to room's ceiling, where heat pumps internal units are usually placed), it is in practice causing some overheating in the rooms that I'm trying to heat by combining traditional (gas powered) heating and those heat pumps, by means of Home Assistant and a common target temperature value.
So I propose to add a library-side setting for applying an offset to both the target and measured temperature values, as written to (target) and read from (measured) the heat pump; that common temperature offset would be on its own programmable by means of the library API (and then exposed in Mitsubishi2MQTT UI as an example); a default value of 0 would avoid any backward compatibility issue.
I do see a potential issue occurring when the target temperature is set by means of the remote, because I don't know whether the library can discriminate when a read-back value was set (internally to the heat pump) by means of the remote or it is just the last value earlier programmed over the CN105 connector by the library itself. I can imagine some possible tricks for overcoming this issue, but I'm not sure they could work in each and every possible circumstance. In any case it would be very acceptable, for my intended usage, to see a mismatch between the target temperature as read on the remote's display and the target temperature read from the library (and Mitsubishi2MQTT and HA therefore).
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi, I'm very new here.
I'm indirectly using the HeatPump library as part of Mitsubishi2MQTT, that I integrated in my house's Home Assistance in 4 instances, one per (Mitsubishi) heat pump that I got installed in the past.
Despite having no issues with the Home Assistant (and HeatPump library) integration when using those heat pumps for cooling, I have as issue when using them for heating: in facts, it looks to me that the Mitsubishi heat pumps, when in heating mode, deliberately set the internal version of the target temperature between 2 and 4 degrees (Celsius) higher than what is commanded by means of the remote or by the CN105 connector (and the HeatPump library therefore).
While I do see some rationale in this choice (hot air floats up to room's ceiling, where heat pumps internal units are usually placed), it is in practice causing some overheating in the rooms that I'm trying to heat by combining traditional (gas powered) heating and those heat pumps, by means of Home Assistant and a common target temperature value.
So I propose to add a library-side setting for applying an offset to both the target and measured temperature values, as written to (target) and read from (measured) the heat pump; that common temperature offset would be on its own programmable by means of the library API (and then exposed in Mitsubishi2MQTT UI as an example); a default value of 0 would avoid any backward compatibility issue.
I do see a potential issue occurring when the target temperature is set by means of the remote, because I don't know whether the library can discriminate when a read-back value was set (internally to the heat pump) by means of the remote or it is just the last value earlier programmed over the CN105 connector by the library itself. I can imagine some possible tricks for overcoming this issue, but I'm not sure they could work in each and every possible circumstance. In any case it would be very acceptable, for my intended usage, to see a mismatch between the target temperature as read on the remote's display and the target temperature read from the library (and Mitsubishi2MQTT and HA therefore).
What do you think ?
Beta Was this translation helpful? Give feedback.
All reactions