@Steveuk23 Try this…
Thanks for that I never spotted that feature 
WebCoRE isn’t sending the appropriate info to the setColor command. It isn’t working with my hue bulbs either. setColor should receive a map of color information. i.e. setColor([hex:#00ff00, level:30]). Although, SmartThings documentation doesn’t list hex as a valid attribute anymore (It used to), the majority of color devices still support it. WebCoRE is sending a single string with the hex value:
setColor being called with #0000ff instead of setColor being called with [hex:#0000ff]
can somebody please help me with this
it will not flash for me i keep on getting
" espcomm_sync failed
spcomm_open failed"
error
also it would really help if anyone had been more specific as to how to wire the RX and TX pins
nobody bothered to specify if it is supposed to go RX to RX and TX to TX or if it is RX to TX and TX to RX i tried it both ways and it is not working
also not specified is what to do with the jumper , do i unjump it once i power on the board
or can i leave it jumped the whole time ,turn it off , unjump it and turn it back on?
also i am using an FT232 FTDI from inland i bought at microcenter
i also went into device manager and tried to set the baud rate to match the 115200 in the command which it was not set at by default , it did not help
and my FTDI has a switch ,5 or 3.3v i set it at 3.3v ,but there is no 3.3v power out pin so i just use the 12v input to power the h801 and connect RX ,TX and GND to the FTDI
here is the log
serialport_receive_C0: 00 instead of C0
resetting board
trying to connect
flush start
setting serial port timeouts to 1 ms
setting serial port timeouts to 1000 ms
flush complete
espcomm_send_command: sending command header
espcomm_send_command: sending command payload
serialport_receive_C0: A0 instead of C0
trying to connect
flush start
setting serial port timeouts to 1 ms
setting serial port timeouts to 1000 ms
flush complete
espcomm_send_command: sending command header
espcomm_send_command: sending command payload
serialport_receive_C0: 00 instead of C0
trying to connect
flush start
setting serial port timeouts to 1 ms
setting serial port timeouts to 1000 ms
flush complete
espcomm_send_command: sending command header
espcomm_send_command: sending command payload
espcomm_send_command: receiving 36868 bytes of data
read 0, requested 1
error: failed reading byte
warning: espcomm_send_command: cant receive slip payload data
warning: espcomm_sync failed
error: espcomm_open failed
C:\Users\anthony\Desktop\ESP easy>esptool.exe -vv -cd nodemcu -cb 11
3 -ca 0x00000 -cf SmartLifeRGBWController.ino.generic.bin
esptool v0.4.6 - © 2014 Ch. Klippel
setting board to nodemcu
setting baudrate from 115200 to 115200
setting port from COM1 to COM3
setting address from 0x00000000 to 0x00000000
espcomm_upload_file
stat SmartLifeRGBWController.ino.generic.bin success
setting serial port timeouts to 1000 ms
opening bootloader
resetting board
trying to connect
flush start
setting serial port timeouts to 1 ms
setting serial port timeouts to 1000 ms
flush complete
espcomm_send_command: sending command header
espcomm_send_command: sending command payload
read 0, requested 1
trying to connect
flush start
setting serial port timeouts to 1 ms
setting serial port timeouts to 1000 ms
flush complete
espcomm_send_command: sending command header
espcomm_send_command: sending command payload
read 0, requested 1
trying to connect
flush start
setting serial port timeouts to 1 ms
setting serial port timeouts to 1000 ms
flush complete
espcomm_send_command: sending command header
espcomm_send_command: sending command payload
read 0, requested 1
resetting board
trying to connect
flush start
setting serial port timeouts to 1 ms
setting serial port timeouts to 1000 ms
flush complete
espcomm_send_command: sending command header
espcomm_send_command: sending command payload
read 0, requested 1
trying to connect
flush start
setting serial port timeouts to 1 ms
setting serial port timeouts to 1000 ms
flush complete
espcomm_send_command: sending command header
espcomm_send_command: sending command payload
serialport_receive_C0: 70 instead of C0
trying to connect
flush start
setting serial port timeouts to 1 ms
setting serial port timeouts to 1000 ms
flush complete
espcomm_send_command: sending command header
espcomm_send_command: sending command payload
serialport_receive_C0: B0 instead of C0
resetting board
trying to connect
flush start
setting serial port timeouts to 1 ms
setting serial port timeouts to 1000 ms
flush complete
espcomm_send_command: sending command header
espcomm_send_command: sending command payload
serialport_receive_C0: 00 instead of C0
trying to connect
flush start
setting serial port timeouts to 1 ms
setting serial port timeouts to 1000 ms
flush complete
espcomm_send_command: sending command header
espcomm_send_command: sending command payload
serialport_receive_C0: 00 instead of C0
trying to connect
flush start
setting serial port timeouts to 1 ms
setting serial port timeouts to 1000 ms
flush complete
espcomm_send_command: sending command header
espcomm_send_command: sending command payload
serialport_receive_C0: 00 instead of C0
warning: espcomm_sync failed
error: espcomm_open failed
C:\Users\anthony\Desktop\ESP easy>esptool.exe -vv -cd nodemcu -cb 11
3 -ca 0x00000 -cf SmartLifeRGBWController.ino.generic.bin
esptool v0.4.6 - © 2014 Ch. Klippel
setting board to nodemcu
setting baudrate from 115200 to 115200
setting port from COM1 to COM3
setting address from 0x00000000 to 0x00000000
espcomm_upload_file
stat SmartLifeRGBWController.ino.generic.bin success
setting serial port timeouts to 1000 ms
opening bootloader
resetting board
trying to connect
flush start
setting serial port timeouts to 1 ms
setting serial port timeouts to 1000 ms
flush complete
espcomm_send_command: sending command header
espcomm_send_command: sending command payload
read 0, requested 1
trying to connect
flush start
setting serial port timeouts to 1 ms
setting serial port timeouts to 1000 ms
flush complete
espcomm_send_command: sending command header
espcomm_send_command: sending command payload
read 0, requested 1
trying to connect
flush start
setting serial port timeouts to 1 ms
setting serial port timeouts to 1000 ms
flush complete
espcomm_send_command: sending command header
espcomm_send_command: sending command payload
read 0, requested 1
resetting board
trying to connect
flush start
setting serial port timeouts to 1 ms
setting serial port timeouts to 1000 ms
flush complete
espcomm_send_command: sending command header
espcomm_send_command: sending command payload
read 0, requested 1
trying to connect
flush start
setting serial port timeouts to 1 ms
setting serial port timeouts to 1000 ms
flush complete
espcomm_send_command: sending command header
espcomm_send_command: sending command payload
read 0, requested 1
trying to connect
flush start
setting serial port timeouts to 1 ms
setting serial port timeouts to 1000 ms
flush complete
espcomm_send_command: sending command header
espcomm_send_command: sending command payload
read 0, requested 1
resetting board
trying to connect
flush start
setting serial port timeouts to 1 ms
setting serial port timeouts to 1000 ms
flush complete
espcomm_send_command: sending command header
espcomm_send_command: sending command payload
read 0, requested 1
trying to connect
flush start
setting serial port timeouts to 1 ms
setting serial port timeouts to 1000 ms
flush complete
espcomm_send_command: sending command header
espcomm_send_command: sending command payload
read 0, requested 1
trying to connect
flush start
setting serial port timeouts to 1 ms
setting serial port timeouts to 1000 ms
flush complete
espcomm_send_command: sending command header
espcomm_send_command: sending command payload
read 0, requested 1
warning: espcomm_sync failed
error: espcomm_open failed
C:\Users\anthony\Desktop\ESP easy>esptool.exe -vv -cd nodemcu -cb 11
3 -ca 0x00000 -cf SmartLifeRGBWController.ino.generic.bin
esptool v0.4.6 - © 2014 Ch. Klippel
setting board to nodemcu
setting baudrate from 115200 to 115200
setting port from COM1 to COM3
setting address from 0x00000000 to 0x00000000
espcomm_upload_file
stat SmartLifeRGBWController.ino.generic.bin success
setting serial port timeouts to 1000 ms
opening bootloader
resetting board
trying to connect
flush start
setting serial port timeouts to 1 ms
setting serial port timeouts to 1000 ms
flush complete
espcomm_send_command: sending command header
espcomm_send_command: sending command payload
read 0, requested 1
trying to connect
flush start
setting serial port timeouts to 1 ms
setting serial port timeouts to 1000 ms
flush complete
espcomm_send_command: sending command header
espcomm_send_command: sending command payload
read 0, requested 1
trying to connect
flush start
setting serial port timeouts to 1 ms
setting serial port timeouts to 1000 ms
flush complete
espcomm_send_command: sending command header
espcomm_send_command: sending command payload
read 0, requested 1
resetting board
trying to connect
flush start
setting serial port timeouts to 1 ms
setting serial port timeouts to 1000 ms
flush complete
espcomm_send_command: sending command header
espcomm_send_command: sending command payload
read 0, requested 1
trying to connect
flush start
setting serial port timeouts to 1 ms
setting serial port timeouts to 1000 ms
flush complete
espcomm_send_command: sending command header
espcomm_send_command: sending command payload
read 0, requested 1
trying to connect
flush start
setting serial port timeouts to 1 ms
setting serial port timeouts to 1000 ms
flush complete
espcomm_send_command: sending command header
espcomm_send_command: sending command payload
read 0, requested 1
resetting board
trying to connect
flush start
setting serial port timeouts to 1 ms
setting serial port timeouts to 1000 ms
flush complete
espcomm_send_command: sending command header
espcomm_send_command: sending command payload
read 0, requested 1
trying to connect
flush start
setting serial port timeouts to 1 ms
setting serial port timeouts to 1000 ms
flush complete
espcomm_send_command: sending command header
espcomm_send_command: sending command payload
read 0, requested 1
trying to connect
flush start
setting serial port timeouts to 1 ms
setting serial port timeouts to 1000 ms
flush complete
espcomm_send_command: sending command header
espcomm_send_command: sending command payload
read 0, requested 1
warning: espcomm_sync failed
error: espcomm_open failed
C:\Users\anthony\Desktop\ESP easy>
Thanks for this
I’ll put a last on their forum ask them to check it.
I might try the same method with the older CoRE maybe that works as expected.
I’ve not actually got a device connected at the moment as I’ve been trying to reset using your method of unplugging but it didn’t work as I had WiFi issues , but I have only tried it twice 
Been so busy with other things
Cheers
Hi
To me it seems like it’s not entering boot mode.
Can you confirm what device your trying to flash ?
What do you mean by removing the jumper a are you talking about the power one you have?
This is a picture I took of my device as I kept getting the pins wrong but this way worked
So mine went
Power
Tx
Rx
Ground
Bought an AL-02 unit. Hoping to have some success with it and this FW. I will let you know. if it works ill be quite excited with getting some more.
i am trying to flash the lixada H801 and i mean the j3 jumper
i tried it both ways now , left on and taken off after i turn on the controller
pretty sure it is in flash mode , when i switch on the controller the green LED blinks once
it does not work either way , funny i see one of the RX TX lights on the FTDI blinking sometimes
maybe i would have better luck with this adapter
?
http://www.microcenter.com/product/389986/osepp_ftdi_breakout_board
or the adafruit usb to serial cable thing, not sure if that is suitable for this though
so does this look like a driver problem? i saw a post in the thread about windows installing a newer driver, so i followed the link and installed the legacy drivers after removing the ones windows installed , i rebooted a few times and reinstalled the drivers a few times still didn’t flash
should i break down and solder the pins to the board? could it be connection from the FTDI to the controller or does this look like the problem is between the PC and FTDI?
EDIT: shit i think the board is bricked now, when i jumper j3 and switch it on no lights come on or flash now
when i switch it on without the jumper the green light stays on steady, before the red and green lights came on ,i hooked it up to the strip and the strip just stay on steady blue and white
is there a way to reset it?
Ah my fault I’m getting my posts confused I thought I was taking about sonoffs.
I didn’t solder anything when flashing my board I held the pins in place and with the jumper I snapped 2 header connectors off and twisted the ends round to make a contact and held them in place also.
So when I powered it on I pulled the jumper off and stated the flash.
If you want to reset it look about 4 posts above as someone has linked on the process of resetting by unplugging and plugging back in.
ok i am pretty sure my h801 is bricked at this point it no longer goes into flash mode
i had to order another one so in the mean time i figured i would test the FTDI further so i tried to get it to write to a pro mini and no luck there either
the arduino commuinty sucks they have no coherent information anywhere on how to even get these FTDI POS to work with windows ,i have looked everywhere and i find no answers at all on how to get proper drivers to make FTDI work in windows
how do they get anything working at all is beyond me
nothing works,this is just too much aggravation i should have just bought the dresden controllers instead and called it a day, these arduino people can not even explain how to get their programming tools to work at all
F this S
It’s strange that I bought a generic one off ebay…
and let Windows install the drivers it wanted and it worked no problem.
Maybe you’ve got a bad one somehow
i don’t know and mine has a chip that says FTDI, probably a counterfeit ,it does not look like the logo is engraved at all , but yours looks like it is definitely not a genuine chip
so you can use this for both the h801 and for a pro mini too right?
i do not really get what the difference is between all these models other than some having 3.3 or 5v pins or both,too bad the seller in UK though i am in the US
Yeah i don’t really know the difference either must have just got lucky.
I don’t know if they work with the pro mini as I don’t have one but they did work with the H801 and the Sonoff devices
The only reason I chose this one is so I wouldn’t be messing changing jumpers for the power as it had both pins.
Try uninstalling the drivers and restart and then let it install the drivers and keep the default properties for it.
You haven’t set it onto 5v by any chance have you?
yeah 5 days straight now and i can not get the FTDI USB to serial working i tried every driver i installed them 3 different way, i let windows install them, i did it manually ,and i used an .EXE installer
none of it worked i also installed legacy drivers from a time before FTDI gate and the bricking drivers , i downloaded the mprog3.5 tool to check for bricks and unbrick but i do not think my board is bricked
seems like the biggest problem is getting a working USB to serial adapter the drivers all suck they do not work at all on windows or on mac, i keep seeing the same posts on arduino forums lots of people can not make this crap work with either windows or mac , i tried it on 2 computers, one on window 7 and one on win8.1 64bit
i also tested my mini USB cables which was not easy to do because i couldn’t think of any devices that use mini USB that use data over the cable ,i had an adapter i ordered by mistake from china for like 38 cents ,mini USB female to micro USB male, so i was able to use it to test my cables, turns out 2 out of 3 were bad so i suggest people to make sure their mini usb cable carries data
not just power , but even the one working cable i have still made no difference
these programmers just do not work in windows the drivers don’t work
even older drivers from before they started including code to make clones not work don’t work , they didn’t need to worry about “clones” because the drivers didn’t even work with original chips even before they modified them
you have a better chance of hitting the lotto than you do of getting USB to serial to work in winblows or mac OS
supposedly it works in linux but i don’t use it
Hello,
I’m trying to use a nodemcu, which is a developer board that uses ESP8266 wifi chip (same as h801), to control my led strip. Has anyone tried to use this board?
I can flash the developed firmware on the chip but, before I can go any further on the project, I have an important doubt regarding the data connection, specifically the gpio port, between the board and the led strip.
This board has several gpio ports. My guess is, since the controller is the same, the communication ports with the led strips for the H801 controller (R,G,B,W1 and W2) are the same ports marked on the board. Just the labeling is different because nodemcu board uses the same id as the chip.
So, my question is: Can you tell me which ports, embedded on the code, the chip uses to communicate with the led strip? Something like R(RED)-GPIO5; B(BLUE)-GPIO4; W2(Warm white)-GPIO6…etc. This will determine where my wire connections between the strip and the nodemcu will be soldered.
Thank you
Best regards
Have a scroll up the comments, you will theres a post by me where I have answered this. I think it was 8,9,10,11,12 or something like that, but as I’m not on my laptop is quite hard to find ATM.
Hi.
Thank you. I looked above and couldn’t find your post with gpio ports.
I did find an erocm1231 post with these ports:
R-15
G-13
B-12
W1-14
W2-4
Can you confirm this is correct? Which of the W is the warm white?
Thank you
Hi, I’ve ordered two of the H801s and I’m excited to get these working with my under cabinet lights… I have a Fibaro RGBW but am probably going to return it in favor of this!
My question is about a physical switch. These are for under cabinet lights and I’d like to put a capacitive touch sensor on both of them individually. I was thinking of using this or this. However, from what I read here, the J3 jumper needs a momentary switch, which means complete the circuit, not send a digital output. (go easy on me, I’m a newbie to electronics 
)
Has anyone used a touch sensor as a physical switch? What did you use? Or, what would I have to add onto the above products to get it to work?
Or… do I need to post elsewhere about this?
Thanks!
You need to make sure that whatever switch you use, its output is valid for the H801. I.e. if the switch outputs 5V when touched, then make sure that you drop it to 3V3 when connecting to the H801, you could do this with either a resistor divider or something like an opto-isolator. You should power the switch from the H801 so that the voltages are tied together, you can do this through the header pins (that would otherwise be used for flashing, since that gives you access to 3V3 (and maybe 5V I cant remember).
Capacitative switches will be momentary by their design and this should work fine, but the key thing is to make sure the voltages are right and that the H801 doesnt get damaged by the signal, whilst also being able to interpret the signal. You might also need to think about debouncing the switch output, since the H801 probably doesnt have debouncing code ( @erocm1231 does it? ) - this effect means that what feels like a single switch press to you might be interpreted as multipl switch presses by the circuit (for example if your finger moves slightly as you go to press the switch).
Whilst I could give you lots more guidance on this, I would say there are lots of questions that still need answering, and it is probably worth you doing a bit of research first (unless somebody posts that they have done exactly this).
I hope that is partially helpful as a starting point!
Hello,
Continuing my adventure…as I said previously, simply put, I’m trying to create a device like this using the developed integration with smarthings.
I have all the electronics schematic I need and i will be using a mosfet do dim my white lights. To do this, the gpio port 14 have to control the mosfet (control ground). Is this correct or am I missing something?
Thank you