It will start up again until you manually change the light. Then it will be off for another 12 hours. If you get multiple notifications a day then you don’t have to worry about the nightlight.
In my case I use it to remind me to take my meds in the morning so it only comes on manually once a day. I have a button I hit after I take the meds. In the evening if it starts doing the auto nightlight I just hit the button again.
OK, cool, that's very manageable. I can set up a rule to toggle the lights at 2am and 2pm, that way I should stay on the 12h cycle and block the local routine coming back to life.
I tried playing with sending it the same state it was in so it wouldn’t change t he notification status. It didn’t work unless I sent it different values. I figured you could read the setting, change it to something else, and then change it back. It was worth the effort for me but it should work.
The Matter version is just as chatty with its Lux but does not have the local routine attached to it like the Zigbee one.
With the Zigbee and updates, @rlithgow1 has some background. Early firmware versions need third reality’s Zigbee hub for updating. I’m not sure if that has changed.
It is in the upper 5% of my Zigbee devices. Presence sensors that check-in every 10s are around 85k messages in that same time. The part that annoys me about the Nightlight is that those messages are low-value information. The C8-Pro connects directly to most of my devices, so I don't even realize any benefit from it supposedly being a prolific repeater.
I have two of the Zigbee version. Mine are not chatty, but their locations don't have much light variance. I appreciate the information about the Local Routine, which is annoying that it cannot be disabled permanently. (It explains some observations.) Now I use it similarly to others: colors to display statuses (red = doors unlocked; orange = doors open or delivery outside; yellow = windows or closet doors open; magenta = camera motion). Those should fire often enough to prevent the Local Routine.
It would be nice to see if the newer firmware was less chatty.
That's the problem I have -- The light levels aren't changing but it still constantly bounces between two values. In the logs I posted previously you can see the lux value change between 4 and 7 serval times over the span of one minute.
This behavior seems to come and go over the day. The device works well enough, but I won't add any more of them. No need to clog the mesh with unneeded messages.
Just a quick update - received and installed two of the Matter versions of this today. Both installed quickly/easily into Third Reality Matter app (they currently have a separate app for Matter devices). Added them to HE and to Google Home (where they show up as three divices, Presence, Lux, and Light) using pairing code from 3R Matter app. Quick and easy.
Was interesting to see they have a separate app for the Matter devices at this point, from a message during the process sounds like they intend to roll all the Matter functionality
back into their main app in the future.
Both are showing same FW version and reporting up to date: 1.00.51. So glad to not see any FW update/version issues (yet).
Haven't done anything w/them so far, need to set up some rules to turn on the light red when doors are open. I do notice that neither responds to motion in front of the sensor at this point, other than reporting active/presence dectected. I'm fine w/that if it sticks, as I don't want/need the nightlight function. Seems more likely that it's going to stay that way for 12 hrs and then the motion/nightlight stuff will start happening...so I'll end up setting up a regular "touch" to keep the motion sensing light off.
One odd thing - until I had turned the light on the device on and off again at least once, the devices didn't populate State info and provide "On/Off" combined buttons on the Device page in HE. Also didn't have any entries in Default Current State drop-down on device Prefernces tab.
Before turning on/off: Separate on/off tiles and Current States was empty, as well as Default Current State (forgot to grab a copy of those two):
The overall initial feeling is easy setup (aside from the initial states info), build quality seems good, positive first impression. They don't seem very chatty yet, but will wait and see how that goes over time.
The next platform being beta tested right now has a possible fix for the issue with this devices original firmware (0030) not be able to OTA update. So hopefully you can update once that comes out.
At this point I kind of wish I had gotten the four pack as well.
I'm deploying the two I have to warn us of open doors when we're leaving the house. One in the utility room and one by the main entryway. Those are the two ways we leave the home and the red (but it turns out it looks purple) light will be on if any of the other doors are open. Light is very noticeable, hard to miss, which I like.
So I have one of the Zigbee model but have not messed with it much. Does it use the light sensor to turn the night light on and off by itself at all? Or is that just up to the user to automate if they want?
Seems more like a multi-sensor with an indicator light than a night light IMO.
The two and four packs are still at their Black Friday pricing.
The local routine only applies to the Zigbee version. The Matter version does not have it.
Yes. On the Zigbee version, this is automatically built-in the sensor. The user can still automate them if desired. Any automation by the user causing the light to come on will disable the built-in routine for 12 hours.
It's the Lux readings that can get chatty. Everything else is normal (at least from my experience).