Aeon Doorbell Type Beta

I have debugging on but where do we find the logs? Never did that type of thing.

[quote=“Phil_Panfili, post:335, topic:28889, full:true”]
where do we find the logs?[/quote]If you log into your smartthings account (https://graph.api.smartthings.com/) with the login you used to initially setup your hub, there’s a link at the top for “Live Logging”.

Just received and hooked up my doorbell today, and got the latest code from @jdawson’s github. The only thing that works when I use this device type is the doorbell from the physical button itself, which is on the wall outside my front door and about 15-20 feet away from the siren.

None of the in-app buttons (within the “Thing”) seem to do anything, however I am seeing this output in the IDE live logging when pressing each button with debug logging enabled:

76983116-457f-4cb2-b45a-4efb38c638e8 7:26:02 PM: debug ---VERSION REPORT V1--- Doorbell is running firmware version: 1.11, Z-Wave version: 3.92 76983116-457f-4cb2-b45a-4efb38c638e8 7:25:59 PM: debug settings: ['debugOutput':'true', 'prefRingtone':'2', 'prefAlarmtone':'3', 'prefVolume':'100', 'prefNumrings':'1'], state: ['prefRingtone':1, 'prefNumrings':1, 'fw':'1.11', 'prefVolume':10, 'prefAlarmtone':1, 'sound':1, 'volume':3, 'notification':true, 'debug':true] 76983116-457f-4cb2-b45a-4efb38c638e8 7:25:59 PM: debug configuration being sent to Doorbell 76983116-457f-4cb2-b45a-4efb38c638e8 7:25:56 PM: debug refresh request sent to Doorbell 76983116-457f-4cb2-b45a-4efb38c638e8 7:25:53 PM: debug Getting battery level for remote control on Doorbell 76983116-457f-4cb2-b45a-4efb38c638e8 7:25:47 PM: debug turning off Doorbell 76983116-457f-4cb2-b45a-4efb38c638e8 7:25:45 PM: debug Alarm test command received 76983116-457f-4cb2-b45a-4efb38c638e8 7:25:45 PM: debug Testing alarm sound 3 on Doorbell 76983116-457f-4cb2-b45a-4efb38c638e8 7:25:43 PM: debug Doorbell has been rung from button. 76983116-457f-4cb2-b45a-4efb38c638e8 7:25:43 PM: debug Ringing Doorbell 76983116-457f-4cb2-b45a-4efb38c638e8 7:25:43 PM: debug Testing doorbell ring 2 on Doorbell 76983116-457f-4cb2-b45a-4efb38c638e8 7:25:41 PM: debug refresh request sent to Doorbell 76983116-457f-4cb2-b45a-4efb38c638e8 7:25:40 PM: debug Doorbell has been rung from button. 76983116-457f-4cb2-b45a-4efb38c638e8 7:25:40 PM: debug Ringing Doorbell 76983116-457f-4cb2-b45a-4efb38c638e8 7:25:40 PM: debug Testing doorbell ring 2 on Doorbell 76983116-457f-4cb2-b45a-4efb38c638e8 7:25:39 PM: debug Doorbell has been rung from button. 76983116-457f-4cb2-b45a-4efb38c638e8 7:25:39 PM: debug Ringing Doorbell 76983116-457f-4cb2-b45a-4efb38c638e8 7:25:39 PM: debug Testing doorbell ring 2 on Doorbell

When I switch the device type back to Aeon Siren, tapping the main button the in-app button will initiate the sound from the siren…

not sure if this is helpful at all …

OK I seem to have everything working pretty good. However, the speaker is really low for announcements.

I have it turned up to 100, but still not loud enough.

Does anyone have any recommendations for this?

It’s really not usable at this volume for announcements.

1 Like

You have to boost your announcements and other files to max levels using something like audacity.

In audacity there is a amplify function you can use to do this.

[quote=“Phil_Panfili, post:338, topic:28889”]
I have it turned up to 100
[/quote]It’s not very loud, but if you have it set to 100, you may not have the volume all the way up because the options are 1-10. Try setting it to 10 and make sure you press the configure button afterwards.

I edited the files in audacity and raised the volume in them. The ones that come with the bell are very quiet

What’s the easiest way to do this with audacity? There are a million options in that app.

amplify

20 characters

I just received the Aeon doorbell today, I set it up with the default Aeon Siren initially and the basic functions appeared to work fine. I removed the device and reset it, then I installed the v0.5 code, went to add new device and correctly detected the doorbell as the “Aeon Doorbell - RV v0.5”, finished pairing it and when I went to test the functions from the device (On/Off, Bell, Alarm, Off, Test Sound) Nothing responds or does anything. I went in to the Live Log and all I see is:

7fac13c7-3f03-4433-a23d-6366728f700a 1:41:39 PM: debug refresh request sent to Aeon Doorbell - RV v0.5
7fac13c7-3f03-4433-a23d-6366728f700a 1:41:09 PM: debug turning off Aeon Doorbell - RV v0.5
7fac13c7-3f03-4433-a23d-6366728f700a 1:32:10 PM: debug turning off Aeon Doorbell - RV v0.5
7fac13c7-3f03-4433-a23d-6366728f700a 1:31:19 PM: debug Aeon Doorbell - RV v0.5 has been rung from button.
7fac13c7-3f03-4433-a23d-6366728f700a 1:31:18 PM: debug Ringing Aeon Doorbell - RV v0.5
7fac13c7-3f03-4433-a23d-6366728f700a 1:31:18 PM: debug Testing doorbell ring 6 on Aeon Doorbell - RV v0.5
7fac13c7-3f03-4433-a23d-6366728f700a 1:31:14 PM: debug turning off Aeon Doorbell - RV v0.5
7fac13c7-3f03-4433-a23d-6366728f700a 1:31:13 PM: debug Aeon Doorbell - RV v0.5 has been rung from playTrack.
7fac13c7-3f03-4433-a23d-6366728f700a 1:31:13 PM: debug Ringing Aeon Doorbell - RV v0.5
7fac13c7-3f03-4433-a23d-6366728f700a 1:31:13 PM: debug Testing doorbell ring 6 on Aeon Doorbell - RV v0.5

It appears the commands are being sent from the ST app to the hub, but nothing is happening. I made sure that the values are filled in.


Any help would be appreciated.

I am having the same issue, I wonder if it has anything to do with the newest version 0.5?

Have you hit the configure button and watched what the logs say? Also, have you installed more tracks than the 5 tracks that come preinstalled? You have the ringtone set to 6, but the device only comes with 5 out of the box.

Also, are you pairing via a double tap of the button?

This is what I get with Configure, and yes I tried different tones under 5 as well:

94ec7345-4c9c-4e33-9f47-2c30473da6eb 2:39:43 PM: debug —VERSION REPORT V1— Aeon Doorbell - RV v0.5 is running firmware version: 1.11, Z-Wave version: 3.92
94ec7345-4c9c-4e33-9f47-2c30473da6eb 2:39:41 PM: debug settings: [‘debugOutput’:‘true’, ‘prefRingtone’:‘2’, ‘prefAlarmtone’:‘3’, ‘prefVolume’:‘10’, ‘prefNumrings’:‘1’], state: [‘prefRingtone’:1, ‘prefNumrings’:1, ‘fw’:‘1.11’, ‘prefVolume’:10, ‘prefAlarmtone’:1, ‘notification’:true, ‘debug’:true]
94ec7345-4c9c-4e33-9f47-2c30473da6eb 2:39:41 PM: debug configuration being sent to Aeon Doorbell - RV v0.5

Odd, you should see a bunch more stuff than that. Try re-pairing, being sure to double tap to pair… Otherwise, I’m not sure what is going on.

I think I found the problem, in the app under “Recently” it says:

“This sensor failed to complete the network security key exchange. If you are unable to control it via SmartThings, you must remove it from your network and add it again”

From what I understand, this is because it failed to get the key during pair. I have tried removing and pairing a few times, even with the doorbell touching the hub and within 1-6 inches apart. I’m not sure what else to try?

1 Like

Yeah this is definitely the problem. I’m not an expert on this, but I believe this device needs to be securely paired to work with @Robert_Vandervoort’s DH. I believe this is done by double tapping the button instead of single tapping during inclusion. (I just tapped repeatedly until it paired…)

Well, I got it working. I think. :joy: I tried the double tap method during pairing, and zwave excluding through the IDE, I’m not sure which one it was but it worked.

Everything seems to be working except for the BELL tile, when pressed it does nothing and the live log shows:

245daadb-e584-4f09-ac5a-8294947dc9b0 3:31:07 PM: debug Aeon Doorbell - RV v0.5 has been rung from button.
245daadb-e584-4f09-ac5a-8294947dc9b0 3:31:06 PM: debug Ringing Aeon Doorbell - RV v0.5
245daadb-e584-4f09-ac5a-8294947dc9b0 3:31:06 PM: debug Testing doorbell ring 2 on Aeon Doorbell - RV v0.5

The ALARM tile on the other hand works fine and shows:

245daadb-e584-4f09-ac5a-8294947dc9b0 3:33:35 PM: debug turning off Aeon Doorbell - RV v0.5
245daadb-e584-4f09-ac5a-8294947dc9b0 3:33:31 PM: debug Aeon Doorbell - RV v0.5 has been rung from button.
245daadb-e584-4f09-ac5a-8294947dc9b0 3:33:31 PM: debug Ringing Aeon Doorbell - RV v0.5
245daadb-e584-4f09-ac5a-8294947dc9b0 3:33:30 PM: debug Alarm test command received
245daadb-e584-4f09-ac5a-8294947dc9b0 3:33:30 PM: debug Testing alarm sound 1 on Aeon Doorbell - RV v0.5

Also, I am not sure what the big main ON/OFF tile is supposed to do, as it also doesn’t appear to do anything.

Just wanted to tell all of you thank you for your awesome work with this device. Love getting notified that someone rang my doorbell :slight_smile:

I am getting the same exact problem as @artkrime (Alarm tile is working, but not the Bell). My 1st objective is to have a door chime…When a door opens, a beep sounds. This does not work. I paired the device securely with no issues.

My only solution at this time is to use the original device type by @thoward1234. That seems to work (with a slight 1-2 sec delay), but I cannot control/select any other sound files for other tasks, such as a regular doorbell, alarm or other notification.

I was hoping that @Robert_Vandervoort’s device type would be able to do that, but it is reacting as stated above by @artkrime

Even though that BELL tile doesn’t work from inside the app, I was still able to setup sound files using Rule Machine, which is better because I can have it speak out loud “Garage door was opened” for example, instead of just a bell which doesn’t tell me what is happening exactly.