I compared this DH against the Aeon Siren and this one takes about 2 seconds longer to start playing from Rule Machine, but the delay is about the same from the mobile app. I have a few ideas as to what could be causing it so I’ll play around with it and post another version if I find a solution.
If you notice any other problems or have suggestions on ways to improve the DH, please let me know.
So I installed mine, all seemed to work; I can hit the mobile app and get it to chime, beep, etc. I see battery at 100%.
The purple icons are empty (which if I didn’t load Mp3s maybe thats why??)
The lower right says “Unknown” for the status.
If I hit the button nothing happens. But it seems to know the battery is 100% so not sure why.
Logs:
d4402326-e49a-471b-bbda-3b17c35b3477 7:30:27 PM: info Front Door Bell Firmware: FirmwareMdReport(checksum: 46903, firmwareId: 1080, manufacturerId: 134)
d4402326-e49a-471b-bbda-3b17c35b3477 7:30:25 PM: info Front Door Bell Send Low Battery Notifications: [1]
d4402326-e49a-471b-bbda-3b17c35b3477 7:30:23 PM: info Front Door Bell Version: VersionReport(applicationSubVersion: 11, applicationVersion: 1, zWaveLibraryType: 3, zWaveProtocolSubVersion: 92, zWaveProtocolVersion: 3)
d4402326-e49a-471b-bbda-3b17c35b3477 7:30:21 PM: info Front Door Bell Send Low Battery Notifications: [1]
d4402326-e49a-471b-bbda-3b17c35b3477 7:30:20 PM: info Front Door Bell Doorbell Track: [3]
d4402326-e49a-471b-bbda-3b17c35b3477 7:30:18 PM: info Front Door Bell Battery: 100
d4402326-e49a-471b-bbda-3b17c35b3477 7:30:16 PM: info Front Door Bell Firmware: FirmwareMdReport(checksum: 46903, firmwareId: 1080, manufacturerId: 134)
d4402326-e49a-471b-bbda-3b17c35b3477 7:30:14 PM: info Front Door Bell Sound Level: [10]
d4402326-e49a-471b-bbda-3b17c35b3477 7:30:12 PM: info Front Door Bell Sound Repeat Times: [1]
d4402326-e49a-471b-bbda-3b17c35b3477 7:30:10 PM: info Front Door Bell Version: VersionReport(applicationSubVersion: 11, applicationVersion: 1, zWaveLibraryType: 3, zWaveProtocolSubVersion: 92, zWaveProtocolVersion: 3)
d4402326-e49a-471b-bbda-3b17c35b3477 7:30:09 PM: info Front Door Bell Association: AssociationReport(groupingIdentifier: 2, maxNodesSupported: 5, nodeId: [], reportsToFollow: 0)
d4402326-e49a-471b-bbda-3b17c35b3477 7:30:07 PM: info Front Door Bell Doorbell Track: [3]
d4402326-e49a-471b-bbda-3b17c35b3477 7:30:05 PM: info Front Door Bell Association: AssociationReport(groupingIdentifier: 1, maxNodesSupported: 5, nodeId: [1], reportsToFollow: 0)
d4402326-e49a-471b-bbda-3b17c35b3477 7:30:03 PM: info Front Door Bell Firmware: FirmwareMdReport(checksum: 46903, firmwareId: 1080, manufacturerId: 134)
d4402326-e49a-471b-bbda-3b17c35b3477 7:30:02 PM: info Front Door Bell Device Notification Type: [2]
d4402326-e49a-471b-bbda-3b17c35b3477 7:30:00 PM: info Front Door Bell Sound Repeat Times: [1]
d4402326-e49a-471b-bbda-3b17c35b3477 7:29:58 PM: info Front Door Bell Association: AssociationReport(groupingIdentifier: 2, maxNodesSupported: 5, nodeId: [], reportsToFollow: 0)
d4402326-e49a-471b-bbda-3b17c35b3477 7:29:56 PM: info Front Door Bell Association: AssociationReport(groupingIdentifier: 1, maxNodesSupported: 5, nodeId: [1], reportsToFollow: 0)
d4402326-e49a-471b-bbda-3b17c35b3477 7:29:55 PM: info Front Door Bell Device Notification Type: [2]
d4402326-e49a-471b-bbda-3b17c35b3477 7:29:53 PM: info Front Door Bell Use Secure Commands: true
d4402326-e49a-471b-bbda-3b17c35b3477 7:29:53 PM: info Front Door Bell Debug Logging Enabled: true
d4402326-e49a-471b-bbda-3b17c35b3477 7:29:53 PM: info Front Door Bell Silent Button Enabled: false
d4402326-e49a-471b-bbda-3b17c35b3477 7:29:53 PM: info Front Door Bell Beep Track: 2
d4402326-e49a-471b-bbda-3b17c35b3477 7:29:53 PM: info Front Door Bell Alarm Track: 4
d4402326-e49a-471b-bbda-3b17c35b3477 7:29:53 PM: info Front Door Bell Current Track: null
Here is what is says in the device type:
Raw Description 0 0 0x1005 0 0 0 d 0x5E 0x86 0x98 0x25 0x70 0x72 0x59 0x85 0x73 0x7A 0x5A 0xEF 0x82
Current States
switch: off
battery: 100 %
presence: present
alarm: off
button: pushed
status: off
Preferences (edit)
Name Type Value
alarmTrack number 4
bellTrack number 3
debugOutput bool true
logConfiguration bool true
silentButton bool false
soundLevel number 10
soundRepeat number 1
toneTrack number 2
useSecureCommands bool true
Any ideas?
If you hit the right or left arrow next to the purple button, it will change to Play 1 and then when you press the button, it will play the track number that it’s displaying. I think the device comes with 5 tracks so in theory, you should be able to use the arrow buttons to navigate and play all the tracks.
If you leave the Play button showing Number 5, anytime the “Play” command is sent to the device, that’s the track that will play. You can use Rule Machine to send the play command or specify the track to play using the playTrack command.
If you turn off the “Log Configuration” preference, pressing the refresh button will check to see if it can communicate with the doorbell and that tile will change from Unknown to either Online or Offline.
If you have the “Log Configuration” turned on, it will output all of the configuration and preference to the live logging window when the Refresh button is pressed, but it doesn’t check the device status which is why it shows Unknown.
Edit: I originally added the “Online/Offline” feature using the Presence and Polling Capabilities so I could send myself alerts when my power goes out or my internet is down.
It turns out that ST doesn’t call the poll method of device handlers automatically so if you want to use this feature to get notified you will have to use something like pollster to periodically call the poll method.
When the settings are saved, it requests the battery level which is why it’s showing 100%. Unfortunately this device only Reports Normal or Low so it will stay at 100% until the battery is low.
In a future update I’ll change that to say Normal instead of 100% to make it less confusing. I’ll also come up with a better solution for the Refresh button.
So if it all works from the app…but the remote button doesn’t do anything from 3 feet away…did I miss a step?
The doorbell button doesn’t work well if it’s in your hand so if you were holding it, try putting it on a hard surface to see if that makes a difference.
The button also has really cheap clips that hold the battery in place, some users have found that bending them slightly towards the battery creates a better connection and fixed their problem.
When you press the button, does it light up and if so, does the doorbell light up?
All good: on the doorbell itself hit the plus and minus at the same time…starts quick flashing, then hit the remote button again.
Now flawless. Thanks!!
[quote=“ehoffman73, post:89, topic:36586”]
hit the plus and minus at the same time…starts quick flashing, then hit the button again
[/quote]That’s good to know, thanks.
Does anyone have any tips on creating MP3 files with a 2 second silent ending to get around the sound file cut off issue with this device?
I’m using http://www.fromtexttospeech.com/ to create some custom voice files for triggers of doors and windows and they are getting cut off pretty regularly so I need to embed some silence at the end.
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’ve released a different DH for the this Doorbell. I’m thinking about submitting it to be published so let me know what you think.
The delay isn’t consistent with either device handler so I’m not sure if it’s better or worse with this one. It does have some changes that I’ve discussed with @JH1 and @eveezy in the past.
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.
Huge thanks for this. Can I just create a new device handler, change the type in the IDE and move from Robert’s code to yours?
LJ
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.
So far, it’s working great with the full version. I like the custom commands to integrate with RM!
LJ
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.
Rule Machine
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.
Kevin
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
Any ideas on the issue here.
Thanks
Richard
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.
I just noticed this fix, is there a trick to making that happen? I still have the unit showing as a presence sensor. Thanks!
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.