@Anticimex said in 
Sensebender Gateway:
MY_CORE_ONLY
Just curious, what does "MY_CORE_ONLY" do? The library mentioned that it should be enabled " if you want to use core functions without loading the framework" . What are the core functions and what is the framework?
Switching to TO92 elements is a great idea and will make soldering much easier to do. However, LE33 still has 0.5 mA supply current and will not be a good choice for battery powered sensors. The TO92 package will always be ON per spec sheet: http://www.st.com/content/ccc/resource/technical/document/datasheet/98/09/12/54/6e/d1/45/36/CD00000545.pdf/files/CD00000545.pdf/jcr:content/translations/en.CD00000545.pdf
The modification I made previously used XC6206 regulator that only requires 1uA supply current. It works pretty well for my battery powered sensors. However, it does not offer a TO92 package. It will be great if someone can suggest an ultra-low supply current voltage regulator in TO92 package.
@ted Hello! Can you share the Eagle file of your version of pcb? I mean this one: http://dirtypcbs.com/view.php?share=19651&accesskey=2e5e31a83bf6fe21510c3bc438e12df7
Sorry for the extreme late response. I've busy with work in the past half year. Hope you still find the attached file useful.
https://dl.dropboxusercontent.com/u/13998152/modified_jBoard-panalize_4x4_hole.brd
@n1ck1355
my only solution is to use two radios, one receives command from the gateway and the other sending command to the bulbs. it might be doable with just 1 arduino by using softSPI.
@n1ck1355
sorry for the delay. Here is what I learned from https://hackaday.io/project/5888-reverse-engineering-the-milight-on-air-protocol
Basically, the mi controller will receive text string and convert them into HEX format and send it to the bulb. The text string should be formatted as the following (+ added for easy of reading, no '+' in the actual command):
ID + color + brightness + button code + seq
The ID is the ID of the bulb to be controlled, it is six byte in ASCII but will be converted into 3 byte HEX before sending to the bulb.
color, brightness and button code are each 2 byte in ASCII and will be converted into 1 byte HEX and send to bulb.
Seq is 2 byte in ASCII but it appears that you can just use "00".
To change color, you need to send a color code (e.g.: "00"=purple, "1B"=red, "40"=yellow,e tc) and using button code "OF".
To change back to white, you use "04" as color code and "13" as button code.
The detailed button code definition can be found here:
https://cdn.hackaday.io/images/1224221432724803073.jpg
Hope this helps.
@n1ck1355 @Jason-Brunk
sorry i'm been really busy with job recently. I used openhab to send the payload to V_VAR1 and S_CUSTOM. When I get home tonight, I'll post the openhab rule file so people can get some sense how to control color.
@Iraklis-Kourtis
The controller is all you need to control the lights. It does not need wifi bridge
@Ł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
@alexsh1
The regulator on the board (AMS1117) consumes several mA at idle. You may need to find an alternative that has uA level quiescent current. I modified the board to use a XC6206 serial LDO (1uA standby current, see my previous post). I have the board manufactured by dirtypcb and have made sensors. Will test the battery life soon.
@Ł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.
