-
Notifications
You must be signed in to change notification settings - Fork 29
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Home Assistant Core 2025.1.0 E Go Charger no Connection #102
Comments
Yeah so while I can access the charger as far as turning it on and off, every other sensor from the device is unavailable, with power consumption the most prominent I reverted back to the last 2024 version as well, for now • home-assistant: 2025.1.0 |
Same problem here, only turning on and off is available. • home-assistant: 2025.1.0 |
I run into the same issue this morning. Reverted back to 2024.12.5 solves the problem. |
Ok thank you for response. There is a Bug/problem with the Integration and the New Home Assistant Core. |
After the ha upgrade I received those two messages, one error, one warning in the ha logs:
|
According to this article: home-assistant/core#108991 |
should be fixed in version 0.26.0 ( PR #103 ) |
Same here, 0.26.0 fixed it. |
Hi, Dieser Fehler stammt von einer benutzerdefinierten Integration Logger: custom_components.goecharger Unable to fetch state for Charger charger1 • home-assistant: 2025.1.1 Any hints? No data is pulled. V2 enabled. |
All entries still show as unavailable for me as well, with Home Assistant v2025.1.1 and go- integration v0.26.0, updated from Git main branch today. When adding a new device (having deleted the old one before), the configure dialog comes up, but after adding, clicking on Configure always yields "Error: Config flow could not be loaded: 500 Internal Server Error Server got itself in trouble". |
I run into the same problem: Error: Config flow could not be loaded: 500 Internal Server Error Server got itself in trouble |
Same Message to me after update to 0.26.0 |
I restarted the go-e charger and HA after this all works fine. |
A restart of go-e charger helped! THX! |
Restarting unfortunately didn't help for me. |
|
Found the problem with my instance: I overlooked a problem with HACS that caused HACS to fail to start at all. Therefor no available updates were displayed anymore. Since I filtered the log for the integrations that were shown as faulty, I didn't immediately saw the HACS problem. Could that maybe the case with your instance, too?
Got that solution here (german language, but the screenshots may help nevertheless): https://community.simon42.com/t/hacs-einrichtungsfehler-aus-seitenleiste-verschwunden-doppelte-repo/43697/3 |
Thanks for the additional potential solution! However, I have not installed the component through HACS but manually through copying the subdirectory (because my homeassistant config directory is managed through Salt stack). So there should be no issue with two conflicting versions. |
Hello, also had the total failure of the plugin since 2025.1.x I am not a good programmer, so use the modified file at your own risk!
|
Describe the bug
A clear and concise description of what the bug is.
Versions (please complete the following information):
Additional context
Since the Upgrade from Home Assistant Core 2025.1.0 the Charger Don t connected more after i go back to Version Home Assistant Core 2024.12.5 all Connections are back.
The text was updated successfully, but these errors were encountered: