Many thanks -- that all makes good sense! I have a few errands to knock out this afternoon, but I try that line change later today and then keep you posted after running with it for a while.
Thanks again!!
Alrighty, that line 437 change looks great so far -- with regular Info logging enabled, now initiating a Refresh yields the desired 2 log events for Smoke & CO status:
But you were right about Last Activity At... Although I'd never noticed it before, doing a Refresh (even before making that line 437 change) does indeed update that timestamp.
Anyway, it's reaffirming warm-fuzzy (even if not totally necessary) to see those log results when I do Refresh -- this is perfect -- thank you!!
Oh, and I'll keep a particular eye on the logs for the next several days to see if there's any unanticipated chattiness or other such weirdness.
This is why I placed mine next to my SC7010BV in the hallway. Apparently Costco finally carries it, at least on there web site but that model does not have a 10 year battery as claimed. Next time at Costco I will see what that carry but a month ago it was only battery powered one that were not wired.
Wired interconnect is required on a new builds these days. It started in Boston over a decade ago and is now required many places. It is very easy to install when have access, like most wiring. Wire does not die, you can go through 10 battery power units and the wires are still there. They do not die if you forget to change the batteries.
I have never seen a hardwired unit with a 10 year battery. I could only find the same SC7010BV that I have on their website and it does not have a 10 year battery. My CO only detector I have next to the furnace is a 10 year battery model but no interconnect. They usually have either a battery or are hardwired. If you can post the model number I will get them. Mine are not due to be changed until 2025 but this is such a rare model I need one.
Meanwhile, Costco sells a wired or battery Nest 2-pack and both "Requires Wifi 2.4GHz Connection". According to Wikipedia "Thread is an IPv6-based, low-power mesh networking technology for Internet of things products" "(on the 2.4 GHz spectrum)". "It uses 6LoWPAN"
I just know the one I bought required WiFi which refused to use my LAN. It did require it and NOT just to connect to each other.
According to Google, most recent code consider wired and wireless interconnect to be equal and there are no state building codes that require wired interconnect.
Home Depot has several models
https://www.homedepot.com/p/Kidde-10-Year-Worry-Free-Hardwired-Combination-Smoke-and-Carbon-Monoxide-Detector-with-Voice-Alarm-and-Ambient-Light-Ring-21029893/305261308
Requires WiFi to set up. But not to work as a detector or to interconnect.
1 Like
Not here in PA. Wired or wireless interconnect is acceptable.
The nest battery version claims 10 year life,, their hard wired version claims 10 year for backup (which generally makes sense since it's hardwired)
It uses bluetooth and wifi to onboard to the nest app, after that it's local. It uses 802.15.4 at 2.4 GHz for the interconnect which doesn't require wifi itself. (you can turn off all the wifi in your home and it still works just fine). The only time it uses lan is when it notifies the app on your phone.
1 Like
firmware version 1.30 is out - supposed to fix the appearance of falling of the network like mine does.. i will flash it soon.. but I cant get it to respond right now since its "fallen" off the network 
Firmware: 1.30 (released 11/2023 as OTA)
- Addressed issues with the DC Signal Sensor occasionally showing offline or becoming unresponsive on select platforms.
I updated a few days ago (went fine), but I didn't have any falling-off issues previously (well, that I'm aware of anyway!)
Mine's always been paired S2 -- no idea if that matters or not.
The update for the Z38 extender has the same release notes, so must be same bug they're squashing there too.
1 Like
Is that before even starting? Can you power cycle the device and hub?
Or try the drivr version of the updater. Z-wave S2 device - how to (maybe!) update firmware with HE It says the directions are for S2 but could for any security.
1 Like
I did the 1.3 update over the past weekend no problem (was and still am using Jeff's driver).
I used the steps in the post Jeff linked above since my ZW stuff is all S2, but those steps should work just fine with no-security devices too.
I'm not using security.
Won't the built in app work with no security?
I've updated several other Zooz devices with it.
It should. But I haven't used it in a long time, so I don't have any recent experience to compare.
Yes, it should, but the driver may work since the built in does not seem to want to.
I have no idea what the problem is, I am just giving suggestions of possible solutions.
It's got 8 pending changes.
I thought this was acting okay, but I didn't check test the smoke detectors for a while.
Then, I see the post above, and though updating firmware wasn't a bad idea.
Oy.
I forgot which box I put it in.
Sounds like you may have experienced the issue which that the firmware update fixes! Falling off the network. Check the "last activity" a the bottom of the device page, although I think possibly doing a configure might mess with that which I assume you did, to get the pending changes message,
Yeah, I did something, refresh or configure, that put a new date there.
How do I recover?
edit: For something that's smoke detector related, you'd think reliability would be a priority, geesh.
Did you try to power cycle it yet? That would be step 1.
If that does not work I assume you need to pair it again, either try to exclude and include or factory reset it and do a z-wave replace to get it back into the same node. If you try the exclude and it does not remove the device from the hub, the replace would be your best bet to avoid creating a ghost.
I just tried that while you were typing.
That did it; it's synced.
It's now updating.
It could've been off line for months.
Geesh. Another reason to regularly test the smokes.
Get this app, problem solved. I would have been notified within 24hrs if the device did not respond to the hub. My drivers are specifically coded to work well with that app and only post events if the device responds (the only exception is if you press configure).
