dlarrick
dlarrick
Closing some old tickets. This one is more of a support-type issue, not a problem with the integration itself.
This is merged, released in v0.3.7-beta. Assuming no issues I'll promote to stable in a week or so.
Closing some old tickets. This one was more of a support discussion, though I'll make a new ticket to be able to change "prefer cache" without removing/re-adding.
v0.3.12 has a change that may improve this situation.
FYI the latest version of PyKumo (v0.3.9) which is pulled in by hass-kumo v0.3.12 implements the ability to reboot the WiFi adapter when it sees certain API errors. I think...
I have been seeing this issue myself for the past couple of days, so it will get fixed once I have time to dig into it. Anyone who's seeing this...
OK, I did a little exploration this evening. The errant indoor units are returning: ``` {'_api_error': 'serializer_error'} ``` for requests they used to process just fine. This is the error...
FYI this has nothing to do with Home Assistant version. This issue is actually in the pykumo library and seems to be caused by something Mitsubishi changed. So it's possible...
I've published a new beta v0.3.5-beta which should resolve this issue. Given the severity I wanted to get a fix out quickly, so I've only done basic testing. Please test...
Things look overall somewhat better but I'm still seeing issues. I also started seeing a lot of '__no_memory' responses from 2 of my 3 indoor units. I power-cycled the system...