@darkpainy Ohhhhhh yes
The list is very long.
I’ve sold hardware to quite a number of countries over the last 10 years.
Although I mainly focus on the UK, where we have a growing number of professional installers.
What do you have in mind?
(@RCZ do you want to tell him where in the world you are 
)
Hello, I have a Velbus installation and I recently integrated it into Home assistant with the Signum module.
Everything works very well except for the status of slatted blinds. In Velbuslink, you must define an operating time. When closing, the slatted blind is displayed close in Home Assistant until the end of the indicated duration. Once this deadline has passed, the store is again displayed as open in Home Assistant. Is it possible to correct the status in any way? Hoping to have been clear enough (I’m starting in this field) Hoping not to have made nonsense by posting here…
Hi
I understand what you’re seeing.
It’s an issue across all UI platforms.
It is because (unlike a dimmer) the VMB2BLE & VMB1BLS don’t share their current status to the bus during the movement.
They wait until the timer has expired to broadcast a status update.
This might change in the future in a firmware update, but I’m not aware of any such plans.
Does that help you?
Hi,
Thank you very much for the super quick response!
It doesn’t help me much but I at least know that it’s not a problem related to my configuration and I thank you for that.
I was asking myself the question because in the Velbus application, the status is correct as well as the possibility of setting a position.
Thank you again and have a good day
You’re very welcome.
Have you seen this closed issue on GitHub?
Velbuslink uses the same status updates that the Blind module transmits, so what you see should be the same across all software.
This should be possible, if the feature isn’t available, can you put a feature request in for it?
I’m happy to work with the HA Velbus developer.
They have accessed my demo units in the past to add features.
Good luck,
Stuart
the main problem is that i do not own any blind modules, so implementing them is not that easy as there is nothing to test them against …
I was talking about the push button simulation in HA 
you asked for the logs, I posted them 
You are always welcome to connect to a test rig here.
after the belfian festival season i have some spare time.
then i can invest some time into ebugging and fixing these.
But not sure wath will happen with velbus and hass in the near future, velbus is developping there own integration for there signum module and it looks like they are not willing to combine the effort.
A subject I have been banging on about for ten years.
For the record, I’m pushing hard to get Velbus supported by as many platforms as possible.
For example, Control4 now has a driver pack for Velbus (which I’ve funded)
As I did for OpenRemote
The Dev(s) for openHAB refused any financial assistance from me regarding the Velbus binding (not wishing to become slaves to the corporate machine)
Rest assured that for as long as MDAR exists, I will actively support your efforts.
I have seen all these articles but my current skills are too limited to allow me to find a solution 
. I will wait until a solution is found I saw while browsing the forums that Cereal2nd makes a lot of contributions, so I’ll believe in it .
If I can help in any way, don’t hesitate.
I have the following modules in my installation: VMB4RYNO, VMB2BLE, VMBDMI-R and the Signum module (VMBSIG)
The middle-east (UAE) is also covered by at least 1 Velbus installation
did anyone manage to get the Velbus Panels into Home Assistant (with interactions). All my buttons are now “binary_sensor.push_button_x” - but ideally I would like to interact with them on Home Assistant…
(for example - I configure a scene in Velbus itself, expose that through VMBELO button 1 - in Home Assistant I make button 1 available as a push button and voila…) - it looks like they are now only sensors… not interactive components
The idea is to expose the front-end of Velbus on HA - and keep the logic in Velbus backend - (for some stuff)
Hi, to use these functions, you must do the 2 automations of the documentation.
It’s a bit tedious but it works😅
can you explain a bit more on this?
i see this in the doc:
# Control light living from Velbus push_button_10
- id: 'Control_light_living_from_Velbus'
alias: "Control light living using Velbus push_button_10"
trigger:
- entity_id: binary_sensor.push_button_10
platform: state
to: "on"
condition: []
action:
- entity_id: light.living
service: light.toggle
but would that expose a clickable button in Home Assistant?
Create the 2 automations (both of the documentation are mandatory) in your automation files and replace the “push button” with the button you want to use and replace the “light” entity with the entity of your choice. Attention, this only works with VMBGPODB modules.
This will not expose a button in HA but will allow you to control an HA entity on a VMBGPODB push button.
ah ok… yeah i wanted to just have the button there…
in OpenHab its a bit easier as the buttons themselves are exposed to the system… and I can just “click” that button from the WebGui and it would execute whatever is configured in Velbus itself… as if I was pushing the button physically
I dream of such simplicity . The Velbus integration is not perfect in HA but people are working on it and I hope that one day everything will work perfectly (the display of the status of the shutters as well as the control of the position would already be great:stuck_out_tongue_winking_eye:)
The exposing of pushable buttons like “simulate button press” in the velbus link software is a feature that I recently requested and is being worked on.
There is still a bug that makes it unusable but most of the code has been added already.
Once it’s ready it’ll be in one of the next HA releases.
Kind regards,
Jeroen