Good afternoon. Up until now, our UPB usage on OH has been through an OmniPro controller (by basically “HomeKit-enabling the Omni using OH”). However, in our office, we don’t have an Omni and I wanted to add our lighting to HomeKit, figuring OH would be a great way to do that (on a PI 3b+ with PoE). This is using the OH3 UPB Serial binding, also.
After getting the initial config built and adding all the lights and appropriate HomeKit Metadata, I linked OH to HomeKit and moved all the lights to their appropriate rooms.
The first thing I noticed was, I can control the lights, but OH doesn’t track their status when changed from the switches themselves. The switches are indeed set to report their level when controlled locally, and you can see the updates within the UPB Config software (UPStart) whenver a switch is manually controlled, it’s just that status change isn’t being reflected in OH.
Second, after letting OpenHABian run for a week to ensure stability, I then power-cycled (to simulate it losing power unexpectedly). Expecting it to come back and be accessible in HomeKit again, when I went to access the Home app, I discovered everything exposed to HomeKit in OH was now reporting as “Updating” eventually becoming “No Response” after a very long timeout period. What confused me about this is this was literally just a reboot, and if I go into OH, I see the status of all the UPB items as ONLINE, so whatever this is, it appears to just be with getting that info over to HomeKit. On the off-chance the reboot may have wiped the HomeKit binding for some reason, I even tried restoring the backup I took right after I finished configuring OH. It restored, and again all items came back as ONLINE, but HomeKit still shows them as Updating/NoResponse.
Also, a graceful reboot didn’t seem to help (as a last resort - and yes, I hate the “Microsoft Fix”, but after manually restarting the services with no positive effect, I thought it couldn’t hurt to try.
I also confirmed the IP is still the same as it was previously (and that the OH IP is matched in the HomeKit config).
After all of this, I then ran updates for the latest OH3 to see if that corrected - it did not.
If I remove the HomeKit addon, the NoResponse is almost instant. Additionally, if I do something blatantly obvious to fail out the HomeKit config (like add /24 to the binding IP), the NoResponse is instant. This suggests it’s talking with HomeKit but the conversation isn’t going well.
Does anyone have any thoughts why this seems to have lost it’s connectivity to HomeKit with just a power-cycle? Or, where I might look in order to troubleshoot this further, since this is making no sense to me currently?