As for the z-wave unit, it seems to be a Fibaro FGBS-222 unit, which is pretty hard to configure from what I understand. Right now i’ve put the following configuration options:
20 (Input 1 operating mode): Normally open alarm input
150 (Input 1 sensitivity): 1
Right now everything works. Whenever I press the doorbell the soundunit plays it’s sound and in home assisstant the “burglar” state goes to “2”. I created an automation which sends a pushnotification to my phone.
The weird thing is, is that whenever i set the input type to bistable (which i think is the correct one for a doorbell) no states are changed whenever i press the button. So the “normally open alarm input” seems to be a workaround for now.
The thing I’m trying to achieve but can’t get to work is that I want to disconnect the soundunit from the buttonpress. I want to be able to disable the sound from my home assistant dashboard. From the manual i understand i need to set the protectionlevel to “2”. But this is where it gets weird. The list of “Node protection” options seems really weird. And whenever i try to put it to “2” it simply doesn’t save. I attached a screenshot here:
Alright after a little more thought I changed my strategy. I attached the soundunit to the 2nd output instead of the first. This allows me to control the soundunit from an automation instead of directly from the input.
I added an input boolean for turning on/off the soundunit. and also one for “allowed use of the doorbell”. This due to people ringing it multiple times which will trigger the sound automation multiple times. So i’ve added a cooldown input_boolean aswell. Looks like this:
deurbel_gong_enabled:
name: Deurbel geluid
initial: on
deurbel_mag_gebruikt_worden:
name: Deurbel mag gebruikt worden
initial: on
Then I have two automations. 1 for the sound unit and 1 for sending a push notification (with an image from my camera on the frontdoor):
#
# Gang - Deurbel gaat. Pushnotification naar telefoons
#
- alias: Gang - Deurbel gaat. Pushnotification naar telefoons
trigger:
- entity_id: sensor.gang_deurbel_burglar
platform: state
to: '2'
action:
- service: onvif.ptz
data:
entity_id: camera.buitencam_voortuin
preset: 2
move_mode: GotoPreset
- delay:
milliseconds: 1500
- service: notify.mobile_app_iphone_1
data:
title: "Deurbel gaat"
message: "Er staat iemand aan de deur"
data:
attachment:
url: https://urltohomeassistant.com{{ state_attr('camera.buitencam_voortuin','entity_picture') }}
content-type: jpeg
url: 'https://urltohomeassistant.com/lovelace/14'
- service: notify.mobile_app_iphone_2
data:
title: "Deurbel gaat"
message: "Er staat iemand aan de deur"
data:
attachment:
url: https://urltohomeassistant.com{{ state_attr('camera.buitencam_voortuin','entity_picture') }}
content-type: jpeg
url: 'https://urltohomeassistant.com/lovelace/14'
- delay:
milliseconds: 1500
- service: onvif.ptz
data:
entity_id: camera.buitencam_voortuin
preset: 1
move_mode: GotoPreset
#
# Gang - Deurbelgong aan zodra er aangebeld wordt
#
- alias: Gang - Deurbelgong aan zodra er aangebeld wordt
trigger:
- entity_id: sensor.gang_deurbel_burglar
platform: state
to: '2'
condition:
- condition: state
entity_id: input_boolean.deurbel_gong_enabled
state: 'on'
- condition: state
entity_id: input_boolean.deurbel_mag_gebruikt_worden
state: 'on'
action:
- service: input_boolean.turn_off
data:
entity_id: input_boolean.deurbel_mag_gebruikt_worden
- service: switch.turn_on
data:
entity_id: switch.gang_deurbel_switch
- delay:
milliseconds: 1000
- service: switch.turn_off
data:
entity_id: switch.gang_deurbel_switch
- delay:
milliseconds: 5000
- service: input_boolean.turn_on
data:
entity_id: input_boolean.deurbel_mag_gebruikt_worden
Indeed it can be achieved by changing Node Protection Level, but it is not supported by standard HA zwave integration. I’ve seen another thread regarding smart implant, where someone described the tools and process to make such change (Fibaro Smart Implant FGBS222)… but personally I did not followed this. I assumed it is too troublesome to remove the node, reconfigure it using aither tools (requires removing also zwave stick) and configure it again… Perhaps whil eadding new smart implant to my configurastion or migrating to new zwave integration I’ll dedicate some time to make it happen.
Have you tried changing Protecting level with the new zwavejs-integration? I’m also trying to change this behavior, but don’t know what these settings should be set to.
Nope, not yet. I’m still on old, deprecated integration and only plan to move some time in spring… I have quite a lot of devices installed outside house and it is not good time to risk migration and having to redo network at this time
