search

cereal2nd / velbus-aio

Velbus Asyncio
Apache License 2.0
15 stars 12 forks source link

velbus integration with home assistant failing #22

Closed panic1 closed 3 years ago

panic1 commented 3 years ago

In the most recent docker builds for home assistant the velbus integration fails with the following message:

2021-11-09 12:10:26 WARNING (MainThread) [velbus-packet] UNKNOWN module, you should initialize a full new velbus scan: packet=08:00:00:00:00:00:00, address=246, modules=dict_keys([16, 17, 18, 19, 20, 32, 33, 34, 35, 36, 37, 38, 39, 48, 49])

panic1 commented 3 years ago

additional information: the version of velbus-aio in this setup is 2021.11.6

cereal2nd commented 3 years ago

can you clean the velbuscache and then restart hass?

panic1 commented 3 years ago

No change. Even started from a fresh, empty config folder and new docker instance, and only did the velbus integration. I'm starting to suspect that I possible have a hardware defect somewhere, although all the modules do seem to be functioning, and a power cycle of the entire velbus installation also didn't resolve it.

cereal2nd commented 3 years ago

can you get me the full log with debug for velbus enabled?

logger:
  default: info
  logs:
    velbus-parser: debug
    velbus-module: debug
    velbus-packet: debug
    velbus-protocol: debug
    velbus: debug
    homeassistant.components.velbus: debug
panic1 commented 3 years ago

hass.log

panic1 commented 3 years ago

For as far as I have deduced: there are 15 input modules (spread out in the range from 16 to 49), and there are 6 output modules. I believe it's those 6 that cause the log to appear? Maybe the logs means nothing bad, and there is something else deadlocking later on?

cereal2nd commented 3 years ago

home-assistant | 2021-11-09 20:38:40 INFO (MainThread) [velbus] All modules loaded so everything is ok.

this message is printed because we receive a velbus message before our initial scan finished. so i think we can close this bug

panic1 commented 3 years ago

So my problem is to be found elsewhere? The inputs seems to be registered in home-assistent, but the output switches are unavailable...

cereal2nd commented 3 years ago

This was not in the ticket, so it's hard to know that your inputs are available but the outputs are not.

In hass, go to integrations -> velbus, hit the entities link here and start typing switch.

Is anything showing up?

panic1 commented 3 years ago

Yes, those are showing up as unavailable, those are stale entires from earlier detections most likely, I've been running and updating as we go this installation for 3 or 4 years now.

I have reverted the home assistant version back to the 2021.10.6 build, and it works again for now (wife approval factor restored). I'll continue my digging into the failures, but I believe we can exclude the velbusaio lib.

DannyDeGaspari commented 3 years ago

Try a reload of the Velbus integration after HA has started from the integrations menu. It looks similar to an issue on my system. I made a fix for it and is currently in a pull request for velbus-aio. If the reload works, then wait for a new release of velbusaio to be integrated in one of the next HA releases.

panic1 commented 3 years ago

I have done multiple reloads, but no change. I haven't had time to dig deeper to learn the protocol and code for myself to start some debugging on this

DannyDeGaspari commented 3 years ago

Did you also try to empty the velbus cache AFTER HA has started and BEFORE the reload ?

panic1 commented 3 years ago

No, previously I shut down home assistant, cleared the cache and restart it