I have the solution that is perfect for me now. It wouldn’t have worked for me without Smartthings.
It’s super fast and doesn’t even drop lights in the Hue Scene changes. I have changed the direct calling interface to all connected devices to Simple Control. It controls my Hue Scenes that include 38 hue lights. Also my 11 Lutron switches and lamp dimmers which are not supported by smart things. It also controls all my electronics. Blasters allow me to turn off and on the 2 TVs and 1 receiver that doesn’t support IP toggle on. Simple Control interface to Echo doesn’t work properly and requires way too many words because it’s supported as a skill that keeps crashing on me. So Smartthings fixes not only that problem but adds tons of rule based home automation.
Here’s what it looks like for voice activated scene changes:
Amazon Alexa talks to Smart Things Switch, Simple Control trigger runs when the ST switch is turned on to call Simple control scene that calls Hue and Lutron lights at the same time.
I setup 1 virtual switch setup per scene in Smartthings. I have 1 rule running in rule engine that looks for a switch to be triggered and turns them all off so I can call them back to back without issues.
I have setup smartthings virtual presence sensors that require one of many to be present in order to trigger mode changes on entry. Mode changes on entry calls Simple control scenes depending on rules in Smartthings.
My system so far has:
SmartThings Hub - 2 outlets, 1 GE fan control, 3 Open Close Sensors(1 for Rubix Cube app that changes colors for all hue lights, 2 motion detectors
Hue Bridge - 38 connected Hue lights
Lutron Caseta Bridge - 4 in wall dimmer switches, 7 Dimmers
Simple Control - 2 Televisions, 2 Apple TVs, 2 Receivers, Cable Box, iPad acts as always on remote watching for iPhone sensor (can trigger presence via toggle switch)
Nest, Nest Camera
Amazon Echo (With 2 dots on the way) I feel like Alexa is my new wife and I have two children on the way…lol. No time for dating when setting all this up.
On my computer required applications:
Airfoil - in order to get the receivers linked via my computer and input sources. It supported synced streaming either through Airplay to receivers or connecting to apple TVs directly.
Simple Sync - for the Simple Controls. It links my remotes and saves my configurations.
Chroma - for computer interface for Hue lights (I tested all the apps and this is the best one)
ObyThing Music - So that SmartThings can call my computer and play messages through my receivers.
iPhone Applications that are necessary:
BeaconThings (For my future Beacons coming in the mail)
Necessary SmartThings Apps:
Hue Lights and groups and Scenes (Oh My!) Of course. I just use it for the groups though and a few individual lights.
Echo (Maybe Alexa Helper- I haven’t had to use it yet)
Change Nest Mode
Hello Home Cube (It lets me call a routine per side and just control all lights rather than figuring out the color saturation also I can call voice messages through ObyThing which is cool)
ObyThing Music Apps
Rule Machine (A necessity)
Simple Sync Connect
Simple Sync Trigger
Really the hardest part of the entire process was setting up hue scenes with 38 lights. I used the iPhone app lumifi to connect to all my hue lights and it gives examples for 9 different really good scenes that it setups up for you out of the box. I really used it as an idea generator for scenes. Then I needed to change the lights based on Groups which isn’t supported in lumifi. You have to be able to match the light color of the similar strips, etc and you can’t due that by just looking at one screen and moving into the next light. They have to be controlled together. I used Huemote on the iPhone or Chroma on the Mac to make changes to grouped lights. Both support groups really well and allow for fast editing of the lights. (Hue app doesn’t support groups and if you try to use hue groups in the app in your scenes to make changes you will pull your hair out. They aren’t labeled and lights just randomly pop in an out of the groups). After I was happy with the changes. Then I opened the Hue app and navigated to Lights Then in the top right clicked create and saved it as a scene.
Then here’s where it gets a little messy. Hue doesn’t delete Scenes. So if you aren’t perfect in the first try on your scene creation and make a change in the hue app and save the scene again it will show up in the scenes list twice. After you delete it in the hue app it isn’t deleted on the bridge. This is really terrible programming on Hue’s part. But they have finally opened it up in the api and you can delete it through the API to keep everything clean for you really really easily. Here’s how:
Get an User ID for the Hue API Debug tool. http://www.developers.meethue.com/documentation/getting-started
Once you have followed the directions above to get a userid connected to the hue bridge:
In the URL put:
/api/(Your Username here from above)/scenes/
Call Get command.
Look for the scene you want to delete. The ID is the first entry.
In the URL put:
/api/(Your Username here from above)/scenes/(ID from the scene you want to delete)
You are all set and you’ve cleaned up your scenes.