Not setting Kumo App / Home Thermostat

[rr326]

I just installed the latest hass-kumo on Home Assistant 2023.10.3. I have a brand new Mitsubishi Kumo Cloud controller.

I can see my HA climate entity. I can set the temperature. BUT, it doesn't register on my physical Mitsubishi thermostat and on the Kumo Cloud App (IOS) it now shows the set point as "- -". (Whereas before it showed "68" and I would expect it to show my new set point: "69".)

I restarted HA. I restarted my IOS app. I don't see any errors in the home-assistant.log under pykumo.

Any ideas?

My Mitsubishi installer, btw, told me they rewrote some aspect of Kumo, so I wonder if this is a new issue?

Happy to give debugging info or to debug myself if you can give me some tips.

[FTI76]

Did you manually set the IP address for each unit within the configuration (Enable local cache)? If not I would try that my understanding is that will bypass Kumo Cloud for controls and talk directly to the units.

[rr326]

I went to "configure" and added my ip. It said to reload the inegration. I didn't know how to do that, so I restarted HA. When I click on the configure / unit settings the IP address is still blank. It looks it didn't properly accept my ip address. (192.168.1.92). No errors in the HA logs. Am I not setting it properly?

[FTI76]

Check the configuration section relating to prefer_cache and see if this helps. If I recall each time you re-configure the unit settings those fields are blank. config/kumo_cache.json https://github.com/dlarrick/hass-kumo

…

-- "It's such a fine line between stupid and clever" - David St. Hubbins

On Dec 6, 2023 at 9:59 AM -0500, Ross Rosen ***@***.***>, wrote: I went to "configure" and added my ip. It said to reload the inegration. I didn't know how to do that, so I restarted HA. When I click on the configure / unit settings the IP address is still blank. It looks it didn't properly accept my ip address. (192.168.1.92). No errors in the HA logs. Am I not setting it properly? — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you commented.Message ID: ***@***.***>

[dlarrick]

It's highly likely you are hitting the issue described in dlarrick/pykumo#15 . TL;DR: the Kumo ecosystem evidently uses a lookup table for F <-> C conversion, whereas HA uses math. If the value HA converts to is not in the table, the app shows "--".

Most of us just don't use the app anymore, and/or ignore the setpoint seen there. I can see how this would be more annoying when a physical thermostat is involved.

There's been some proof-of-concept code in that other ticket, but no actual pull requests.

[rr326]

I think @dlarrick is correct. I will close this.

Note - in this case, it does not display on the Kumo App, nor does it display properly on the wall thermostat, but it actually DOES properly set the temperature. (Which I can tell because it went up to the temp I set on HA.)

[rr326]

See dlarrick/pykumo#15