Perhaps you should’ve reached out for support first. I’ve not seen any other users saying that it stopped Hue working…. I’m sure Hubitat will appreciate your thanks 
5 Likes
I agree or maybe try reverting back to the previous build to see if that cured the problem. That way it proves whether the update was at fault....... 
3 Likes
Wow, I never thought my question/problem would have generated so many comments. Lol.
Just so you know, I did fix this problem (me not reading the update notes) and now mine works great!
Paul
2 Likes
Does any of us ever truly fix our "RTFM" problems? 
1 Like
Oh Christ.
(a) there aren't many people who actively participate. Check any discussions for proof, there's a handful of users.
(b) out of that small number of users, an even smaller percentage voice opinions on specific topics.
(c) now, if that's true in the main forum, how many people do you really think comment in the beta forums?
Trying to catagorise anything which has so many grey areas is a nightmare. Full of disagreements because there are few (if any) right answers.
Someone suggested having an "expand all" option. Seems like a fix to me.
Nothing to fix, the new structure works perfectly as is.
Every platform I’ve ever used separates integrations from automations.
"Nothing to fix"?
I'd say that's an opinion.
Giving an "expand all" option sounds like an excellent way to keep everyone happy. You could have it "your way", others could have it their way.
/ sigh. Pointless.
On this topic, it's really not close enough to my heart to bother getting that involved with. I just hate seeing things change, which agitate people, when there's probably a way to keep a field full of happy campers. Instead of telling the troubled individuals to suck it up.
It is an opinion, that is true.
I’m not going to lie, despite liking the change instantly, it’s still taken me some adjustment to get used to. But it’s a logical change, and one worth adjusting to.
Oh, you must be referring to the Costco shopping experience.
This is a long thread so I might have missed it, but I noticed that when you clone a rule, after you’re done the focus jumps back to “Apps” instead of staying in “Automations”. @gopher.ny
1 Like
Because it is an app which does the cloning. Maybe?
Didn’t even consider the reason, just pointing out the unexpected workflow.
- Working on an automation
- Clone that automation (from within the automation) to get a derivative to work on.
- open new automation…. NOPE I’m now viewing the “apps”
na due to hierarchy change. probably should be updated to go back to whichever category it came from.
You mean this issue? Or something different?
That’s it. I missed it.
