Fibaro Smoke stuck on Smoke detected

[thesebastianf]

Hi
I have a Fibaro Smoke Detector.
It did start this morning with a few false Alarms...

I removed the battery and reinserted it.
Now it is silent but still Shows Smoke detected on the zwavejs UI.

I did wake it Up a Couple Times but despite I See it updating other values the Smoke detected stays.

Any hints?

[robertsLando]

@AlCalzone I cannot move the discussion to zwave-js, I think it's a GH bug

[AlCalzone]

@thesebastianf you could try re-interviewing it, but I'm not sure that will help. Smoke alarms "push" changes to the controller and theres usually no way to query the state. By pulling the battery you probably made it forget that it has to send the idle notification.

[thesebastianf]

hey triggering the reinterview caused the smoke sensor to start the alarm again.

or it was pure coincidence that a false alarm was caused within a second after reinterviewing and waking it up.
however this made the detector to also send an idle afterwards.

I used them now a couple of years with openhab and very recently moved to zwavejs.
Is there a possibility that zwavejs resetted setting like sensitivity when the detector was interviewd the first time? I ask because I havent seen false alarm a very long time now (it was also a pain with those fibaros at the start but I got it under control with low sesitivity...)

overall ... I remember why I hated them :D:D:D

[AlCalzone]

You cannot trigger an alarm on a smoke sensor via Z-Wave.

Whats more likely is that your batteries are going bad and the power draw while being awake for a longer time causes the sensor to warn you of low batteries.

Z-Wave JS doesn't reconfigure your devices, aside from making sure they have a proper lifeline to the controller.

[thesebastianf]

no I could see it really was the smoke notification channel and not low batt or something else.

It just felt strange that it did start when startging the reinterview. I know the only flirs detector is the popp one where you can trigger an alarm from the controller.

I thought maybe the "re interview" and wake up I did - triggered some logic on the device itself and it "rediscovered" its own "smoke detected" status was still true and caused it. No clue ...
I do like with the other fibaros I tossed years ago .. a second false alarm the next days and I just dismiss it and look for another device with less flaws :D

[AlCalzone]

Or the sudden power draw causes a fluke in the sensor. Who knows...

[thesebastianf]

btw since I have famous @AlCalzone looking in this thread... is there something you could do to push
https://community.home-assistant.io/t/zwave-js-request-to-invert-covers/303156 at NabuCasa either zwave or core integtration?

Inverting those via template sensors is really a pain as value_template and position_template cannot been set concurrently in a template cover, so HA assumed the cover is open, when position is 100 and cover is closed when position is 0.
sorry for hijacking ... but there a lot of threads around that topic.

[czesiu20]

I noticed the same issue with my Heiman HS1SA-Z Smoke detector. Refreshing and waking up has no effect. Only re-interview allows to restore the idle state.

Additionally strange water sensor appeared:

of which is not available and cannot be removed:

[czesiu20]

After re-interview in Z-Wave JS to MQTT I can see that the device is in the Idle state:

but in the HA interface i can see Smoke detected:

The zwave_js.refresh_value service has no effect.

[AlCalzone]

Sounds like something for https://github.com/home-assistant/core

[thecobra666]

I've also had this. The solution was very easy. Trigger the smoke sensor and let it reset.

[czesiu20]

Great advice. Especially when the reset takes two days and you wonder the house is still there, because u are on vacation. Definitely this is not the case you mentioned. Fortunately, only the device's status is obsolete. The device is working properly, activating sirene and opening the blinds in the case smoke is detected.

[sanderlv]

Same here, had a false alarm and removed the batteries, when reinserting the batteries now stuck:

Any clue on how to get it going again?

[thesebastianf]

The answer is in the Second Post above.
Reinterview