in this log it seems that there is communication to the bus.
2025-05-27 23:02:27.509 INFO (MainThread) [velbus-handler] Starting handling scan 70
2025-05-27 23:02:27.510 INFO (MainThread) [velbus-handler] Starting scan 70
2025-05-27 23:02:27.510 ERROR (MainThread) [velbus-protocol] Restarting Velbus writer due to AttributeError(“‘NoneType’ object has no attribute ‘is_closing’”)
what module_type is 70?
FYI
That is the beauty of a CANbus based system, you can have multiple devices without an issue, which includes USB interfaces.
As long as they all respect the bus timings.
The logs show that Home Assistant receives the correct data (CounterValueMessage with power and energy), the only problem that needs to be fixed is setting consumption and injection as sensors when initialising in Home Assistant instead of binary_sensors.
I’m not sure how to do this, otherwise I’d be happy to help!
I now see there is no data for “channel”: 2 aka my injection channel. There is, though, for “channel”: 17 which is not in use 
Hi
I have home assistant running with velbus (on a raspberry pi 4) which is connected through ethernet to the signum module.
I installed a new PIRO module, and this module is detected, but not recognised:
025-10-19 22:03:17.803 INFO (MainThread) [velbus-handler] Found module at address 55 (0x37): VMBPIRO-20
2025-10-19 22:03:17.808 WARNING (MainThread) [velbus-module] No module spec for 59
2025-10-19 22:03:17.809 DEBUG (MainThread) [velbus-handler] Module 55 (0x37) detected: start loading
Strangly enough, the log says adress 55 and afterwards no spec for 59?
I already tried changing the adress, but this changed the adresses also in the log of home assistant, but didnt get the module in home assistant.
I have another (older) PIRO which does work:
2025-10-19 22:03:17.589 INFO (MainThread) [velbus-handler] Found module at address 44 (0x2c): VMBPIRO
2025-10-19 22:03:17.599 DEBUG (MainThread) [velbus-handler] Module 44 (0x2c) detected: start loading
Any idea on what to do? Is the new VMB-PIRO2 not supported yet?
Thanks!!
55 = address
59 = module type
this error clearly says that this module is not (yet) implemented
Hi,
I upgraded my Velbus Signum so now it uses Home Assistant instead of OpenHAB. However, since I’ve done that, the integration in my original Home Assistant stopped working. All entities were marked as disabled and reloading did nothing. So I removed the integration and added it again, but still not all devices are showing up.
Weirdly, some devices pop up sometimes and disappear again later. I have all VMB8PBU (switches) devices popping up quite consistently, and one time the VMBGP1 (touchpads & heating) devices showed up as well, but I’m always missing the VMB4RYLD devices, which contain the lights so are quite important.
Lastly, the logs show this:
2025-10-28 16:11:00.622 ERROR (MainThread) [homeassistant.components.binary_sensor] Setup of platform velbus is taking longer than 60 seconds. Startup will proceed without waiting any longer.
2025-10-28 16:11:00.623 ERROR (MainThread) [homeassistant.components.button] Setup of platform velbus is taking longer than 60 seconds. Startup will proceed without waiting any longer.
2025-10-28 16:11:00.623 ERROR (MainThread) [homeassistant.components.climate] Setup of platform velbus is taking longer than 60 seconds. Startup will proceed without waiting any longer.
2025-10-28 16:11:00.623 ERROR (MainThread) [homeassistant.components.cover] Setup of platform velbus is taking longer than 60 seconds. Startup will proceed without waiting any longer.
2025-10-28 16:11:00.623 ERROR (MainThread) [homeassistant.components.light] Setup of platform velbus is taking longer than 60 seconds. Startup will proceed without waiting any longer.
2025-10-28 16:11:00.623 ERROR (MainThread) [homeassistant.components.select] Setup of platform velbus is taking longer than 60 seconds. Startup will proceed without waiting any longer.
2025-10-28 16:11:00.624 ERROR (MainThread) [homeassistant.components.sensor] Setup of platform velbus is taking longer than 60 seconds. Startup will proceed without waiting any longer.
2025-10-28 16:11:00.624 ERROR (MainThread) [homeassistant.components.switch] Setup of platform velbus is taking longer than 60 seconds. Startup will proceed without waiting any longer.
And then a lot of these
2025-10-28 16:11:31.179 INFO (MainThread) [velbus-handler] Scan module 25 failed: not present or unavailable
2025-10-28 16:11:31.179 INFO (MainThread) [velbus-handler] Starting handling scan 26
2025-10-28 16:11:31.180 INFO (MainThread) [velbus-handler] Starting scan 26
2025-10-28 16:11:34.183 INFO (MainThread) [velbus-handler] Scan module 26 failed: not present or unavailable
2025-10-28 16:11:34.183 INFO (MainThread) [velbus-handler] Starting handling scan 27
2025-10-28 16:11:34.184 INFO (MainThread) [velbus-handler] Starting scan 27
2025-10-28 16:11:37.185 INFO (MainThread) [velbus-handler] Scan module 27 failed: not present or unavailable
And finally these
2025-10-28 16:22:58.917 ERROR (MainThread) [homeassistant.components.binary_sensor] Platform velbus does not generate unique IDs. ID 39884-1 already exists - ignoring binary_sensor.garage_licht
2025-10-28 16:22:58.919 ERROR (MainThread) [homeassistant.components.binary_sensor] Platform velbus does not generate unique IDs. ID 39884-2 already exists - ignoring binary_sensor.garage_poort
2025-10-28 16:22:58.920 ERROR (MainThread) [homeassistant.components.binary_sensor] Platform velbus does not generate unique IDs. ID 39515-1 already exists - ignoring binary_sensor.garage_licht_2
2025-10-28 16:22:58.921 ERROR (MainThread) [homeassistant.components.binary_sensor] Platform velbus does not generate unique IDs. ID 39515-2 already exists - ignoring binary_sensor.garage_poort_2
2025-10-28 16:22:58.947 ERROR (MainThread) [homeassistant.components.binary_sensor] Platform velbus does not generate unique IDs. ID 30036-1 already exists - ignoring binary_sensor.toilet
2025-10-28 16:22:58.948 ERROR (MainThread) [homeassistant.components.binary_sensor] Platform velbus does not generate unique IDs. ID 5194-1 already exists - ignoring binary_sensor.berging
2025-10-28 16:22:58.951 ERROR (MainThread) [homeassistant.components.button] Platform velbus does not generate unique IDs. ID 39884-2 already exists - ignoring button.garage_poort
2025-10-28 16:22:58.959 ERROR (MainThread) [homeassistant.components.button] Platform velbus does not generate unique IDs. ID 39515-2 already exists - ignoring button.garage_poort_2
2025-10-28 16:22:58.972 ERROR (MainThread) [homeassistant.components.light] Platform velbus does not generate unique IDs. ID 39884-2 already exists - ignoring light.led_garage_poort
2025-10-28 16:22:58.974 ERROR (MainThread) [homeassistant.components.light] Platform velbus does not generate unique IDs. ID 39515-2 already exists - ignoring light.led_garage_poort_2
2025-10-28 16:22:58.979 ERROR (MainThread) [homeassistant.components.select] Platform velbus does not generate unique IDs. ID 39884-96-program_select already exists - ignoring select.selected_program
2025-10-28 16:22:58.980 ERROR (MainThread) [homeassistant.components.select] Platform velbus does not generate unique IDs. ID 39515-96-program_select already exists - ignoring select.selected_program_2
2025-10-28 16:22:58.980 ERROR (MainThread) [homeassistant.components.select] Platform velbus does not generate unique IDs. ID 30036-96-program_select already exists - ignoring select.selected_program_3
2025-10-28 16:22:58.980 ERROR (MainThread) [homeassistant.components.select] Platform velbus does not generate unique IDs. ID 5194-96-program_select already exists - ignoring select.selected_program_4
Does anyone have any idea how to fix this? Thanks in advance!
Probably a misconfigured parameter for connection throught the Signum. See Velbus - Home Assistant
Quick thought
As you are using the Signum as a TCP gateway for your full HomeAssistant instance…
Is it something as simple as your Bridge settings in HomeAssistant need updating to match the new TCP server settings in your New style Signum?
TLS etc
Have you set a Token in Signum that needs adding?
I think it’s always been port 27015 and has the IP address of your Signum changed?
Hi @Cereal2nd, the Velbus integration is failing when using the latest HA 2025.12.0 (Velbus 2025.11.0). In HA 2025.11.0 no problem with Velbus.
Any ideas ?
2025-12-05 14:38:13.253 ERROR (MainThread) [homeassistant.components.binary_sensor] Error while setting up velbus platform for binary_sensor: 10
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 451, in _async_setup_platform
await asyncio.shield(awaitable)
File "/usr/src/homeassistant/homeassistant/components/velbus/switch.py", line 23, in async_setup_entry
await entry.runtime_data.scan_task
KeyError: 10
2025-12-05 14:38:13.254 ERROR (MainThread) [homeassistant.components.button] Error while setting up velbus platform for button: 10
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 451, in _async_setup_platform
await asyncio.shield(awaitable)
File "/usr/src/homeassistant/homeassistant/components/velbus/switch.py", line 23, in async_setup_entry
await entry.runtime_data.scan_task
KeyError: 10
2025-12-05 14:38:13.255 ERROR (MainThread) [homeassistant.components.climate] Error while setting up velbus platform for climate: 10
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 451, in _async_setup_platform
await asyncio.shield(awaitable)
File "/usr/src/homeassistant/homeassistant/components/velbus/switch.py", line 23, in async_setup_entry
await entry.runtime_data.scan_task
KeyError: 10
2025-12-05 14:38:13.255 ERROR (MainThread) [homeassistant.components.cover] Error while setting up velbus platform for cover: 10
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 451, in _async_setup_platform
await asyncio.shield(awaitable)
File "/usr/src/homeassistant/homeassistant/components/velbus/switch.py", line 23, in async_setup_entry
await entry.runtime_data.scan_task
KeyError: 10
2025-12-05 14:38:13.256 ERROR (MainThread) [homeassistant.components.light] Error while setting up velbus platform for light: 10
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 451, in _async_setup_platform
await asyncio.shield(awaitable)
File "/usr/src/homeassistant/homeassistant/components/velbus/switch.py", line 23, in async_setup_entry
await entry.runtime_data.scan_task
KeyError: 10
2025-12-05 14:38:13.257 ERROR (MainThread) [homeassistant.components.select] Error while setting up velbus platform for select: 10
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 451, in _async_setup_platform
await asyncio.shield(awaitable)
File "/usr/src/homeassistant/homeassistant/components/velbus/switch.py", line 23, in async_setup_entry
await entry.runtime_data.scan_task
KeyError: 10
2025-12-05 14:38:13.257 ERROR (MainThread) [homeassistant.components.sensor] Error while setting up velbus platform for sensor: 10
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 451, in _async_setup_platform
await asyncio.shield(awaitable)
File "/usr/src/homeassistant/homeassistant/components/velbus/switch.py", line 23, in async_setup_entry
await entry.runtime_data.scan_task
KeyError: 10
2025-12-05 14:38:13.258 ERROR (MainThread) [homeassistant.components.switch] Error while setting up velbus platform for switch: 10
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 451, in _async_setup_platform
await asyncio.shield(awaitable)
File "/usr/src/homeassistant/homeassistant/components/velbus/switch.py", line 23, in async_setup_entry
await entry.runtime_data.scan_task
KeyError: 10
Clearing the Velbus cache fixed the problem. Long time ago I needed to do that.