I don’t see that after power failure. Assuming power failure is the same as turning the power off!
Is there any chance somebody could share ‘candy cane’, ‘fireplace’ and ‘christmas lights’ settings?
Amazing work with this project btw, really great!.
I have not experienced it either. Have had several power outages and unplug and plug them in all them time.
@onetrav @pcgirl65 I am trying to gather some more information.
-
What firmware were you running at the time of the issue? You can see the firmware by going to /info. It will show you the version and the date.
-
Did you have to enter the static IP address or any other non-default settings again after connecting it to wifi?
I had a power failure, of my own making, on one of mine. After I powered the device back up, I just got a green light then after 4-5 seconds it went out. I had to actually reflash the device to get it back to life.
That’s on the latest firmware, and right before the power went out on it, it had been flickering. I think I had a loose connection, then I accidentally yanked the power out completely. That could be similar to a brown out condition.
When I flip breakers to do work, and flip them back on, none have had any trouble coming back online. I have 8 of them now I think…
Hey Michael, we seem to be in the same circles:
Eric, the firmware is 2.0.2. I only use the white connection and my lights aren’t dimmable so I don’t think that I need to update the firmware often. I have had the power go out before but this time the power was out for a couple of hours. Once I reconnected them to the wifi, they had their correct Static IP that I had setup originally.
1 Like
Hi Eric.
I’ve just started following this thread as I was searching for something along these lines. Geat job based on the solution and all the interest in this.
Can ask a question relating the native Smartlife WiFi controller. I’ve been searching for the manual for that product online but not found anything yet. I will be ordering one regardless to have a play with it/the solution.
My question relates to how this works out of the box. If its a WiFi controller, can it response to basic http get/post requests to turn it on or change colors from a typical browser?
I was looking for something urber simple to show a red or green light which I’d then control upstream from another trigger. My use case, if a gate was left open (monitored by simple open close sensor) I would then build a in-wall led and have the status controlled by the sensor all packed neatly inside a homemade decora cover plate to give a visual to the gate status, mounted flush near our rear garage door to glance at before letting the dogs run havoc.
I already have ST virtual switches to issue http commands and they work great. Hoping I could achieve the same out of the box??
Thoughts/comments most welcome.
Can you please describe the process of checking the firmware? /info doesn’t mean much to me. Sorry.
go to http://ipaddress/info in your browser.
Replace “ipaddress” with the ipaddress of your H801 controller. It will return info that resembles this:
{“version”:“2.0.5”, “date”:“Oct 11 2016 11:36:38”, “mac”:“xxxxxxxxxxxx”}
The device communicates via http and it is fully compatible with the SmartThings ecosystem. It sounds like you would be able to accomplish what you want with the SmartLife controller, a contact sensor, and SmartLighting. By the way, here is the manual for the device:
https://smartlifeautomated.wordpress.com/2016/08/22/smartlife-rgbw-controller-documentation/
1 Like
Like SHITE! LOL, seriously these are terrible with the firmware they come with. You download an app that sucks, then you connect to it, which takes over your phones WiFi of course, then you can join it to your WiFi, but I couldn’t get it to join to three different routers! So basically, disconnect from WiFi, connect to this, adjust, connect back to your normal WiFi.
The color wheel they give you is nice I guess, very responsive, but honestly they are basically unusable as intended.
Thanks for confirming and sharing. Much appreciated
Ha, thanks for the heads up. I was hoping I could just poke an http post request to turn it on or turn on with xxx color ref.
I would never need to go to their app or webpage other than the initial setup. Sounds like the smart move would be to drop the custom firmware on it and use the app being described here. Was thinking my use case was capable from the native product.
I have other IP based devices that do not work inside ST persay, I simply control them via virtual http uri switch from Smartthings.
Version 2.0.3 for me on all 3 of mine. No non-default settings. May have just been a fluke. I updated my router and they lost Internet during the update and they came back online ok.
With this firmware from Eric you can just send an http message to the device and have it do whatever. Check Eric’s device handler and you can see the postActions. @erocm1231 please let me know if this is in anyway incorrect.
1 Like
Yes, that is correct. Also, the documentation link above has a list of all the http endpoints and how they work.
Sorry, I actually missed that post somehow!
So, I think I got everything done right. I got the firmware installed, and connected to smartthings. I can control the color of the strip, but I have two problem. I have firmware 2.0.4, and I just updated to the latest device handler and app.
1: When I click on the “Configure” button, it doesn’t do anything.
2: The programs don’t work. I get the following error in the Live Logging.
bda519cd-943c-41ec-b4dd-e7e5a5f00f73 8:51:31 PM: error groovy.lang.GroovyRuntimeException: Ambiguous method overloading for method script14764912615001522078577#sendEvent.
Cannot resolve which method to invoke for [null, class java.util.LinkedHashMap] due to overlapping prototypes between:
[class java.lang.String, interface java.util.Map]
[class physicalgraph.app.DeviceWrapper, interface java.util.Map] @ line 715
bda519cd-943c-41ec-b4dd-e7e5a5f00f73 8:51:31 PM: debug getChildDevices(false), children=1
bda519cd-943c-41ec-b4dd-e7e5a5f00f73 8:51:31 PM: debug physicalHandler called with event: name:switch1 source:DEVICE value:on isStateChange: true isPhysical: false isDigital: false data: null device: SmartLife RGBW Controller (192.168.1.107)
c66f82cc-71ea-434d-bb6d-f4f812022f23 8:51:30 PM: debug {"running":"true", "program":"1", "power":"on"}
c66f82cc-71ea-434d-bb6d-f4f812022f23 8:51:30 PM: debug uri /program?value=f~00004d~100-1500_x~b3~100_g~000000~100_x~cc~100&repeat=-1&number=1
c66f82cc-71ea-434d-bb6d-f4f812022f23 8:51:30 PM: debug onOffCmd(1, 1)
Any thoughts?
Ok, I was able to get the programs working. I must have had the program wrong or something, which was giving the error. Still no configure page though.
Also, both Yellow and Orange are Green.
The device in the ST app has an edit option with some settings. The configure button just preps the device by sending your settings and defaults, won’t show anything and shouldn’t be needed more than one or two traps when first setup.
Gotcha, thanks. I thought is opened the web configuration page.
This is a great setup! I ordered several of these and things are starting to trickle in. I also ordered an FTDI adapter that is still on the slow boat however was curious since I have a computer here with a serial port if I could just connect the H801 to the serial port and flash it using that?
I read on another site that if I power it with just 12v at the VCC/GND I just need the data RX/TX connected. So far I am not having any luck 
Here is some of the output I am getting when trying to flash directly from my serial port
C:\FlashTool>esptool.exe -vv -cd nodemcu -cb 115200 -cp COM4 -ca 0x00000 -cf H801.bin
esptool v0.4.6 - © 2014 Ch. Klippel ck@atelier-klippel.de
setting board to nodemcu
setting baudrate from 115200 to 115200
setting port from COM1 to COM4
setting address from 0x00000000 to 0x00000000
espcomm_upload_file
stat H801.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
espcomm_send_command: receiving 36 bytes of data
warning: espcomm_send_command: wrong direction/command: 0x00 0x08, expected 0x01 0x08