I wonder if the 12 hour window after a command impacts the chatty behavior too? My sensor goes through periods of quiet alternating with periods of endless banter.
Would you please ask if the sensitivity can be set? I'm sitting about five feet in front of one and I have to wave my arms frantically to get it to trigger.
Most of the time I like the pet aware sensitivity of some sensors. In this case I am looking more for the sensitivity of an Iris V2. If it can't be configured then I don't mind that much but it would be good to have the manufacturer state what to expect. It seems to be a narrow detection cone with low sensitivity -- or did I just get a bad device?
Just shoot a message to support there and they're really responsive.
Ah, I thought you had an unofficial contact with them. I'll check out the support pages. Thanks
1 Like
I sent them a support request on Monday about my problem with the motion detection. I have not received any response from them. I am going to uninstall and return to Amazon when I get the time
I really want this to work, but I am quickly approaching this point. In addition to chattiness, I have observed a failure rate of about 20% in setting the appropriate light level. The device page reports as expected, so the physical light is intermittently failing to perform.
I was also getting alerts in the logs about the Location Events logs for”spammyDevices” saying it’s producing hundreds of events.
I’ve updated the firmware and that has sorta stopped for a few days.
But I had another oddity start up right after. The device would turn on the light from motion without a rule or anything.
Hitting “Configure” seemed to have made that stop for the mean time.
Only thing I don’t like now is that from the Device Page you can only adjust the light properties, not motion or Lux.
Check several posts up in this thread. Sending commands to the light will disable the auto on/off for 12 hours. Seems to be a feature. Note the bolded text.
Was this firmware update issue ever solved (obviously, not solved, but maybe a workaround)? I just got one of these. It's on the version shown. There's an update to 48, but it won't work as shown below.... just keeps "starting"
- endpointId: 01
- application: 3C
- firmwareMT: 130D-0000-0000003C
- manufacturer: Third Reality, Inc
- model: 3RSNL02043Z
- softwareBuild: v0.00.60
I don't know if it was ever resolved. I never ended up using the device as planned. It just didn't have the coverage I was looking for and I never got a response on how the detection cone was setup (like the motion sensors show).
I have been thinking about using the nightlight functionality for another project but haven't moved it to the new hub yet.
Long shot but you could try re-pairing the device(w/o removing it) right next to the hub, then try the firmware update
Thanks for the suggestion. Tried this and a few other things. No luck yet. I've posted in Third Reality support forum to see if I can find any answers there.
2 Likes
I have the device on a C8p and clicking on Update does nothing. I can see regular events in the logs but if I try to update the firmware from the device page nothing is logged. I don't even get the "unable to update device" message.
What hub and firmware are you running? I'm on a C8p with 2.3.9.150.
I'm on C8p on 2.3.9.150 as well. This also happens to me on some attempts. I think I only get the multiple attempts after a re-pair of the night light or a power cycle of the hub.
No additional help yet from Third Reality support site. Here's the link if anyone wants to add on to see if we can get more attention on it (thanks @wiegout):
1 Like
Worth a try. It seems like such a cool device if it worked... Other Third Reality devices are really good. And I updated the firmware on a Zigbee Smart Plug of theirs just yesterday and it went smooth as can be. This night light though...
Yeah, typically have a good experience with their products as well. The fact that the device settings don't allow you to prevent the light from turning on automatically for motion at night is a huge miss... a bit of a dumb smart device.
There isn't a setting but if you control the light directly it will disable the nightlight for 12 hours. Playing around with the driver I see that if you change the hue it changes but doesn't turn on the light, The next time you turn it on it is at the new hue.
So I just setup a simple rule to test if this is enough to keep it from activating.
It runs three times a day. Samples the current hue and tells the device to set that hue. This way if it is on it won't change color. Two things: I don't know if just setting the hue is enough to keep it from going back to auto mode. Even if that works I don't know if setting it to the current value will work.
At this point I won't know until tomorrow if it works. I suppose a good test would be to leave the rule off and wait for it to go into auto mode. Then wait for the light to turn off, set the hue in the driver, and then trigger the motion sensor. I think I'll left the rule off for now and wait for the light to reset and do the manual test.
You can manually turn off the local routine with a short press of the reset button. Short press with a green light means the local routine is on. Short press with a red light means the local routine is disabled.
Also, the local routine is for folks who buy this device but never connect it to a hub. It works as a motion sensing nightlight automatically.
Ah yes, I forgot about the reset button toggle. Even if you have it turned off it comes back on if you don't trigger it for 12 hours (or there about). That's what triggered the rule above.
Thank you! I suppose this info was in the user manual, but I guess I'm not accustomed to reading those and expect the ability to control the features of a smart device from the device settings. For those who have also disposed of the instruction manual, the link on Third Reality manuals site is broken, but I extrapolated the location from the other links, and you can find it here:
