another new protocol?

[laureysruben]

I just bought a trust smart home ACD-200, which should be the new brand for coco (marketed as kaku belgium/netherlands). According to what's on the package and website this is compatible with coco/kaku, but it's not working for me.

To test my hardware I decided to install pilight, and get both the receiver and the sender running at once. When sending from pilight I actually got my switch (a dimming socket) to work. When sending from homebridge I see a signal coming in on pilight, but it's not the correct signal. It is recognized by pilight as protocol "arctec_switch_old", with no id or unit filled in. The working signal from pilight-send show "arctec_switch" as protocol.

This is my settings:

{ "platform": "KlikAanKlikUit", "driver" : { "type" : "rpi", "pin" : 11 }, "accessories" : [ { "name" : "Lamp Eettafel", "type" : "Lightbulb", "dimmable" : true, "address" : "5601", "device" : "1" }, { "name": "Sfeerlamp", "type": "Lightbulb", "dimmable": true, "address": "5602", "device": "2" }]

This is what pilight is sending (as seen by pilight-receive):

{ "origin": "sender", "protocol": "arctech_switch", "message": { "id": 5602, "unit": 2, "state": "off" }, "repeat": 1, "uuid": "0000-b8-27-eb-f5d33f" }

When switching the light on through homebridge, this is what I see:

{ "message": { "id": 0, "unit": 0, "state": "off" }, "origin": "receiver", "protocol": "arctech_switch_old", "uuid": "0000-b8-27-eb-f5d33f", "repeats": 1 } { "message": { "id": 1, "unit": 4, "state": "up" }, "origin": "receiver", "protocol": "arctech_screen_old", "uuid": "0000-b8-27-eb-f5d33f", "repeats": 1 } { "message": { "id": 0, "unit": 0, "state": "off" }, "origin": "receiver", "protocol": "arctech_switch_old", "uuid": "0000-b8-27-eb-f5d33f", "repeats": 2 } { "message": { "id": 1, "unit": 0, "state": "up" }, "origin": "receiver", "protocol": "arctech_screen_old", "uuid": "0000-b8-27-eb-f5d33f", "repeats": 2 } { "message": { "id": 0, "unit": 0, "state": "off" }, "origin": "receiver", "protocol": "arctech_switch_old", "uuid": "0000-b8-27-eb-f5d33f", "repeats": 3 } { "message": { "id": 0, "unit": 0, "state": "off" }, "origin": "receiver", "protocol": "arctech_switch_old", "uuid": "0000-b8-27-eb-f5d33f", "repeats": 4 } { "message": { "id": 0, "unit": 0, "state": "off" }, "origin": "receiver", "protocol": "arctech_switch_old", "uuid": "0000-b8-27-eb-f5d33f", "repeats": 5 } { "message": { "id": 1, "unit": 0, "state": "up" }, "origin": "receiver", "protocol": "arctech_screen_old", "uuid": "0000-b8-27-eb-f5d33f", "repeats": 3 }``

Is there something wrong with my config, or is there really a protocol not supported by this library?

[robertklep]

Try using proper Number values instead of String's (i.e. remove the quotes around the address and device values):

"address": 5602,
"device": 2

This is how the driver distinguishes between arctec_switch_old (using strings) and arctec_switch (using numbers).

[laureysruben]

My god, I can't believe I missed that. I'll try to change this tonight and see if it works! I hope I can finally tell siri to turn the lights on :)

[greensouth]

Excuse me if I seem a bit retarded... but I have a Trust/Kaku ICS-2000 station and the way I have to add new stuff to the app, or syncing with the remote, is by putting the sockets and sensors in "learning" mode. Then, after pressing a remote button, or touching an option in the app, is added to it, or synced with the remote.

There is no way to know the address or device id. How do you know what code correspond with the device so I can add it to config.json?

Next week i'm getting a RF Receiver to attach to my PI for further testing.

Also... Are you planning on adding support for KAKU movement and door/window sensors? That would be great.

Thanks!!

[robertklep]

@greensouth old devices have a dial on the device with which you set the address and device id. If you have self-learning devices, I use the kaku executable (provided by another package that I wrote, kaku-rpi) to learn a new code into the device that I subsequently use in the Homebridge configuration.

However, at least in theory (I don't think I ever tried), you can just use a random address and device id in your Homebridge configuration, put the target device in learning mode, and send the On command (through the Home app, or through Siri).

As for the movement/door/window-sensors: I don't have any of those devices so it's difficult for me to add support to them. Also, they require a receiver, whilst my plugin (at this point) only supports transmitters.