are all modules configured to send sensor updates?
via velbuslink you can configure this.
we do not poll, we wait until a module sends an update
are all modules configured to send sensor updates?
via velbuslink you can configure this.
we do not poll, we wait until a module sends an update
Aha, good to know, I’ll check that this evening Thanks!
That did it, thanks!!
Hi,
i have a velbus system with a connection to a signum module.
Now i want to connect it to Home assistant…
I installed the velbus integration, but i’m stuck at the connection string…
What should i use to connect home assistant with the signum module?
i have read through this thread, but did not find a answer to this…
the connection string is build like this:
tls://password@host:27015
Hi fella
Someone put a comment on one of my videos, asking about the MemoText feature.
Apparently, a MemoText message appears, but as soon as he presses a button, it vanishes
Is this how you intended it to work?
(As in, does HA automatically send the NULL message?)
See comments in this video - https://youtu.be/hSgGj2zHdUE?si=BfVLH_UhiWfkXAfV
Their HA Community post on this subject
What must be wrong with my yaml ? cos the memotext is not in my oled (GPOD )
alias: memo via usb
description: ""
trigger: []
condition: []
action:
- service: velbus.set_memo_text
data:
interface: dev/ttyACM0
memo_text: testUSB
address: 20
mode: single
shoulde be /dev/ttyACM0
I have created an integration with my velbus installation in HA (the new Home Assistant Green).
The gaz and water counter of the VMB7IN do not work in the energy dashboard of HA. They are not recognized as gaz and water counter and HA says it’s a problem xith the integration.
Is it a bug in the integration? Or a configuration to change in velbuslink?
Thanks
Hello,
I saw on the velbus-aio github that a function had been added to toggle the edge LEDs on the edgelit switches. I searched for the service but it is not there. I saw that on April 1 of this year @wlcrs was talking about writing this service call. Is this functionality already available?
Thanks!
Robbe
Hi
These behave the same way as a normal #Velbus feedback light / LED.
Set / ON
Clear / OFF
Slow_blink
Fast_blink
Very_fast_blink
It’s only the colour setting that is more complex.
@Cereal2nd
Am I correct in saying that HA supports affecting Velbus feedback states?
Is this example in the docs still valid?
@Cereal2nd
What’s the correct way of reporting this bug?
Is there an appropriate TAG on GitHub for these?
@fontainechristophe
Please note the response from Maikel below.
Thanks @Cereal2nd
Hello,
Thanks for this. Yesterday I added the hidden feedback led entities and I guess I was not patient enough, I could not switch the status, they were always displayed as “on” (even if they were off). When I tried the same thing this morning, I was able to change the status. I’m not at home for the moment so I can’t tell if the LEDs are really on or off, but it seems to work. So I just had to wait a little longer before trying to change the feedback status of the LEDs.
For the colour setting: it would be nice if that would work too!
You’re very welcome.
I’m not very good with HomeAssistant, but happy to share what little I know.
A little odd that it needed some time to adjust, but again, happy that it’s working for you.
But don’t forget…
If something else in your system requires the LED to be “ON”, any lower command will be ignored.
Think of the logic as an OR gate.
That’s a lot deeper in the software and may be outside of the roadmap for integration.
It should be noted that ad-hoc colour setting happens by writing directly to the memory map and isn’t advised as a long term solution.
However…
Don’t forget that you can assign colour change events to button presses and other events.
If it’s possible to mimic button events from HA, you could activate unused button groups of an OLED panel (without enabling their respective page on the display) and assign each actions to set the colours you want.
Alternatively…
I have got a flow for NodeRed that will set colours on the fly…
bugreports should go here:
Hi,
I tested it now I am at home but the feeback led is not lighting up. When I toggle the physical button to turn on the light, the led feedback state in home assistant follows (even if there is no feedback led programmed in velbus). So if I turn the light on, in home assistant the feedback led switches to on (but the led itself is not on), and it switches off when I turn of the light. But when I toggle the feedback led entity in home assistant nothing happens. Is it nessacary that the feedback led functionality is enabled on the specific module in velbuslink?
i never played with the feedback leds.
i just toggle the state of the relay/button i do nothing more.
so in your setup you created a feedback led on a module X, and you want to show the state of channel Z on module Y?
Via hass you toggle Y/Z via the gui and you expect the feedback-led to lght up?
is this your scenario?
The Edgelit lights are quite complex to fit inside the model of Home Assistant. I’ve tried a few approaches, but none were satisfactory. A custom service call would be the easiest solution, but I’m quite wary about it getting through the code review stage of HA.
Some of the problems I remember:
Maybe I’ll be able to take this feature back up in the coming winter months, but I’ll need some input from @Cereal2nd on what the best approach will be.
I don’t know enough about how the cogs work within HA, but I do know a thing or two about Velbus
Correct, these should never be seen as something that can report a state or be polled.
Especially the Ambient colour options.
Feedback state is probably the same, certainly when you consider that a Velbus panel is monitoring the state changes on (potentially) many modules, to derive the correct Feedback state.
If intending to solely use HA for Feedback state, it is probably best NOT to have that button affected directly by any Velbus activity.
(Which is fine if using that button action for Media Player control, outside of Velbus for example)
To a point they are.
In so much as there are a number of palette presets that are configured with VelbusLink for each Edge Lit panel.
A Velbus action simply calls that Palette number with the required function.
I’m not sure that would ever be possible on any platform.
The Control4 solution is to offer a list of palette presets for the C4 programmer to choose from.
That is a very good point.
There is also the very serious issue of “writing to the memory block too many times” and potentially damaging it.
Because, to set the Ambient or feedback colour value, the state must be written to the memory map, followed by a “reset” command.
I have this working in a Node-RED flow, for use on my demo unit on the understanding that I am risking bricking (or at least damaging) my demo modules.
I would refer everyone back to my previous comment, regarding creating the required colour effects / actions within Velbuslink against “spare” button or relay channels, then trigger the change from HA…
(I know that mimicking button events is now possible in openHAB and Control4, as it always has been with OpenRemote)
This way you can change as many or as few sides as you wish, with or without flashing effect, with one event from HA.
I hope this helps.
As always, feel free to remotely connect to a unit here if you want to do some testing.
I would much rather you “brick” one of my demo units, than a module in your own home/s.
Hello all, I was just wondering if there was some kind of implementation in HA for the dual mode functioning of push and touch buttons (e.g. for double press).
For instance, if I set a button in Velbuslink to dual mode, will it create corresponding virtual buttons in HA? or something similar?
Thank you !