in 0.104 we should have solved almost all problems with the velbus integration.
Hello,
Iām a new user of Home assistant, i did try the build in Velbus integration with my velbus installation but did not suport the most of my modules, now i see there is Python-Velbus with better support and up to date.
But (sorry Iām new here) donāt understand how to add Python-Velbus to my new installation (on raspbery Pi4-HassOS 3.10)
Is there some kind of step by step manual to make the integration for a noob like me?
I have only experience with c# programming.
I donāt understand what you want to achieve. Using the Velbus integration at Home Assistant it automatically loads the Python-velbus lib in the background. Do you run the latest Home Assistant version (0.105.4 at the moment)?
Iāve did a fresh installation, but the Velbus integration didnāt work anymoreā¦
HA is using python-velbus 2.0.42, but with a manual install of python-velbus 2.0.43 itās working again.
fixed with the following PR
hopefully this makes it into 0.107.1
1 Like
Iāve foud another issueā¦
When I use the VelbusLink tool and do a scan, Iāve get the following messages in the log
20-03-21 14:12:16 WARNING (velbus-process-reader) [velbus] Message size not recognized
2020-03-21 14:12:16 WARNING (velbus-process-reader) [velbus] Priority not recognized
2020-03-21 14:12:16 WARNING (velbus-process-reader) [velbus] Message size not recognized
2020-03-21 14:12:16 WARNING (velbus-process-reader) [velbus] Priority not recognized
2020-03-21 14:12:16 WARNING (velbus-process-reader) [velbus] Message size not recognized
2020-03-21 14:12:16 WARNING (velbus-process-reader) [velbus] Priority not recognized
2020-03-21 14:12:16 WARNING (velbus-process-reader) [velbus] Message size not recognized
2020-03-21 14:12:16 WARNING (velbus-process-reader) [velbus] Priority not recognized
2020-03-21 14:12:16 WARNING (velbus-process-reader) [velbus] Message size not recognized
2020-03-21 14:12:16 WARNING (velbus-process-reader) [velbus] Priority not recognized
2020-03-21 14:12:16 WARNING (velbus-process-reader) [velbus] Message size not recognized
2020-03-21 14:12:16 WARNING (velbus-process-reader) [velbus] Priority not recognized
2020-03-21 14:12:16 WARNING (velbus-process-reader) [velbus] Message size not recognized
2020-03-21 14:12:16 WARNING (velbus-process-reader) [velbus] Priority not recognized
2020-03-21 14:12:16 WARNING (velbus-process-reader) [velbus] Message size not recognized
2020-03-21 14:12:16 WARNING (velbus-process-reader) [velbus] Priority not recognized
2020-03-21 14:12:16 WARNING (velbus-process-reader) [velbus] Message size not recognized
2020-03-21 14:12:16 WARNING (velbus-process-reader) [velbus] Priority not recognized
2020-03-21 14:12:16 WARNING (velbus-process-reader) [velbus] Message size not recognized
2020-03-21 14:12:16 WARNING (velbus-process-reader) [velbus] Priority not recognized
And it never stops, I need to restart HAā¦
this is a known problem, but until now i did not find a solution for it.
feel free to help us out 
anyone knows when the following would be integrated? 
WARNING (Thread-2) [velbus] Module VMBGPOD-2 is not yet supported
WARNING (Thread-2) [velbus] Module VMBIRM is not yet supported
WARNING (Thread-2) [velbus] Module VMBGPOD-2 does not yet support sub modules
the vmbpirm i have at home and is on my todo list
for the gpod-2 if someone can go through the protocol manual and let me know what the difference is between version2 and version 1 i can implement this one to.
I donāt own these modules so i can not test them
1 Like
Is there a (easy) way to update the velbus Entity names?
I renamed some items in Velbuslink, but the Entity names are not updated in HA. Removing the integration is also working but maybe there is a better solution?
Hi,
is the gpod-2 already integrated?
no
iām working on an async implementation based on the moduleprotocolfile used in openhab
this will give use a lot more modules that are supported (almost all).
But i need testers
2 Likes
not sure if i can help but im willing to try for the VMBPIRM + VMBGPOD-2
if i wouldnt reply fast here, poke me on discord (im on your velbus one)
Hi,
I have been searching for a Zigbee solution and found the marvelous ZHA; outstanding tool!
Already have a decent working setup (on that another platform OH, without this kind of Zigbee integration).
It has been unfortunately very quiet on the Velbus development, most recent integrated activity goes way back.
But now I am in doubt, should I get/keep 2 platforms side by side? That would be a bit it silly/pittyā¦
Managed to find the local files for version 2021.7.3 thru Docker:
usr/local/lib/python3.9/site-packages/velbus/
@Cereal2nd how can I test (and maybe expand?) your 2021 github progress?
@ggaljoen what parts are you missing in HASS for velbus?
a lot of the stuff is working, not wure what parts are not working yet.
but indeed it has been a while since i did some work for it
@Cereal2nd most/all of the unknown messages, I would like to get rid off.
And the incomplete functionality of those modules ofcourse.
2021-07-16 15:17:24 WARNING (velbus-process-reader) [velbus] Module VMBGPOD-2 is not yet supported
2021-07-16 15:17:24 WARNING (velbus-process-reader) [velbus] Module VMBGPOD-2 does not yet support sub modules
2021-07-16 15:17:29 WARNING (velbus-process-reader) [velbus] Module VMBEL4 does not yet support sub modules
2021-07-16 15:20:24 WARNING (velbus-process-reader) [velbus] received unrecognized command 229 from module 165 (54)
2021-07-16 15:20:24 WARNING (velbus-process-reader) [velbus] received unrecognized command 230 from module 113
i do not have access to those 3 modules, so i cnaāt implement them.
Those 2 unrecognized commands are not problems, they will not give problems in the installation
I have, can you point me out (guide) how to test/implement support for those in my system and, if approved later on, for others aswell?
if you can do some python programming its pretty easy todo
this is the source code of the lib:
Most common response from āsomebody who knowsā 
; can I just change āthe files in useā (thru docker) and have result or is it more complex then that?