I have a lot of rules I don't know if there is a limit. Is there such thing as too many? Everything is working.
It really depends more on the type of rules you have, hub model, installed applications, device handlers, and device types.
The C7 has more processing power than the C5 and the C5 more than C4.
Obviously, simple rules, like when a switch or motion sensor event occurs, do something simple, like turn on a light or make a chime. Other more complex rules, for example infinitely loop, send receive http requests, etc, may chew up one's hub resources..
Lastly, IMHO, everyone's hub has different configurations, user applications, and device handlers that can take a toll on the resources that RM needs.
I do not think there is a defined limit to how many one can create, so when your hub starts behaving slowly, needs to be frequently rebooted, that when you know that you have some investigating to do. Luckily HE's log view has some nice device and application statistics.
Thanks that makes sense most of my rules are super simple. I am on a C7 just made the jump from smartthings I had been there for years. I should have come over to Hubitat sooner it is so much quicker. I have over 100 devices and thought it would take forever to make the transition but it only took me about a week. A bonus is I am still married LOL.
4 Likes
false. the only difference between the C5 and C7 is the z-wave radio
5 Likes
With "Device Stats" and "App Stats", they provide a percentage of time they were using hub resources. Does anyone know what reasonable numbers look like? These are currently mine:
I have 80 or more devices, and it looks like 3 of them are using over 50% of the HE resources used by devices. But in total the devices are only using hub resources 0.3% of the time. Similar low numbers on the apps.
I have:
42 - Rule Machine Rules
4 - Simple Automations
2 - Zone Motion Controllers
1 - Thermostat Scheduler
1 - NHL Game Day Live
1 - Mode Manager
1 - Maker API
1 - Lutron Integrator
1 - Lock Code Manager
1 - IFTTT Integrator
1 - HSM
1 - HubiGraphs
10 - Hubitat Dashboards
4 - Groups and Scenes
5 - Button Controllers
1 - Hubitat Package Manager
1 - Squeezebox Connect
No idea if 42 RM rules is a lot or a little. My hub is a C5.
You and I have the much of the same past. I cut my home automation teeth on ST V1. I survived a horrible migration to V2 with outages and device incompatibilities. I spent literally thousands of hours creating custom Smartapps and DTH's for distribution to many users, all over the globe. It was an exciting time for me!
Then Samsung acquired ST. It was the end of SmartThings as a little company with dedicated engineers that cared about their users. Samsung only cared about their appliance line for integration, all else was an annoyance to them. I suffered frequent cloud outages, no response from invisible support, a horrible new defective mobile client and crazy strategy to limit their cloud servers for hosting one's custom Smartapps, etc. For me, I had to jump ship and never look back.
I migrated over 80+ devices/sensors to HE (C5 & C7) and I can say overall I am satisfied. I only wish that the C7's Z-Wave was stable, but the C5 is rock solid. I think that the added Z-Wave security in C7 has caused me many hours to debug, work around, and accomodate, mostly with Zooz switches and Zooz/Fibaro motion sensors. But once I purchased a UZB and mastered PC Controller on VMWare Fusion, I'm back in business.
1 Like
I haven't experienced any z wave problems yet, though I probably will I have 4 Aeotec TriSensors that I paired with security enabled because I didn't know it was better to leave it off yet. I also still have a few pistons in webcore that are way to detailed for me to try to bring them into Rule Machine. I would like to but they are complex and took me forever to get working. Maybe some day.
I agree with your observation on processing power, but here is my reasoning.
I can tell you, from my personal experience, the C7 is much faster (hence my comment on overall performance like optimal gear ratios using the same car engine) for the same applications and device response times I have on my C5. I have hd the same devices on both, and in my network configuration and hubs in the same location, the C7 is quicker. Hands down!
The 700 series Z-Wave chip most likely (See #1 below) allows the C7 to perform faster than the 500 series Z-Wave chip on the C5. Also maybe the C7 has some better o/s code optimization with the 700 series API's, etc than the C5's. Hard to really tell!
What makes 700 series Z-Wave better?
- Z-Wave is all about control and automation. 700 series does it quickest. An 18% more powerful CPU is coupled with wireless transfers reaching 100 kbit/s and instantaneous security. 700 series calculates the quickest and acts the quickest.
- The 700 series power performance is hugely improved. Wireless communication uses 64% less power and improvements to resting and active performance means battery life can be as much as 10 years when fully optimized.
- Z-Wave Plus cements its position as the best platform for wirelessly connected devices with 700 series. With a wireless range of up to 800 metres / 2,600 feet (hop mode), Z-Wave devices can now communicate 250% further using significantly less power.
I really donāt see that 40 Rules in RM is a nowhere near a problem as long as they are efficient. I would sincerely hope not anyway.
Hubitat have repeatedly stated that processing power and memory are not an issue in their hub. Their constraints if relevant come from I/O and other bandwidth areas.
So just stay efficient with your rules and you can add many many more. Try to trigger rules on significant state changes and not something that runs periodically or triggers very frequently. The number of rules arenāt important itās how many run every minute/hour. Untriggered rules use almost no resources.
The new log pages in the latest release will show you what loading your RM rules are placing on your hub
2 Likes
Youāre both right
ZWave is faster on C7 but the rest, and hence the performance of RM is the same. ZWave based actions within RM will be faster.
2 Likes
Just as reference, here are the performance and other improvements in the 300-700 Z-Wave radios. So when the overall performance of C4, C5 and C7 are compared, one has to take into consideration the performance of individual components like the Z-Wave radio.
I'm not saying that one or more of these Z-Wave chip improvements in the radio may result in a specific faster HE benchmark, but a faster Z-Wave radio and the new API's might make similar HE CPU models run differently depending on the wide variability of other factors (e.g. devices, applications, network mesh, internet speed, firmware release, etc...)
| 300 series | 500 series | 700 series | |
|---|---|---|---|
| Hardware Platform | |||
| CPU / MCU | Optimized 8051 CPU Core | Optimized 8051 CPU Core | ARMĀ® Cortex M4 |
| CPU / MCU Speed | 16 MHz | 32 MHz | 39 MHz |
| Memory | 2 kB | 16 kB | 64 kB |
| Flash Memory | 32 kB | 128 kB | 512 kB |
| Gecko | No | No | Yes |
| SAW Filter | No | Optional | Inbuilt |
1 Like
I don't doubt this but I have only moved 4 Z-Wave devices out of 10 and actually my experience on C7 cf. C5 with just those is an absolute mess. They are the nearest devices, all line of sight.
So whilst it may have benefitted you it has been , and still is an absolute mess for me. It's not a big issue as ZWave is not important to me though. I wanted to use HE as my 'best of best' hub but now I'm forced to revert to 500 series on another controller and intend to use zwavejs2mqtt.
Anyway this is OT ... sorry
Just counted on my C-5 Hub, I have 108 rules just in Rule Machine and 28 in Simple Automation Rules.
3 Likes
I have over a hundred. No problem. Love Rule Machine.
3 Likes
Your hub has been running 29 hours and it has been running apps for only 16 minutes of that that. You are fine !!
