When a trigger happens, and a rule runs for the first time does whatever memory it used get completely freed after completion of the task?
I'd read on another forum that it stays in memory and will run faster the next time, but that memory is not freed up.
Thanks!
Citation needed. 
Back to the question, I'd assume the difference should be minimal either way, though there could be caching or something that affects actual usage but isn't necessarily indicative of a problem. But the platform does run on Java (and Groovy), and garbage collection is probably not perfect.
If you have specific concerns, there are ways to view the stats for your system, e.g., the /hub/advanced/freeOSMemory endpoint for your question.
Thanks!
Any value in having more than 1 Hubitat hub? - HomeSeer Message Board
I'd actually like to understand at what point having two Hubitats is a value add...and things like if they communicate on packet transmissions to eliminate collisions and overlap?
There's nothing special about having two Hubitat hubs here compared to anything else you might have. You can share devices between them using Hub Mesh (a built-in feature) or similar third-party (app and driver) solutions, but that is just over your LAN, nothing to do with the underlying protocols like Zigbee or Z-Wave that it seems like you might be asking about. (These do have built-in things like CCA, or clear channel assessment, for Zigbee that are supposed to help even if you have something like another Zigbee network on the same channel, overlapping Wi-Fi, or similar, but that's the protocol itself and nothing specific to Hubitat.)
There are various threads you can find here where some discuss the reasons they choose two (or more) hubs. You can probably find several with a search.
As always...THANKS for quick and detailed responses!
I asked because I had multiple z-wave interfaces on my HS4 deployment and that was kind of frown on by some of the guys.
I'll chime in. I run two hubs, a C5 and a C7. The C5 hub has my Iris V1 devices. A few years back, I thought they were creating issues when on the same hub as the newer Iris V2 and other devices so I decided to isolate them. Since I have it set up and working well, I saw no need to try to combine them on one hub. The C7 hub has all the newer Zigbee devices plus the few Z-Wave devices I have. I've been debating upgrading the C5 hub to a C7 hub that I have on hand. Right now, that one is a spare in case one or the other stops working. I have not seen the need to upgrade to the C8 hub, preferring to wait until I don't see as many C8 issues. Plus, I understand that the C8 hub has issues with Iris V1 devices. I haven't been following closely to see if those have been resolved, but I also don't want to fix something that (for me at least) isn't broken.
THANKS!
I generally don't see a lot more lag than other products I've used. I just want to be sure I don't build myself into any corners. I've had few misses, but not bad at all and I think changing up the timing has helped a lot.
For instance...I truly love the Homeseer switches with the 7 LED's on the front. They provide easy visual status for 4 locks, house mode, if the humidifier needs a new filter, and at night if there's movement outside. That's a lot of updates that happen when geofence changes occur too...on 5 of them each in a different room. Then add in lights/doors locks/HVAC etc.
Is it asking a lot of any home automation network? It shouldn't be. Not 23 years after z-wave started. I was still around IPX and AppleTalk back then and IP had just become dominant a couple years earlier. 
Correct and I don't think Hubitat is going to correct it based on what Mike said in another thread. They just won't work properly with the 3.0 controller. They would need a firmware update which obviously is not available.
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.
Download the Hubitat app
