Very cool, thanks! I just placed my order for a hub. I'll try out your app and report back.
Also cool to hear it's easy to program custom apps in Groovy. I look forward to getting started!
1 Like
I do something similar but currently just use temperature per mode in rule machine. Basically if it turns on whilst in this mode go to this Kelvin 
.
You would just do when this button pressed then use temperature per mode a trigger.
1 Like
Hi, you mentioned you have your bulbes directly connected to your HE. Are those zwave bulbes? People here do not recommend it on zigbee. I want to get rid of the Hue bridge... so maybe your set up is a working example?
Mine are but they are my only ZigBee devices, only then is it a good idea to have them directly paired.
All of my bulbs are Wi-Fi (MagicHome) or Zigbee (both Hue and Osram).
As @BorrisTheCat said, It’s not recommended to do it this way, but I’ve never had an issue with any repeaters or anything. I have a bunch of other Zigbee devices on my network, too. My bulbs are always on, though. I digitally turn them off and on with the switches I built in my SmartThings Button teardown thread.
Okey then. maybe I try it room by room from unimportant to more used.
thanks.
also thanks @BorrisTheCat
2 Likes
Just getting started with my set up using RM and Sylvania Lightify switches. Strangely upon first press, the Hue bulb goes to a full bright, soft white (what seems to be) default state, and only upon second press of the same button does it go to my setting per the active condition in RM. You run into this at all? I'm still hacking at it...
I ran into a similar problem, but with sengled bulbs, (and they simply didn't turn on after first press rather than a white default even though the rule activated per the logs) so I think we can probably rule out the bulbs as the cause. Do you use the groups and scenes app? I found that if I remove the bulbs from a group then reprogram the rule to perform the action on each bulb individually it fixes the problem. This is of course a workaround.
Nope but if sounds like you haven't configured the switch on hubitat yet. Make sure you click configure on the device page for the switch then do the special button press to wake up the switch. What are you using to take the button command? RM or button controller.
Hmmm... groups and scenes app? I should probably check that out. Bear with me, I'm very green at this (though I work with computers for a living so hopefully it will quickly click (no pun intended)). What I'm doing is all in RM - just checking the checkbox next to each of my room's bulbs and setting the desired HSL config.
I may not have. I added the switch (for clarity's sake, please note this is a "smart dimmer remote" not a smart switch that is wired to my electric panel) as a device, and then I went straight to RM and created a triggered event for a press of button 1 and a press of button 2. Sounds like there was an intermediate step I missed...?
RM. Is there an advantage to using a button controller as a middle-man? Is button controller a virtual device?
Haha I get it, I'm new too, lots of stuff to explore! I think we have different issues then, good luck.
Thanks for the luck and the comments. It's at least helpful to know this happens with other bulbs besides just mine.
possibly, i had to do it on my osram switches.
Go to the device page and 1st confirm what driver its using. If it's lightify smart switch then click on the configure button after pressing the 2 configure buttons on the switch (can't remember which ones, so check the manual)
button controller is just a basic when this button is pressed do this, when its held do this. With RM its more when this is pressed and these conditions match then do this.
So if it's simple button controller app is what you want to use.
I'm not home now so can't look exactly, but I do know the driver was coming up as specifically Sylvania Lightify. I'll go through the configuration. So what I'm concluding from your comments is that if my rules are still acting wonky after I configure the switch, I may be able to fix that using a button controller app. In that scenario, do I then add the button controller to my RM rule rather than the switch itself?
I appreciate all the help!!
no its one or the other before RM 3.0 I used to have to get RM to trigger a Virtual button that would trigger the button controler to do some things but now this is all in RM. It is just easier to use the built in button controller app if you just want to do basic stuff (less to de bug)
post a screenshot of your rule
Took some logs. Even though the rule registered and is what actually changed the HSL value of the bulbs, you can see the default hue/saturation values are what was assigned to the bulb around 07:55:32.356 pm plus or minus two events. Only after the second press of button 1 did they take the appropriate color.
Additionally, at the top of the log (latest entries) I can't explain the hue/saturation values. I don't have those h/s values anywhere in my rules. The lights did indeed appear to turn off though.
The "off" rule is in my post above. Here is the "evening" rule:
I created a new thread since this one evolved too far past its original topic.
