-
Notifications
You must be signed in to change notification settings - Fork 42
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
"Error setting up entry" after full power down #146
Comments
Heres additional logs that might help
|
This issue appears to be related to #144. It has been fixed in the master branch, so it may resolve this issue as well. You can get the master branch using HACS, so could you try it out? If the IP address has changed, you should be able to migrate to the new IP address by turning the power on/off on the target device. |
This issue may have been fixed in Version 3.7.7, so I'm closing this. If the problem continues, you can reopen it. |
I installed ECHONETLite a few weeks ago and everything has been working perfectly.
I'm just getting some solar panels installed so the whole house has had power cut temporarily so the Air Condiitioner lost power, and I gracefully shut down the Home Assistant docker.
Now the power is back on and Home Assistant is alive and well with everything working except EchonetLite.
Heres the log file:
Everything else is working in Home Assistant, and the crappy Mitsubishi cloud app is still able to control the aircon (I know this is a different protocol, but just confirming that the aircon has network connectivity)
What are the troubleshooting steps from here?
Thanks
The text was updated successfully, but these errors were encountered: