Thanks everyone for the reports. We are currently investigating the issue. As far as I can tell it looks like a recent change to ZHA may be causing it, but we don’t have the root cause yet. I looked to see if there are similar cases that have popped up and I think this is a good guess:
I’m checking with our engineers to see if something similar could be happening with our device(s). Since the workaround is fairly simple, I created a patch that anyone can use as a test. I will have to write up a how to, but some of you guys are very talented and might know how to apply it. It just runs inside of the Home Assistant terminal:
inov.li/IRbxhx1646F/patch_inovelli_keepalive.py
You first run it with a check:
python3 patch_inovelli_keepalive.py --check
Then, run it without the check:
python3 patch_inovelli_keepalive.py
Then restart Home Assistant. We will keep digging but I think this is a good lead.