Mi-Light controller for Mysensors
-
Hi Ted
I understand now:)
I changed remote id to diffrent values but now my first dummy switch paired to my first bulb doesn't work.
I need to have another arduino to control another bulb?
Best regards -
Another question...
Is there possibility to add to this code another one to control DHT11 temp and humidity sensor (from my sensors library)
I wanted to have 2 thing in one:)
Best regards -
Hi Ted
I understand now:)
I changed remote id to diffrent values but now my first dummy switch paired to my first bulb doesn't work.
I need to have another arduino to control another bulb?
Best regards@Łukasz-Kostrzewa
The way I'd suggest is to modify the program to add more switches, each switch uses a different remote ID. Alternatively, you can use your controller to generate the necessary command string (with custom ID specific to the bulbs you want to control) and send it to the custom node as an ASCII string. The custom node will relay whatever command it receives to the bulbs. -
Thx for answer
I am noob in programming. Maybe You can post an example how to modify the code?
Best regards
-
Excellent project! I have implemented reversed engineering for (1) some switches (2) LightWaveRF sockets. I tried to implemented Mi-Light with Mysensors but I having spent some time I decided to just buy a WiFi hub ($7) as it is natively supported in Domoticz.
Mi-Light is an excellent product price wise compare to Philips Hue
-
Hi
Anyone have idea how to modify the code to pair domoticz to more than one bulb?
With actual code I am able to ON/OFF only one bulb :(Any idea?
Best regards
-
Anybody?
-
I would also like this to work with domoticz but as I lack the skills nececary I am now waiting on the next RFlink firmware witch is adding the feature of controlling mi-lights.
I still think that the node/repeater as descripbed in this topic would be better but as I have no options the RFlink is better than using the standard milight bridge an any way.I have added a NRF24L01 PA to my RFlink gateway and am hoping that the range will cover my whole house.
-
Thx for info
Best regards -
I have new problem.
I paired wrong bulb and now I can't unpair it.
How to do that?
Best regards -
Hi Ted,
Your project looks really amazing and I think it is exactly what I was looking for.
I want to change my lighting at home. I am thinking of adding 8 LED strips that will be controlled by 2 x 4 Mi-Light remote controls and 2 x wifi bridges. As I would like to still be able to use the wall switches to turn them on/off I was thinking of using your solution. Do you think it will be feasible with your project? Also is there a way to reduce the wifi bridges to 1 instead of having 2?Thank you for this great project!
Iraklis
-
I have new problem.
I paired wrong bulb and now I can't unpair it.
How to do that?
Best regards@Łukasz-Kostrzewa
sorry for the delay. you need to send the unpair command right after turning on the light. see https://hackaday.io/project/5888-reverse-engineering-the-milight-on-air-protocol -
Hi Ted,
Your project looks really amazing and I think it is exactly what I was looking for.
I want to change my lighting at home. I am thinking of adding 8 LED strips that will be controlled by 2 x 4 Mi-Light remote controls and 2 x wifi bridges. As I would like to still be able to use the wall switches to turn them on/off I was thinking of using your solution. Do you think it will be feasible with your project? Also is there a way to reduce the wifi bridges to 1 instead of having 2?Thank you for this great project!
Iraklis
@Iraklis-Kourtis
The controller is all you need to control the lights. It does not need wifi bridge -
Has this been converted to 2.0?
Also, to build the controller for this i don't need anything special other than the arduino + nrf24l01 correct? I am VERY interested in this
-
i got 2 of my milight bulbs in today. Just wondering if anyone is still using this?
-
@Jason-Brunk said:
n today. Just wondering if anyone is still using this?
I would like to use this solution as it seams to be really great to have both a NRF/Mi-light-Repeater for every "node". But my skils are not enough to make this work with RGB-strips/bulbs and to have it working with domoticz. I am using the standard Domoticz way of controllign them using the original mi-light gateways and have also experimented with RF-link mi-light control.
But my dream-scenario is that some nice coding-wiz will post a complete solution that even newbies can integrate this in this forum-thread. But I would not count on it.
-
I have done a little bit of tinkering with it today. i have not cleaned up the code yet, but I have been able to get my arduino repeater to pair with one of the lights, and turn it on and off. My progress so far.
- Convert to using the mysensor 2.0 framework
- setup a bulb and paired
- can turn bulb on and off
My next step is to see if i can change colors on the bulb. The only thing I noticed is there is a small delay when switching the radio between the mysensors rf and the milight rf protocol. I may later see if it's possible to do 2 radios. But for now progress is being made with a repeater node.
Once it's working, Ill see if i can post some samples of how I controlled it via mqtt. (I use openhab)
If the original author of this sketch is interested I will provide him current code progress. Or I can throw it on github if anyone is interested in tinkering with it. I definitely want to get some documentation together for how to get multiple bulbs working on it.
-
I have put my mods on github.
https://github.com/brunkj/MySensorsMiLight/
I have not been able to mess with it since the weekend. Still trying to get some info on the RGB part. If anyone wants to take a shot at it let me know if you make any progress :)
-
spent some more time working on this. Still not having luck figuring out a what to send to the V_VAR1 to get the bulb to do anything
I can send simple on off for S_LIGHT V_STATUS
if (message.type == V_STATUS) { //Serial.println("triggered V_STATUS"); mlr.begin(); // Change light status Serial.println(message.getBool()); if ( message.getBool()) { Serial.println("here"); // Serial.println("triggered ON"); sendCommand (outgoingPacket_on, sizeof(outgoingPacket_on)); } else { // Serial.println("triggered off"); sendCommand(outgoingPacket_off, sizeof(outgoingPacket_off)); } _begin(); }Easy. But the V_VAR1 on S_CUSTOM I can't figure out what to put in the payload
if (message.type == V_VAR1) { // Serial.println("triggered V_VAR1"); incomingCommand = (char *)message.getCustom(); Serial.println((char *)message.getCustom()); mlr.begin(); Serial.println("#############"); for (int i=0; i<sizeof(outgoingPacket); i++) { outgoingPacket[i] = 16*char_to_uint8_t(incomingCommand[i*2]) + char_to_uint8_t(incomingCommand[i*2+1]); Serial.println(outgoingPacket[i]); } Serial.println("#############"); Serial.write(outgoingPacket, 7); sendCommand(outgoingPacket, sizeof(outgoingPacket)); _begin(); }I have referenced the hacking milight protocol pages and many other, I just can't seem to get it right to get my bulb to do anything.
Anyone want to take a shot at it? or have payload data I could try?
full sketch
#define MY_DEBUG #define MY_RADIO_NRF24 #define MY_REPEATER_FEATURE #include <MyConfig.h> #include <MySensors.h> #include <SPI.h> #define CE_PIN 9 //CE and CSN pin for nrf24 radio #define CSN_PIN 10 #include <nRF_24L01.h> #include <avr/power.h> #include <printf.h> #include "PL1167_nRF24.h" #include "MiLightRadio.h" #define NODE_ID 100 #define mi_command_repeat 30 //# of times to resend the command to bulb RF_24 mi_radio(CE_PIN, CSN_PIN); PL1167_nRF24 prf(mi_radio); MiLightRadio mlr(prf); // B0-176 F2-242 EA-234 6D B0 02 f0 static uint8_t outgoingPacket_on[7] = { 0xB0, 0xF2, 0xEA, 0x6D, 0x91, 0x03, 0x00}; //the first three #s are remote ID, replace with yours static uint8_t outgoingPacket_off[7] = { 0xB0, 0xF2, 0xEA, 0x04, 0x91, 0x04, 0x00}; uint8_t outgoingPacket[7]; #define sizeofincomingCommand 15 //command comes in text form of 7 uint8_t, with an additional NULL at end char *incomingCommand; //array for incoming command boolean mi_radio_state = false; void presentation() { //Send the sensor node sketch version information to the gateway sendSketchInfo("Milight controller", "1.0"); } void setup() { //clock_prescale_set(clock_div_2); //for a barebone atmega328p, this will make the CPU running at 4MHz. //Serial.begin(115200); // The third argument enables repeater mode. //Send the sensor node sketch version information to the gateway present(0, S_LIGHT); present(1, S_CUSTOM); } void receive(const MyMessage &message) { // The command will be transmitted in V_VAR1 type, in the following 7 byte format: ID1 ID2 ID3 COLOR BRIGHTNESS COMMAND. // see https://hackaday.io/project/5888-reverse-engineering-the-milight-on-air-protocol Serial.println(message.type); if (message.type == V_STATUS) { //Serial.println("triggered V_STATUS"); mlr.begin(); // Change light status Serial.println(message.getBool()); if ( message.getBool()) { Serial.println("here"); // Serial.println("triggered ON"); sendCommand (outgoingPacket_on, sizeof(outgoingPacket_on)); } else { // Serial.println("triggered off"); sendCommand(outgoingPacket_off, sizeof(outgoingPacket_off)); } _begin(); } if (message.type == V_VAR1) { // Serial.println("triggered V_VAR1"); incomingCommand = (char *)message.getCustom(); Serial.println((char *)message.getCustom()); mlr.begin(); Serial.println("#############"); for (int i=0; i<sizeof(outgoingPacket); i++) { outgoingPacket[i] = 16*char_to_uint8_t(incomingCommand[i*2]) + char_to_uint8_t(incomingCommand[i*2+1]); Serial.println(outgoingPacket[i]); } Serial.println("#############"); Serial.write(outgoingPacket, 7); sendCommand(outgoingPacket, sizeof(outgoingPacket)); _begin(); } //gw.begin(incomingMessage, NODE_ID, true); } void sendCommand(uint8_t mi_Command[7], int sizeofcommand) { for (int i = 0; i < mi_command_repeat; i++) { mlr.write(mi_Command, sizeofcommand); } } uint8_t char_to_uint8_t(char c) { uint8_t i; if (c <= '9') i = c - '0'; else if (c >= 'a') i = c - 'a' + 10; else i = c - 'A' + 10; return i; } -
@Jason-Brunk
unfortunately i havnt got my own milight bulbs but for what i've seen on the
reverse engineered protocol page the payload must be something like
"07B0F2EA359001B9ACF9" for all on or
"07B0F2EA7D910FD4EC72" for greenor the part "07B0F2EA" must be the ID so the payload
is somethink like "359001B9ACF9" for all on and
"7D910FD4EC72" for green