there is also a clear cache service for velbus
here you can clear the full cache or on a per module basis
1 Like
Hello,
My Velbus gateway changed its IP address after rebooting, how can I modify it in HA without deleting all my previous work?
Because I guess that deleting the velbus integration and re-adding it will render all my previous configurations useless?
Thanks a lot
This was asked a few weeks ago
See this answer
1 Like
I did not see the āAC modeā yet in 2023.2ā¦ do I need to reload something or did it get backlogged?
yeah i confused this with another error
there is a bit more work, but iāll make the change now
2 Likes
Hi everyone,
I set up my Velbus-integration in Home Assistant a few months ago, and everything was working fine. However, today I had to restart my NAS, and since then all switches in my velbus integration are gone. I tried reloading the integration and even removing it and adding it again, but the devices containing the switches (VMB4RYLD and so on) canāt be found in Home Assistant anymore. Everything still works in VelbusLink and in the Signum app.
Anyone know how to fix this?
Thanks in advance!
can you download a diagnostics and add it here?
Same. No more entities.
Thanks for looking into this.
Diagnostics can be found here:
https://justpaste.it/d3dp3
Let me know if you need anything else
according to this everything is loaded.
can you clear the velbus cache? (there is a service for this)
Cleared the cache and reloaded the integration, but the devices still arenāt found.
Indeed, everything that the integration finds is loaded correctly. There are however some devices (all devices containing the switches, which actually control the lights) that arenāt found by the integration.
Is there any way I can see which devices are discoverable from my VMBSIG module, so we can find out if the problem is on the Velbus or the Home Assistant side?
@Nyrax
Can you share the module types that you ācanāt seeā in your HomeAssistant setup?
For example
The summary in Velbuslink Tools that shows how many of each module type in your project Vs what you can see in HomeAssistant
So the first image is all my modules in VelbusLink. The second image (see comment below) are the ones that are found in Home Assistant. As you can see, all VMB4RYLD and VMBDMI-R modules are missing, and most of the VMB4RYNO modules (however, the one VMB4RYNO module that is found shows āThis entity is no longer being provided by the velbus integration. If the entity is no longer in use, delete it in settings.ā on each of the switches, so I canāt control that one either)
Hi all,
Looked into this some more today, and found the following in the logs when reloading the integration:
2023-03-17 08:36:10.189 ERROR (MainThread) [homeassistant.components.binary_sensor] Setup of platform velbus is taking longer than 60 seconds. Startup will proceed without waiting any longer.
2023-03-17 08:36:10.238 ERROR (MainThread) [homeassistant.components.button] Setup of platform velbus is taking longer than 60 seconds. Startup will proceed without waiting any longer.
2023-03-17 08:36:10.246 ERROR (MainThread) [homeassistant.components.climate] Setup of platform velbus is taking longer than 60 seconds. Startup will proceed without waiting any longer.
2023-03-17 08:36:10.267 ERROR (MainThread) [homeassistant.components.cover] Setup of platform velbus is taking longer than 60 seconds. Startup will proceed without waiting any longer.
2023-03-17 08:36:10.268 ERROR (MainThread) [homeassistant.components.light] Setup of platform velbus is taking longer than 60 seconds. Startup will proceed without waiting any longer.
2023-03-17 08:36:10.294 ERROR (MainThread) [homeassistant.components.sensor] Setup of platform velbus is taking longer than 60 seconds. Startup will proceed without waiting any longer.
2023-03-17 08:36:10.311 ERROR (MainThread) [homeassistant.components.switch] Setup of platform velbus is taking longer than 60 seconds. Startup will proceed without waiting any longer.
The logs are also filled with the following:
2023-03-17 08:36:11.930 WARNING (MainThread) [velbus-packet] UNKNOWN module, you should initialize a full new velbus scan: packet=ff, address=241, modules=dict_keys([16, 17, 18, 19, 20, 21, 23, 24, 2, 25, 32, 33, 34, 35, 36, 41, 48, 3, 49, 51, 4, 69])
2023-03-17 08:36:11.972 WARNING (MainThread) [velbus-packet] UNKNOWN module, you should initialize a full new velbus scan: packet=01:00:00:00:00:00:00, address=241, modules=dict_keys([16, 17, 18, 19, 20, 21, 23, 24, 2, 25, 32, 33, 34, 35, 36, 41, 48, 3, 49, 51, 4, 69])
2023-03-17 08:36:11.973 WARNING (MainThread) [velbus-packet] UNKNOWN module, you should initialize a full new velbus scan: packet=02:00:00:00:00:00:00, address=241, modules=dict_keys([16, 17, 18, 19, 20, 21, 23, 24, 2, 25, 32, 33, 34, 35, 36, 41, 48, 3, 49, 51, 4, 69])
2023-03-17 08:36:11.977 WARNING (MainThread) [velbus-packet] UNKNOWN module, you should initialize a full new velbus scan: packet=04:00:00:00:00:00:00, address=241, modules=dict_keys([16, 17, 18, 19, 20, 21, 23, 24, 2, 25, 32, 33, 34, 35, 36, 41, 48, 3, 49, 51, 4, 69])
Over and over and over, with the addresses of the modules that are missing.
I executed velbus.scan multiple times (although Iām not sure Iām doing it right) and this doesnāt seem to help at all.
Iāve had the same problem a long time ago with a VMBLCDW in the middle of the address range and blocking the scan for āunrecognize moduleā. It seems that your VMBSIG is blocking the scan so try to change its address to FE ( the last one) to see if it helps.
Hi all, last update on this issue, since I fixed it.
The problem was that one of the modules (a light switch) had been accidently disconnected, which made the module unreachable. The scan of all modules stopped at that address, which was in the middle of the address range, so everything beyond that wasnāt discovered. Reconnecting the module fixed the issue.
1 Like
What was the best way to rescan the bus ? I added some modules I need to show up in Home Assistant ā¦
but this requires an input (the interface)
can I just put the serverIP:port there?
R
1 Like