Anything in the logs? Since there are no detents in the wheel I could easily see the encoder getting stuck between two positions and constantly spam events.
Mine has been fine, but the IKEA warehouse took almost 4 weeks to get it to me so it’s only been connected a few days.
So is that the same reason we aren't able to use the Linkind remote? (push on/off, hold to dim up/dn) They pair fine, they're really nice, (and small) and cost $6.72 ea. from the fine folks at Amazon.com
I use it "touchlink" with a pair of Cree bulbs that are already in HE. Convenient on the guest nightstand. (The remote pairs with HE, but is just a "device")
I think there might be a bug with the Battery Reporting feature of the custom driver. The HEX value sent by the device doesn't seem to be correctly transformed to int.
In the example above, I don't understand how 0x003C gets transformed in 30.0, but I might be overlooking something.
This is the value returned by zigbee.getEvent (line 99) at the top of the parse function. The else if battery section further down (lines 127 to 129) is never called.
If I comment out line 99 I can then fall in the else if on line 127 and get a battery value that seems to be more coherent.
Hi All, I returned the Symfonisk remotes I had and then decided I would give it one more go with a new one. I did the latest platform update and paired the new remote and so far the battery life looks like it might be ok. I guess I'll need to wait a couple more days to be sure, so time will tell.
Thanks for that, the IKEA leaflet shows press and hold for greater than 10 seconds, rather than 4 rapid presses, but your method worked, theirs didn't.