Device ID are not necessarily unique about hue-sensors-hass

[sevenofnine-jni]

I see that you have found the problem. Is there anything I can do to help?

[robmarkcole]

Yes you can help, as we need to identify a unique device ID that can be used. You will see that Hue represents a single SML motion sensor (henceforth referred to as the parent sensor) as a group of three child sensors (motion, light level, temperature) each of which has as uniqueid. I had observed that characters 0-5 in the final set in uniqueid separated by : , appeared to link the three child sensors, so use those characters as the key to group them to the parent sensor. Clearly those 5 characters are not unique to a single parent sensor, so we need to identify the correct way of generating a key to associated child to parent sensors.

The alternative is just to treat each child sensor as a unique sensor, and leave it to the user to group them in HA.

[sevenofnine-jni]

If you use this part of the id 00:17:88:01:02:13:db:2e it seems to be unique? And also able to link them to the parent.

[sevenofnine-jni]

I broke out all sensors from my api responce and formated the text to easily see the id's and as far as I can see it is possible to use the part of the id I stated above. See this pastebin. https://pastebin.com/1z77Ba14

[point-4ward]

Wrong issue: comment moved

[sevenofnine-jni]

Or why not use the complete unique id? All three child sensors share the same uniqueid except for the very last 4 digits that is stating what kind of sensor it is. 0400 = light, 0402 = temp and 0406 is motion.

[robmarkcole]

OK fixed in 9b388de and release v0.4, thanks!

[sevenofnine-jni]

Works great now. Thanks for the fix.