No, what I was trying to achieve was to have a “night light” for my kid, so having the feedback leds glow softly in the night.
What I needed to do was to enable the feedback leds in VelbusLink, after that it worked as expected.
Thanks everyone for your input! I will need to dive a little bit more into VelbusLink to learn how everything is linked toghether.
simple answer: No
longer answer: No but it can be build, we already support longpress on the bus so should be possible.
Initially you mentioned
Which option do you need?
Dual mode is simply triggering a second (Non-physical) Velbus button channel, whereas Long_Press of the same Velbus protocol button (physical button) is something else.
any option is fine as long as it does not trigger a short press before the long one.
with the Trigrr software that I have at home, their method of triggering a long press first triggers a short press, so that’s not good…
In Velbuslink you can trigger a longpress with dual mode, which is nice as it doesn’t trigger a short press.
So my question is, is there a way to also do that on HA?
Thx !
I understand where you are now.
There is a little confusion.
Dual mode IS NOT creating a “Long_Press” event for the button.
Let me explain.
Take a single button Glass panel for example (This is the same for ALL Velbus hardware)
By default, it only has 1 button active.
To create a “Dual Mode”, we have to activate a second “Virtual” button
Which is then used in the Button Mode tab
No doubt, you have seen the “Long Press Time”, which is what might be causing the confusion here.
What happens with Dual Mode is this.
If you press the (only) physical button on the panel and release it, a “Press” (followed by a “release”) event for Button 1 is put on the bus.
However, if you press and hold that physical button, what actually happens is a “Press” (followed by a “release”) event for Button 2 is put on the bus.
(Long_press events just don’t happen when a button is in “Dual Mode”)
So if you are asking “how do I mimic the Dual Mode”, what you are actually looking for is a Button event for “Button 2”
However, are you asking for a way to create a “HA UI Long Press converted into a different event” within HA, which I think would be a very different question.
Sorry for going around in circles a bit, we just need to be clear on what behaviour you have from your Velbus hardware and what you want to do in HA.
Just for absolute clarity, that is exactly how the Velbus protocol works.
It’s the output device within Velbus that has to know to ignore the Press event and wait for a Long_Press.
That said, it’s fine if you ONLY put a Long_Press event onto the bus, as long as it is followed by a Release, at some stage.
Interesting I see, thanks for the write up !
Hi @MDAR , @Cereal2nd ,
First of all: appreciate all the effort you put in this Velbus support!
Since a few versions ago , I’ve had some issues when restarting HA.
The log is spammed with the following error:
Logger: root
Source: deps/lib/python3.11/site-packages/velbusaio/raw_message.py:68
First occurred: 4:08:01 PM (377 occurrences)
Last logged: 4:08:55 PM
Could not parse the message b'0ffb050802008bca7f0000010000'. Truncating invalid data.
Could not parse the message b'0ffb0508ec02110002008bca7f00'. Truncating invalid data.
Could not parse the message b'0ffb0508ec021100806400000000'. Truncating invalid data.
Could not parse the message b'0ffb0508ec021100806400000200'. Truncating invalid data.
Could not parse the message b'0ffb02008bca0ffb0508ec021100'. Truncating invalid data.
Not sure what to do with this.
When I restart HA a few times, when I’m lucky it stops and it functions normally.
When I then restart or update HA again after a while, this returns.
Not sure why it’s happening and why it’s fixed randomly after a few restarts (seems like I just need to be lucky when restarting, sometimes it happens, sometimes it’s fine).
Any ideas?
(I’ve just updated to 2023.10.5)
Hi
This really is a question that only @Cereal2nd can help with.
Anyone that’s seen my code writing skills will know that I’m not the man to ask.
this looks like a bug in the parser.
Is there a posibility that i login onto your bus via a tcp/ip connection to debug this?
Hey all ! I am just wondering what your start-up times are, my Velbus integration takes the most time by really far (78 devices, 1132 entities)
I am using the VMBUSBIP, would using another gateway speed up anything? thx !
(running HAOS on lenovo M710q)
no, this is the nature of velbus.
The scan and full read-out takes a long time, so there is no way to speed this up. The initial (first) startup time can be really long, the later startups should be faster (for me its almost 180 seconds for 30 devices)
Hey,
i am trying to implement velbus into home assistant.
I can install automation, link it etc…but whatever i do i don’t see any entities …
If i go in the log file…i see a lot of communication to velbus.
I found some info here…
I tried to clear cache of velbus, reloaded integration…
This is what i see in the log…
2023-12-07 11:39:47.543 DEBUG (MainThread) [velbus] Reconnecting to transport
2023-12-07 11:39:47.575 INFO (MainThread) [velbus-protocol] Connection established to Velbus
2023-12-07 11:39:47.603 WARNING (MainThread) [velbus-protocol] EOF received from Velbus
2023-12-07 11:39:47.604 DEBUG (MainThread) [velbus] Reconnecting to transport
2023-12-07 11:39:47.628 WARNING (MainThread) [homeassistant.components.binary_sensor] Setup of binary_sensor platform velbus is taking over 10 seconds.
2023-12-07 11:39:47.628 WARNING (MainThread) [homeassistant.components.button] Setup of button platform velbus is taking over 10 seconds.
2023-12-07 11:39:47.629 WARNING (MainThread) [homeassistant.components.climate] Setup of climate platform velbus is taking over 10 seconds.
2023-12-07 11:39:47.629 WARNING (MainThread) [homeassistant.components.cover] Setup of cover platform velbus is taking over 10 seconds.
2023-12-07 11:39:47.629 WARNING (MainThread) [homeassistant.components.light] Setup of light platform velbus is taking over 10 seconds.
2023-12-07 11:39:47.629 WARNING (MainThread) [homeassistant.components.select] Setup of select platform velbus is taking over 10 seconds.
2023-12-07 11:39:47.631 WARNING (MainThread) [homeassistant.components.sensor] Setup of sensor platform velbus is taking over 10 seconds.
2023-12-07 11:39:47.632 WARNING (MainThread) [homeassistant.components.switch] Setup of switch platform velbus is taking over 10 seconds.
2023-12-07 11:39:47.639 INFO (MainThread) [velbus-protocol] Connection established to Velbus
2023-12-07 11:39:47.664 WARNING (MainThread) [velbus-protocol] EOF received from Velbus
2023-12-07 11:39:47.664 DEBUG (MainThread) [velbus] Reconnecting to transport
2023-12-07 11:39:47.696 INFO (MainThread) [velbus-protocol] Connection established to Velbus
2023-12-07 11:39:47.725 WARNING (MainThread) [velbus-protocol] EOF received from Velbus
2023-12-07 11:39:47.725 DEBUG (MainThread) [velbus] Reconnecting to transport
2023-12-07 11:39:47.759 INFO (MainThread) [velbus-protocol] Connection established to Velbus
2023-12-07 11:39:47.787 WARNING (MainThread) [velbus-protocol] EOF received from Velbus
2023-12-07 11:39:47.788 DEBUG (MainThread) [velbus] Reconnecting to transport
2023-12-07 11:39:47.823 INFO (MainThread) [velbus-protocol] Connection established to Velbus
2023-12-07 11:39:47.849 WARNING (MainThread) [velbus-protocol] EOF received from Velbus
2023-12-07 11:39:47.849 DEBUG (MainThread) [velbus] Reconnecting to transport
2023-12-07 11:39:47.878 INFO (MainThread) [velbus-protocol] Connection established to Velbus
2023-12-07 11:39:47.911 WARNING (MainThread) [velbus-protocol] EOF received from Velbus
then i go this
2023-12-07 11:39:53.353 ERROR (MainThread) [velbus] Not all modules are loaded within a timeout of 600 seconds, continuing with the loaded modules
2023-12-07 11:39:53.353 ERROR (MainThread) [velbus] Not all modules are loaded within a timeout of 600 seconds, continuing with the loaded modules
2023-12-07 11:39:53.354 ERROR (MainThread) [velbus] Not all modules are loaded within a timeout of 600 seconds, continuing with the loaded modules
2023-12-07 11:39:53.354 ERROR (MainThread) [velbus] Not all modules are loaded within a timeout of 600 seconds, continuing with the loaded modules
2023-12-07 11:39:53.354 ERROR (MainThread) [velbus] Not all modules are loaded within a timeout of 600 seconds, continuing with the loaded modules
2023-12-07 11:39:53.354 ERROR (MainThread) [velbus] Not all modules are loaded within a timeout of 600 seconds, continuing with the loaded modules
2023-12-07 11:39:53.355 ERROR (MainThread) [velbus] Not all modules are loaded within a timeout of 600 seconds, continuing with the loaded modules
2023-12-07 11:39:53.355 ERROR (MainThread) [velbus] Not all modules are loaded within a timeout of 600 seconds, continuing with the loaded modules
2023-12-07 11:39:53.355 ERROR (MainThread) [velbus] Not all modules are loaded within a timeout of 600 seconds, continuing with the loaded modules
2023-12-07 11:39:53.355 ERROR (MainThread) [velbus] Not all modules are loaded within a timeout of 600 seconds, continuing with the loaded modules
2023-12-07 11:39:53.355 ERROR (MainThread) [velbus] Not all modules are loaded within a timeout of 600 seconds, continuing with the loaded modules
2023-12-07 11:39:53.356 ERROR (MainThread) [velbus] Not all modules are loaded within a timeout of 600 seconds, continuing with the loaded modules
2023-12-07 11:39:53.356 ERROR (MainThread) [velbus] Not all modules are loaded within a timeout of 600 seconds, continuing with the loaded modules
2023-12-07 11:39:53.356 ERROR (MainThread) [velbus] Not all modules are loaded within a timeout of 600 seconds, continuing with the loaded modules
2023-12-07 11:39:53.357 ERROR (MainThread) [velbus] Not all modules are loaded within a timeout of 600 seconds, continuing with the loaded modules
2023-12-07 11:39:53.357 ERROR (MainThread) [velbus] Not all modules are loaded within a timeout of 600 seconds, continuing with the loaded modules
2023-12-07 11:39:53.357 ERROR (MainThread) [velbus] Not all modules are loaded within a timeout of 600 seconds, continuing with the loaded modules
2023-12-07 11:39:53.357 ERROR (MainThread) [velbus] Not all modules are loaded within a timeout of 600 seconds, continuing with the loaded modules
2023-12-07 11:39:53.357 ERROR (MainThread) [velbus] Not all modules are loaded within a timeout of 600 seconds, continuing with the loaded modules
and after some time i get this
2023-12-07 11:39:53.419 ERROR (MainThread) [velbus] Not all modules are loaded within a timeout of 600 seconds, continuing with the loaded modules
2023-12-07 11:39:53.419 ERROR (MainThread) [velbus] Not all modules are loaded within a timeout of 600 seconds, continuing with the loaded modules
2023-12-07 11:39:53.419 ERROR (MainThread) [velbus] Not all modules are loaded within a timeout of 600 seconds, continuing with the loaded modules
2023-12-07 11:39:53.419 WARNING (MainThread) [velbus-protocol] EOF received from Velbus
2023-12-07 11:39:53.419 DEBUG (MainThread) [velbus] Reconnecting to transport
2023-12-07 11:39:53.452 INFO (MainThread) [velbus-protocol] Connection established to Velbus
nothing regarding velbus after this…but no entities 
Is there something else i can try?
i’m on a rasbery pi, with these versions
enable the debug log for this integration, it will give you a lot more info.
How are you connecting to the bus? what connection string?
I’m using “tls://192.168.0.194:27015”
i already did this…and it seems there is a lot of traffic for it…but it shows the same errors…
2023-12-03 13:25:59.807 DEBUG (MainThread) [velbus-protocol] TX: RawMessage(priority=fb, address=9d, rtr=True, command=None, data=b’‘)
2023-12-03 13:25:59.809 WARNING (MainThread) [velbus-protocol] EOF received from Velbus
2023-12-03 13:25:59.842 INFO (MainThread) [velbus-protocol] Connection established to Velbus
2023-12-03 13:25:59.869 DEBUG (MainThread) [velbus-protocol] TX: RawMessage(priority=fb, address=9e, rtr=True, command=None, data=b’‘)
2023-12-03 13:25:59.873 WARNING (MainThread) [velbus-protocol] EOF received from Velbus
2023-12-03 13:25:59.905 INFO (MainThread) [velbus-protocol] Connection established to Velbus
2023-12-03 13:25:59.932 DEBUG (MainThread) [velbus-protocol] TX: RawMessage(priority=fb, address=9f, rtr=True, command=None, data=b’‘)
2023-12-03 13:25:59.935 WARNING (MainThread) [velbus-protocol] EOF received from Velbus
2023-12-03 13:25:59.967 INFO (MainThread) [velbus-protocol] Connection established to Velbus
2023-12-03 13:25:59.995 DEBUG (MainThread) [velbus-protocol] TX: RawMessage(priority=fb, address=a0, rtr=True, command=None, data=b’‘)
2023-12-03 13:26:00.000 WARNING (MainThread) [velbus-protocol] EOF received from Velbus
2023-12-03 13:26:00.033 INFO (MainThread) [velbus-protocol] Connection established to Velbus
2023-12-03 13:26:00.039 WARNING (MainThread) [homeassistant.components.binary_sensor] Setup of binary_sensor platform velbus is taking over 10 seconds.
2023-12-03 13:26:00.040 WARNING (MainThread) [homeassistant.components.button] Setup of button platform velbus is taking over 10 seconds.
2023-12-03 13:26:00.040 WARNING (MainThread) [homeassistant.components.climate] Setup of climate platform velbus is taking over 10 seconds.
2023-12-03 13:26:00.041 WARNING (MainThread) [homeassistant.components.cover] Setup of cover platform velbus is taking over 10 seconds.
2023-12-03 13:26:00.041 WARNING (MainThread) [homeassistant.components.light] Setup of light platform velbus is taking over 10 seconds.
2023-12-03 13:26:00.041 WARNING (MainThread) [homeassistant.components.select] Setup of select platform velbus is taking over 10 seconds.
2023-12-03 13:26:00.041 WARNING (MainThread) [homeassistant.components.sensor] Setup of sensor platform velbus is taking over 10 seconds.
2023-12-03 13:26:00.041 WARNING (MainThread) [homeassistant.components.switch] Setup of switch platform velbus is taking over 10 seconds.
2023-12-03 13:26:00.058 DEBUG (MainThread) [velbus-protocol] TX: RawMessage(priority=fb, address=a1, rtr=True, command=None, data=b’‘)
2023-12-03 13:26:00.061 WARNING (MainThread) [velbus-protocol] EOF received from Velbus
2023-12-03 13:26:00.091 INFO (MainThread) [velbus-protocol] Connection established to Velbus
2023-12-03 13:26:00.121 DEBUG (MainThread) [velbus-protocol] TX: RawMessage(priority=fb, address=a2, rtr=True, command=None, data=b’‘)
2023-12-03 13:26:00.125 WARNING (MainThread) [velbus-protocol] EOF received from Velbus
2023-12-03 13:26:00.159 INFO (MainThread) [velbus-protocol] Connection established to Velbus
2023-12-03 13:26:00.184 DEBUG (MainThread) [velbus-protocol] TX: RawMessage(priority=fb, address=a3, rtr=True, command=None, data=b’‘)
2023-12-03 13:26:00.187 WARNING (MainThread) [velbus-protocol] EOF received from Velbus
2023-12-03 13:26:00.219 INFO (MainThread) [velbus-protocol] Connection established to Velbus
2023-12-03 13:26:00.247 DEBUG (MainThread) [velbus-protocol] TX: RawMessage(priority=fb, address=a4, rtr=True, command=None, data=b’‘)
2023-12-03 13:26:00.249 WARNING (MainThread) [velbus-protocol] EOF received from Velbus
2023-12-03 13:26:00.283 INFO (MainThread) [velbus-protocol] Connection established to Velbus
2023-12-03 13:26:00.309 DEBUG (MainThread) [velbus-protocol] TX: RawMessage(priority=fb, address=a5, rtr=True, command=None, data=b’‘)
2023-12-03 13:26:00.311 WARNING (MainThread) [velbus-protocol] EOF received from Velbus
2023-12-03 13:26:00.341 INFO (MainThread) [velbus-protocol] Connection established to Velbus
2023-12-03 13:26:00.371 DEBUG (MainThread) [velbus-protocol] TX: RawMessage(priority=fb, address=a6, rtr=True, command=None, data=b’‘)
2023-12-03 13:26:00.375 WARNING (MainThread) [velbus-protocol] EOF received from Velbus
2023-12-03 13:26:00.406 INFO (MainThread) [velbus-protocol] Connection established to Velbus
2023-12-03 13:26:00.432 DEBUG (MainThread) [velbus-protocol] TX: RawMessage(priority=fb, address=a7, rtr=True, command=None, data=b’‘)
2023-12-03 13:26:00.436 WARNING (MainThread) [velbus-protocol] EOF received from Velbus
2023-12-03 13:26:00.469 INFO (MainThread) [velbus-protocol] Connection established to Velbus
2023-12-03 13:26:00.496 DEBUG (MainThread) [velbus-protocol] TX: RawMessage(priority=fb, address=a8, rtr=True, command=None, data=b’‘)
2023-12-03 13:26:00.500 WARNING (MainThread) [velbus-protocol] EOF received from Velbus
2023-12-03 13:26:00.532 INFO (MainThread) [velbus-protocol] Connection established to Velbus
2023-12-03 13:26:00.558 DEBUG (MainThread) [velbus-protocol] TX: RawMessage(priority=fb, address=a9, rtr=True, command=None, data=b’‘)
2023-12-03 13:26:00.561 WARNING (MainThread) [velbus-protocol] EOF received from Velbus
2023-12-03 13:26:00.594 INFO (MainThread) [velbus-protocol] Connection established to Velbus
2023-12-03 13:26:00.620 DEBUG (MainThread) [velbus-protocol] TX: RawMessage(priority=fb, address=aa, rtr=True, command=None, data=b’')
2023-12-03 13:26:00.623 WARNING (MainThread) [velbus-protocol] EOF received from Velbus
I then get this and after that constantly rx info…
2023-12-03 13:26:06.018 ERROR (MainThread) [velbus] Not all modules are loaded within a timeout of 600 seconds, continuing with the loaded modules
2023-12-03 13:26:06.018 ERROR (MainThread) [velbus] Not all modules are loaded within a timeout of 600 seconds, continuing with the loaded modules
2023-12-03 13:26:06.019 ERROR (MainThread) [velbus] Not all modules are loaded within a timeout of 600 seconds, continuing with the loaded modules
2023-12-03 13:26:06.019 ERROR (MainThread) [velbus] Not all modules are loaded within a timeout of 600 seconds, continuing with the loaded modules
2023-12-03 13:26:06.019 ERROR (MainThread) [velbus] Not all modules are loaded within a timeout of 600 seconds, continuing with the loaded modules
2023-12-03 13:26:06.019 ERROR (MainThread) [velbus] Not all modules are loaded within a timeout of 600 seconds, continuing with the loaded modules
2023-12-03 13:26:06.020 ERROR (MainThread) [velbus] Not all modules are loaded within a timeout of 600 seconds, continuing with the loaded modules
2023-12-03 13:26:06.020 ERROR (MainThread) [velbus] Not all modules are loaded within a timeout of 600 seconds, continuing with the loaded modules
2023-12-03 13:26:06.020 ERROR (MainThread) [velbus] Not all modules are loaded within a timeout of 600 seconds, continuing with the loaded modules
2023-12-03 13:26:06.020 ERROR (MainThread) [velbus] Not all modules are loaded within a timeout of 600 seconds, continuing with the loaded modules
2023-12-03 13:26:06.021 ERROR (MainThread) [velbus] Not all modules are loaded within a timeout of 600 seconds, continuing with the loaded modules
2023-12-03 13:26:06.021 ERROR (MainThread) [velbus] Not all modules are loaded within a timeout of 600 seconds, continuing with the loaded modules
2023-12-03 13:26:06.021 ERROR (MainThread) [velbus] Not all modules are loaded within a timeout of 600 seconds, continuing with the loaded modules
2023-12-03 13:26:06.021 ERROR (MainThread) [velbus] Not all modules are loaded within a timeout of 600 seconds, continuing with the loaded modules
2023-12-03 13:26:06.022 ERROR (MainThread) [velbus] Not all modules are loaded within a timeout of 600 seconds, continuing with the loaded modules
2023-12-03 13:26:06.022 ERROR (MainThread) [velbus] Not all modules are loaded within a timeout of 600 seconds, continuing with the loaded modules
2023-12-03 13:26:06.022 ERROR (MainThread) [velbus] Not all modules are loaded within a timeout of 600 seconds, continuing with the loaded modules
2023-12-03 13:26:06.022 ERROR (MainThread) [velbus] Not all modules are loaded within a timeout of 600 seconds, continuing with the loaded modules
2023-12-03 13:26:06.023 ERROR (MainThread) [velbus] Not all modules are loaded within a timeout of 600 seconds, continuing with the loaded modules
2023-12-03 13:26:06.023 ERROR (MainThread) [velbus] Not all modules are loaded within a timeout of 600 seconds, continuing with the loaded modules
2023-12-03 13:26:06.023 WARNING (MainThread) [velbus-protocol] EOF received from Velbus
2023-12-03 13:26:06.028 DEBUG (MainThread) [velbus-protocol] Ending Velbus write message from send queue
2023-12-03 13:26:06.058 INFO (MainThread) [velbus-protocol] Connection established to Velbus
2023-12-03 13:26:06.059 DEBUG (MainThread) [velbus-protocol] Starting Velbus write message from send queue
2023-12-03 13:26:06.059 DEBUG (MainThread) [velbus-protocol] Acquiring write lock
2023-12-03 13:26:09.336 DEBUG (MainThread) [velbus-protocol] RX: RawMessage(priority=fb, address=50, rtr=False, command=230, data=b’e6 04 11 f6 a0 23 28’)
2023-12-03 13:26:09.345 DEBUG (MainThread) [velbus-protocol] RX: RawMessage(priority=fb, address=50, rtr=False, command=169, data=b’a9 00 00 5a 34 00 89’)
2023-12-03 13:26:09.356 DEBUG (MainThread) [velbus-protocol] RX: RawMessage(priority=fb, address=50, rtr=False, command=172, data=b’ac 02 00 20 20 30 2e 30’)
2023-12-03 13:26:09.367 DEBUG (MainThread) [velbus-protocol] RX: RawMessage(priority=fb, address=50, rtr=False, command=172, data=b’ac 02 05 20 6d 6d 2f 68’)
2023-12-03 13:26:09.375 DEBUG (MainThread) [velbus-protocol] RX: RawMessage(priority=fb, address=50, rtr=False, command=172, data=b’ac 02 0a 00’)
2023-12-03 13:26:09.388 DEBUG (MainThread) [velbus-protocol] RX: RawMessage(priority=fb, address=50, rtr=False, command=172, data=b’ac 04 00 20 32 33 30 39’)
2023-12-03 13:26:09.399 DEBUG (MainThread) [velbus-protocol] RX: RawMessage(priority=fb, address=50, rtr=False, command=172, data=b’ac 04 05 32 20 6c 75 78’)
2023-12-03 13:26:09.407 DEBUG (MainThread) [velbus-protocol] RX: RawMessage(priority=fb, address=50, rtr=False, command=172, data=b’ac 04 0a 00’)
2023-12-03 13:26:09.419 DEBUG (MainThread) [velbus-protocol] RX: RawMessage(priority=fb, address=50, rtr=False, command=172, data=b’ac 08 00 20 31 33 2e 37’)
2023-12-03 13:26:09.430 DEBUG (MainThread) [velbus-protocol] RX: RawMessage(priority=fb, address=50, rtr=False, command=172, data=b’ac 08 05 20 6b 6d 2f 68’)
2023-12-03 13:26:09.438 DEBUG (MainThread) [velbus-protocol] RX: RawMessage(priority=fb, address=50, rtr=False, command=172, data=b’ac 08 0a 00’)
2023-12-03 13:26:19.298 DEBUG (MainThread) [velbus-protocol] RX: RawMessage(priority=fb, address=50, rtr=False, command=230, data=b’e6 04 19 f6 a0 23 28’)
2023-12-03 13:26:19.306 DEBUG (MainThread) [velbus-protocol] RX: RawMessage(priority=fb, address=50, rtr=False, command=169, data=b’a9 00 00 5a 34 00 af’)
2023-12-03 13:26:19.318 DEBUG (MainThread) [velbus-protocol] RX: RawMessage(priority=fb, address=50, rtr=False, command=172, data=b’ac 02 00 20 20 30 2e 30’)
2023-12-03 13:26:19.329 DEBUG (MainThread) [velbus-protocol] RX: RawMessage(priority=fb, address=50, rtr=False, command=172, data=b’ac 02 05 20 6d 6d 2f 68’)
2023-12-03 13:26:19.337 DEBUG (MainThread) [velbus-protocol] RX: RawMessage(priority=fb, address=50, rtr=False, command=172, data=b’ac 02 0a 00’)
2023-12-03 13:26:19.349 DEBUG (MainThread) [velbus-protocol] RX: RawMessage(priority=fb, address=50, rtr=False, command=172, data=b’ac 04 00 20 32 33 30 39’)
2023-12-03 13:26:19.361 DEBUG (MainThread) [velbus-protocol] RX: RawMessage(priority=fb, address=50, rtr=False, command=172, data=b’ac 04 05 32 20 6c 75 78’)
2023-12-03 13:26:19.368 DEBUG (MainThread) [velbus-protocol] RX: RawMessage(priority=fb, address=50, rtr=False, command=172, data=b’ac 04 0a 00’)
2023-12-03 13:26:19.381 DEBUG (MainThread) [velbus-protocol] RX: RawMessage(priority=fb, address=50, rtr=False, command=172, data=b’ac 08 00 20 31 37 2e 35’)
EOF received from Velbus
Do you have an authentication password set on the signum?
Hm…i don’t know.
This is the system of a friend of mine. He asked to start him up in home assistant and link his signum system…so i’m not really know whats all done by him…
How can i see if he has done that, and if so does it needs to be removed, or do i need to connect in another way?
thats in the GUI of the signum
ok…thnx i will ask him…
If he has done that do i need to use a different connection?
then you need to use:
tls://password@host:27015
Hi everyone,
I was wondering if there was any progress with the following integrations… I’m hoping the Signum now supporting HA would speed up things a bit 
…
“Cooling mode” for Thermostats…
Setting programs on the VMBELO and GP series through HA
Accessing / virtualizing buttons of the BELO/GP series in HA…
As perhaps I can then match a button in HA to the scene defined in Velbus …