search

sidoh / esp8266_milight_hub

Replacement for a Milight/LimitlessLED hub hosted on an ESP8266
MIT License
932 stars 219 forks source link

Is it possible implement new OEM (partially Milight) protocol? #72

Closed itProfi closed 4 years ago

itProfi commented 7 years ago

I recieve yesterday some RGBW OEM China LED plate - https://detail.1688.com/offer/522143371857.html?spm=a2615.2177701.0.0.hO79R9 When i sniff it, i see this syncword 0x050A 0x55AA and channels 0x04 (4) and 0x4A( 74), command with 7 byte payload, like 0xC2 0xDC 0xA0 0xAB 0x01 0xBE 0x00 (Power On All), 0xC2 0xDC 0xA0 0xAB 0x02 0xC1 0x00 (power Off ALL). I believe that this is very similar to the description of the old MiLigh protocol - http://arduino-projects4u.com/milight-rf-control/ Can you help me for it's implemention?

sidoh commented 7 years ago

Sure, if you can figure out the command structure I can take a look.

itProfi commented 7 years ago

Ok, thanks. But only after the 2-3 of May. I will be very busy :)

itProfi commented 5 years ago

Hi, Chris! Yesterday, i again try investigate those packets with some modificatios on MilightRadioConfig.cpp

#include <MiLightRadioConfig.h>

MiLightRadioConfig MiLightRadioConfig::ALL_CONFIGS[] = {
 // MiLightRadioConfig(0x147A, 0x258B, 7, 9, 40, 71, 0xAA, 0x05), // rgbw
  MiLightRadioConfig(0x050A, 0x55AA, 7, 4, 39, 74, 0xAA, 0x05), // rgbw
  MiLightRadioConfig(0x050A, 0x55AA, 7, 4, 39, 74, 0xAA, 0x05), // cct
  MiLightRadioConfig(0x7236, 0x1809, 9, 8, 39, 70, 0xAA, 0x05), // rgb+cct, fut089
  MiLightRadioConfig(0x9AAB, 0xBCCD, 6, 3, 38, 73, 0x55, 0x0A)  // rgb
};

In serial port, i try some information (radio is LT8900) - crc wrong etc.. How i can see raw packets, what i recieve from those remotes?

sidoh commented 5 years ago

Compile with DEBUG_PRINTF on. Listening with LT8900 is pretty broken honestly. Would recommend using the nRF24.

itProfi commented 5 years ago

I sniff all button from my remote via nRF24: OEM_partially_milight oem_milight.txt Please, help!!

itProfi commented 5 years ago

Chris, help, please..)

sidoh commented 5 years ago

This is pretty different. Honestly don't think it makes sense to add support unless there is for some reason a lot of people with this same device. Can offer some tips on decoding it and adding support in your own fork, though.

itProfi commented 5 years ago

OK .. If you can, give advice on his support in my fork..

itProfi commented 4 years ago

Chris?

sidoh commented 4 years ago

sorry, not going to have time to give detailed instructions. you can check out this PR adding support for a new remote type:

https://github.com/sidoh/esp8266_milight_hub/pull/490

you'll need to decode the packet structure yourself, though.

itProfi commented 4 years ago

ok, thanks..i try..))

sidoh commented 4 years ago

Nice. It looked pretty similar to RGBW structure, for what it's worth. Gonna close the issue, but happy to continue the discussion. Good luck!

ZeMilkmann commented 3 years ago

@itProfi Did you ever finish implementing this protocol? I have a RGB+CCT lamp with a remote I couldn't sniff with the default configuration but the lamp pairs and reacts to an old CCT remote I had laying around. Trying to sniff that gives me what I have written below, so I assume we may have the same or a very similar protocol

cct packet received (7 bytes):
Request type  : 5A