Homekit - Accessory Not Supported

Im having an issue with one of my Yeelights in the Home app. I am able to connect, setup and control the light in the Mi and Yeelight apps on my iPhone but when i open the Home app it says the light is “Not Supported”. If i check the log when i enter homebridge it does say it connects/true.

The weird issue is if i disconnect/unpair that globe and repair it from a “factory reset” the Home app will see it and control it but then it will go back to the “Not Supported” state after a brief time.

Has anybody else had this issue? I am able to connect and control my other 12 Yeelights in my house via the Home app without any issues, it’s just this one globe and because it works with the Mi and Yeelight apps I know its not an issue with the globe.

Thanks

Could you post some log here? So we can know what’s wrong.

Mymacbookpro:~ mymac$ homebridge
[7/10/2017, 5:34:40 PM] Loaded plugin: homebridge-server
[7/10/2017, 5:34:40 PM] Registering platform ‘homebridge-server.Server’
[7/10/2017, 5:34:40 PM] —
failed to load BLE module!
[7/10/2017, 5:34:40 PM] Loaded plugin: homebridge-yeelight
[7/10/2017, 5:34:40 PM] Registering platform ‘homebridge-yeelight.yeelight’
[7/10/2017, 5:34:40 PM] —
[7/10/2017, 5:34:40 PM] Loaded config.json with 0 accessories and 2 platforms.
[7/10/2017, 5:34:40 PM] —
[7/10/2017, 5:34:40 PM] Loading 2 platforms…
[7/10/2017, 5:34:40 PM] [Homebridge Server] Initializing Server platform…
[7/10/2017, 5:34:40 PM] [yeelight] Initializing yeelight platform…
[7/10/2017, 5:34:40 PM] [yeelight] YeePlatform Init
[7/10/2017, 5:34:40 PM] Loading 0 accessories…
Scan this code with your HomeKit App on your iOS device to pair with Homebridge:

┌────────────┐     
│ 031-45-154 │     
└────────────┘     

[7/10/2017, 5:34:40 PM] [yeelight] DidFinishLaunching
no ble cap, skip ble device discovery
[7/10/2017, 5:34:40 PM] [Homebridge Server] is listening on: http://1??.1??.0.6:8765
[7/10/2017, 5:34:40 PM] Homebridge is running on port 51826.
add to multicast group
listen on 0.0.0.0
no did or loc found!
[7/10/2017, 5:34:40 PM] [yeelight] cached accessory: 0x000000000335b5d1
already in device list!
[7/10/2017, 5:34:40 PM] [yeelight] cached accessory: 0x00000000035e46ad
[7/10/2017, 5:34:40 PM] [yeelight] cached accessory: 0x00000000035e4e8f
[7/10/2017, 5:34:40 PM] [yeelight] cached accessory: 0x00000000034748e6
[7/10/2017, 5:34:40 PM] [yeelight] cached accessory: 0x000000000335b2ec
already in device list!
[7/10/2017, 5:34:40 PM] [yeelight] cached accessory: 0x00000000035ad64d
[7/10/2017, 5:34:40 PM] [yeelight] cached accessory: 0x00000000035e4c84
[7/10/2017, 5:34:40 PM] [yeelight] cached accessory: 0x00000000035e4d5d
already in device list!
already in device list!
[7/10/2017, 5:34:40 PM] [yeelight] cached accessory: 0x00000000035e49f5
[7/10/2017, 5:34:40 PM] [yeelight] cached accessory: 0x000000000335d84e
already in device list!
already in device list!
[7/10/2017, 5:34:40 PM] [yeelight] cached accessory: 0x000000000335cc05
already in device list!
[7/10/2017, 5:34:40 PM] [yeelight] cached accessory: 0x00000000035b4446
already in device list!
already in device list!
already in device list!
already in device list!
already in device list!
[7/10/2017, 5:34:40 PM] [yeelight] cached accessory: 0x00000000035b4233
connect ok!
[7/10/2017, 5:34:40 PM] [yeelight] accesseory reachable
[7/10/2017, 5:34:40 PM] [yeelight] dev connected 0x000000000335b5d1 true
connect ok!
[7/10/2017, 5:34:40 PM] [yeelight] accesseory reachable
[7/10/2017, 5:34:40 PM] [yeelight] dev connected 0x00000000034748e6 true
connect ok!
[7/10/2017, 5:34:40 PM] [yeelight] accesseory reachable
[7/10/2017, 5:34:40 PM] [yeelight] dev connected 0x00000000035e4c84 true
connect ok!
[7/10/2017, 5:34:40 PM] [yeelight] accesseory reachable
[7/10/2017, 5:34:40 PM] [yeelight] dev connected 0x00000000035e4e8f true
connect ok!
[7/10/2017, 5:34:40 PM] [yeelight] accesseory reachable
[7/10/2017, 5:34:40 PM] [yeelight] dev connected 0x00000000035e46ad true
connect ok!
[7/10/2017, 5:34:40 PM] [yeelight] accesseory reachable
[7/10/2017, 5:34:40 PM] [yeelight] dev connected 0x000000000335b2ec true
connect ok!
[7/10/2017, 5:34:40 PM] [yeelight] accesseory reachable
[7/10/2017, 5:34:40 PM] [yeelight] dev connected 0x00000000035ad64d true
connect ok!
[7/10/2017, 5:34:40 PM] [yeelight] accesseory reachable
[7/10/2017, 5:34:40 PM] [yeelight] dev connected 0x00000000035e49f5 true
connect ok!
[7/10/2017, 5:34:40 PM] [yeelight] accesseory reachable
[7/10/2017, 5:34:40 PM] [yeelight] dev connected 0x00000000035e4d5d true
connect ok!
[7/10/2017, 5:34:40 PM] [yeelight] accesseory reachable
[7/10/2017, 5:34:40 PM] [yeelight] dev connected 0x000000000335cc05 true
already in device list!
connect ok!
[7/10/2017, 5:34:40 PM] [yeelight] accesseory reachable
[7/10/2017, 5:34:40 PM] [yeelight] dev connected 0x000000000335d84e true
connect ok!
[7/10/2017, 5:34:40 PM] [yeelight] accesseory reachable
[7/10/2017, 5:34:40 PM] [yeelight] dev connected 0x00000000035b4233 true
connect ok!
[7/10/2017, 5:34:40 PM] [yeelight] accesseory reachable
[7/10/2017, 5:34:40 PM] [yeelight] dev connected 0x00000000035b4446 true
send hb to: 0x000000000335b5d1

I hope this helps

That’s really strange, from the log everything looks good … Is this one the same model as other 11?
The only solution I can think is to remove all cached files under ~/.homebridge and re-add them.

This morning I removed homebridge from the Home App and re-added it again. I was able to control all the lights but I couldn’t change the name of move it into another room and it was saying The Accessory is Blocked. As i was able to control the light i would just put up with that but then when i followed the details to run homebridge on start up (following the steps on this link https://github.com/nfarina/homebridge/wiki/Install-Homebridge-on-macOS) it then said the accessory was not supported (like in the photos and not being able to be controlled) and it is still saying The Accessory is Blocked. I have tried stopping the plist. but that doesn’t fix the issue.

Is there a way to unblock the accessory? The Yeelights are up to date (version 1.4.1_52) and I’m running the ios 11 public beta. I have been able to add other Yeelights with this one still playing up so I’m not sure why it is this one globe. The globe has the same information as the others so I believe the globes are the same model. I have tried deleting all the cached files as well

Hope this information sheds some more light on the issue

I figured out the issue. It was ios 11. I downgraded to 10.3.2 and everything works fine!

Thanks for your update! It’s a relief …