In the previous Velbus integration, this module has always worked perfectly. The only one, as far as I know, was the VMB1TCW and the VMB4PD, who where not integrated. The VMB1TS module is still available at Velleman.
yes, in the previous version it worked, but keep in mind this is a complete rewrite of the module.
about the vmb1ts module, i start to think that there was an error somewhere in the script.
as the loading and loaded variable are both false, and if i read the code correctly this should never happen, except if an exception occured during the initialize of the module.
Can you try to give me the full log (in text version)? or contact met on discord cereal#0919
At first glance the update didn’t really improve my situation either. For some reason now device names aren’t complete anymore. Clearing the cache and even re-adding the integration results in the same scrambled up names. For example instead of Shutter Relay 1, the device is now added as shttr Relay 1. Same with Push Garden is now Pus Garden.
I even rewrote the whole bus using VelbusLink to make sure the device names were correct but that didn’t seem to do the trick. I’ll monitor if this affects the functionality in the long run.
vmbgp4pir does also support a thermostat not?
in that case it should be avilable as a thermostat, is it maybe an idea to export both, a climate device and a sensor for each module that supports temperature and climate?
Yes. That changed now. The thermostat function is back but the individual temp entity is no longer available. Not a big issue since its part of the current thermostat temp
However in same case it might be useful to have the individual temp also
Hi Cereal2nd, I noticed that the issues described above by other users are still present in the 2021.11.1 release. Its about the incomplete or missing characters in the channel names, and the climate that is sometimes not working properly.
I have a solution for these issues and requires a small change in velbusaio. It works well when I test velbusaio separately on my system. But in Home Assistant, Velbus is not fully loaded when HA is restarted. After HA startup you have to do a reload of the Velbus integration to fully load the Velbus modules. This is not related to my change. Maybe you can help here. Once it works well, I can do a pull request of velbusaio.