Alarm when opening the door contact
I would like to integrate several door contacts via LoRaWan because we currently have several cases of property damage.
My idea:
A door contact opener is opened – notification by email /SMS to the registered recipient.
At the same time, however, a siren and a signal light should be activated as a deterrent.
I would do this with a rule. (If door contact opens, then notification receiver and alarm output for 45 seconds)
Has anyone ever implemented such a USE case?
I haven’t found a siren yet that I can integrate directly into LoRaWan. A lamp/siren combination would be best.
- 3 Replies
Hello Lukas,
exciting use case, even if it’s sad that you need solutions for it at all. Have you made any further progress here? If not, here’s a first idea I’d like to try:
Existing socket(s) with a smart plug (such as this one: https://iot.zenner.shop/en/nke-WATTECO-Smart-Plug-LoRaWAN-Radio-Socket-p-170791) to the radio-controlled socket convert and connect and control “signal light” and “siren” to it. As a result, they do not necessarily have to support LoRawAN and it may be a little easier to find suitable devices for it or one that can do both. Then store appropriate rules via the RuleEngine in the B.One Middleware, which sends a downlink to the radio-controlled socket with the appropriate command when it is opened (possibly simply power on when opening and power off when closing).
How does that sound to you? Like I said, I’d just give it a try. Let’s see what comes out of it in the end 🙂
Best regards
Michael
Good morning,
no, we haven’t got any further yet, it’s still in the planning stage.
I had also considered the solution with the sockets, but rejected the fact that the siren would be relatively easy to put out of operation.
Hello Lukas, the idea that the whole thing no longer works when the power is switched off is of course correct. But you would have the same problem with a LoraWan solution. In order for the “alarm” to go off promptly, you would have to use a Class C solution, which is usually not a battery solution. But if you use a Class A solution, your “visit” may have gone by the time the node reports again and the subsequent downlink turns on your siren. BTW I think it’s a very bad idea to plan “siren ON” and “siren OFF” as 2 commands, if for whatever reason the 2nd command to turn off doesn’t come on, it can cause real trouble. If so, you should provide it with an automatic switch-off (called PulseTime by Tasmota).