-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Entities Not Populated After Integration Installation #146
Comments
This is pretty common. The integration gets the units' local IP address from the KumoCloud service. If you chose "prefer cache" at setup, this is done only once, at setup. If not, it's done at HA startup. But, the KumoCloud service is pretty bad about updating this value in their API. For some folks it never even seems to get set. So, you have a few choices:
|
meanwhile - installing HACS - my units were detected - and everything was lovely
edit: after some fnckery - i reassigned IPs in the network, HA VM reboots and reassignments, and locked IPs to the PACs, then adjusted the Kumo Config to set IPs there... |
Entities related to Kumo integration not populated after integration installation.
Mitsubishi Mini Split Installation circa 2020
3 heads, one wifi I/f
Network ID changed after Kumo was installed
HA logs show references to old network ID being used and failing when attempting to retrieve entity info
Kumo phone app successfully connects to devices with correct information shown.
The text was updated successfully, but these errors were encountered: