• 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


Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Nexa doorbell (arctech) device configuration
#1
I am having troubles adding my doorbell as a device in pilight.

Listening to the device through pilight-receive gives me three different kind of messages repeated a number of times:
Code:
{
    "message": {
        "id": 19707905,
        "all": 1,
        "state": "up"
    },
    "origin": "receiver",
    "protocol": "arctech_screen",
    "uuid": "0000-b8-27-eb-b2f641",
    "repeats": 1
}
{
    "message": {
        "id": 19707905,
        "all": 1,
        "state": "on"
    },
    "origin": "receiver",
    "protocol": "arctech_switch",
    "uuid": "0000-b8-27-eb-b2f641",
    "repeats": 1
}
{
    "message": {
        "id": 19707905,
        "all": 1,
        "state": "opened"
    },
    "origin": "receiver",
    "protocol": "arctech_contact",
    "uuid": "0000-b8-27-eb-b2f641",
    "repeats": 1
}

Trying to configure a device for this I've tried with
Code:
"devices": {
        "living": {
            "protocol": [ "kaku_screen" ],
            "id": [{
                "id": 19707905,
                "all":1
            }],
            "state": "down"
        }
    },

and so on with kaku_screen_old, kaku_switch, kaku_switch_old..
They all complain that the id field is invalid, which is probably true as the protocols seems to think it should be shorter.

Furthermore, my message lacks a unit which seems to be required by all of these protocols.

Anyone know how to get around this?
 
Reply
#2
The issue is that you can't have all in the id part.
https://wiki.pilight.org/doku.php/arctech_switch_v7_0

The all goes here:
Code:
"protocol": [ "kaku_switch" ],
"id": [{
    "id": 100,
    "unit": 0
}],
"state": "off",
"all": 1
 
Reply
#3
Ah yes, thank you.

Edit: My cheap 433 sender was apparently disturbing my 433 receiver, once I got that out of the way it worked with a unit of 0!

Code:
"devices": {
                "living": {
                        "protocol": [ "kaku_switch" ],
                        "id": [{
                                "id": 19707905,
                                "unit": 0
                        }],
                        "all": 1,
                        "state": "off"
                }
        },
 
Reply
  


Possibly Related Threads...
Thread Author Replies Views Last Post
Smile config, device uuid <-> id Twain 3 1,823 09-29-2020, 11:07 AM
Last Post: coolinx
  MQTT external Broker (not local) configuration nicky 3 445 06-02-2020, 05:00 PM
Last Post: curlymo
  Configuration example with program and ACTION to control MPD tomk 0 896 09-12-2017, 07:02 PM
Last Post: tomk
  Hacking my own Doorbell Naga 1 1,051 07-29-2017, 08:54 AM
Last Post: curlymo
  Time to handle configuration edits properly amahlaka 4 1,726 03-19-2017, 04:26 PM
Last Post: pilino1234
Question Controlling device values using a script (updating temperature manually) H4R0 1 1,421 12-07-2016, 09:55 AM
Last Post: pilino1234
  config device #1 "living", missing protocol jjlf 5 2,653 11-08-2016, 11:55 PM
Last Post: jjlf
  One Device Multiple Rules ColdScythe 1 1,159 11-07-2016, 07:07 PM
Last Post: curlymo
  Kaku doorbell Joeks 0 1,295 04-22-2016, 11:43 AM
Last Post: Joeks
  [solved] can't get GUI configured, error "...config gui element #1 "xyz", device not pitpat 7 3,291 02-22-2016, 10:04 PM
Last Post: pitpat

Forum Jump:


Browsing: 1 Guest(s)