I just brought an innr I85C colour bulb + smartthings hub (this is my first smart home hub/device). After doing some basic research on hue, zigbee and z-wave obviously purchasing the smartthings hub for it’s software and it’s support of both protocols.
I purchases the innr bulb as I read a couple of review where people said they worked, it was much cheaper than a hue bulb and did not require but in theory also works with a hue bridge should I have gone that way.
But to my disapointment after serveral hours of trying to pair it I got no where and starting trawling the web again for answers only to find many people saying they won’t work with ST.
Thinking I would have to return it I tried a few more times to try and pair it and on the 8th time a generic ‘thing’ shows up on my ST hub.
I can’t do anything with it so assume it’s not properly paired, and tell the ST hub to forget it and then try pairing again, this time I get it on the 4th attempt but again it’s a generic ‘thing’
Come back to read and find these posts stating they innr are doing a custom device handler, but can find no mention of that anywhere else not least with innr support.
Then I read you can crate your own so long as you can get it paired and can get the zigbee info including device ids and clusters.
On this basis I created my own from the Zigbee RGBW template, fill in the bits for the innr device from the logs, remove my generic thing, repair and it works. All features seem to be a-ok, brightness, hue, temp and on/off.
Then had the idea that I might now need my handler, so again remove the thing, repair and get a generic thing again, edit it to use the Zigbee RGBW device and type and it’s a-ok.
So perfectly compatible if you willing to edit the device or if you want it to be found automatically create a custom device type.
The real problem lay in the pairing of it. I have now have had 40 attempts at pairing with 10 successful, with the last 6 being consistently reproducable.
The issue is timing in the pairing process. You must not wait too long or too soon after you start ST discovery.
I found the following sequence works for me
Turn bulb on and off at switch 3 times with 1.5s delay between earch switch.
Start ST discovery (within 1.5s - so tricky, have to hold phone in 1 hand, other on switch)
Continuing switching the bulb another 3 times, go the 2 flashes and then single flash indicating paired and it shows up on the ST hub.
Now the real sore point about all of this is not just the timing issue, but the fact the bulb lies about being paired, in every single attempt to pair the bulb, it does it’s usual 2 flash to show active, then single flash following to show paired, when in fact it was no paired.
There is certainly no one in the street I live with any other zigbee devices so this bulb just flat out lies about being paired.
Sorry for the long rant my first smart device has been quite an adventure, but hope its useful information.
Summary:
Bulb lies about being paired.
Bulb needs explicit timing to actually pair, (9s total, 4.5s of switching 3 times with 1.5s gaps, then ST discovery, followed by another 4.5s of switching)
Thing is not recognized, but manually editing thing and assigning device type Zigbee RGBW works.
