[RESOLVED]Aeotec Doorbell 6 After 2.1.7.118 Update

[Ryan780]

Okay. I can do it later this afternoon.

Could this be related to the change to z-wave.

V2.1.7.118 problems configuring z wave devices

Basic Set v2 and Central Scene v3 were both added in 2.1.7, but I was told they weren't added to the release notes because user-perspective and even developer-perspective behavior is the same (it defaults to the previous versions unless otherwise specified in your call to zwave.parse). I haven't noticed any problems like the above. Is this any device or just particular ones? Stock drivers of custom drivers? Does the Basic Z-Wave tool from Hubitat give the same results for the same devices? (If …

[mike.maxwell]

don't know, that's why I'm hoping to get confirmation that the issue is specific and was introduced in 2.1.7

[bertabcd1234]

Just had a friend with this doorbell try it (I don't have one) on the latest firmware, and he said the same thing: doorbell button doesn't do anything, but all aspects of the siren portion seem to be fine.

[mrutenbeck]

@bertabcd1234 had me try mine and as he said it is experiencing the same issues. If I use the device page and press button one, the doorbell still chimes even though nothing is in the log. However the chime is contorted sounding and sometimes will sound 4 or 5 times in about 15 seconds. If I press the physical button, everything is normal except there is no record of it being pressed in Hubitat.

[billmeek]

Mike,

In the latest version (2.1.7.121) no chime playing events were showing up in the system logs. I rolled my Hubitat back to 2.1.6.117, played the chime, and it shows in the log:

dev:2602019-12-06 01:10:06.666 pm infoSiren 1 - Chime (Aeotec) stopped
dev:2602019-12-06 01:10:01.781 pm infoSiren 1 - Chime (Aeotec) playing '1. Ding Dong'

I have the Aeotec Siren, not the doorbell version. Therefore I do not have the button to test. I used the Beep from the Chime child device page of Hubitat.

[Ryan780]

I can confirm, rolling back to 2.1.6.118 shows the events for the button being pressed. So, it is definitely something in 2.1.7 which makes the doorbell not work anymore.

[mike.maxwell]

Alright, thanks for that we'll dig into it.

[Ryan780]

Thanks Mike.

[Ryan780]

Any update on this yet @mike.maxwell?

[mike.maxwell]

Fix is being tested.

[potts.mike]

Is this resolved in the latest firmware?

[mike.maxwell]

yes

[jakokln]

So I am having a similar issue with the doorbell currently. Recent migration from ST, and migrated this over about a week ago. As I have been trying to get my smart home back on its feet I noticed today that the doorbell isn't logging for me either.

I have a Webcore piston which monitors when a doorbell button is pressed and notifies me what door, and what time the button was pressed. I noticed the piston has never been ran, so this leads me to believe it has not worked since I set it up. I have setup logging as well, and upon pressing the button it does not log.

My hub firmware is 2.2.3.148. I'm happy to test things as necessary, but am still fairly new to Hubitat in general, so might need some help along the way. Let me know if I can help in any way.

[sujit]

Hi @jakokln

This is an old thread, which was fixed sometime last year.

However, looks like few Doorbell 6 users (including me) are experiencing the same issue as yours. The button is not generating any events. Here is the link to the new thread:

Aeotec doorbell 6

Evening all, Just upgraded from domo to new hubitat C7. I have paired my doorbell 6, got it to split into sub devices, it works as a doorbell, but does not register any events when the button is pressed. Ami I missing something? SW 2.2.3.145 Thanks. James

A recent post from bobbyD mentions the next update will have many bug fixes for existing drivers. So hopefully that will fix the issue.

[opdoffer]

I was hoping that 2.2.4 (released yesterday) was resolving this issue. Unfortunately the issue is still there. No events after button pressed.

This is a big dissapointment for me for a device that is on the compatibility list. It makes it it completely useless in an home automation situation and not smart at all. Now it is just like an expensive normal doorbell.

[james7]

@opdoffer apparently you need to go to your parent device for the doorbell, and change the driver to Aeotec Siren 6 New, click Configure, and it should remove the child devices and put everything into the one device. I haven't had time to check yet, but plan to later when home.

[ted2]

Thanks @james7! Just moved to a new house so I finally got to set up my C7 and Doorbell 6, which worked great except for the notification. Switching to Siren 6 New as you said fixed that.

[opdoffer]

@james7 Yes that worked! Many thanks for your help.

[Zulee]

I have had issues registering button press with this doorbell for hours now and found this thread.

I have changed to Siren 6 New but I still don't get button press logged only that the chime is playing. Do any of you get a button pressed activity with Siren 6 New?

dev:1622021-01-04 13:26:18.854 debugskip:BasicSet(value:0)

dev:1622021-01-04 13:26:18.850 debugparse:zw device: 06, command: 2001, payload: 00 , isMulticast: false

dev:1622021-01-04 13:26:18.271 infoAeotec Doorbell chime is stopped

dev:1622021-01-04 13:26:18.260 debugEp: 0, Notification: NotificationReport(v1AlarmType:0, v1AlarmLevel:0, reserved:0, notificationStatus:255, notificationType:14, event:0, sequence:false, eventParametersLength:0, eventParameter:[])

dev:1622021-01-04 13:26:18.253 debugparse:zw device: 06, command: 7105, payload: 00 00 00 FF 0E 00 00 , isMulticast: false

dev:1622021-01-04 13:26:13.358 debugskip:BasicSet(value:255)

dev:1622021-01-04 13:26:13.353 debugparse:zw device: 06, command: 2001, payload: FF , isMulticast: false

dev:1622021-01-04 13:26:12.765 infoAeotec Doorbell chime is playing

dev:1622021-01-04 13:26:12.760 debugEp: 0, Notification: NotificationReport(v1AlarmType:0, v1AlarmLevel:0, reserved:0, notificationStatus:255, notificationType:14, event:1, sequence:false, eventParametersLength:0, eventParameter:[])

dev:1622021-01-04 13:26:12.753 debugparse:zw device: 06, command: 7105, payload: 00 00 00 FF 0E 01 00 , isMulticast: false

--- Live Log Started, waiting for events ---