Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Ecowitt doesn't work after HA upgrade! #155

Open
Jonvelle53 opened this issue May 6, 2023 · 23 comments
Open

Ecowitt doesn't work after HA upgrade! #155

Jonvelle53 opened this issue May 6, 2023 · 23 comments

Comments

@Jonvelle53
Copy link

No description provided.

@Jonvelle53
Copy link
Author

Do you also get support here, or where?
Sorry, but my English is very bad.

@cdohrman
Copy link

cdohrman commented May 7, 2023

same here, not sure how to handle it and not sure where to get support and who would fix it.

@albenex
Copy link

albenex commented May 7, 2023

had same issue because updated to HA 2023.5 while using HACS Ecowitt integration.
solved by:
-removing HACS Ecowitt integration (bypass warning that integration is configured)
-reboot HA
-remove old zombie Ecowitt configuration
-reboot HA
-add new configuration for Ecowitt using already-included Ecowitt integration

note: obviously IP will remain the same but endpoint path and port for server will change, depending on your configuration.
note2: you'll have to rename old entities on frontend because names will be different.

This was referenced May 7, 2023
Open
Open
@FeroX-Ron
Copy link

-reboot HA
all steps done

-remove old zombie Ecowitt configuration -reboot
where to remove?

@albenex
Copy link

albenex commented May 8, 2023

-reboot HA all steps done

-remove old zombie Ecowitt configuration -reboot where to remove?

in my case i still had old entities configured so i went to Settings - Integrations, selected and removed Ecowitt integration using 3 dots -> remove and then restarted.
maybe you already deleted old integration.

@FeroX-Ron
Copy link

FeroX-Ron commented May 8, 2023 •
edited
Loading

thanks, was my bad

@Jonvelle53
Copy link
Author

Jonvelle53 commented May 8, 2023 via email

@seidler2547
Copy link

Sorry, but the information given here is wrong. In the current state, this integration cannot work with Home Assistant 2023.5 because of an incompatibility. Here is the fix: #153

@Jonvelle53
Copy link
Author

Ok., thx

@kpWl
Copy link

kpWl commented May 11, 2023

Das Gleiche Problem habe ich seit HA 2023.5. Ich bin ohne Unterstützung nicht in der Lage, meine ecowitt wieder online zu bekommen - SCHADE. Kann ich irgendwie zu der Vorversion zurück?

@Jonvelle53
Copy link
Author

Jonvelle53 commented May 11, 2023 via email

@FeroX-Ron
Copy link

Hallo @Jonvelle53 ,

die alte Integration in HACS löschen.
Neustart
Danach die Integration aus dem Core (ecowitt) installieren, also nix mehr über HACS

Das ist jetzt eine offizielle Integration.

LG Ron

@Jonvelle53
Copy link
Author

Jonvelle53 commented May 12, 2023 •
edited
Loading

Danke Dir. Das hatte ich schon verstanden. Allerdings ging das Löschen irgendwie nicht. Gefühlt erst nach dem 50-sten mal nebst Neustarts.
Jetzt hab ich's endlich geschafft!
LG Luz

@Jonvelle53
Copy link
Author

Jonvelle53 commented May 12, 2023 via email

@snarlingllama
Copy link

Quick question, for the posts on this issue that are describing the installation of the "new" Ecowitt integration...

Are you reinstalling the HACS instance or the official integration?

@albenex
Copy link

albenex commented May 15, 2023

Quick question, for the posts on this issue that are describing the installation of the "new" Ecowitt integration...

Are you reinstalling the HACS instance or the official integration?

using official integration as the old one from HACS is not supported yet

@Jonvelle53
Copy link
Author

my old installation was the HACS integration!
And now i have the HA integration.

@toddeschroder
Copy link

Broken with 2023.5

Can't delete.

Tried to delete integration 30+ times and from various controllers followed by restart each time. Enabled or disabled.
No luck.

Can't install.

ERROR: Config flow could not be loaded: {"message":"Invalid handler specified"}
Removed line "registry = await async_get_entity_registry(self.hass)" as stated in #153
No luck.

@nliaudat
Copy link

cannot import name 'async_get_registry' from 'homeassistant.helpers.entity_registry' (/usr/src/homeassistant/homeassistant/helpers/entity_registry.py)

@ferdfer
Copy link

ferdfer commented Jun 27, 2023 •
edited
Loading

Solved!!!

Change in /config/custom_components/ecowitt/init.py

This two lines:

https://github.com/garbled1/homeassistant_ecowitt/pull/153/files

@iNaiks
Copy link

iNaiks commented Jul 19, 2023

Solved!!!

Change in /config/custom_components/ecowitt/init.py

This two lines:

https://github.com/garbled1/homeassistant_ecowitt/pull/153/files

It works !!!! fantastic !!! 🤩🥳.

@iNaiks iNaiks mentioned this issue Jul 19, 2023
Open
@mr-p666 mr-p666 mentioned this issue Sep 14, 2023
Open
@travisterrell travisterrell mentioned this issue Oct 31, 2023
Closed
@mr-p666 mr-p666 mentioned this issue Dec 6, 2023
Open
@Eric-IOT
Copy link

Solved!!!
Change in /config/custom_components/ecowitt/init.py
This two lines:
https://github.com/garbled1/homeassistant_ecowitt/pull/153/files

It works !!!! fantastic !!! 🤩🥳.

Solved!!!

Change in /config/custom_components/ecowitt/init.py

This two lines:

https://github.com/garbled1/homeassistant_ecowitt/pull/153/files

just perfect, it solved my case too... i was running the latest version of Hass on Synology... 👍 🥇

@JohnnyPrimus JohnnyPrimus mentioned this issue Jun 11, 2024
Closed
@githubStrini
Copy link

Thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests