I see issues every second in my log file. The warnings are related to velbus, the errors I dont know:
2025-08-12 09:38:02.761 WARNING (MainThread) [velbus-handler] NOT FOUND IN command_registry: RawMessage(priority=fb, address=0d, rtr=False, command=169, data=b’a9 00 30’)
2025-08-12 09:38:02.813 WARNING (MainThread) [velbus-handler] NOT FOUND IN command_registry: RawMessage(priority=fb, address=15, rtr=False, command=169, data=b’a9 00 10’)
2025-08-12 09:38:02.863 WARNING (MainThread) [velbus-handler] NOT FOUND IN command_registry: RawMessage(priority=fb, address=12, rtr=False, command=169, data=b’a9 00 1d’)
2025-08-12 09:38:02.915 WARNING (MainThread) [velbus-handler] NOT FOUND IN command_registry: RawMessage(priority=fb, address=09, rtr=False, command=169, data=b’a9 03 d5’)
is this the Signum or a manual install of HA? if the latter - you should file a bug report in the velbus module on github - or reply on the HA velbus topic on the home assistant community…
if its the signum - then open a ticket with velbus
You sure its Signum then? The Signum is a highly controlled version of home assistant that comes as a single module… you cannot install it into your own server…
Ah ok, as far as I understood, signum has its own controlled HA implementation but also allows to connect the velbus installation to homeassitant… At least I need to provide the signum ip address when configuring the velbus-HA integration…?
Or am I wrong?
If you can connect to your Signum from Velbuslink, but using the TCP-IP option, then those are exactly the details you’d need to use in your full HA instance.
Probably something along the lines of
tls://192.168.x.x:25017
But if you’ve setup a TLS token, you’ll need to enter that too.
To me it seems like there’s a module (VMBPIR-20) that’s not fully supported and hence throwing those warnings. It’s the community Velbus integration that logs these messages.
