-
Notifications
You must be signed in to change notification settings - Fork 1
LEDs C4 will not pair #1
Comments
Looks like they use different kinds of remotes. Could be that it's using a completely different encoding, or it could simply be that the fixed part of the address is just different. Internally there are 8 bits for the address, only 4 of them can be changed using the dip switches. The fan I built this app for was this one: https://www.lampen24.nl/formentera-plafondventilator-met-afstandsbediening.html Unfortunately I don't have the fan nor a Homey anymore right now. I moved to another place, Homey and the fan didn't. You could try running the app using the developer tools, see what the debug output says as that might give a clue what needs to be changed. |
Ok, thanks for the reply. Too bad, I specifically looked for a LEDS C4 so I knew it was compatible with Homey.
I am not a coder but I am handy with computers, (I do have a Homey 😊) so if you can point me in the right direction on how to trouble shoot this.
You say the developer tools… I found this section where you can record signals transmitted by remotes. If I send you a file I recorded would you be able to pin point the problem?
Regards,
Glenn
From: Erik Scheffers <notifications@github.com>
Sent: dinsdag 12 juni 2018 17:19
To: eriks5/com.leds-c4 <com.leds-c4@noreply.github.com>
Cc: DrDoom1 <dr.doom@quicknet.nl>; Author <author@noreply.github.com>
Subject: Re: [eriks5/com.leds-c4] LEDs C4 will not pair (#1)
Looks like they use different kinds of remotes. Could be that it's using a completely different encoding, or it could simply be that the fixed part of the address is just different. Internally there are 8 bits for the address, only 4 of them can be changed using the dip switches.
The fan I built this app for was this one: https://www.lampen24.nl/formentera-plafondventilator-met-afstandsbediening.html
Unfortunately I don't have the fan nor a Homey anymore right now. I moved to another place, Homey and the fan didn't.
You could try running the app using the developer tools, see what the debug output says as that might give a clue what needs to be changed.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub <#1 (comment)> , or mute the thread <https://github.com/notifications/unsubscribe-auth/AmVQ4LY5bpxHFzEkBAyzQBejvlT3NouEks5t79v-gaJpZM4Uj2Ok> . <https://github.com/notifications/beacon/AmVQ4HnbroQQlfqOWRER_yRt8KGf4sQZks5t79v-gaJpZM4Uj2Ok.gif>
|
I meant the instructions here: https://developer.athom.com/docs/apps/tutorial-Getting%20Started.html (skipping step 4 since you want to use an existing project, not create a new one) You'd need to download this app from github and run it using the developer tools so you can see the debugging output directly from Homey. To get all debug output you'd also need to uncomment line 92 of In the debugging output it will show the commands received when you press a button on the remote if it uses the same signals but different addressing. |
Erik,
I got so far that I can see the payload appear if I press a button of the fan in the LED C4 app from homey:
Hello world!
Initializing driver for ceiling_fan with log level Info and capture level Warn
[Info] adding device { overridden: false,
dipswitches: [ false, true, false, true ],
id: 'pt2260:20202222',
address: '20202222',
state: 0,
dim: 0,
driver_id: 'ceiling_fan' }
[Info] [Signal pt2260] registered signal
Initializing driver for fan_remote with log level Info and capture level Warn
[Info] [Signal pt2260] send payload: 202022220110
[Info] [Signal pt2260] send payload: 202022220110
(btw: How do I stop this logging? CTRL+C does not do the trick)
But I do not see ‘new’ payload if I press a button on my own remote. I have un commented line 92 to no avail.
It now looks like below. Is that OK?
},
90 devices: {
91 ceiling_fan: {
92 logLevel: 1,
93 extends: ['generic_ceiling_fan_with_light', 'fan_control', 'fan_triggers', 'fan_actions'],
94 name: 'devices.ceiling_fan.name',
95 icon: './assets/ceiling_fan/icon.svg',
96 images: {
Any tips on how to proceed?
Regards,
G.
From: Erik Scheffers <notifications@github.com>
Sent: zondag 17 juni 2018 21:26
To: eriks5/com.leds-c4 <com.leds-c4@noreply.github.com>
Cc: DrDoom1 <dr.doom@quicknet.nl>; Author <author@noreply.github.com>
Subject: Re: [eriks5/com.leds-c4] LEDs C4 will not pair (#1)
I meant the instructions here: https://developer.athom.com/docs/apps/tutorial-Getting%20Started.html (skipping step 4 since you want to use an existing project, not create a new one)
You'd need to download this app from github and run it using the developer tools so you can see the debugging output directly from Homey.
To get all debug output you'd also need to uncomment line 92 of config.js in the 433_generator directory, maybe even change logLevel to 1 to get all possible output
In the debugging output it will show the commands received when you press a button on the remote if it uses the same signals but different addressing.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub <#1 (comment)> , or mute the thread <https://github.com/notifications/unsubscribe-auth/AmVQ4KBIBYnKzyq0CvaKpe5KoIxYbfdjks5t9q1egaJpZM4Uj2Ok> .
|
I have the same fan, would love if someone could look into this. |
Hi Erik,
I was wondering if you could help me with the following:
With the nice weather the last couple of weeks I went out and got me a LED-C4 fan.
It is this fan:
https://www.lampen24.nl/witte-plafondventilator-borneo-met-licht.html
Unfortunately, I am not able to pair it with Homey using your LED-C4 app. The remote is different then depicted in the app but is does have the 4 dip switches.
It came with this remote:
https://www.amazon.co.uk/Leds-C4-71-14-accessorio-Remote-Control/dp/B00DEBFFPM/ref=sr_1_4/259-0443520-4388637?
Pairing with the dipswitch setting doesn't work neither does letting Homey detect the remote. Of course I have tried several dipswitch settings.
You have any idea how I can get this to work? Is there a way to troubleshoot?
Thanks in advance,
Glenn
The text was updated successfully, but these errors were encountered: