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.

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

Requires reboot of Cerbo GX after Homeassistant restart #176

Open
AminShAT opened this issue Mar 3, 2024 · 5 comments
Open

Requires reboot of Cerbo GX after Homeassistant restart #176

AminShAT opened this issue Mar 3, 2024 · 5 comments
Labels
stale Issues marked as stale will be closed after 3 months of further inactivity

Comments

@AminShAT
Copy link

AminShAT commented Mar 3, 2024

The integration always loses connection to the Victron installation, once you restart Home Assistant (e.g. for Updates). I always need to reboot the Cerbo GX afterwards to get it connected again.

@braamvh
Copy link

braamvh commented Mar 4, 2024

This sounds like a network issue. The integration keeps working for me if either side is rebooted, but I do have my both my Cerbo and HA connected via a physical Ethernet cable (not to the same switch, but the switches are also connected).

@AminShAT
Copy link
Author

AminShAT commented Mar 4, 2024

Same here. Even on the same switch. I don't think it is a network connection because the Node red connection works instantly after reboot. It is just the integration that can not talk to the Cerbo.

@peregrines2
Copy link

Same Problem here unfortunately.
Using Ethernet ... so I think it is related to something else :(

@AminShAT
Copy link
Author

AminShAT commented Mar 10, 2024

Something in HomeAssistant is completely screwing up my Modbus protocol. My Victron Wallbox lost connection to the Cerbo twice a day.

When I turned off HomeAssistant all together, it worked fine.

I have now HomeAssistant running without the Victron integration and currently also Nodered turned off. That works fine as well.

I suspect the Victron integration being the root cause for this. I will keep you updated.

@sfstar
Copy link
Owner

sfstar commented Mar 13, 2024

Thank you for opening this issue.
Would it be possible for you to enable debug logging for the integration and provide the logdump in this issue thread?
Thanks in advance.

@sfstar sfstar added the stale Issues marked as stale will be closed after 3 months of further inactivity label May 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stale Issues marked as stale will be closed after 3 months of further inactivity
Projects
None yet
Development

No branches or pull requests

4 participants