Can you first remove the velbus integration from HA, stop HA and again try to remove the cache folder entirely?
Then at boot readd the velbus integration.
Kind regards,
Jeroen
whats the exact connection-string you use?
To enable more debugging you can add this to your config.aml
logger:
default: info
logs:
velbus-parser: debug
velbus-module: debug
velbus-packet: debug
velbus-protocol: debug
velbus: debug
homeassistant.components.velbus: debug
indeed, the device registrations will not be removed by the velbus cache.
how to remove this is unknown for me ā¦
maybe this is a bug and we should fix this in the following releases, so maybe create a bugreport for this
@darkpainy Iām reluctant to removing the Velbus integration and then adding it again, but I did. It solved the double entries. But I also had to fix all my automations which were still pointing to the entities who are not there anymore.
@Cereal2nd Indeed nothing wrong with the cache.
But it means that over time with all the updates which I do at least every month, it got this double entries. Some of the automations already pointed to the good ones, they are still working. But the oldest automations were broken.
Anyway, thanks for the tip.
1 Like
Indeed, updating things in velbus link will mess with HA entities.
I only started using HA after I finished all my work in velbus link.
Maybe this is solfable, HA is getting all the names from velbus and creating all the entities from that. it currently does not remove any entities if pre-existing ones stop existing nor does it update old entities to new names. Maybe there is a common identifier (for example the bus ID for an entity) which can be used.
can you send me the diagnostics of the full entity?
this will help me debug this
Hi Darkpainy,
Thank you for your answer.
My Signum is in the same network.
I think so
Iām not an expert, I cannot answer for the docker network mode.
Itās too difficult for me.
If someone of you have the time to connect to my computer and do the check, Iāll pay for the work.
Thank you a lot
Diagnostics of which entity do you want ? The double entities are gone now, so I canāt look into that anymore.
Hi Jonathan,
Tomorow Iām working from home, so if you have some time I could help you in a remote session for 30min - 1h.
Are you running docker and HA on a linux machine? hopefullyā¦ because iāve never tried any of this on windowsā¦ (but it is possible I readā¦)
A skype & teamviewer session on a windows machine with SSH access to your (hopfully linux device) should be enough for me to check some things together with you if you want.
ps: this is a forum with people to help others, you donāt need to pay anyone / anything ā¦!
Kind regards,
Jeroen
Of the full integration, there is diagnostics on the device level and on the integration level.
All things are in the dev branch, so they will be available from the first .7 release
1 Like
Hi @Cereal2nd ,
Sorry for the super late reply, I had a child and itās been super hectic lately xD
Anyway, I now have the latest HomeAssistant version and still have this same issue.
When the blinds close, this all works but the entity gets an immediate āopenedā response when the cover is closed; which results in a wrong position state (open vs closed).
Any ideas on this since back then?
Not a huge deal of course, but Iām wondering if itās just my installation or a general bug.
Thanks for your awesome work, mate! Love the integration of my home (Velbus) with HA!
1 Like
I was testing the new feature to simulate button presses on one of my glass pannels but it does not seem to work correctly yet.
The feature is there in HA (I can enable a button and click it)
hereās the log from debugging:
Button press home assitant
2022-08-02 11:14:58 DEBUG (MainThread) [velbus-protocol] TX: RawMessage(priority=f8, address=2d, rtr=False, command=0, data=b'00 00 00 00')
simulate button press velbus link software
2022-08-02 11:16:07 DEBUG (MainThread) [velbus-protocol] Received 10 bytes from Velbus: b'0f f8 2d 04 00 20 00 00 a8 04'
2022-08-02 11:16:07 DEBUG (MainThread) [velbus-protocol] RX: RawMessage(priority=f8, address=2d, rtr=False, command=0, data=b'00 20 00 00')
2022-08-02 11:16:07 DEBUG (MainThread) [velbus-packet] Received {"name": "PushButtonStatusMessage", "priority": 248, "address": 45, "rtr": false, "data": "", "closed": [6], "opened": [], "closed_long": []}
2022-08-02 11:16:07 DEBUG (MainThread) [velbus-protocol] Received 10 bytes from Velbus: b'0f f8 2d 04 00 00 20 00 a8 04'
2022-08-02 11:16:07 DEBUG (MainThread) [velbus-protocol] RX: RawMessage(priority=f8, address=2d, rtr=False, command=0, data=b'00 00 20 00')
2022-08-02 11:16:07 DEBUG (MainThread) [velbus-packet] Received {"name": "PushButtonStatusMessage", "priority": 248, "address": 45, "rtr": false, "data": "", "closed": [], "opened": [6], "closed_long": []}
So, the payload of the home assistant button is 00, where for the velbus link button press it is 20 for open and 20 for close shortly after that.
Hope we can fix it 
Thanks in advance.
Kind regards,
Jeroen
can you show me the log of velbuslink?
Was on small holiday, will give you the logs tomorrow
this is the velbus link log when I press the button on home assistant:
06/08/2022 22:44:02.406 RECV 0F F8 2D 04 00 00 00 00 C8 04
06/08/2022 22:44:03.404 RECV 0F F8 2D 04 00 00 00 00 C8 04
this is the velbus link log when i use the āsimulate button presā inside velbus link:
06/08/2022 22:44:34.559 SEND 0F F8 2D 04 00 20 00 00 A8 04
06/08/2022 22:44:34.613 SEND 0F F8 2D 04 00 00 20 00 A8 04
Kind regards,
Jeroen
Iām running Velbus (with Home Assistant) in a warm country where the thermostats only run in Cool modeā¦ however, Home Assistant thinks they are all in heating mode without the option to switch to cool mode (Failed to call service climate/set_hvac_mode - is the error) ā¦
perhaps a small bug in the plugin?
is Velbus deployed in other countries than Belgium and the Netherlands 
?