Anyone using this with HA?
It doesn’t present a binary sensor and none of sensor show change when doorbell ring. They do show they have been triggered, just no value change.
this is not for a zwave doorbell, but the same principle should apply.
I’ve defined my doorbell sensor this way:
- platform: rfxtrx
automatic_add: True
devices:
0716004500910560:
name: doorbell
data_type:
- Sound
fire_event: true
and the automation goes this way:
- alias: Doorbell Notification
initial_state: true
trigger:
- platform: event
event_type: signal_received
event_data:
entity_id: sensor.doorbell_sound
thank you
this works but what I want is acutal state change to be reported by device and registered in HA
I can trigger off event but this will lead to false alert for things other than button press.
I am wonding if this is configurable parameter or HA’s open-zwave config need updating
you most likely won’t see a state change as the doorbell doesn’t go from [say] off to on, it only gets an event fired when you press the button. At least that’s how mine works…
I don’t understand that. What other signal would come from your doorbell? This automation example I provided only triggers on even fired from doorbell
Adjust as you need for your doorbell
True.
I expected function like motion sensor, ON for some period. I thought it may parse out the individual doorbell buttons pressed (button1 vs button2)or other info to zwave.
I use different automation and trigger on state_change directly. I am trying to reduce the number of “translation” sensors used only for converting data. I had too many at one point
In this case the alarm(shock sensor on siren) may trigger it.
There is a sensor.aeotec_limited_zw162_doorbell_6_sourcenodeid_# that I would expect to show binary or detailed (which button) info but always = 1. Adding up to 6 doorbell button is possible with this unit and I want to know if I can identify triggering button
I just got my Aeotec Doorbell 6 today. When I paired it with HA all I see is the zwave node and a bunch of sensors (alarm_type, alarm_level, burglar, sourcenodeid, power_management). I excluded the device and added it back with “Secure Add” and now I only have maybe 5 sensors of varying types. I have no clue how to configure this thing from here.
Did the device come with a manual?
It should tell you in there how to set the report type to send. I think there should be a few settings that could control that feature.
I know on other Aeotec Zwave devices you need to set the report type to either binary or “hail” to have it create a binary sensor and/or report it’s state back to other zwave devices including the controller.
I had to do that on my Aeotec Zwave microswitches.
I looked for the manual on the Aeotec site but it’s not on their support page anywhere that I could find yet.
EDIT:
Did you happen to find anywhere to buy an additional wireless button for the doorbell?
I don’t think the buttons are available for purchase independently yet.
What’s weird is the zwave device that shows up in HA doesn’t have any config options. I’m going to try to upgrade OpenZwave tomorrow. Apparently they just recently added the doorbell 6.
Engineering spec is here: https://doc.eedomus.com/files/Engineering%20Specification%20-%20Aeotec%20Doorbell%206%20%20.pdf
I couldn’t interpret anything that would help, but maybe someone else can?
No. Could not find where to buy extra button
Yes. But it is really quickstart guide. I looked at an engineer doc I found for it (this is refered to a lot) but saw nothing re: reports.
How is this done? I looked but did not see how this is done.
I just looked at my Aeotec zwave switch and it’s under parameter 80 (notification status) I switched it to “hail” and then HA was able to see when the switch was manually operated.
Could you provide a link to that please?
Thanks! I’ll look at it and see if I can figure anything out.
Just an FYI, setting parameter 80 to Hail can potentially flood the network with updates from the device that it bogs down the network and can cripple it to where nothing else can communicate. This is more of an issue with devices that do power monitoring or have multiple sensors. You probably want to set parameter 80 to Basic. Everything still works in terms of updates, just without the flood of network traffic. Hail was the old workaround to the patent on instantaneous updates of zwave devices held by Lutron. Basically Hail means the device will send a broadcast message out to the network for any device that will listen to that node and say “I have an update”. The controller is the only device that will respond to broadcast domain messages so it listens then sends a request to the device asking what it’s current state is, then the node responds with its state.
On my Aeotec gen 5 microswitch’s I had to set the notification to hail or the controller didn’t pick up the fact that the switch was turned on locally via the connected manual switch.
I believe if I remember correctly those are the only devices I needed to set that way. The rest are either set to basic or binary report types.
I’m not sure what you mean by this.
What events are you seeing and where do you see them when you push the button on the remote?
I looked at the eng doc and it doesn’t look like there is any ability to change the report type but it does say which event is type is fired and the event number.
Maybe if we had the data you are seeing change when other things change (such as pushing the remote button) we can decipher the info in the eng doc to make sense of what is going on.
When doorbell is pressed, last_changed and last_updated is changed and event generated
Currently I trigger automation from State Change Event
State is always = 0
BEFORE PRESS DOORBELL
{“attributes”: {“friendly_name”: “Aeotec Limited ZW162 Doorbell 6 SourceNodeId”, “node_id”: 46, “unit_of_measurement”: “”, “value_id”: “72057594815725601”, “value_index”: 2, “value_instance”: 1}, “context”: {“id”: “46a3342bfcf9431c8dff4773a478ff6d”, “parent_id”: null, “user_id”: null}, “entity_id”: “sensor.aeotec_limited_zw162_doorbell_6_sourcenodeid_3”, “last_changed”: “2019-06-14T18:51:28.161078+00:00”, “last_updated”: “2019-06-14T18:51:28.161078+00:00”, “state”: “0”}
AFTER PRESS DOORBELL
{“attributes”: {“friendly_name”: “Aeotec Limited ZW162 Doorbell 6 SourceNodeId”, “node_id”: 46, “unit_of_measurement”: “”, “value_id”: “72057594815725601”, “value_index”: 2, “value_instance”: 1}, “context”: {“id”: “187501cba0484c438a8bbd60f666e8ec”, “parent_id”: null, “user_id”: null}, “entity_id”: “sensor.aeotec_limited_zw162_doorbell_6_sourcenodeid_3”, “last_changed”: “2019-06-15T04:23:09.484747+00:00”, “last_updated”: “2019-06-15T04:23:09.484747+00:00”, “state”: “0”}
What are all of the different entities that get created when you add the device to HA?
My current entities are below.
Only Burglar has shown state change. 254 to 9. This may be result of unit unpowered and running on battery for some time. I have triggered shock sensor and this did not cause value change. only generate event like doorbell push.
Power management has remained at value 254
All other entities have remained at 0
sensor.aeotec_limited_zw162_doorbell_6_alarm_level_4
sensor.aeotec_limited_zw162_doorbell_6_alarm_type_4
sensor.aeotec_limited_zw162_doorbell_6_burglar_3
sensor.aeotec_limited_zw162_doorbell_6_sourcenodeid_3
sensor.aeotec_limited_zw162_doorbell_6_power_management_3
I’m very surprised that the alarm_level and/or burglar sensors don’t react to the button presses. Those are the entities I usually see changing no matter if there is a binary sensor that exists or not.
I would be surprised if the sourcenodeid sensor changed in response to a button press. I’ve never ever seen that change on any of my zwave devices.
is there anything in the zwave log that indicates any state changes when you push the button?
log below. I would expect this is from the button press
2019-06-15 04:23:09.127 Detail, Node046, Received: 0x01, 0x08, 0x00, 0x04, 0x00, 0x2e, 0x02, 0x98, 0x40, 0x07
2019-06-15 04:23:09.128 Info, Node046, Received SecurityCmd_NonceGet from node 46
2019-06-15 04:23:09.128 Info, NONCES: 0xf4, 0xf1, 0xff, 0x9b, 0x03, 0xf0, 0x00, 0xef
2019-06-15 04:23:09.128 Info, NONCES: 0xd0, 0xe7, 0x4c, 0x2d, 0x5c, 0x36, 0x4a, 0xdb
2019-06-15 04:23:09.128 Info, NONCES: 0x2e, 0x85, 0x83, 0xd4, 0x98, 0x1f, 0xba, 0x48
2019-06-15 04:23:09.128 Info, NONCES: 0xbc, 0x8a, 0x71, 0xe5, 0xeb, 0x64, 0x52, 0xe0
2019-06-15 04:23:09.128 Info, NONCES: 0x57, 0x52, 0x7b, 0x5a, 0x42, 0x7c, 0x4a, 0x12
2019-06-15 04:23:09.128 Info, NONCES: 0x64, 0x97, 0x40, 0xc0, 0xce, 0x8a, 0x9b, 0xfb
2019-06-15 04:23:09.128 Info, NONCES: 0x10, 0x1f, 0xcf, 0xa8, 0x3e, 0x89, 0xf1, 0xfb
2019-06-15 04:23:09.128 Info, NONCES: 0x5a, 0x1b, 0xfc, 0x28, 0xa5, 0x98, 0x23, 0xb5
2019-06-15 04:23:09.128 Info, Node046, Sending (WakeUp) message (Callback ID=0x01, Expected Reply=0x00) - Nonce_Report - 0x01, 0x11, 0x00, 0x13, 0x2e, 0x0a, 0x98, 0x80, 0x5a, 0x1b, 0xfc, 0x28, 0xa5, 0x98, 0x23, 0xb5, 0x05, 0x01, 0xfb:
2019-06-15 04:23:09.136 Detail, Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2019-06-15 04:23:09.136 Detail, ZW_SEND_DATA delivered to Z-Wave stack
2019-06-15 04:23:09.269 Detail, Received: 0x01, 0x07, 0x00, 0x13, 0x01, 0x00, 0x00, 0x0e, 0xe4
2019-06-15 04:23:09.269 Detail, ZW_SEND_DATA Request with callback ID 0x01 received (expected 0x01)
2019-06-15 04:23:09.367 Detail, Node046, Received: 0x01, 0x23, 0x00, 0x04, 0x00, 0x2e, 0x1d, 0x98, 0x81, 0x7d, 0xe8, 0xde, 0x04, 0x9e, 0xfb, 0xf0, 0x31, 0xc5, 0x25, 0x83, 0xeb, 0x7f, 0x55, 0xfb, 0x2f, 0xb0, 0xf3, 0x5a, 0x9c, 0xba, 0xf0, 0xe3, 0x6e, 0x3f, 0xa3, 0x9e, 0x2f
2019-06-15 04:23:09.368 Info, Raw: 0x98, 0x81, 0x7d, 0xe8, 0xde, 0x04, 0x9e, 0xfb, 0xf0, 0x31, 0xc5, 0x25, 0x83, 0xeb, 0x7f, 0x55, 0xfb, 0x2f, 0xb0, 0xf3, 0x5a, 0x9c, 0xba, 0xf0, 0xe3, 0x6e, 0x3f, 0xa3, 0x9e, 0x2f
2019-06-15 04:23:09.368 Detail, Node046, Decrypted Packet: 0x00, 0x71, 0x05, 0x00, 0x00, 0x00, 0xff, 0x0e, 0x01, 0x00
2019-06-15 04:23:09.368 Detail,
2019-06-15 04:23:09.368 Info, Node046, Received Alarm report: type=0, level=0, sensorSrcID=0, type:Unknown type event:1, status=255
2019-06-15 04:23:09.368 Detail, Node046, Refreshed Value: old value=0, new value=0, type=byte
2019-06-15 04:23:09.368 Detail, Node046, Changes to this value are not verified
2019-06-15 04:23:09.368 Detail, Node046, Refreshed Value: old value=0, new value=0, type=byte
2019-06-15 04:23:09.368 Detail, Node046, Changes to this value are not verified
2019-06-15 04:23:09.368 Detail, Node046, Refreshed Value: old value=0, new value=0, type=byte
2019-06-15 04:23:09.368 Detail, Node046, Changes to this value are not verified
2019-06-15 04:23:09.368 Detail, Node046, Notification: ValueChanged
2019-06-15 04:23:09.373 Detail, Node046, Notification: ValueChanged
2019-06-15 04:23:09.376 Detail, Node046, Notification: ValueChangedI’m not seeing anything we can work with so I think I’m out of ideas.
I think I’ll just sit back and watch this thread and hopefully somebody smarter than me (not too hard to do…
) will offer some other information.
I’ve been watching for these doorbells to be released for a bit now and I’m kind of disappointed that they don’t work right out of the box yet.