• 10 dec 2017: forum version update. In case of issues use this topic.
  • 30 nov 2017: pilight moved servers. In case of issues use this topic.
Hello There, Guest! Login Register


ACDB-7000A KaKu doorbell
#1
Hello,

I have a ACDB-7000A Doorbell

when I use pilight-receive and press the button and release I get:

Code:
{
        "message": {
                "id": 25800834,
                "all": 1,
                "state": "up"
        },
        "origin": "receiver",
        "protocol": "arctech_screen",
        "uuid": "0000-b8-27-eb-07c0ea",
        "repeats": 1
}
{
        "message": {
                "id": 25800834,
                "all": 1,
                "state": "on"
        },
        "origin": "receiver",
        "protocol": "arctech_switch",
        "uuid": "0000-b8-27-eb-07c0ea",
        "repeats": 1
}
{
        "message": {
                "id": 25800834,
                "all": 1,
                "state": "opened"
        },
        "origin": "receiver",
        "protocol": "arctech_contact",
        "uuid": "0000-b8-27-eb-07c0ea",
        "repeats": 1
}

So https://wiki.pilight.org/doku.php/archtech_contact should work.

Pasting the following code in config.json and running pilight-daemon -D results in
pilight-daemon: ERROR: config device #8 "living", missing protocol

Code:
"living": {
         "name": "Living",
                "door": {
                        "name": "Door",
                        "protocol": [ "kaku_contact" ],
            "id": [{
                "id": 100,
                "unit": 0
            }],
                        "state": "closed"
                }
        }

changing the protocol to arctech_contact and again pilight-daemon -D results in
pilight-daemon: ERROR: config device #8 "living", missing protocol

what config do I need?
 
Reply
#2
The example was wrong. Fixed it.
 
Reply
#3
Copied the new example and ERROR: config device #8 "living", missing protocol persists.
Is it okay that pilight-receive finds arctech_contact and the example is kaku_contact?
 
Reply
#4
Some testing further I have this:

Device:
Code:
        "DoorBell": {
            "protocol": [ "kaku_contact" ],
            "id": [{
                "id": 25800834,
                "unit": 0
            }],
            "state": "closed"
        },
        "DoorBellNotification": {
            "protocol": [ "program" ],
            "id": [{
                "name": "DoorBellNotification"
            }],
            "program": "/bin/bash",
            "arguments": "/etc/pilight/DoorBellNotification.sh",
            "stop-command": "",
            "start-command": "/bin/bash /etc/pilight/DoorBellNotification.sh",
            "state": "stopped",
            "pid": 0
        },

Rule:
Code:
        "DoorBellRule": {
            "rule": "IF DoorBell.state == opened THEN switch DEVICE DoorBellNotification TO running",
            "active": 1
        }

In the pilight.log I get

Code:
{"message":{"id":25800834,"all":1,"state":"on"},"origin":"receiver","protocol":"arctech_switch","uuid":"0000-b8-27-eb-07c0ea","repeats":1}
{"message":{"id":25800834,"all":1,"state":"on"},"origin":"receiver","protocol":"arctech_switch","uuid":"0000-b8-27-eb-07c0ea","repeats":1}
{"message":{"id":25800834,"all":1,"state":"up"},"origin":"receiver","protocol":"arctech_screen","uuid":"0000-b8-27-eb-07c0ea","repeats":1}
{"message":{"id":25800834,"all":1,"state":"up"},"origin":"receiver","protocol":"arctech_screen","uuid":"0000-b8-27-eb-07c0ea","repeats":1}
{"origin":"update","type":6,"devices":["DoorBell"],"values":{"timestamp":1504441214,"state":"opened"}}
{"origin":"update","type":6,"devices":["DoorBell"],"values":{"timestamp":1504441214,"state":"opened"}}
{"message":{"id":25800834,"all":1,"state":"opened"},"origin":"receiver","protocol":"arctech_contact","uuid":"0000-b8-27-eb-07c0ea","repeats":1}
{"message":{"id":25800834,"all":1,"state":"opened"},"origin":"receiver","protocol":"arctech_contact","uuid":"0000-b8-27-eb-07c0ea","repeats":1}

Looks like when I pressed the doorbell this signal is received and recognized.

The DoorbellNoticiation-program is not run.

When I use a rule for impuls remote switches I get

Code:
[Sep 03 11:50:58:839816] pilight-daemon: INFO: executed rule: Lamp2B_on_LampNotification
[Sep 03 11:50:58:850220] pilight-daemon: INFO: started "switch" action for device "Lamp2BNotification"
[Sep 03 11:50:58:871154] pilight-daemon: INFO: stopped "switch" action for device "Lamp2BNotification"
[Sep 03 11:51:02:641690] pilight-daemon: INFO: executed rule: Lamp2C_on_LampNotification

What am I doing wrong for getting the notification to run?
 
Reply
#5
I would advice you to use the API for these purposes.
 
Reply
#6
(09-03-2017, 01:58 PM)curlymo Wrote: I would advice you to use the API for these purposes.

Can you please explain? It looks like nothings happens when using arctech protocol with a KaKu doorbell. It is detected but the rule is not executed. I think the api or program is the next step.
 
Reply
#7
I didn't read that the executing rule was with a different device. Can you check what happens when you switch a generic_switch in that rule?
 
Reply
  


Possibly Related Threads...
Thread Author Replies Views Last Post
  KaKu @ Gamma houtig 0 1,105 01-19-2016, 11:01 AM
Last Post: houtig
  piBell doorbell pushover notifier Jeroenk 0 1,000 11-10-2015, 10:08 AM
Last Post: Jeroenk
  New doorbell? mike 0 1,327 01-14-2015, 07:58 AM
Last Post: mike
  Remote KAKU AYCT-102 lechiel 4 2,698 01-09-2015, 12:13 AM
Last Post: curlymo
  interest in almost new pir sensors kaku? d.m.raspberry 0 1,291 03-29-2014, 04:08 PM
Last Post: d.m.raspberry

Forum Jump:


Browsing: 1 Guest(s)