UPB - unresponsive yet HA doesn't realize it

I’m using the UPB integration. Prior to HA and UPB I used HCA and UPB (HCA is sort of the gold standard for UPB integration as the author of HCA also wrote the “upstart” software that does all UPB configuration. My UPB stuff has worked for years (under HCA), so I’m pretty comfortable the upstart config and all my hardware is solid.

UPB is very good at sending status information. Typically when you send a command it replies with a status. Or you can request a status at any time. When you restart HA and reboot the host (Pi in my case) you can tell the integration is doing status requests of all the UPB devices as it identifies the state.

So here is my issue. About once a week (and I think getting more frequent), the UPB devices stop responding - but HA thinks they are responding. HA for example says a light is on. I turn it off in HA, then HA reports it is now off. However, the light is actually still on. This happens with all UPB lights at the same time (the problem isn’t local to a specific device). HA thinks the light is receiving the command and acting properly on it - but the light is not changing.

Reloading the integration makes no difference. Restarting HA makes no difference. Rebooting the Pi fixes the problem however. After a reboot, everything functions as should be expected until at some later time when it stops again. It only happens with UPB, and when it does it affects all my UPB devices. I didn’t look at my logs the last time it happened (I know :frowning: ) - but I promise to next time.

Has anyone else seen this or am I the only UPB user with this issue? (I suspect I am one of a pretty small group of users anyway :slight_smile:

Any suggestions on what I could do to further trouble shoot this? I don’t know how to force the problem to occur - I can only wait until it happens.

One thought I had was to fire up HCA the next time this happens and confirm HCA can talk to the devices - but I’m pretty sure it will be able to and I’m not sure what that would tell me anyway. Given that rebooting the Pi solves the problem - I’m pretty certain this is related to the Pi/HA setup.

And also - I think my UPB setup in HA did work for about a month before I first saw this problem. During that month I did add a number of new integrations and automations (only started with HA a few months ago so am busy writing and adding stuff almost every day.

I’m using the UPB integration and I haven’t experienced the problem you described.

Home Assistant Supervised 2022.10.5 Debian 11 on an old laptop (USB-CIM from Simply Automated).

Driver glitch?

Tell us more about your Home Assistant configuration (installation method, version, etc).

running on a Pi 4, 8gb ram

“Operating System 9.3”

Your installation type is Home Assistant OS.

I opted for Home Assistant Supervised on Debian because, at the time I installed it, Home Assistant OS lacked the required drivers to communicate with a USB-based CIM/PIM whereas Debian 10 did. Maybe it has it now but I don’t want to switch to it. All this to say that I probably can’t offer much help because I am not using Home Assistant OS.

Always appreciate anyone that tries!