New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Keep Getting Accessory Note Found in home.app #14
Comments
Hi - without any further info pretty hard to be sure… By security update - I presume you mean installing cyptography? I presume the plugin starts without errors? This is all pretty basic low level stuff that no one else is seeing - so would presume there is some user error somewhere along the way, but without further information it is impossible to comment. |
current setup, Mac Mini M1 (MacOS 12.4) with Indigo 2022.1. Using a Insteon PowerLinc 2413U, Firmware 9.9. Here is the debug log file from Indigo: HomeKitLink Siri Set Logging to DEBUG It appears that Indigo is publishing everything OK, but when I tried to add the accessory to a freshly (re)imaged iPhone 13, it gives me Accessory Not found after I scan in the QR code. |
OK. Well broadly it is either a plugin issue, or a HomeKit app issue. Although as general rule wouldn’t use the restart all Bridges menu item - isn’t needed. Use the main restart Plugin selection - more fool proof. But: & Back to plugin. & further |
Having the same issue--iOS Home app shows Connecting to Bridge then after a few minutes--"unable to add accessory; accessory is not reachable." I tried removing published devices from bridge, deleted bridge device and created a new bridge device. Indigo shows it as operational. No errors in the Indigo log. Indigo 2022.1.1 |
As best I can tell - this will be a HomeKit connection issue, as without errors seems unlikely to be plugin. Obviously most others are connecting fine. Will write a FAQ somewhere for future reference: The plugin tests port before it uses them for the Bridge (so they should be fine). If any question that might be port issue can in advanced settings change default port number add, minus hundred for example. This should NOT be issue as would give error on startup. Basically HomeKit can’t connect to your Indigo Mac. This is pretty generic: But worthwhile reviewing. |
Try: This appears to result from some cache issue in the Home app as resetting homebridge (above) does not resolve the issue. This WiFi trick appears to work however: Reset Pairing/Accessories as described above. &” This error can also occur when [mDNS] needs to be configured, e.g. when Avanti needs to be setup on Linux. |
Thanks--this worked!!
|
I did a complete reset of Indigo and used the new 0.6.5 plugin and that seemed to have fixed it...pretty sure it had something to do with the mDNS issue... |
I'm getting the same issue. It seems the bridges are not broadcast via mDNS. I use Avahi on my pfSense and all other services are broadcasting fine from the Indigo Mac mini. However, for the plugin, nothing seems to be broadcast (I have setup three bridges to try, still no service broadcast for the respective ports 51826, 51827, 51828). I have a _companion-link._tcp. broadcast on port 49155 but I'm not sure if that's to do with the plugin. Any ideas? |
Hi Accessory not found is a pretty generic issue - in your case would guess another cause relating to network Either mDNS isn’t leaving your Mac to be seen or it is being blocked somewhere. Companion is nothing to do with plugin would upgrade to the latest version - specifically https://github.com/Ghawken/HomeKitLink-Siri/releases/tag/0.6.16 failing the new version working off the bat would trial the mDNS settings starting with IPv4 only setting. (these settings can break mDNS but nothing that can’t be fixed by setting back to original and restarting plugin) |
Thanks, I'll give the new version a try and report back. |
Got the plugin installed, installed the security update via terminal, Indigo 2022.1 sees the plugin, was able to create the new HKLS item and went to add the QR Code to my home app and it spins forever and finally gives up and says accessory not added.
The text was updated successfully, but these errors were encountered: