RFXcom and klik-aan-klik-uit (KAKU) doorbell

Had the same. I added a separate switch in HA with another unit code that I learned on the receiver.

This way you can ring the bell only when you want.
Receive the knob code with HA. Do some logic/automation and send the other code to the receiver , or don’t and send a telegram message or flash a light when the kids are in bed…

You don’t learn the actual knob code on the chime part, only in HA.

Thanks. That was my workaround, so will try that.

The bell is used for a ‘mess call’ to alert my kid to come downstairs for dinner.
Since mostly he is gaming with headphones on, I will also launch a big red light in front of his face (behind his monitor) :slight_smile:

Similar issue now @koen01 @Danielhiversen.

I have a kaku remote with 3 on/off buttons and 1 all off button. What I want is to catch the event of that last button. I want it to strat a scene that switches off all light in the living room, including hue.

Switches:

switch:
  - platform: rfxtrx
    automatic_add: false
    devices:
      0b11001000bb136201010f60: # 0bb13621 kaku remote 1
        name: KAKU Remote 1
      0b11001000bb136202010f60: # 0bb13622 kaku remote 2
        name: KAKU Remote 2
      0b11001000bb136203010f60: # 0bb13623 kaku remote 3
        name: KAKU Remote 3

This is the debug log when I click the all off button:

2018-03-19 22:45:09 DEBUG (Thread-3) [homeassistant.components.rfxtrx] Receive RFXCOM event from (Device_id: 0bb13621 Class: LightingDevice Sub: 0, Pkt_id: 0b11000700bb136201030070)
2018-03-19 22:45:09 DEBUG (Thread-3) [homeassistant.components.rfxtrx] Device_id: 0bb13621 device_update. Command: Group off

What should the automation trigger look like?

[quote=“koen01, post:4, topic:3155”]

  event_type: button_pressed

change to ‘Group Off’. , does that work?

This is the current config, where the door bell event is catched, but the all off remote button isn’t.
What I noticed is, that the all off id 0b11000f00bb136201030070 looks similar to that of button 1 0b11001000bb136201010f60 , so the switch.kaku_remote_all_off sensor is not created.

############################################################
## Switch
############################################################

switch:
  - platform: rfxtrx
    automatic_add: false
    devices:
      0b11001000bb136201010f60: # 0bb13621 kaku remote 1
        name: KAKU Remote 1
      0b11001000bb136202010f60: # 0bb13622 kaku remote 2
        name: KAKU Remote 2
      0b11001000bb136203010f60: # 0bb13623 kaku remote 3
        name: KAKU Remote 3
      0b11000f00bb136201030070: 
        name: KAKU Remote All Off
        fire_event: true
      0b110005011afee601040f60: # beldrukker woonkamer
        name: Mess Call
        fire_event: true

############################################################
## Automation
############################################################

automation:
  - alias: Mess Call Pressed
    trigger:
      - platform: event
        event_type: button_pressed
        event_data: {"entity_id": "switch.mess_call"}
    action:
      - service: notify.telegram
        data:
          title: 'Etenstijd'
          message: 'Etenstijd!'
  - alias: KAKU Remote All Off
    trigger:
      - platform: event
        event_type: button_pressed
        event_data: {"entity_id": "switch.kaku_remote_all_off"}
    action:
      - service: notify.telegram
        data:
          message: 'all off'

What I didn’t understand at first is, that I needed to catch the event from ‘button 1’.
I have managed to get it working this way:

############################################################
## Switch
############################################################

switch:
  - platform: rfxtrx
    devices:
      0b11001000bb136201010f60: # 0bb13621 kaku remote 1
        name: KAKU Remote 1
        fire_event: true # to catch 'group off' event
      0b11001000bb136202010f60: # 0bb13622 kaku remote 2
        name: KAKU Remote 2
      0b11001000bb136203010f60: # 0bb13623 kaku remote 3
        name: KAKU Remote 3

############################################################
## Automation
############################################################

automation:
  - alias: KAKU Remote Group Off
    trigger:
      - platform: event
        event_type: button_pressed
        event_data: {"entity_id": "switch.kaku_remote_1", "state" : "group off"}
    action:
      - service: light.turn_off
        entity_id: group.living_lights
      - service: logbook.log
        data:
          name: Woonkamerverlichting
          message: uitgeschakeld
      - service: notify.telegram
        data:
          message: 'Woonkamerverlichting uitgeschakeld'

I found some help from this post:

I have the doorbell working but the problem is that i do get the telegram message 6 times every time the button is pressed.
This is a bit to much but i can not find how to fix it
This the automation i used

- alias: deur bel
  initial_state: 'on'
  trigger:
    platform: event
    event_type: button_pressed
    event_data: {"entity_id": "switch.deur_bel"}
  action:
  - service: notify.telegram_gijs
    data:
      message: Er staat iemand aan de deur
      data:
        photo:
        - url: http://my-camera-ip/image.jpg

This is the switch

 -  platform: rfxtrx
    devices:
      0b1100000154843a01040f60:      
        name: Deur Bel  
        fire_event: True

Your automation is the almost the same is mine. Only difference is that - url is indented in my config, so like this

photo:
  - url: http://my-camera-ip/image.jpg

Otherwise you can add the following code which I use to only receive one message if the button gets pressed again within 10 seconds.

condition:
  - condition: template
    value_template: '{{ (as_timestamp(now()) - as_timestamp(states.automation.<your_automation>.attributes.last_triggered | default(0)) | int > 10)}}'

It keeps giving me 6 messages every time even with the conditions.
I think the button fires 6 signals in a very short time.
I use a ACDB-7000A

Have the same doorbell and no issues here.

Are you using packages? If so check this https://github.com/home-assistant/home-assistant/issues/14856#issuecomment-403308134.

Just bought a new doorbell at the action for €5,99 that works with the sonoff bridge, problem solved :slight_smile:

I assume that you guys are all talking about the actual button (ACDB-7000A).

However, I don’t have the button, I only have the receiver (ACDB-7000C) and I want HA to send a signal to it to tell the doorbell to ring.

How on earth do I add this device? I assume that I need to do something similar to how I added my Somfy RTS, by plugging the RFXcom device into a pc and then putting KAKU in learn mode.

But the details… I have no idea… does anyone know?

You don’t need to add the bell device. Just add a switch or input boolean with the rfxtrx platform and make up some valid device code. Your rfx module will broadcast that code. Put the bell in learn mode and switch on your virtual bell. That’s it.

Yup, that did it, who knew it was so easy :smiley:

Maybe someone who can help.
I have the Kaku doorbell. How do I set it automatic back to an off state after x seconds.
Now it always stays on.

Late reply but I did it like this:

  alias: Doorbell_main_entrance
  trigger:
  - event_data:
      entity_id: switch.main_entrance
      state: group on
    event_type: button_pressed
    platform: event
  action:
  - data:
      message: Main entrance
    service: notify.ios_zinkens_iphone
  - alias: ''
    data:
      entity_id: switch.main_entrance
    service: switch.turn_on
  - delay: 00:00:05
  - data:
      entity_id: switch.main_entrance
    service: switch.turn_off

That way I will get a notification and the “dummy”-switch will switch to on for 5 sec and back to off.

Hi Koen,

Ik hope you can help me out. i have the KlikAanKlikUit ACDB-7000BC and i can’t tigger anything when i push on the bell button.

If i ring my doorbel i see the folwoing data on the rfx manager.

17-12-2020 03:23:00:322= 0710010041080770
Packettype = Lighting1
subtype = ARC
Sequence nbr = 0
housecode = A
unitcode = 8
Command = Chime
Signal level = 7 -64dBm

Please help. im working on this already for 3 days
Thanks already

Hi Jeroen,

No sure what the relation is between the rfx manager code and the doorbell id, but here’s my configuration of my rfxcom doorbell:

rfxtrx:
  device: /dev/ttyUSB1
  debug: false
  automatic_add: true
  devices:
    0b11001f01a3cf4a0c010f80:
      fire_event: True

If you put the automatic add option in, you should see the device com up in your devices:


The fire event is important for automation.

After thats configured you can automate like this:

- alias: Doorbell pressed rfxcom
  initial_state: true
  trigger:
    platform: state
    entity_id: binary_sensor.ac_1a3cf4a_12
  action:
    - service: notify.telegram_x
      data:
        title: Doorbell pressed!
        message: Doorbell pressed!
        data:
          photo:
            - url: http://linktoipcamsnapshot
              caption: 'Doorbell pressed'

2 Likes

hi how did you add a different sound?

I’ve tried this over a hunderd times but can’t find the right device code.
Can anybody give me a clue what device code I’ve to use?
I followed this manual: RFXCOM RFXtrx - Home Assistant
“*manually add a device, in the options window, an event code can be added in the field Enter event code to add” But I can’t find the right code :frowning: