-
Notifications
You must be signed in to change notification settings - Fork 70
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
New update broke ecowitt #150
Comments
Oh and you can't uninstall it. Async something error. |
I redownloadeded the 0.6 version of the integration and that still works. After a reboot everything works as it should. |
Errors I get:
|
I get this error since Update to HAS 5.0 How to solve? Setup failed for custom integration ecowitt: Unable to import component: cannot import name 'async_get_registry' from 'homeassistant.helpers.entity_registry' (/usr/src/homeassistant/homeassistant/helpers/entity_registry.py) |
Solution is: #149 |
Doesnt work for me. I removed everything, redownloaded the 0.7 version of the integration, but cannot set it up under integrations. It gives me the message "Config flow could not be loaded: {"message: "Invalid Handler specified"} Redownloading the 0.6 version of the integration works then. |
@pvizeli |
Here is the official integration I far as I understand. this HACS version is no longer maintained. |
Aah... Got it now. All working again... |
Hi when i reinstall the official integration then i got the same error as Remko76. |
is here any solution? |
The HACS version is not maintained anymore. Uninstall and setup the official integration. |
had same issue because updated to HA 2023.5 while using HACS Ecowitt integration. note: obviously IP will remain the same but endpoint path and port for server will change, depending on your configuration. |
So how can I keep the naming of sensors? And can someone just update the hacs one to the regular one? Also the version 0.6 won't change to Fahrenheit. And I don't know if the new update will break more stuff. |
Solved --> #155 (comment) |
I dont know what's up but the new update totally broke it. Sorry.
The text was updated successfully, but these errors were encountered: