So I’ve had a white label Monoprice smoke detector (made by Vision) setup for a while with no issues. Seems to be working fine. I just recently purchased a bunch (seven) First Alert ZCombo smoke/CO detectors.
They all added without any problems, but they all added in as Tripped. During this process I also hit the test button on the Vision and it too changed to Tripped. A few hours later and they were all still Tripped. I haven’t tested the Vision one recently and honestly don’t remember if it Untrips itself or not. So anyway I manually set them all to Tripped = 0.
Does anyone know if they are supposed to Untrip themselves?
The problem is that over the next 90 minutes or so all of the First Alerts were back as Tripped. I again set Tripped = 0 and within 90 minutes they were all Tripped.
Since I manually Untripped the Vision one it has been fine. I’m on firmware version 1.7.690.
Anyone have any tips or ideas about what I can do to troubleshoot this?
I have 4 of these installed and yes they do un-trip automatically if the “AutoUntrip” value is set, mine (by default) is set at 60 which I assume means 60 seconds. Did yours also include in the armed state…?
I did not add the “AutoUntrip” variable, did you use the built in installer wizard for the First Alert Combo or did you include them as a generic device…?
Hmz. Today I submitted a ticket to vera for my fibaro V2 Smoke detectors. One of them suddenly beeped like hell. No fire, no smoke. Changed the battery and all was gone. Strange thing is I had changed 3 batteries for 3 detectors all a while ago and all were new. 2 remaining are still full… and according to the smoke detector the other 1 was also still full…
Leaving me with an uncertain situation about what caused the fire alarm trigger…
Best Home Automation shopping experience. Shop at Ezlo!