I started 100% node red.
As I move ahead a couple years later I’ve moved some to core automation - but not just because it’s less or more complex.
Honestly my room by room occupancy stuf stays in NR. It’s just better for me in NR. But. Depending on what the function of the automation is or what my requirements are, lots moved back.
Pretty much my decision point is either:
'do I need to guarantee that this automation is running if HA is up? Then, Automation because the NR container or addon can start and close independently of HA. That for me is:
Any automation that enhances or augments the function of a specific device e.g. Life safety concerns, light synchronization on Zen32s, sync multiple states. Most of my auto off timers at a device level, autolock / auto arm, most proximity based automations, etc. Basically anything that if I turn off NR it doesn’t leave my system functionally broken.
So what does that leave?
The room engine. (matrixes time v. Occupancy v. Mode v. Etc.) Motion in room sets room occupied for x. Setting ‘Occupied’ when the house is in mode x triggers scene.roomY_modeZ_occcupied
That solution by itself is 25 ‘room’ flows (each room is it’s own) and 4 subflows (the shared flows between the rooms)
AutoVac - 4 flows. One for vac control one for the scheduler, and a couple for system sync
Time of day - picks a home mode based on a set of time windows defined by helpers Morning, Home, Evening, Night, Late Night, Away, Pause. And also auto adjusts based on occupancy, calendar (work/weekend/vacation)
So it’s not Just ‘complexity’ for me it’s more about it’s the right tool for the job.