Popp Smoke Detector and Siren

You’ll have realized I was prodding for a clue. I know nothing about these things, but it would be reasonable if the device had two siren switch channels; one that made the fire alarm noise (and could be triggered by other sensors) and one that made the generic warble noise (e.g from your doorbell).

1 Like

Exactly that is the case. It’s intended by the manufacturer!

@chris

I renamed my item names!

Now, everything seems to be OK.

image

As I’ve mentioned before, the binding doesn’t know about items, so I doubt that the names will be the issue here. So long as the items types are matched to the channel types, this should be fine…

Anyway, if it’s now working, then I guess that’s the main thing.

1 Like

Thanks a lot for all your help and patience. :slight_smile:

But I’m going to do further investigations.

I’ll keep you informed when I found out the exact reason…

1 Like

@chris

Here are my results of further investigations:

Event sensor_binary switch_binary triggered?
Smoke detection yes no
Low battery (= 0 %) yes no
Siren switched ON manually yes yes
.
.
Neither in the product manual nor the Popp support (still waiting for an answer) explain this behavior.
.
As you can see in above table, sensor_binary always is triggerd by different events and is set to ON. After the event ended, sensor_binary automatically returns to OFF.

My mistake was assuming that when the siren is turned ON (by switching it ON) the sensor_binary will not be triggered. I assumed that switching ON the siren is NOT an alarm in the true sense.

After finding out, I was able to adjust my rules. :slight_smile:

1 Like

Thanks @Celaeno1.

Do you mind adding this to the database? There is a Usage Information section for exactly this sort of thing and I think it would really be good to add this there. It will then automatically be added to the openHAB documentation so it’s not lost somewhere in the forum.

1 Like

@chris

No, I do not mind. But I first have to read your Database Guide.

Not too much to read for this - just create a user account, if you don’t have one, then let me know so I can update your access to allow you to edit the database. Then you will have some edit buttons - click the one in the top right -:

image

and update the usage information -:
image

You can use the formatting taskbar to create tables if you like, and then it should be formatted nicely when it gets exported to the documentation.

Thanks :+1:

1 Like

I have updated your account :slight_smile:

1 Like

Thanks a lot.

Unfortunately today I have no time to edit it. But I’m going to do it tomorow.

1 Like

No problem at all - thanks.

1 Like

@HomeAutomation How does your rule with these POP smokedetectors look like?

Which rule do you mean? Notification when battery is empty?

@Celaeno1 I would also be interested in your low battery rule if it triggers with the sensor binary… :wink:

I have such a rule, but unfortunately it makes no sense. You will hear the smoke sensor beeping long before it is getting triggered.

But I could post it here if you like.

rule "Batterie-Alarm bei Popp WZ ist 0"
	when 
		Item POPP_Smoke_2_Battery changed from 100 to 0
	then
		sendBroadcastNotification("Batterie im Wohnzimmer ist leer")
end

Yes thanks and the rule when the alarm goes off?

@Celaeno1 Thank you for sharing. I thgought you get some more battery values now by combining it using a “sensor_binary” channel rather than just 100 and 0.

No, they are UNDEF, 100 or 0. That’s it.

See also this post.

Done :grinning:

1 Like