Has anybody seen any documentation on the sensitivity and detection cone for the Third Reality Multi-Function Night Light? I have an unusual mounting location and the detection hasn't been as good as I had hoped.
As I'm typing this I have been waving at it. It looks like the cone may be acceptable. It might be the sensitivity. One hand doesn't seem to trigger it. I'll continue to experiment with it but it would be know where to set the expectations.
A wave of the hand does trigger mine.
I’m sure it works great. I’m just trying to find the best angle for mounting it. For example, the motion sensor behaves differently if you mount it upside down.
I would like to find a similar description of how the nightlight works.
Merry Christmas To All !
I received a third reality nightlight today, got it all setup and it all of the functions seem to be working (motion, luminescence, switch). Two things I noticed that I’m wondering if anyone has experience with is, sometimes when I change the color of the RGB light, the light turns off. The device still reports it as on but I have to either press “on” again or press “set color” again and it will come back on and set the correct color.
The other thing I noticed is that the “flash” function does not work. If I press flash when the led is on, nothing happens. If I press flash when the led is off the led will come on dim but not flash.
has anyone else experienced the same issues?
The firmware of the nightlight is 130D-0000-00000032
And
The software of the nightlight is v0.00.50
Thank you all and happy new year!
I also have both of these problems. It turning itself off for color change is a huge usability issue. Turning it on when it's already on also has the same issue (turns off while reporting on), so it's hard to work around.
I just got one and it has .60 software with firmwareMT: 130D-0000-0000003C. I also see the issue with both the device page on button seeming to toggle but the switch always reporting ON and the set color button also toggling while switch remains ON.
I have a routine to turn on the light on motion and set the color or level based on mode. What I would like is in mode night the color to come on as RED but what I get for the first instance during this mode is the light coming up as white and then switching to red. Setting the color before turning on does not seem to work.
I'm experiencing the same problem. Firmware is 130D-0000-0000003C and software is v0.00.60.
Discovered a work-around of sorts. If subsequent setColor calls change all three parameters (hue, saturation, level), then the device changes colors successfully. (It still suffers from "on" toggling the device.) After defining my colors to have saturation/levels like 100, 99, 98, etc., my rules are behaving properly. A hack, but usable.
I have 2 of these, one matter and one Zigbee. Had something unusual going on on the Zigbee one.
I don't use the built in motion detect due to it's location and a small dog. I have a separate motion detector to trigger it only at night. It has worked fine for over a month.
Yesterday I had the power shut off for a few minutes while I replaced an outlet, not the one the unit is plugged into but on the same circuit. After the power came back on the night light lit up, which is to be expected. I shut it off but a few minutes later it came back on. Did this off and on all afternoon. I cannot find any reason for that. Nothing in the logs or events. Finally stopped late evening.
It's no big deal, but wondering if anyone had any idea as to why it would do that.
After cutting/restoring power, perhaps it re-entered the "Local Routine" mode. This causes it to act as automatic night light (low light + motion = on). If you manually adjust the light, it will stop this behavior. (As well, you need to adjust it every 12 hours, or it will return to that mode again.)
I was not aware of that. So as long as I do something with the light, turn on/off, set color, etc. it will stay out of that mode?
EDIT: Found the manual where it talks about pushing the button thru the little hole to turn this on/off. If I turn it off that way will it then be permently off?
Unfortunately, the button only disables it temporarily (for 12 hours). As you mentioned, you'll must do something else (toggle on/off, set color) every 12 hours or so to keep the mode from reactivating.
Man, I am having a heckuva time wresting with the setColor custom action in Rule Machine -- I feel ike I have tried every possible combination of entries, but still no joy...
Any chance you can post a screenshot of a successful setColor custom-action setup from one of your rules? Many thanks in advance!
Unfortunately, I can't help with Rule Machine, as I've never used it. I use my own app for all my automations. It makes the standard setColor() call with a map as the input. The map has keys of hue, saturation, and level ... all values are integers. As other have noted in different threads, red can be an issue.
OK, thanks - that gives me one idea to try, so I appreciate it! 
some devices do not support every color.. could it be if the color is not supported it just shuts off.. i know the hsm 200 i think i have will set a color but not the color you specify if passed a color it does not support..
I actually had red working for months ... and then it stopped working via setColor. No changes on my side. Gremlins!
I ended up setting these desired color-alert options by simply treating it a color bulb - that seems to work great so far... Should've just thought of that to begin with! 
I have no plans to use Red, but I'll remember that may be thorny if I change my mind.
Thanks again!
Download the Hubitat app
