search

rahimkhoja / Atomik_Controller

GNU General Public License v2.0
0 stars 1 forks source link

New RGB+CCT bulbs? #1

Open jjensn opened 7 years ago

jjensn commented 7 years ago

Am I correct in assuming you figured out how to control the new CCT bulbs?

anthonyangel commented 7 years ago

I've tested with the new RGB CCT remote and the FUT066 downlight, not much luck on either front!

I can't pair the remote with the Atomik controller. I have paired the downlight (tried as a dual white as well as a RGB+W bulb), it successfully pairs (and flashes red), but then can't be controlled

rahimkhoja commented 7 years ago

I haven't had time to add to this project, however

SSH in to the controller . type sudo service atomik-transceiver stop ( this stops the transceiver )

then type: sudo transceiver -t 2 -d (this starts the transceiver in debug white mode)

You will see what is being transmitted to the bulbs in white mode. this may help figure out the newer CCT-RGB bulbs. if you have a remote for the newer bulbs, press lots of buttons on it too see if it is detected by the transceiver. You can also send commands to bulbs via this command. When I have the time I will use this to decipher the new CCT-RGB on air protocol.

for color type: sudo transceiver -d (this starts the transceiver in debug color mode)

type: sudo transceiver -h (shows you how to send commands)

anthonyangel commented 7 years ago

I've tried this, and the transceiver doesn't pick anything up from the remote, is there a way of changing the frequency?

WoodsterDK commented 7 years ago

Hi, The channels are different, and so is the sync word.

The new bulbs receives on the channels 70,39,8, and channel diversity is used like in the old protocol by sending on all three channels repeated about 20 times.

The sync word used is:

Syncword:0x1809000000007236 -> Sync0 = 0x7236, Sync3 = 0x1809

I can receive, but not decode the frames.

rahimkhoja commented 7 years ago

thanks WoodsterDK

this is all good info!

WoodsterDK commented 7 years ago

The new protocol is 9 byte long, and seems to use a random first byte as a key for the decoding. It looks like a crc and a frameid is also included. I have samples from to remotes, and also looks like the two byte id is used. See here: https://authometion.com/forum/viewtopic.php?f=2&t=639

WoodsterDK commented 7 years ago

Ideas are welcome for reversing the protocol.

rahimkhoja commented 7 years ago

It may or may not work..

I have added the channels and Sync words to the Transceiver source.

if you compile it, it should detect the remotes and perhaps help decode the transmissions. ( I Hope ) ( the easy compile command is in the transceiver.cpp comments )

As I don't have the remotes I can't test changes I made to the code.

The code should only be able to listen to the new channels.

after compiling use this command to try and listen to WoodsterDK's channels

sudo transceiver -t 3 -d

I hope it helps