Closed kristofbriers closed 5 months ago
Hey there @cereal2nd, @brefra, mind taking a look at this issue as it has been labeled with an integration (velbus
) you are listed as a code owner for? Thanks!
(message by CodeOwnersMention)
velbus documentation velbus source (message by IssueLinks)
This is normal, after some time it should be finished.
Can take up to 5 minutes the first time.
It does not have this issue with 2024.4.1. And even after a couple of hours all the velbus modules are all grayed out...
(switches,sensors,...) I have switched back and forward between 2024.4.1 and 2024.4.3 but I can't get it working in the latest version
Also, It looks like it can't read all of the modules names anymore..
Can you get me a diagnostics download?
On Fri, 19 Apr 2024, 20:58 kristofbriers, @.***> wrote:
It does not have this issue with 2024.4.1. And even after a couple of hours all the velbus modules(switches,sensors,...) are all grayed out...
— Reply to this email directly, view it on GitHub https://github.com/home-assistant/core/issues/115859#issuecomment-2067127439, or unsubscribe https://github.com/notifications/unsubscribe-auth/AA4LF4OTXQ3TLICTOE5Y5F3Y6FSNJAVCNFSM6AAAAABGPTYRYWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANRXGEZDONBTHE . You are receiving this because you were mentioned.Message ID: @.***>
Can you get me a diagnostics download? … On Fri, 19 Apr 2024, 20:58 kristofbriers, @.> wrote: It does not have this issue with 2024.4.1. And even after a couple of hours all the velbus modules(switches,sensors,...) are all grayed out... — Reply to this email directly, view it on GitHub <#115859 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AA4LF4OTXQ3TLICTOE5Y5F3Y6FSNJAVCNFSM6AAAAABGPTYRYWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANRXGEZDONBTHE . You are receiving this because you were mentioned.Message ID: @.>
I created a empty test homeassistent VM and have the same issue when I only added velbus: Here is the diagnostics file: config_entry-velbus-d81a80ea7878a6e8c4623433520f35ae.json
Issue is the same in version 2024.4.4. It takes 20times longer to start velbus and can't find all the module names correctly.
in the logs i see this:
so it looks like the connection is aborted during setup
Issue is the same in version 2024.4.4. It takes 20times longer to start velbus and can't find all the module names correctly.
can you get me the hass logfile and the diagnostics dump?
I use velserv on a raspberry pi to connect. to velbus Can it have something to do with that? Strange thing is it keeps working on 2024.4.1...
Sure, here are the log files home-assistant_2024-04-24T09-53-33.355Z.log home-assistant_velbus_2024-04-24T10-06-52.501Z.log
I think I got it working! I was still using https://github.com/jeroends/velserv as tcp bridge I'm now using https://github.com/velbus/velbus-tcp-snap and it works like a charm!
I will continue testing it... @Cereal2nd Thanks for the tip on the velbus connection error!
perfect, we can close this one then?
The problem
Velbus plugin is having trouble starting up after upgrade to 2024.4.3
What version of Home Assistant Core has the issue?
2024.4.3
What was the last working version of Home Assistant Core?
2024.4.1
What type of installation are you running?
Home Assistant OS
Integration causing the issue
velbus
Link to integration documentation on our website
https://www.home-assistant.io/integrations/velbus/
Diagnostics information
home-assistant_velbus_2024-04-19T18-05-11.372Z.log
Example YAML snippet
No response
Anything in the logs that might be useful for us?
Additional information
No response