I’ve been using Audacity ( http://audacityteam.org/ ). There’s an option for “Silence” in the “Generate” menu that allows you to specify the amount of time you want to add. Before you add the silence you should click the end of the track because that’s where you want the silence added. Afterwards you can use the export option in the File menu to save your changes. If I remember correctly, it made me install some other component in order to export mp3s, but it provided instructions.
I have about 40 devices and the doorbell is my favorite, but it has some quirks and the reviews are really bad. I haven’t had problems with the range, but I have the button mounted to an inside wall about 20’ from the device. It’s at the top of my stairs so it’s not a direct line of sight, but the signal doesn’t have to go through any exterior walls.
I have it setup so that the button toggles my night settings instead of playing a sound. I’ve been pressing it every morning and night for about a month and I can’t think of any times where it didn’t detect the button push.
Yes, that should work. After you’ve done that, you will see some extra fields without labels at the bottom of the settings screen. Those are left over from the previous DH and they won’t hurt anything, but if you delete their contents they won’t show up again.
There have been a couple of users that got stuck in one of the modified versions of Robert’s code and were unable to delete the device or change the type in the IDE. If that happens, you will need to overwrite the old code with the new code and then change the namespace and app name back to the old values so it thinks it’s still the same device handler. Once you’ve done that, you should be able to change the type to the new DH and then delete the old one.
I changed the functionality in this DH so if you have anything setup that expects the doorbell button to trigger the switch.on event, they will need to be modified to use the button one pushed event.
I also created the Aeotec Doorbell DH which won’t break your existing rules so you might want to start with that one instead. That’s the one I plan on trying to get published, but I’m waiting until more users have confirmed that it works.
Except when the physical doorbell button is pressed, the device takes a couple of seconds to start playing the track, but the delay doesn’t appear to be as bad with the Aeotec Doorbell DH.
You can now use Smart Home Monitor and Speaker Notify with Sound to play mp3s by track number on the Aeon Labs Doorbell.
** See first post in topic for most recent version of this DH **
You’ve always been able to do this using Rule Machine, but it no longer requires setting up Custom Commands for each track.
Smart Home Monitor
The Custom Monitoring section of SHM supports Audio Notifications and if you choose “Custom Message” for the Notification, you can specify a track number to play in the “Play this message” field.
Speaker Notify with Sound
You can setup a Custom Message action and specify a track number to play in the “Play this message” field.
You can use the “Send or speak a message” action to play a specific track number. You do this by entering the track number in the “Custom message to send” field, enabling the “Speak this message?” option, and choosing the doorbell for the “On this music device”.
For all the methods mentioned above, the custom text can either be a track number or one of the following commands:
I don’t plan on publishing this device handler so I figured ease of use is a lot more important than following device handler best practices.
I have a Aeon Door bell and I have tried to copy your code into a new device handler so I can install the device.
Unfortunately when I copy the code into the From Code section of "Create a New device handler " and I save it throws up the error message below:
Org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: script1462084106900242037055.groovy: 802: unexpected token: API @ line 802, column 8. Status API Training Shop Blog About ^ 1 error
It looks like you’re pasting more than just the code. When you click the link in the first post it takes you to the code on GitHub, but on that page, you should click the “Raw” button located above the code. That will display a clean version of the code that you can copy and paste into the device handler.
The original bug had to do with the way the presence tile appeared. I’m not sure why, but the new version of the mobile app messed up the look of the tile if you named it “presence” so to fix the problem, I just had to change its name.
If you don’t like the fact that this device acts as a presence sensor, you can use my Aeotec Doorbell DH instead. It’s basically a stripped down version of this device handler.
The device doesn’t have any type of presence detection so I’m not sure how that would work.
The device will appear “present” when it’s online and “not present” when it’s not responding. I added that capability as a way to detect when either my internet goes down or I lose power, but since SmartThings rarely polls zwave devices, it only works if you manually press the refresh button or if you use a SmartApp like pollster to regularly poll the device.
The Beacon capability fits better with the way it’s being used and probably wouldn’t cause it to appear in the Family tab, but that capability caused problems with the Android mobile app so I had to use the Presence Sensor capability instead.
There have been a few updates since I ran into that problem so they’ve probably fixed it, but if I change it to the Beacon Capability now, it will break things for anyone using the Presence Sensor capability.
It actually shows present when someone pushes the doorbell for me, I use this as opposed to a button notification because presence won’t go away immediately if someone pushes the button twice. This prevents duplicate notifications on the TV for me lol