Request: Would it be possible to assert / de-assert a 'Maintenance Cycle' location event a few minutes before/after the maintenance cycle begins?
Why: Over the last few days, we have had to take the dogs out between 2 and 2:30 am. The system response time has been so bad, that the lights didn't come on until after I was back in the house and headed back to my room. Maybe 60 to 90 seconds?? Sometimes even longer. Sometimes there was no response. (NodeRed response monitoring is going in next) Unfortunately, HE didn't detect the door closing, and three minutes after I was settled back in my bed, and nearly asleep. Sonos announces "The HVAC system will be shut off in the two minutes. The following windows or doors are still open ...." Needless to say the wife said something like.. "Can you please fix your stupid electronic girlfriend" So, back out of bed, open and close the back door, and then try to set the security system via Alexa. "I'm sorry 'Security System' is not responding right now. Frustrated, I grab the tablet, start the HUE app, and turn all of the lights off. So much for quietly taking the dogs out.
'maintenance cycle' location event assertion would set/clear a GV that would facilitate the following during the maintenance cycle.
Turn on some low intensity interior/exterior path lighting
Disable all motion lighting apps
Disable Contact sensor TTS notification
Disable Window/Door still open Thermostat Override
Set the System Response Time Bulb (Green:fast, Yellow:slow, Red:problem, Blue = Maintenance Active)
More importantly, provide awareness as to why the system response time is so slow. The wife would very much appreciate it, as would I.
Please help me up-vote this request to fruition, if you think this would bring value to your HE experience!!!
Would like to know when it starts and ends, so I can easily associate the performance problems I occasionally have with it. How long does maintenance take to complete?
I would assume it is based on the number of devices, rules, apps?
My point is though, let's say you show that there are performance impacts during the backup window. Then what? You can't turn them off... You know it's going to happen every morning at 2 a.m....
Hubitat already knows that there are hub performance impacts during the maintenance window. That's been shown by a dozen people if it's been shown by one.
Obviously it's up to you to make a feature request, and that's fine. I just don't see how this feature request actually does anything to help you in the end.
There are a few database and config backup housekeeping tasks that run at 2am. Normal system maintenance stuff, but it can (rather, it DOES) impact hub performance during that window.
You are absolutely right @JasonJoel , I could do that, but this industry trend is all about customized home automation. I want to address issues like maintenance in the same detail fashion of tailored rules that I use to control the rest of my system. Not by guessing or estimating when things happen, rather rely on notifications to trigger functions the way I want them to work.
I have a night mode setup for this. It makes sure that no matter what I do (accept trip the alarm) everything is low impact (lights dimmed to 10, no tts, etc.) Isn't that just the easiest way here?
Does anybody know what the 'maintenance cycle' actually does.
I know it does a backup which doesn't take that long.
I haven't been impacted by this as I need my beauty sleep but I was wondering what it is actually doing and why it is having such an impact on people.
I don't know how much time daily maintenance procedures are expected to take to complete, but if maint. always starts at 2am, then mine was busy still at ~2:45am, or something went wrong. By 5am when I got up, everything was working perfectly again.
but I was wondering what it is actually doing and why it is having such an impact on people.
