Can you s Nd me the diff? Or create a pull request in the velbusaio module for this?
Any chance you could look into the missing sensor values for VMBMETEO as well for an upcoming release?
if we can setup a debug session, yes contact me on discord
@Bart_Coppens, @bvedomotic, @Geert_Verbist, and maybe others too : Can you try HA 2021.11.2, a fix should be there for the Not all modules are loaded... message. This should resolve the incomplete channel names and sometimes missing climate.
After the update you should clear the cache: home-assistant\config.storage\velbuscache
Then do a reload of the velbus integration, after max 10 mins check if all modules are there.
Let us know the outcome.
Updating now
Looks good. Individual temp sensors are back. No errors in the logs. Needs further testing but it seems really good
Great, thanks for feedback
Great, I hope all errors with the move to async are resolved now.
If there are feature requests let me know, the coming months I have some free time, so I should be able to add these.
Things where I think of:
- control forced on, forced off, inhibit and locked for channels
Hi Cereal2nd, I have still the issue that after a restart of HA the Velbus integration does not load the status of all modules, only of the first few. I have to do a manual reload of the Velbus integration to load the status of all modules. Maybe because the Velbus load is taking too long it is aborted during startup by HA ?
Can you enable the debug for velbus. Remove the cache and start Hass again.
And then provide me with the log file.
Thanks for the tip about the log. I found the problem. It is the timeout of the velbus scan that is set too short (15 s). At HA startup, the scan is very slow and times out. After startup and with a reload of the Velbus integration, the scan speed is what is expected and not timing out. I’ll see if I can find a proper solution for this. Just increasing the timeout will help but there will be a system where this timeout will again be too short.
Ok, I tried these steps:
- remove the velbus integration
- Reboot the host
- Removed the cache through SSH:
rm -R config/.storage/velbuscache - Added the integration back
- Waited…
And after 10 minutes I still got the [velbus] Not all modules are loaded within a timeout of 600 seconds, continuing with the loaded modules error. Some of the loading seems to have worked, but a lot of the naming is lacking now. Running 2021.11.3. Are there other steps I should take?
How much time was there between step 2 and 3 ?
Can you try this: with HA running, clear the velbuscache, then reload the velbus integration from the integrations menu. If you still have problems then post a log with following settings: velbus integration with home assistant failing · Issue #22 · Cereal2nd/velbus-aio · GitHub
About my previous message: I removed the cache right after the reboot.
I updated to 2021.11.4 and it seems like your suggestion works better indeed: I removed the cache with HA running, cleared the cache and reloaded the velbus integration. In the end I got a [velbus] All modules loaded.
BUT, I still get these – tail of my log:
2021-11-17 21:10:07 WARNING (MainThread) [velbus] Waiting for module 39
2021-11-17 21:10:07 WARNING (MainThread) [velbus] Waiting for module 40
2021-11-17 21:10:07 INFO (MainThread) [velbus] Not all modules loaded yet, waiting 15 seconds
2021-11-17 21:10:22 WARNING (MainThread) [velbus] Waiting for module 36
2021-11-17 21:10:22 WARNING (MainThread) [velbus] Waiting for module 37
2021-11-17 21:10:22 WARNING (MainThread) [velbus] Waiting for module 38
2021-11-17 21:10:22 WARNING (MainThread) [velbus] Waiting for module 39
2021-11-17 21:10:22 WARNING (MainThread) [velbus] Waiting for module 40
2021-11-17 21:10:22 INFO (MainThread) [velbus] Not all modules loaded yet, waiting 15 seconds
2021-11-17 21:10:37 WARNING (MainThread) [velbus] Waiting for module 38
2021-11-17 21:10:37 WARNING (MainThread) [velbus] Waiting for module 39
2021-11-17 21:10:37 WARNING (MainThread) [velbus] Waiting for module 40
2021-11-17 21:10:37 INFO (MainThread) [velbus] Not all modules loaded yet, waiting 15 seconds
2021-11-17 21:10:52 INFO (MainThread) [velbus] All modules loaded
2021-11-17 21:12:48 WARNING (MainThread) [velbus-packet] UNKNOWN module, you should initialize a full new velbus scan: packet=08:00:01:80:00:00:00, address=243, modules=dict_keys([16, 17, 18, 19, 20, 21,
22, 23, 24, 25, 32, 33, 34, 35, 36, 37, 38, 39, 40])
2021-11-17 21:12:48 WARNING (MainThread) [velbus-packet] UNKNOWN module, you should initialize a full new velbus scan: packet=08:00:00, address=243, modules=dict_keys([16, 17, 18, 19, 20, 21, 22, 23, 24,
25, 32, 33, 34, 35, 36, 37, 38, 39, 40])
2021-11-17 21:12:49 WARNING (MainThread) [velbus-packet] UNKNOWN module, you should initialize a full new velbus scan: packet=08:00:00:00:00:00:00, address=243, modules=dict_keys([16, 17, 18, 19, 20, 21,
22, 23, 24, 25, 32, 33, 34, 35, 36, 37, 38, 39, 40])
2021-11-17 21:12:49 WARNING (MainThread) [velbus-packet] UNKNOWN module, you should initialize a full new velbus scan: packet=00:08:00, address=243, modules=dict_keys([16, 17, 18, 19, 20, 21, 22, 23, 24,
25, 32, 33, 34, 35, 36, 37, 38, 39, 40])
2021-11-17 21:12:50 WARNING (MainThread) [velbus-packet] UNKNOWN module, you should initialize a full new velbus scan: packet=02:00:01:80:00:00:00, address=247, modules=dict_keys([16, 17, 18, 19, 20, 21,
22, 23, 24, 25, 32, 33, 34, 35, 36, 37, 38, 39, 40])
2021-11-17 21:12:50 WARNING (MainThread) [velbus-packet] UNKNOWN module, you should initialize a full new velbus scan: packet=02:00:00, address=247, modules=dict_keys([16, 17, 18, 19, 20, 21, 22, 23, 24,
25, 32, 33, 34, 35, 36, 37, 38, 39, 40])
2021-11-17 21:12:52 WARNING (MainThread) [velbus-packet] UNKNOWN module, you should initialize a full new velbus scan: packet=02:00:00:00:00:00:00, address=247, modules=dict_keys([16, 17, 18, 19, 20, 21,
22, 23, 24, 25, 32, 33, 34, 35, 36, 37, 38, 39, 40])
2021-11-17 21:12:52 WARNING (MainThread) [velbus-packet] UNKNOWN module, you should initialize a full new velbus scan: packet=00:02:00, address=247, modules=dict_keys([16, 17, 18, 19, 20, 21, 22, 23, 24,
25, 32, 33, 34, 35, 36, 37, 38, 39, 40])
2021-11-17 21:17:08 INFO (MainThread) [homeassistant.components.websocket_api.http.connection] [547201877760] Connection closed by client
2021-11-17 21:17:25 ERROR (MainThread) [frontend.js.latest.202111090] :0:0 ResizeObserver loop completed with undelivered notifications.
2021-11-17 21:17:52 WARNING (MainThread) [velbus-packet] UNKNOWN module, you should initialize a full new velbus scan: packet=02:00:00:00:00:00:00, address=246, modules=dict_keys([16, 17, 18, 19, 20, 21,
22, 23, 24, 25, 32, 33, 34, 35, 36, 37, 38, 39, 40])
2021-11-17 21:17:52 WARNING (MainThread) [velbus-packet] UNKNOWN module, you should initialize a full new velbus scan: packet=00:02:00, address=246, modules=dict_keys([16, 17, 18, 19, 20, 21, 22, 23, 24,
25, 32, 33, 34, 35, 36, 37, 38, 39, 40])
2021-11-17 21:17:54 WARNING (MainThread) [velbus-packet] UNKNOWN module, you should initialize a full new velbus scan: packet=02:00:01:80:00:00:00, address=246, modules=dict_keys([16, 17, 18, 19, 20, 21,
22, 23, 24, 25, 32, 33, 34, 35, 36, 37, 38, 39, 40])
2021-11-17 21:17:54 WARNING (MainThread) [velbus-packet] UNKNOWN module, you should initialize a full new velbus scan: packet=02:00:00, address=246, modules=dict_keys([16, 17, 18, 19, 20, 21, 22, 23, 24,
25, 32, 33, 34, 35, 36, 37, 38, 39, 40])
2021-11-17 21:18:05 ERROR (MainThread) [frontend.js.latest.202111090] :0:0 ResizeObserver loop completed with undelivered notifications.
2021-11-17 21:18:08 INFO (MainThread) [homeassistant.components.websocket_api.http.connection] [547198107456] Connection closed by client
2021-11-17 21:18:09 ERROR (MainThread) [frontend.js.latest.202111090] :0:0 ResizeObserver loop completed with undelivered notifications.
Before these problems started, my velbus setup was loaded with a LOT of names attached to them. Like they’re configured in the Velbus system. Now they’re loaded in a generic way. And the errors indicate that indeed, something is still going wrong?
I see you have a lot of velbus modules and the ones shown as unkown all have a high address value (> 243). Only modules up to address 40 seem to be loaded.
A fix for this has been implemented in velbus-aio: Fix requirement of reload of Velbus integration in HA after startup. by DannyDeGaspari · Pull Request #23 · Cereal2nd/velbus-aio · GitHub.
You can try to update it in your HA setup or wait for the next maintenance release of HA (2021.11.5).
And always clear the cache after you encountered problems. If you still see issues in the log, let it know.
@DDG My entire house lighting is powered by velbus, so I do indeed have several modules. 
I just upgraded to 2021.11.5 and without me doing anything, everything started working again. I see the usual ‘names’ on the switches again, and they work. Thx for your help!
From my side I can confirm the VMBMETEO is now fully supported on latest release including readout of the analog sensors like rainfall, wind speed and illuminance. Thanks @Cereal2nd for the support!
I did see loading issues before release 11.5 where sometimes modules were missing after startup but still need to evaluate on latest release @DDG
I also run version 2021.11.5 and with the VMBELO there is a gap in the sensor list. Where Velbuslink indicates heater, pump and Alarm1 pressed, HA indicates boost and cooler active. The same occurs with the VMBGPO modules.
This is something i never checked, so can be that there is still a bug.
can you create an issue at: