Help with address

[ggamehdtv]

Hello,

I am setting up kaku for homebridge but my question is how you can get the address for in the config file.

Best regards

[robertklep]

Unless you also have a receiver, you can't find out the address.

However, since most (all?) recent KaKu devices can be assigned multiple addresses, it's much easier to just make up your own address and device, put the device in learning mode, and send the "On" command while they are listening. That way, they will learn the address that you configured in the Homebridge config.

[ggamehdtv]

Havent thought of that thank you!

[ggamehdtv]

I just tried it that way but the kaku device is not responding on my signal. I did install everything as needed to the GPIO pins and used the physical numbering for the config.

config: "platform": "KlikAanKlikUit",
"driver": {
"type": "rpi",
"pin": 37
},
"accessories": [
{
"name": "Licht Woonkamer",
"type": "Lightbulb",
"dimmable": false,
"address": "560251",
"device": "1"
},
{
"name": "Licht TV",
"type": "Switch",
"address": "5602",
"device": "4"
},
{
"name": "Lamp Serre",
"type": "Switch",
"dimmable": false,
"address": 5602,
"device": 5

[robertklep]

Can you post your full config? Also, both address and device should not contain quote characters ("). In what you're showing, only "Lamp Serre" is correct in that respect.

I'm not sure what the maximum allowable value of address is, but it's probably best to keep it below 32768.

[ggamehdtv]

Here is my full config with the changes in it you said. still not working.
{
"bridge": {
"name": "Homekitbridge",
"username": "CC:22:3D:E3:CE:32",
"port": 51826,
"pin": "031-45-130",
"manufacturer": "@nfarina",
"model": "Homebridge",
"serialNumber": "0.4.20"
},
"description": "This is an example configuration file with one fake accessory and one fake platform. You can use this as a template for creating your own configuration file containing devices you actually own.",
"accessories": [
{
"accessory": "NefitEasy",
"name": "thermostaat",
"options": {
"serialNumber": "Key",
"accessKey": "Key",
"password": "Key"
}
}
],
"platforms": [
{
"platform": "Server",
"port": 8765,
"name": "Homebridge Server",
"log": "/home/pi/desktop",
"restart": "homebridge"
},
{
"platform": "KlikAanKlikUit",
"driver": {
"type": "rpi",
"pin": "37"
},
"accessories": [
{
"name": "Licht Woonkamer",
"type": "Lightbulb",
"dimmable": false,
"address": 32767,
"device": 1
},
{
"name": "Licht TV",
"type": "Switch",
"address": "5602",
"device": "4"
},
{
"name": "Lamp Serre",
"type": "Switch",
"dimmable": false,
"address": 5602,
"device": 5
}
]
}
]
}

[robertklep]

It looks okay to me, but to be sure, also make the pin value a number, by removing the quotes:

"pin" : 37

(FWIW, I use pin 8 myself, but I don't see why pin 37 won't work)

How are you sending the "On" command? FWIW, perhaps it's easier to install my dedicated CLI to send On/Off commands to KaKu devices:

$ sudo npm i kaku-rpi -g

(perhaps the sudo is optional, first try without it)

Then, you can send an On command to any address/device you want:

$ kaku 37 5602 5 1

Once that has worked, and you managed to get the KaKu device to learn the code, you can use that code in the Homebridge configuration.

[ggamehdtv]

I tried it that way but it is not working. I will try it all better next week.

[ggamehdtv]

I tried it today again and I measured if there is a signal over pin 8 by clicking the on command. I saw a raise in voltage so the pi is transmitting data over the pin. it was about 0,70 volts. or is it not enough for transmitting?

[robertklep]

The signal consists of 1's and 0's, so 0.70v is only an average (although it seems low). How exactly is the sensor connected to the RPi? Can you make a photo?

[ggamehdtv]

[robertklep]

Thanks 👍 So the yellow wire is connected to "ATAD"? I don't think I've ever seen a transmitter with 4 connections.

[ggamehdtv]

the yellow wire is connected to the signal connector on the transmitter.
It should be able to work like this in the documentation of the transmitter and receiver are they telling that it only needs 3 things connected: Vcc, Ground and Signal.
http://wiki.seeedstudio.com/wiki/Grove_-_433MHz_Simple_RF_link_kit

[robertklep]

Hang on: it looks like your power isn't connected properly. If I see it correctly, the red wire on the "Speaker" connector is on pin 2, and the black is on pin 8. That's not right, the black one should be on a GND pin, so pin 6.

Never mind, your ground is coming from pin 39.

I can't say that I have any more ideas on what's going wrong :(

[ggamehdtv]

But is it correctly that your plugin should work with the klikaanklikuit APA3-1500R

[robertklep]

I can't say with 100% certainty because I don't have any similar outlet.

However, I do have PAR-1000 ("old" outlets), ACD-3500 ("new" outlets), AFR-60 and ALED-2009, and all of these work. I also know from people that have other devices that work.

[mbakker96]

Hi, I've 3 klik aan devices. One in my room and 2 in the kitchen. In my room worked very well, because I connected it with self learning. The two in the kitchen are connected to the remote. slider at pos 1 and addresses 1 and 2. But both can I not connect to homebridge. I set adress and device both at 1 in my config.json but there are not turning on / off.

What is the correct address?

[robertklep]

@mbakker96 which devices are they, specifically (model numbers)?

[mbakker96]

I use the ACM 1000.

[robertklep]

The ACM-1000 is a learning device though, isn't it? According to the documentation, it supports up to 6 transmitters, so you should be able to make it learn both your remote's code ánd a code that gets sent by homebridge-klikaanklikuit.

I can recommend my tool kaku-rpi to send codes for the device to learn, which you can subsequently add to Homebridge's config.json.