[SOLVED]Warning sound with alarm

[Snaad 1]

Hi guys,

 

Not sure if I can post the right here, but we'll see:)

I'm using a HC2 with Fibaro door sensors and motion sensors and an Aeon Labs siren. Works perfectly, if the sound of the siren doesn;t scare any burglars it will sure as hell make them deaf.

But what I can't seem to figure out, is whether it is possible to first send of a warning sound. Like maybe the first 30 seconds after a sensor is breached that a light beep will sound, in stead of full on blasting the sound of a thousand high pitched baby screams. Anyone got an idea?

Thanks in advance!

[Cafun 13]

Hello Snaad,

I was also looking for a solution for this.

At this moment I sent a turnOn command to the Aeon Labs siren and a turnOff command 250ms later. Then after 2 seconds I send again a turnOn command and turnOff command 250ms later. This will sounds like a beep.

I know this is not optimal, but for now the only solution I have for it.

 

If someone has another solution, please share.

[Wimjanse 15]

Hi

 

I had same issue, but also my wife wanted a small beep when she opened the front door, so she was reminded to deactivate the alarm. As I already had a Raspberry Pi in the switchboard closet (meterkast), I decided to hook-up a piezo buzzer to the Raspberry Pi. I activate the buzzer through some LUA code from a virtual device.

 

So now when the door opens when alarm is activated, the buzzer goes for 30 seconds, and switches off when the alarm is deactivated. I also use it when I activate the alarm, beeping slow for 25 seconds, and then fast during the last 5 seconds, so we know when alarm becomes active.

[Cafun 13]

I think that is a great solution Wim! I also have a Raspberry Pi in the switchboard closet. I've ordered a Piezo buzzer.

 

Can you share your LUA code?

[Sirhideo 9]

I am using an old Android tablet mounted on wall as a TTS engine. if home status is away and the door sensor is breached then the scene trigger the TTS engine with  "warning statment".  After a certain of time or other condition (for example, home status still hasn't changed) my siren starts to make the guy deaf. I can share the code if you like this approach.

Edited October 19, 2017 by Sirhideo

[Cafun 13]

I'm curious in how you did that, can you share the code?

I do have a tablet laying around doing nothing

[Sirhideo 9]

@Cafun You need to install an apk on your android, thanks to @davanha for developing this great app. Mine is running Android 5.0.  Also you may want to setup default TTS language on your android tablet as your native but I do not know whether google supports that.

 

Please login or register to see this link.

Please login or register to see this link.

 

The app is pretty straight forward. You know, you can also connect your tablet with a better bluetooth speaker and I'm sure you will feel good...

 

Once this is done, I use the code also can be found at above post as an agent/middleware/engine or whatever you call (thanks to @RH_Dreambox) to trigger the alarm statement.   Before implement this, create a global called TTS (upper)

 

Please login or register to see this code.

Lastly, I use the below small piece of code to trigger 2 scenes, 1 is the above code to trigger the voice, 2nd is what I want to do after a period of time (60 seconds in my case).  You may want to turn on your siren, lock the room doors, turn on lights etc with the second scene call.  Careful every space in your warning statment you need to meet the html requirement.  I am using Chinese characters so no space in between each word.

 

Please login or register to see this code.

Side note though, I haven't take deep look on google TTS mehanism.  It looks like there is a delay between each parse.  So far 30 seconds interval looks good.  So if you are going to extend the usage of the TTS engine code you will need to pay attention if you want to send multiple messages with different scenes to it Say I have a hourly time report scene but I cannot send two message at 10:00 to TTS engine scene because google cannot handle it.

 

 

Edited October 20, 2017 by Sirhideo

[Cafun 13]

@

Please login or register to see this link.

 Thanks! I'll try it.

[Wimjanse 15]

@Cafun / others

 

Herewith attached my solution on how to activate / stop a piëzo-buzzer from a HC2, using a Raspberry Pi as intermediate.

 

In case of any questions on this, don't hesitate to ask.

 

Have fun,

Wim

 

 

Please login or register to see this attachment.

[Cafun 13]

Thanks Wim!

 

@Snaad: Hope you have enough examples here that work for you.

[Snaad 1]

Guys, this is more than I expected:) I'm gonna try these examples, I'm not really familiar with Raspberry Pi or the TTS engine, I'll let you know how this is going to work out. 

Thanks a million @Wimjanse, @Sirhideo and @Cafun! Really appreciate it!

[play3man 5]

@cafun Hi, how did you set command in ms? Is it only possible with HC2? And is possible to change or sete dB with/for scene?

Edited January 24, 2018 by play3man

[Wimjanse 15]

Look into the attachment to my earlier posting, you see the amount of ms that i use to on/off the piezo. And no, besides this you cannot control dB of a piezo, its a simple on/off device.

 

[Cafun 13]

19 hours ago, play3man said:

@cafun Hi, how did you set command in ms? Is it only possible with HC2? And is possible to change or sete dB with/for scene?

 

What Wim said

[petergebruers 1,268]

14 hours ago, Wimjanse said:

Look into the attachment to my earlier posting, you see the amount of ms that i use to on/off the piezo. And no, besides this you cannot control dB of a piezo, its a simple on/off device.

 

 

Thank you for sharing your solution. Nice document!

 

Can I add something regarding "piezo" devices, but often also called "buzzers"? They actually come in at least three categories: the one you mentioned, a cavity containing a piezo or magnetic assembly plus a driver. Drivers can be 3 V but also 5 or 12 (and higher) with some tolerance. So you power them and the driver makes the piezo vibrate at a particular frequency and this makes them very loud. The second type is simply a piezo, but with no driver, they often are sold as disks with a metalized surface but they can look exactly like the first type too! You'll have to add some driver, most likely a coil and a transistor, to get high voltage. Still basically only on/off, because the cavity or disk resonates at a particular frequency (but you can modulate them, to make chirping sounds). The third type is like a speaker in a cavity, but typically with a higher impedance than a traditional speaker and a limited frequency response. Could be 16 or 48 ohm for instance. These have a resonance peak as well, but it is wider than the first type. They do not have a driver, so you have too feed them a square wave, for instance 3 or 4 kHz. So here you can get a limited set of tones, but one of them will be loudest. Again, they can look exactly like the other types (small black "can")...

 

So to summarize... please check the datasheet thoroughly before you order one!

[Wimjanse 15]

Hi @petergebruers

thanks for the explanation on “buzzers”/piezo devices, I did not know that there are different devices with the same name.

But this explains, because originally I had ordered two different kinds with Conrad, and one kind I couldn’t get working with my Raspberry, while the other I could switch on/off easily by just connecting to a GPIO pin on the RasPi.

Thanks again for the further clarification