If its garbage with CRC errors the hub just drops it, usually the network ID is not even right so the hub would think its not meant for its mesh. But the radio still has to deal with it. You wont see anything in the ZIP zwave logs. Not sure if Zwave JS would log it or not.
Its like a self inflicted DoS attack on zwave.
Here's the latest. The network has been stable since I removed the Ecolink from the network yesterday.
I think the siren is defective. Today I did a factory reset on it - that behaved as expected. But now it appears bricked. Action Button should put it in pairing mode - but nothing. No button pushes seem to do anything.
I miss my Aeon siren - too bad the battery swelled up and broke the siren apart. Hate their new one because it has a separate plug - that's how I ended up with this Ecolink. ~sigh
Update on Z-Wave logs. I do see logs - but only when devices are switched on or off by HE. There do not appear to be any status-type messages.
Again - I want to say you guys, this whole community, ROCKS! It is so nice that not only Hubitat staff, but also a lot of really smart folks jump in here and help people. TYVM!
Correct, on ZIP those logs are nearly useless.
If you need a new device, might want to check out the newish Zooz ZSE50:
Yeah, those came out in August. I bought the Ecolink in July. If I only knew it was coming.
On a new note. I heard back from Ecolink. Fix action for factory reset failed - well isn't pretty. Have to either wait for battery do drain OR pop the face off and DX the battery then plug in and factory reset again. WELLLLL....
I learned the "face" has two layers, the metal screen part and that is glued to the plastic body face. It is the latter, obviously, that I needed to take off - wish I knew that.
The plastic face has two "snaps" on each side that have to be pushed to release (from inside) AND they were also glued! I only broke one.
After getting it apart - factory reset did NOT work. Did a general exclusion after that and the unknown device was removed and magically the siren went back into pairing mode. Yes, I had excluded it several times yesterday - I even tried using ZW stick to no avail. Oh well.
I was able to add it back into SS and it paired in about 2-3 minutes. Has single hop to hub and nothing "wonky" in logs or ZW logs. Maybe it is fixed. IDK - but I just ordered 3 ZSE50 to replace my 3 mis-matched sirens. Too fun.
Thats normal, the first log from a device will show like that then the next ones after that will have the device. Known issue with the ZIP logs.
Something is finally normal for me, lol.
