[RELEASE] Aeon Labs Aeotec Doorbell

Got it working. Figured out the right github path.

1 Like

[quote=“dperschonok, post:12, topic:39166”]
This guide also shows you how to update apps and devices once they are in your IDE.
[/quote]Thanks again for helping me get my repository configured correctly and for providing the information on how to link it. I’ve wanted to be able to update Rule Machine this way for a while, but I didn’t know how.

That should do the trick :slight_smile:

When I made that comment, I meant that with what you posted the first time, I was able to setup RM which is something I had wanted to do for a while. Thanks anyways for the additional information.

1 Like

Hello Kevin,

Huge thanks for this! I can select the doorbell as a speech device. But when I do this, I don’t hear any sound using TTS. If I switch back to my Samsung speaker, it works. Is it normal?

LJ

[quote=“Luvien, post:17, topic:39166”]
I can select the doorbell as a speech device. But when I do this, I don’t hear any sound using TTS.
[/quote] The device handler in the first post of this topic doesn’t support the Speech or Music Player capabilities.

I wanted to get a DH for this doorbell published, but since I’m unable to fully implement those capabilities with this device, ST would have most likely automatically rejected my submission which is why I have 2 versions.

My other device handler, the Aeon Labs Multifunction Doorbell supports the Speech capability, but it can’t be used as a true speech device.

The Aeon Labs Doorbell allows you to store up to 100, 20 Second mp3 files and all the Speech capability allows you to do is specify a track number to play. If the message is anything other than a number between 1-100, the speech command will be ignored.

There are some free online websites that allow you to generate speech based mp3 files so that’s what a lot of people are doing with these Device Handlers.

In order to use the custom commands in the DH listed in the first post of this topic, you need to use an app that supports custom commands, like Rule Machine. If you want to be able to play track numbers using the Speech or Music Player capabilities, you need to use the other device handler I mentioned.

Kevin,

Thank you for the well detailed post. I will use my Samsung R5 for on the fly TTS and the doorbell to play mp3. Do you have a suggestion for the best website that can do mp3 in english and french? I don’t care if I have to pay, I just want something easy.

Thanks!

LJ

[quote=“Luvien, post:19, topic:39166”]
Do you have a suggestion for the best website that can do mp3 in english and french? I don’t care if I have to pay, I just want something easy.
[/quote]I’ve tried a lot of them and my favorite is IVONA, it’s fairly simple to extract the mp3s from the example page, but it’s technically a paid site so I can’t go into detail due to SmartThings TOS.

Remember to add some silence to the end of the tracks or they’ll end up getting cutoff.

1 Like

Does anyone have any idea as to y the doorbell just seems to be turning it self off? It was working perfectly for months… Then recently people come to my door push bell and nothing happens… Then if I go to speak to press button on it, bell will ring when pressed… But then it just stops working again?

I can’t seem to figure out y.

I haven’t heard of that happening to anyone else, but here are some ideas:

The button can be finicky so if you didn’t test it yourself before pressing the button on the speaker, it’s possible that it didn’t work because of the way they pushed it.

That’s not an excuse, a doorbell button should just work no matter how it’s pressed, but it’s a common problem with this device.

If it happens again, you should try the button yourself and if it doesn’t work, then try the doorbell button in the mobile app. If the physical button doesn’t work, but the one int he mobile app does, you’ll know that the device is fine, it’s the button that stops responding.

If it’s been happening a lot lately, it’s possible the battery is getting low. I wrote two of the device handlers for this doorbell, but I’m not sure if they report a low battery properly because I haven’t had any batteries get low enough to test it.

You could also try performing a factor reset on the device. To do this, you need to unpair the device and then hold the button on the speaker for at least 20 seconds. I’ve done this multiple times and it’s never deleted my custom sound files, but it’s probably still a good idea to back them up first.

*** Please don’t post the same question to multiple topics…

I think I’ll try to factory reset today… When you say unpair the device, do you mean unpair from SmartThings? Do I have to delete everything associated with it in SmartThings?

Correct

[quote=“Phil_Panfili, post:23, topic:39166, full:true”] Do I have to delete everything associated with it in SmartThings?
[/quote]
You won’t be able to remove the device if it’s being used by any SmartApps. Last time I did this, I didn’t want to have to re-create all my rule machine rules that were using it, so switched them to a virtual doorbell and them switched them back afterwards.

I just published the virtual aeon doorbell DTH to my github repo so you can use it to create a virtual device. You could probably do the same with the real DTH, but this version doesn’t do anything so you won’t get a bunch of errors if any of the SmartApps end up trying to use the virtual device.

I just released a new version that should work when the device is included Secure or Non-Secure. If you’ve had problems using this device in the past, you may want to try this version.

New Mute Feature:

This version allows you to set the Volume to 0. When the volume is 0 and the doorbell button is pressed, the switch.on event will get raised, but it won’t make a sound. This also mutes the alarm button, but you can override the volume on the fly using the new commands below.

New commands:

  • playTrackAtVolume(track, volume): Plays the specified track at the specified volume and when the track finishes, it sets the volume back to the device default. This command is supported by CoRE.

  • playRepeatTrack(track, repeat): Plays the specified track the specified number of repeat times. The device limits the maximum play time to about 20 seconds. This can be used in CoRE, but you have to manually add the 2 numeric parameters.

  • playRepeatTrackAtVolume(track, repeat, volume): Plays the specified track, the specified number of repeat times at the specified volume. The device limits the maximum play time to about 20 seconds. This can be used in CoRE, but you have to manually add the 3 numeric parameters.


This DTH is a stripped down version of the Aeon Labs Multifunction Doorbell DTH. If the only SmartApp you’re using with this device is CoRE, I recommend using this DTH.

You have to use switch.on to detect doorbell press instead of button 1 pushed, but this DTH is a lot faster, allows you to cut off the playing track by playing another track, allows you to easily play tracks at different volumes, allows you to mute the doorbell and still detect that it was pushed.


You may notice that changing the slider in the mobile app sometimes doesn’t change the value shown. The values will refresh if you re-open the device or open the device settings and hit the back button.

This problem happens on all 3 of my Android devices, but each device has a different slider with the problem so I’m pretty sure it’s an issue with the ST Android app and not this DTH.

You can find the latest version of the Aeotec Doorbell DTH in the first post of this Topic.

I am getting this error when creating New SmartApp in the API upon pushing “Create”

No signature of method: script1469383309819358503110.metadata() is applicable for argument types: (script1469383309819358503110$_run_closure1) values: [script1469383309819358503110$_run_closure1@5ad3767e] Possible solutions: getMetadata(), getState(), setState(java.lang.Object), metaClass(groovy.lang.Closure)

Grabbed code from GitHub link and tried twice, made sure I had copied all code…

It’s a Device Type, not a SmartApp…

Duhhh… Sorry, too many interruptions going on today :confused:

A few notes after playing around with this…

  1. I was able to use the OEM button as a Switch in CoRE and get lights to work, etc. I had set the doorbell track to 100 to keep it silent in the Multifunction DTH and it carried over. For the record, I am using a Z-Wave Door Contact wired to a NuTone button for extended range and reliability from my gate outside.

  2. Please add labels to the settings page in app. The variables are showing, but cryptic without labels.

  3. For Actions, the doorbell no longer shows up as a Music Player, only as a Siren. (by design?) To change an existing Piston I had to change to Siren and then delete.

  4. Using Audacity, I am building a great library of sounds, always generating a little silence to start and end of files. You can also generate a nice Risset Drum at 2000 Hz to generate a pre-chime in the track. I am also using the SpeakIt! Chrome Extension to capture text to speech in Audacity. Audacity rocks and will capture anything played though your PC speakers!

  5. Staying very solid for me, I will not have to go back to the Multifunction DTH.

Thanks @krlaframboise for the continued support and improvements. This device is a great inexpensive speaker add-on for most applications, and you get a free (short range) button to use. Too bad it gets such bad reviews on Amazon, etc. for people without your great DTH and support.

With this DTH, all of the track settings and volume settings are configured with the UI sliders. The values shown in the settings screen are left over from the other DTH. I haven’t figured out a way to automatically remove them when you switch device handlers, but if you manually delete the values, they won’t appear again. Don’t delete them if you plan on switching back to the other DTH or you’ll have to set them all up again.

It never did for this DTH, only the “multifunction” version of the DTH had it because since it’s not an actual music player, I’m pretty sure it would have been rejected by ST. ST just created a new capability called “Audio Notification” which appears to be intended for this type of device so I plan on adding that capability in a future version. It will probably take a long time for ST to use it in their SmartApps, but CoRE will probably have it soon, if it doesn’t have it already. Even if it’s not added to CoRE, all the commands will still appear as custom commands.

This doesn’t help you at this point, but you could have created a virtual device with my Virtual Aeon Doorbell DTH and used it as a temporary placeholder for all of the SmartApps using the doorbell. I think you can use that DTH as a placeholder for my other sirens too.

Having two DTHs available is confusing and a pain to maintain so I might want try and phase the other one out at some point. It’s not like ST is actually publishing any DTHs that users are submitting so I’m no longer that concerned about it.

I will admit that at the moment, the music player capability makes it accessible to a lot more applications and provides the additional sound option “play”. I also sometimes find it easier to change the track in the settings rather than having to use the sliders.

There are several factors that have led to the low reviews, but this version should eliminate the need to pair it multiple times in order to get it to do anything so that might help a little. I also just added it to the Unofficially Supported Devices list of the ThingsThatAreSmart Wiki so that might make it easier for users to find.

1 Like

OK, an update on trying to use the OEM button seperately… in CoRE using the doorbell as a switch (changes to On), to make another Action such as turning a light on works, and silent (track 100).

HOWEVER, the above piston also detects any other activities by the doorbell. My hourly chime and other voice notifications also turn on the light. I played around with CoRE Interaction set to Physical and Programmatic with no success. In summary, I can not figure out a way to use the OEM button seperately with this DTH.

This shouldn’t be happening, the only thing that should turn the device on is the doorbell button or executing the “switch.on” command.

I’ll take a look at the code.