I am considering purchasing one of these, is this now working properly is HA?
Yes/no
Yes. Can get notifications on doorbell press and alarm.
No. These are not sensors and you must c
Use templates to workaround. Support is added into current OZW version that HA is working to implement.
Thank you for sharing this, @tmjpugh. You have any specifics as to when the developers of HA got their hands on this, and when could we hope for a release?
… and could you elaborate on how the notifications you mention is achieved?
@FlangeMonkey I’ve not been able to get it to work with RFXTRX. From the documentation I’ve read it is not supported on any of the protocols. I also read of the 1byOne doorbell which is supposed to be the same thing, but uses the Byron SX protocol which rfxtrx does support. Unfortunately that’s also proving allusive, although that might be as I haven’t yet had the opportunity to strip out all other uses of rfxtrx to identify the individual doorbell i want to recognise (I use rfxtrx for light, and blind operation).
unless RFXTRX can work with the zwave protocol it won’t work.
Here is an automation I use:
- 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: notify.pushbullet_notify
data:
message: 'Someone is at one of the doors'
I have a front door and back door that uses the same doorbell base unit with two different buttons paired to it. Since the unit isn’t fully integrated with the old zwave version it can’t split the two buttons out from each other so I only can get a generic “some is at a door” notification as indicated above.
Thank you for sharing. I am looking for the other way around, though.
I have the Aeotech Siren 6, and I have made my own doorbell button, from which I want to trigger the Siren 6, which has the same chime component as the Aeotech Doorbell.
My action would be triggering the chime with one of the build-in doorbell chimes, and of course sound a smoke alarm.
Sirens in are fully supported in OZW 1.6. OZW 1.4 lacks support for the Sound Switch Command class, which is used to turn on/off the siren and select a tone.
For the Aeotec Siren 6 at least, the tech manual says you can trigger it with a Basic Set command. You don’t get control of the tone (uses the stored default tone id). I think you can do a Basic Set from HA, but it’s a little complicated. You could use the zwave.set_node_value service.
To turn on:
zwave.set_node_value
node_id: node
value_id: value_id
value: 255
To turn off, set the value to 0. The challenge is finding the value_id. You can call the zwave.print_node service and it will dump a bunch of data to the HA console. You would have search the output for the BASIC command class and copy the value id, which is some large integer value like 72057594395230208.
1 Like
What is the current status of this? Did 1.6 ever get added to home assistant? Not sure how to check what version I am on. I added the device securely and got 5 entities, all which don’t change when I press the doorbell. Is there any way to get if the doorbell was rang or not by using zwave.node_event? Also, the volume is way too loud on the ringer. What value or how do I send a zwave command to lower it by 50%? I see the zwave manager page there are options to send data.
OZW 1.6 is included as a beta in HA 0.110. Not much is particularly usable yet, though. I added the doorbell, and it adds 8 Devices and a bunch of entities, about 25% of which were enabled and the rest were disabled. I can’t seem to do anything with any of the devices or entities, though.
HA doesn’t have a suitable integration type for these kinds of doorbells/sirens, so just adding OZW 1.6 is not going to solve this.
For now, you’ll need to either use OZW Admin or send MQTT commands.
I have been able to adjust the config values, like tones, volume and lights, via the ozw-admin tool as @freshcoast has suggested.
Hello
I tried the set_node_value, but it failed.
I get the value_id from entites informations (tried all). Can it really work like that ?
Thanks
You would have to use the value id of the Basic command class value. That would not be exposed as an entity.
Hi,
I´ve just paired the Aeotech Doorbell with my home assistant server ver. 111.3 but as anyone else, I also have problems detecting the push of the button in my automation.
I did follow the guide from @tmjpugh but it still doesn’t work.
when selecting “Basic Set to nodes in group 4” I select this:
“When chimes starts playing tone, send basic set 0xff. when chimes stop…basic set 0x00”
after selecting I click “Set configuration Parameter”
But when i push the button only this is seen in the log:
> 2020-06-19 13:53:41.477 Detail, Node011, Received: 0x01, 0x0f, 0x00, 0x04, 0x00, 0x0b, 0x09, 0x71, 0x05, 0x00, 0x00, 0x00, 0xff, 0x0e, 0x01, 0x00, 0x72
> 2020-06-19 13:53:41.477 Detail,
> 2020-06-19 13:53:41.477 Info, Node011, Received Alarm report: type=0, level=0, sensorSrcID=0, type:Unknown type event:1, status=255
> 2020-06-19 13:53:41.477 Detail, Node011, Refreshed Value: old value=0, new value=0, type=byte
> 2020-06-19 13:53:41.477 Detail, Node011, Changes to this value are not verified
> 2020-06-19 13:53:41.477 Detail, Node011, Refreshed Value: old value=0, new value=0, type=byte
> 2020-06-19 13:53:41.477 Detail, Node011, Changes to this value are not verified
> 2020-06-19 13:53:41.477 Detail, Node011, Refreshed Value: old value=0, new value=0, type=byte
> 2020-06-19 13:53:41.477 Detail, Node011, Changes to this value are not verified
> 2020-06-19 13:53:41.478 Detail, Node011, Notification: ValueChanged
> 2020-06-19 13:53:41.480 Detail, Node011, Notification: ValueChanged
> 2020-06-19 13:53:41.481 Detail, Node011, Notification: ValueChanged
> 2020-06-19 13:53:46.980 Detail, Node011, Received: 0x01, 0x0f, 0x00, 0x04, 0x00, 0x0b, 0x09, 0x71, 0x05, 0x00, 0x00, 0x00, 0xff, 0x0e, 0x00, 0x00, 0x73
> 2020-06-19 13:53:46.980 Detail,
> 2020-06-19 13:53:46.980 Info, Node011, Received Alarm report: type=0, level=0, sensorSrcID=0, type:Unknown type event:0, status=255
> 2020-06-19 13:53:46.980 Detail, Node011, Refreshed Value: old value=0, new value=0, type=byte
> 2020-06-19 13:53:46.980 Detail, Node011, Changes to this value are not verified
> 2020-06-19 13:53:46.980 Detail, Node011, Refreshed Value: old value=0, new value=0, type=byte
> 2020-06-19 13:53:46.980 Detail, Node011, Changes to this value are not verified
> 2020-06-19 13:53:46.980 Detail, Node011, Refreshed Value: old value=0, new value=0, type=byte
> 2020-06-19 13:53:46.980 Detail, Node011, Changes to this value are not verified
> 2020-06-19 13:53:46.980 Detail, Node011, Notification: ValueChanged
> 2020-06-19 13:53:46.982 Detail, Node011, Notification: ValueChanged
> 2020-06-19 13:53:46.983 Detail, Node011, Notification: ValueChanged
When I look at @tmjpugh output:
> 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
I see that the message “sending event notification” is there - Anyone have a clue about why this is not working for me?
Hi @tmjpugh
Can you clarify what "Associating the controller node (ID 1) to group 4 of the root device " means (or how its done)
Im struggling to get event from the pushed button into my automations
/Krede
Hi @tmjpugh
I too have just installed a Doorbell 6 using OZW 1.6. It installed like a dream and my automation is working using the doorbell siren that is activated when the Doorbell is pushed. The siren is activated by the default button 1:
- id: 'xxxxxxxxxxxx'
alias: Doorbell rings
trigger:
- entity_id: binary_sensor.sound_switch_doorbell_1_siren_active
platform: state
to: 'on'
action:
- data:
duration: 30
entity_id: camera.front_door
filename: {{ now().strftime("%Y%m%d-%H%M%S") }}.mp4
service: camera.record
- data: {}
service: script.nnnnnnnnnn
- data:
message: Doorbell
service: notify.me
initial_state: true
The automation takes a video recording of a camera output, starts a script (Which flashes a lamp) and then sends a notification to my phone using Simplepush.
I cannot help much more, I have like yourself just got the device. All I can do is show you what is working for me.
I hope that helps.
Honestly this 1yr back and I stop using this doorbell shortly after so I forget how this working in HA.
@pfinnigan seems to have this working so maybe he can provide better info
This the automation I use for sending a notification:
- 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: notify.pushbullet_notify
data:
message: 'Someone is at one of the doors'
I’m considering to upgrade to OZW 1.6 to see if that fixes my issue around triggering the automation. But I dont know the impact of upgrading… was it an easy task for you ?
Do you mind to share the log lines from the Zwave log right after button push? I would like to compare with my own 