Bleasel wrote:About five days ago all bridged devices are showing "No Response" on:
MacBookPro, OS 13.4.1; Home v7.0
Iphone 13, iOS 16.5.1
iPad Min OS 15.7.7
HomePod
Indigo 2022.2
Homekitlink Siri 0.6.16
HOWEVER
They all work on MacPro (Mid 2012). OS 10.14.6. Home v3.0
When I add a new device, it is shown on all systems, but only responsive on the MacPro
All devices are are the same WiFi network.
Hi
You have a very odd collection of various versions of HomeKit. I would suspect that is something to do with it.
Home v7.0 & v3.0 — ? What are you referring to here. HomeKit doesn’t have a specific version number, it uses the OS version. (or so I believe?)
Devices newer than OS16.4 the new HomeKit architecture are not backward compatible with older devices. By the fact that you have a number of older devices and OS, I would presume you are using the <16.4 old HomeKit architecture, with a number of the newer apps which now aren’t working. I would suggest it is probably the nature of this aspect that is now causing problems.
As a general rule if working on one client, then won’t be plugin issue - will be HomeKit broader network issue, versions, or mDNS issue for various clients.
There is one exception to this which is the UUID binary update that 0.6.16 fixes (only when paired though). There are a few reports of clients showing non-response because expecting binary data rather than paired key which was previously used. It hasn’t been clearly seen in the wild as it were, and I haven’t seen it, but 0.6.16 - fixes that as an future issue. To check this as an possibility a HKLS plugin bridge will need to be deleted in the Home app, then Reset Accessory in the HKLS plugin menu (selecting bridge), and then restart HKLS plugin. Then repair the same bridge (all the devices attached to it will remain and won’t need to be re-setup) using QR code and Home App.
So:
Try one or another:
1. Check mDNS issue on these devices (using discovery app) as per the troubleshooting post
2. Delete Bridge from Home app as above, reset, and repair - to see whether changes.
Failing these 2 options - would suggesting upgrade arch (which will likely have to at some stage) even though will render some clients unusable.
Glenn
Sent from my iPad using Tapatalk