Just FYI, with the latest Hubitat update, program imports are working much better (because of the change below):
1 Like
OK, so I think I am trying to do a very similar thing that @aaron is doing. I am using three H801's in my kitchen for cabinet lighting and I am wanting to turn on specific channels of the H801 to light up the LED strips on that specific channel.
Anyway, I am not sure how to set up RM to fire off a custom command to the SmartLife RGBW driver? How did you do that in Rule Machine? I am familiar with how to do it via virtual switches but I want to understand the power of @bravenel RM better using the SmartLife RGBW driver.
Just create a new custom command. Select the switch capability, and then select your SmartLife RGBW bulb, then New Custom Command. It will then show you all of the commands available for it, and you can pick one. You can also select parameters if the command takes one or more parameters.
Since @ericm added the support for scenes you may want to use that. Easier to select you color and not have to create a custom command each time. Scenes will capture your H801 color choice and then you just turn on/off kitchen cabinets. Much easier now.
I am using the child devices now for programs. So my TV cycles colors, upper cabinets cycle colors based on holiday (red/green every 6 minutes for Christmas) and I leave the bottom cabinets a nice natural white.
1 Like
For some reason with new driver, Alexa won't control child devices and Googel won't control parent device....
Your problem description is kind of cryptic and I think you meant to post this in the [RELEASE] H801 & Other ESP8266 Based RGBW Controllers (SmartLife) thread to get support from the developer.
Can't determine if Alexa or Google even see the devices based on your description.
Did you check your Alexa or Google Home app to see if the devices are present? You should start there to see where the issue is. For me in Alexa, the steps are from the main Hubitat home screen, click Apps, click Amazon Echo Skill, then select the new devices that the driver builds for you IF you manually created them using the enable. The new driver is creating a virtual switches and you are saying the physical parent device shows up in Alexa and Google Home and is controllable but not the child devices?
I just tested mine and the parent and my child devices are controlling fine by Amazon Echo.
In Google Home parent device is not present, I guess because google does not see it as incompatible. Can't even select in in Google hubitat app.
In Alexa parent device works fine, all child devices are present, but Alexa won't child devices with voice. Just telling me I could not find the device called .... However, and that is really puzzled me, I can control all child device from Alexa app manually. Parent device works fine in Alexa app with voice.
Ahh, maybe it's due to the naming being to close to something else and Alexa can't figure it out by voice? Just for clarity, are you using the Amazon Echo Skill app? Or the original version Amazon Alexa App which is was isn't as flexible as the newer Amazon Echo Skill
I am using Amazon Echo Skill. Was using same skill before with original H801 driver. With original driver, everything worked well. I even removed all devices from Alexa and added them back...
Well, I am out of suggestions other than trying posting this in the forum for the Amazon Echo Skill integration. I think it has something to do with that app more than something to do with @ericm driver. I made him aware of the situation by the way just in case it is on the driver side.
As far as Google Home integration I haven't started that migration process yet.
I don't have any issues that you are having.
Some things you need to know:
- The child device ONLY activates the program. It does NOT turn the H801 on/off
- The Parent device is the ONLY way to turn off your programs
I have a device called TV-RGBW with child program accounts called TV-Program 1, ...6. If I say "Alexa, Turn on TV-Program 6" my lighting effects go on and continue. If I say "Alexa, turn off TV-Program 6" nothing happens. If I say "Alexa, turn off TV-RGBW" the lights turn off.
Using latest code for both app and drivers. No issues.
Actually depends on program, it does turn on. H801. Turn off child, stops the program, but does not turn off H801.
I will try to rename child programs once more, but that is strange because I had same name since ST.
But, are you able to control main device with Google home?
I haven’t tried Google Home. I have a device and will give it a try later tonight. Works with Alexa though.
I think there is something wrong with Alexa from Amazon side. Removed Philips Hue skill from Alexa app completely and yet Alexa will find all my hue lights and scenes. For H801 child devices, I could not use any device name that I had before with old driver, had to come up with complete deferment names otherwise Alexa would answer "that device is not available", but would control same device manually.
Google Home worked too. No issues with current drivers and app.
I think I was completely confused here. Just to be clear. You are referring to the child programs of the Actions Programs not the child devices of the output channels? Sorry, I was referring to the new child devices of the H801 channels that @ericm just released not the special action programming. I am not using those in Alexa.
Where is that at? I think I may have to load a newer version of the H801 firmware. 
1 Like
I also tested Google Home. Everything working there. Not sure what would be up with Alexa, but from a driver point of view there isn't much that could be wrong.
You are right about the programs. Turning off a program child device stops the program from running but it doesn't turn off the LED strip. If you have the strip flashing red and blue with a program and turn that program off it will stop cycling through red and blue and stay on whichever color it ended on.
