Aeotech ZW162 Doorbell

Configuration Z-Wave
21

ditto

Shock sensor log below

2019-06-15 05:31:09.355 Detail, Node046,   Received: 0x01, 0x08, 0x00, 0x04, 0x00, 0x2e, 0x02, 0x98, 0x40, 0x07
2019-06-15 05:31:09.355 Info, Node046, Received SecurityCmd_NonceGet from node 46
2019-06-15 05:31:09.355 Info, NONCES: 0xb8, 0xf2, 0x5d, 0xf6, 0x7c, 0x4f, 0xf1, 0x91
2019-06-15 05:31:09.355 Info, NONCES: 0x4b, 0xe0, 0x54, 0xf0, 0x78, 0x78, 0xa6, 0x30
2019-06-15 05:31:09.355 Info, NONCES: 0x6b, 0x04, 0x27, 0xe7, 0x53, 0x19, 0x79, 0x05
2019-06-15 05:31:09.355 Info, NONCES: 0xb7, 0x77, 0x3d, 0x30, 0xef, 0xe4, 0x60, 0x5a
2019-06-15 05:31:09.355 Info, NONCES: 0x57, 0x52, 0x7b, 0x5a, 0x42, 0x7c, 0x4a, 0x12
2019-06-15 05:31:09.355 Info, NONCES: 0x64, 0x97, 0x40, 0xc0, 0xce, 0x8a, 0x9b, 0xfb
2019-06-15 05:31:09.355 Info, NONCES: 0x10, 0x1f, 0xcf, 0xa8, 0x3e, 0x89, 0xf1, 0xfb
2019-06-15 05:31:09.355 Info, NONCES: 0x5a, 0x1b, 0xfc, 0x28, 0xa5, 0x98, 0x23, 0xb5
2019-06-15 05:31:09.355 Info, Node046, Sending (WakeUp) message (Callback ID=0x01, Expected Reply=0x00) - Nonce_Report - 0x01, 0x11, 0x00, 0x13, 0x2e, 0x0a, 0x98, 0x80, 0xb7, 0x77, 0x3d, 0x30, 0xef, 0xe4, 0x60, 0x5a, 0x05, 0x01, 0x39:
2019-06-15 05:31:09.365 Detail,   Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2019-06-15 05:31:09.365 Detail,   ZW_SEND_DATA delivered to Z-Wave stack
2019-06-15 05:31:09.497 Detail,   Received: 0x01, 0x07, 0x00, 0x13, 0x01, 0x00, 0x00, 0x0e, 0xe4
2019-06-15 05:31:09.497 Detail,   ZW_SEND_DATA Request with callback ID 0x01 received (expected 0x01)
2019-06-15 05:31:09.589 Detail, Node046,   Received: 0x01, 0x23, 0x00, 0x04, 0x00, 0x2e, 0x1d, 0x98, 0x81, 0xb1, 0xc0, 0xf8, 0x04, 0xac, 0xab, 0x6d, 0x8d, 0x1b, 0x91, 0x46, 0xfd, 0xfa, 0x82, 0x2d, 0x18, 0x13, 0xb3, 0xb7, 0x20, 0xed, 0x21, 0x5f, 0xef, 0xa8, 0xc6, 0x99, 0x58
2019-06-15 05:31:09.589 Info, Raw: 0x98, 0x81, 0xb1, 0xc0, 0xf8, 0x04, 0xac, 0xab, 0x6d, 0x8d, 0x1b, 0x91, 0x46, 0xfd, 0xfa, 0x82, 0x2d, 0x18, 0x13, 0xb3, 0xb7, 0x20, 0xed, 0x21, 0x5f, 0xef, 0xa8, 0xc6, 0x99, 0x58
2019-06-15 05:31:09.589 Detail, Node046, Decrypted Packet: 0x00, 0x71, 0x05, 0x00, 0x00, 0x00, 0xff, 0x07, 0x09, 0x00
2019-06-15 05:31:09.589 Detail,
2019-06-15 05:31:09.589 Info, Node046, Received Alarm report: type=0, level=0, sensorSrcID=0, type:Burglar event:9, status=255
2019-06-15 05:31:09.589 Detail, Node046, Refreshed Value: old value=0, new value=0, type=byte
2019-06-15 05:31:09.589 Detail, Node046, Changes to this value are not verified
2019-06-15 05:31:09.589 Detail, Node046, Refreshed Value: old value=0, new value=0, type=byte
2019-06-15 05:31:09.589 Detail, Node046, Changes to this value are not verified
2019-06-15 05:31:09.589 Detail, Node046, Refreshed Value: old value=0, new value=0, type=byte
2019-06-15 05:31:09.589 Detail, Node046, Changes to this value are not verified
2019-06-15 05:31:09.589 Detail, Node046, Refreshed Value: old value=9, new value=9, type=byte
2019-06-15 05:31:09.589 Detail, Node046, Changes to this value are not verified
2019-06-15 05:31:09.589 Detail, Node046, Notification: ValueChanged
2019-06-15 05:31:09.593 Detail, Node046, Notification: ValueChanged
2019-06-15 05:31:09.597 Detail, Node046, Notification: ValueChanged
2019-06-15 05:31:09.601 Detail, Node046, Notification: ValueChanged
2019-06-15 05:31:09.656 Detail, Node046,   Received: 0x01, 0x08, 0x00, 0x04, 0x00, 0x2e, 0x02, 0x98, 0x40, 0x07
2019-06-15 05:31:09.656 Info, Node046, Received SecurityCmd_NonceGet from node 46
2019-06-15 05:31:09.656 Info, NONCES: 0xb8, 0xf2, 0x5d, 0xf6, 0x7c, 0x4f, 0xf1, 0x91
2019-06-15 05:31:09.656 Info, NONCES: 0x4b, 0xe0, 0x54, 0xf0, 0x78, 0x78, 0xa6, 0x30
2019-06-15 05:31:09.656 Info, NONCES: 0x6b, 0x04, 0x27, 0xe7, 0x53, 0x19, 0x79, 0x05
2019-06-15 05:31:09.656 Info, NONCES: 0xb7, 0x77, 0x3d, 0x30, 0xef, 0xe4, 0x60, 0x5a
2019-06-15 05:31:09.656 Info, NONCES: 0xe8, 0x88, 0x42, 0x3c, 0xa1, 0xbc, 0x41, 0x8d
2019-06-15 05:31:09.656 Info, NONCES: 0x64, 0x97, 0x40, 0xc0, 0xce, 0x8a, 0x9b, 0xfb
2019-06-15 05:31:09.656 Info, NONCES: 0x10, 0x1f, 0xcf, 0xa8, 0x3e, 0x89, 0xf1, 0xfb
2019-06-15 05:31:09.656 Info, NONCES: 0x5a, 0x1b, 0xfc, 0x28, 0xa5, 0x98, 0x23, 0xb5
2019-06-15 05:31:09.656 Info, Node046, Sending (WakeUp) message (Callback ID=0x01, Expected Reply=0x00) - Nonce_Report - 0x01, 0x11, 0x00, 0x13, 0x2e, 0x0a, 0x98, 0x80, 0xe8, 0x88, 0x42, 0x3c, 0xa1, 0xbc, 0x41, 0x8d, 0x05, 0x01, 0x0a:
2019-06-15 05:31:09.665 Detail,   Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2019-06-15 05:31:09.665 Detail,   ZW_SEND_DATA delivered to Z-Wave stack
2019-06-15 05:31:09.807 Detail,   Received: 0x01, 0x07, 0x00, 0x13, 0x01, 0x00, 0x00, 0x0f, 0xe5
2019-06-15 05:31:09.807 Detail,   ZW_SEND_DATA Request with callback ID 0x01 received (expected 0x01)
2019-06-15 05:31:09.899 Detail, Node046,   Received: 0x01, 0x23, 0x00, 0x04, 0x00, 0x2e, 0x1d, 0x98, 0x81, 0xd1, 0xcb, 0xf0, 0x76, 0x3d, 0x34, 0xd4, 0x1e, 0x1c, 0x78, 0x1d, 0x06, 0x0d, 0xd0, 0xfc, 0x4b, 0xfa, 0x96, 0xe8, 0x0f, 0xad, 0x41, 0x72, 0x5f, 0x68, 0xd3, 0x17, 0x5e
2019-06-15 05:31:09.899 Info, Raw: 0x98, 0x81, 0xd1, 0xcb, 0xf0, 0x76, 0x3d, 0x34, 0xd4, 0x1e, 0x1c, 0x78, 0x1d, 0x06, 0x0d, 0xd0, 0xfc, 0x4b, 0xfa, 0x96, 0xe8, 0x0f, 0xad, 0x41, 0x72, 0x5f, 0x68, 0xd3, 0x17, 0x5e
2019-06-15 05:31:09.899 Detail, Node046, Decrypted Packet: 0x00, 0x71, 0x05, 0x00, 0x00, 0x00, 0xff, 0x0e, 0x01, 0x00
2019-06-15 05:31:09.899 Detail,
2019-06-15 05:31:09.899 Info, Node046, Received Alarm report: type=0, level=0, sensorSrcID=0, type:Unknown type event:1, status=255
2019-06-15 05:31:09.899 Detail, Node046, Refreshed Value: old value=0, new value=0, type=byte
2019-06-15 05:31:09.899 Detail, Node046, Changes to this value are not verified
2019-06-15 05:31:09.899 Detail, Node046, Refreshed Value: old value=0, new value=0, type=byte
2019-06-15 05:31:09.899 Detail, Node046, Changes to this value are not verified
2019-06-15 05:31:09.899 Detail, Node046, Refreshed Value: old value=0, new value=0, type=byte
2019-06-15 05:31:09.899 Detail, Node046, Changes to this value are not verified
2019-06-15 05:31:09.899 Detail, Node046, Notification: ValueChanged
2019-06-15 05:31:09.903 Detail, Node046, Notification: ValueChanged
2019-06-15 05:31:09.907 Detail, Node046, Notification: ValueChanged
22

@Fishwaldo mentioned in Discord that the Doorbell 6 is supported in OZW v1.6, maybe he can clarify if it’s functional at all in v1.4. HA only supports OZW v1.4.

If I understand the manual correctly, the doorbell chime will send a Siren notification (0xE) when triggered. The Siren notification type was added in v6 of the Notification Command Class. OZW v1.4 only supports Notification v3, thus it cannot understand the data it is receiving, which is evident in the log messages. 1.6 supports v8 so it understand Siren notifications. You would theoretically have a siren entity once 1.6 is supported.

The doorbell also sends the button events via Basic Set commands to group associations. You might be able to workaround the lack of notification support by using an automation that triggers on the node event data. See the tech spec: page 18 has the root device associations, and page 19 has the Endpoint 3 (button #1) associations. The doorbell is multichannel, so it can appear to have multiple devices, and you can associate to each of them. I don’t know how OZW presents that to HA, if it does. Associating the controller node (ID 1) to group 4 of the root device, or group 2 of endpoint 3, will cause the controller (HA) to receive doorbell #1 button events. I don’t have this device to try though, so I’m just guessing this from reading the manual.

Besides the notifications, the Sound Switch class is required to change the tone or trigger the chime from HA. That class was implemented in OZW v1.6. There might be ways to work around the tone selection using config param #1, but it wouldn’t be easy.

23

I am reading up on zwave for better understanding and had started testing Doorbell #1 Group 4 to see if I can see this node data. If I get result I will post here.

24

I knew somebody smart would pop in here eventually. :smile:

Is there any timeline on when HA will update to the new OZW version? Or is it possible for us to update OZW ourselves manually? Which would, frankly, be a PITA to have to every update. But if it gets this working it might be worth it to the people who already bought one of these.

25

I don’t know of any timelines since I’m not a dev (I just follow the conversations), but it’s not possible to upgrade simply by compiling your own version of OZW. OZW 1.6 is a major change and not at all compatible with 1.4. Before HA can even support it, the Python library needs to be updated, which is in progress. I don’t really have a clue if the Python library hides all the changes introduced in 1.6, so if not HA will then need to be updated. There are also very few HA Z-Wave devs (one?), unfortunately.

26

added controller to doorbell#1 (group 4)

set "Basic Set to nodes in Group 4"to “When Chime starts playing tone, send Basic Set 0xFF. When Chime stops playing tone, send Basic Set 0x00”

level switches 255 to 0 when press doorbell
not sure what to do with this however as I can only see this in zwave log but dont see how to pull that in HA

2019-06-15 09:22:00.837 Info, Node046, Received Basic set from node 46: level=255.  Sending event notification.
2019-06-15 09:22:00.837 Detail, Node046, Notification: NodeEvent

EDIT
Just realized my goal here was to determine if OZW upgrade was required or if possible to make some change to get this going. @freshcoast somewhat answered this.

For now best option may be to trigger automation off state changes since this works out of the box and wait for OZW 1.6

27

So, I’ve been digging this morning and it looks like the HA fork of OpenZwave includes files for the Doorbell 6 (https://github.com/home-assistant/open-zwave/blob/hass/config/aeotec/zw162.xml), but I updated to the latest version of HA this morning and I still can’t set any config parameters for the doorbell, and I’m not seeing any updates in the HA frontend when the button is pressed.

Is there any way I can get to the zwave config files in my installation of HA to see if that zw162.xml file is present?

28

Are you able to configure anything?
under “node config options” for this device I have configurations listed below

1: Light Effect and Tone Play Mode for Browse
2: Light Effect and Tone Effect for Tampering
3: Light Effect and Tone Effect for Doorbell 1
4: Light Effect and Tone Effect for Doorbell 2
5: Light Effect and Tone Effect for Doorbell 3
6: Light Effect and Tone Effect for Environment
7: Light Effect and Tone Effect for Security
8: Light Effect and Tone Effect for Endpoint Emergency
16: Light Effect 1
17: Light Effect 2
18: Light Effect 3
19: Light Effect 4
20: Light Effect 5
21: Light Effect 6
22: Light Effect 7
32: Basic Set to nodes in Group 2
33: Basic Set to nodes in Group 3
34: Basic Set to nodes in Group 4
35: Basic Set to nodes in Group 5
36: Basic Set to nodes in Group 6
38: Basic Set to nodes in Group 8
39: Basic Set to nodes in Group 9
48: Trigger Unpairing Button Mode
49: Trigger pairing Button Mode
50: Report which Pairing Button Mode is triggered
51: Report which Buttons had been paired
52: Get the information of #1 Button
53: Get the information of #2 Button
54: Get the information of #3 Button
255: Reset To Factory Defaults
29

No. I don’t have any options there. Maybe I need to exclude the device and try adding again?

30

Yes. exclude and add as Secure Node

31

Excluded the node, restarted HA, added as secure node, ran network heal, restarted HA.

Still don’t have any config options :frowning:

When I click on the drop down for Node config options, nothing happens.

Here is the node information, if that helps.

image
image318×613 17 KB

32

Shows as unknown.
What version HA?

33

Just updated to 0.94.3 this morning. Was doing the same thing yesterday.

image

34

Exclude. Reboot. Verify removed. Add secure. Reboot. Check

35

You can use the event data as a trigger in an automation. I linked the event doc in my previous post. 255 means the button was pressed.

3 Likes
36

Turns out my install had multiple directories with OZW config in them. I had to specify the correct path in configuration.yaml and then remove the doorbell’s entry from zwcfg*.xml and reboot HA. It finally shows up! Thanks for the help!

I’ll be trying to trigger events based on the button press, as well as triggering the siren as part of my alarm system.

37

Let me know if you can trigger siren.
Havent tried and hadnt wasnt even planning to use this but actually is a good idea

38

kryt1kal,

May i please trouble you for the name of the ozw config file?

39

My particular OZW config was located at [path to venv]/lib/python3.6/site-packages/python-openzwave/ozw_config/ if I remember correctly (I’m currently away from home but can check later if need-be).

40

If anyone is interested n how to use this in an automation I have one set up and working.

I used the configuration posted @tmjpugh above in this post:

When added to my system it was added as node 30.

Here is a test automation that I set up to turn on a boolean and works successfully:

  - alias: Doorbell
    trigger:
      platform: event
      event_type: zwave.node_event
      event_data:
        entity_id: zwave.aeotec_limited_zw162_doorbell_6
        basic_level: 255
        node_id: 30
    action:
      service: homeassistant.turn_on
      entity_id: input_boolean.bool_14
4 Likes