Open obviouspenguin opened 1 month ago
I am having the exact same issue with mine. Only seems to affect my new HS 200 – BL devices.
Seeing the same issue. Have the HS 200 - LA
Same here. Have HS200 with hardware version 5.26 (bought as a double switch HS200-2) while the other HS200 with hardware version 5.0 seem to work fine. Did TPLink change something in their protocol?
Any chance of getting this issue looked at please?
Seems like this also affects the WiFi only variants as well. Got a new 3 pack white with hardware rev 5.26 on firmware 1.0.2. One noticeable thing with the provisioning process is that it’s different and you also get some additional options that I haven’t seen before (auto turn off, led indicator mode change, delayed shut off, and default state).
wonder if they closed the hole to push people towards the matter/homekit switches?
Also facing the exact same issue. My older HS200 switches are discovered just fine, the new HS200 BLE switches are not found. When I add them to manual discovery, the bridge just restarts itself every few seconds too.
Interesting note, I bought single packs instead with hardware rev 5.6 and they behave like normal.
Is there an existing issue for this?
What happened?
I purchased a new black colored version of the Kasa HS200. Connected it to WiFi and it’s showing on my Google home and Kasa apps. I cannot get it to appear in homebridge. I have a dozen other HS200 switches that work just fine. I’m not sure if this is a newer version of the HS200 switch as it initially paired with Bluetooth via the Kasa app. I’ve never had to do that with the others.
What, if anything, has recently changed?
Homebridge is up to date. Nothing has changed. The other switches are just fine.
Version
8.0.3
Node Version
20.13.0
Homebridge Version
1.8.1
Which OS/Platform?
Linux
Relevant log output
Configuration