Closed jlg89 closed 4 months ago
This was a real head-scratcher, and almost had me to the point of deleting and recreating the entire HomeKit home. Fortunately, I had the notion to unplug the Apple TV that has been acting as the primary hub, and force a switch to the secondary. Once that happened, I was able to delete the "ghost" devices, and then bring the other Apple TV back online.
So, this was an issue with a home hub having a wonky device cache, or something.
Is there an existing issue for this?
What happened?
The plugin reports 43 cached devices, which is correct. However, many of the TPLink devices are appearing twice in HomeKit. One instance works correctly, the duplicate is "not responding" and cannot be removed. If I try to remove using the Home app, nothing happens; if I do it with the Controller app, it either says "Cannot remove non-bridge accessory" or "Object not found." All of the devices with duplicates are above 100-series (HS220, HS210, HS200, KS200M, HS300, KP303) -- but not all of the 200/300-series devices have duplicates.
Oddly, some (not all) of the "ghost" accessories indicate that they are integrated via the "East Stairs" bridge -- which is not, nor has it ever been, a bridge. It's an HS210 switch.
What, if anything, has recently changed?
I was using HOOBS. Deleted all the HOOBS bridges from HomeKit, confirmed everything was cleared. Set up a fresh "vanilla" homebridge instance on a different Raspberry Pi, created bridges using the same basic config as before, added the new bridges to HomeKit, recreated all the scenes and automations.
Note that the homebridge Raspberry Pi has both ethernet and WiFi interfaces, the ethernet is on 192.168.3.0/24 and the WiFi is on 192.168.11.0/24, and all the TPLink devices are on the WiFi subnet, so the "broadcast" directive is used in the config to limit the plugin to that one.
Version
8.0.2
Node Version
20.11.1
Homebridge Version
1.7.0
Which OS/Platform?
Linux hb-ebc 6.1.0-rpi7-rpi-v8 #1 SMP PREEMPT Debian 1:6.1.63-1+rpt1 (2023-11-24) aarch64 GNU/Linux
Relevant log output
Configuration