I’ve also found it difficult to choose the exact track so I plan on making the sliders smaller in the next version and adding left and right arrows for each one. That will allow you to easy jump to near the track you want and use the arrows to fine tune the selection.
[quote=“binhton, post:8, topic:39166”]
For track selection, I think your suggestion of using arrow for back/forth is easier to use.
[/quote]I’ve made this change in version 1.3, please let me know if you find it easier to use or if you’d rather see these options in the settings like they are with the Aeon Labs Multifunction Doorbell DH.
The link to version 1.3 can be found in the first post of this topic.
I really find your doorbell and siren device types to be great. Any way you can set it up so that we can get your updates directly through the SmartThings IDE instead of having to copy/paste? Thanks again!!
[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.
[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.
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.
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.
[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.
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 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…
[quote=“Phil_Panfili, post:23, topic:39166, full:true”] Do I have to delete everything associated with it in SmartThings?
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.
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…