Have just ordered one of these sensors to have a play with.
Thank you for all your efforts in publishing this info so others can use it.
Rick
The NullPointerExceptions disappeared from the logs with the new update, but the same problem does persist. It seems the device is only able to report the values in the first 5-10 minutes and even then does so only if I ask to refresh the value. Very odd behaviour.
.
That’s definitely not what my device does. It floods my hub with data on every single change in raw data since the first day I got it. I’ll post a live log shortly.
This was just for 1 minute!
I have another one coming soon, so I’ll see how that new device behaves. I’d still keep trying to remove and rejoin your device, or at least hold down the button to start the reset and join process on the device while going through the adding a new device process.
EDIT: Just as another data point, I’ve had 170 raw data values sent from the senor since I posted that image.
Please go back into settings and change the first parameter to 15 and the second to 20. Tap on Save if using the Classic app. Let me know what live logging says.
.
That’s the basic cluster and model identifier. That should definitely NOT be unknown because that’s bound during the configuration process of the device when it joins.
That tells me the sensor didn’t complete the join process successfully. You can try and force the configuration again by one of a couple ways I’ve seen work:
- tap on the Configure tile in the Classic app, and then immediately press the button on the sensor
or - press the button on the sensor and immediately tap on the Configure tile in the Classic app.
I recommend being within close proximity of the hub, or maybe another zigbee repeater.
Very true. For some people it joined correctly right away, and others it took a few attempts.
Are you using my latest DTH? Those live log debug messages are normally commented out, unless you’ve removed the “//” from line 61. I just want to make sure you’re using the latest.
My understanding is that it uses the new zigbee 3.0, will be interesting to see if these suffer from the same drop off as the previous versions of other devices.
So far they’ve been rock solid.
Amazing 
Go into settings and manually type in the default values, like 10 and 21. It doesn’t matter because the sensor doesn’t seem to honor those settings. I may just eliminate that altogether since it causes more problems than it’s worth.
It works for one of my sensors and the other works after I removed the battery cover and put the battery back in…anyways thank you for your advice and the great DTH!
My light sensor is working without any connection problem since the installation 2 week ago, are the problems related to the new firmware? I didn’t upgrade my firmware, still using 000.030.00005, now struggling whether to upgrade firmware.
No it was something else on ST’s end that was causing these issues. Since this sensor doesn’t seem to honor those attributes, I’ve removed the preferences again so it won’t cause others any issues.
You really have no choice. The hub’s firmware is pushed out by SmartThings. You can’t stop it, or schedule it for another date/time.
I see, thanks.
By the way, I would like to ask how can I change the main tile to display lux rather than the battery level?
Oh now that’s interesting. In the new app, I don’t see that. I just get “Checking status” instead of what you see. I may need to switch DTH’s and then back to get that to work right. I pretty much use the Classic app, so that never bothered me. To get that to change, the DTH’s metadata needs to recognize ocfDeviceType: “oic.r.sensor.illuminance”. That’s actually already documented within ST’s documentation, but it’s not working.
I thought you’d find this interesting regarding how the new app inconsistently displays this device (heck, almost any device for that matter):
I have 2 of these sensors, and here’s how they look on 2 different devices:
Sensor #1
Sensor #2
Same DTH, different results. There’s nothing I can do to fix that.
FYI @blake.arnold