I'm curious how you handle stuff like this:
Toggle zigbee switch to on:
If no lights on, turn on to specific color/level per mode, per presence, etc.
If some lights on, turn to specific color/level per mode.
If all lights already on, but not 100% bright, turn to daylight/100% brightness.
If all lights at 100%, then 'pin' lights for 20 minutes before allowing triggered-off lighting to work again.
Hold zigbee switch to on:
turn on auto on/off lighting for given room
Things along that level. These are really basic tasks I would want to happen when I tap a switch. Contextually-aware, essentially. Do you guys accomplish all this stuff with 'simple' automations?
Or is it that you only do really basic stuff with the switches, lights, devices, etc? I have a hard time imagining using anything but RM, WC, or writing my own app for this stuff.
All of these are conditionals. I personally wouldn't use the conditional in these and just say at this event do this. I have designated areas that I want to do certain things with certain events. Like when I come home turn on the entryway lights and hallway lights. If I wanted to expand on that and have those lights do something for different modes I would create a second rule with whatever trigger and its settings specified and restrict it to that mode. My bathroom is another example during the day turn on the lights full brightness when motion detected. At night turn on to 5% brightness when motion detected. Here's some other examples also...
Okay, I am starting to see the method to your madness... though I wonder at the end of the day, is it really better to have 8 'simple' rules, when you could have a single RM? I wonder where the break-even point is in terms of effort, overhead, reliability, etc. That's the beauty, but also the greatest shortcoming of a platform like this. So many ways to skin the cat.
Performance is going to benefit from fewest lines of code. The more processing power it takes to navigate a large rule the less power is available for another Event. Second Event has to wait for the first. We're discussing fractions of a second, on a device that does a billion things per second, all day, all night. So it's going to become apparent ONLY when a number of Events get backed up behind a longer running automation. Events spaced far enough apart just keeps the processor from getting too cold and a jam packed Rule is OK.
Awesome! Glad you finally got everything where it belongs
I'm constantly impressed by how much I'm able to do with my two production hubs. My main hub is still a C4, but the improved Z-Wave performance of my C7 that was swapped for my original C3 hub has been tremendous. I'm not looking forward to the work involved to get there, but I plan to migrate my C4 to a C7 sometime in the next couple of months so I can benefit from the improved Z-Wave performance for my main hub and have a path for easy future migrations.
Hey thanks for this!
I am quite new to Hubitat and had purchased one hub some months back thinking that it is all I need.
Little did I know that one could use more than one hub.
Now that I know, surely I will purchase more!
I hope support for the Fibaro products grows..... I had blindly purchased Fibaro products assuming that any Z Wave device works with the hub......but I have learned a lot in the meantime and solved some problems already with the help of a great community
Just something I found interesting... I'm not sure I had a hardware defect after all, despite support thinking so. I was having so many problems with my dashboards, so I went in and played around a bit. The local links worked fine, but not cloud. Weird. These worked fine for years. I started building new ones, and they wouldn't work in the cloud either.
I cleared the tokens, and new dashboards worked in the cloud. Okay cool, that's a start, but still my most important and complicated dashboards did not work with cloud links.
Turns out what fixed it was to toggle off all devices in the settings, and manually-select each one. This makes it a HUGE pain to add new stuff on the fly, but it seems to have fixed my problems. Now this (allegedly defective) C4 is much more responsive, and the dashboards work.
I wish I knew how the dashboard code works, because it doesn't make sense that by simply allowing it to 'see' all devices, it would bring a hub to its knees. I wasn't even ingesting that data, nor was I actively displaying and of those dashes. Just a lot of background overhead that doesn't add up. Interesting stuff to me.
and a jam packed Rule is OK.
