From what I can tell, the Notifier App feature to add a delay on an event (For How Long?) only allows a "minute" setting. I'd like to use "seconds" for most of my delays. I can do this in Basic Rules, but I would like to keep all notifications in the Notifier App if possible. Am I missing something, or is a there a chance this could be changed?
I've moved your post to Feature Requests.
To satisfy my curiosity, can you describe a use case where a delay of 59 seconds or less is necessary for notification?
Thanks!
Sure. For any contact closure, I like to have a little debounce delay. I have seen when my garage door position switch might make, break, and then remake within a couple of seconds. I have a gate switch that I believe could have the same issue. So I would prefer to have a 3 second delay on these cases.
No idea if this would work, but does that field take a decimal? If it does, it may not go to 2 places, but you could try 0.05 (=3/60)
I'm at office, so I can't verify myself right now
Yeah, I tried, but no go. The field will not take a decimal.
Do you want to use any of the more advanced repeat settings in that app? Or just a single notification?
You might be better off using Rule Machine, and creating an "and Stays" trigger.
Then you can do notifications from there. For just a single notification it is easy. If you want to repeat it that gets a little more complicated.
Well, worth a shot.
FWIW, I've moved almost all of my Notifiers to Rule Machine, since I found that most benefited from having access to additional helpful options that improve/refine those notifications. I still have a few simple things in Notifier, but I'm considering moving those to RM too (simply to consolidate stuff).
2 Likes
For these particular notifications I am using Basic Rules because it does allow seconds entry for the delay time. It does not have repeat options, however, but not needed in these cases. I have other notification cases where I want repeat, but the delay is not necessary (water leaks detection). I have considered moving all notifications to RM, but man, RM seems like overkill for such a simple application. And again, there is a Notifier App, so it seems I could do all my basic notifications under that one app.
Got it - thank you got explaining your use case.
IMO, the debounce should be in the trigger (recognition of sensor status) and not the action (notification).
The “and stays” option in RM triggers permits that.
The Notifier App asks "What Event do you want to monitor for notification?". So it is a trigger and it does have a delay option on that trigger. It is just is limited to minutes. Would that be a difficult change to make that seconds? Or minutes and seconds, like other apps allow?
Yeah I agree, it is in the trigger on the notifications app already the way it asks the question. It is basically the same as an "and stays" trigger for Rule Machine.
I have also wanted to put in 30 seconds for a few I have setup but just settled on 1 minute being good enough. If I was dead set on making it less I would have just created it in rule machine (since I am familiar with that already).
There are other built in app that have a minutes box and I am able to put in 0.5 for 30 seconds, so it seems like it should be a pretty easy fix for Hubitat to just allow decimal values in that input box.
1 Like
Not doing features enhancements for Notifier at this time, "pretty easy fix" or not. This use case is easily done in Rule Machine. We aren't planning to enhance simple apps like Notifier with RM features, when you can just use a rule to do the automation. That's why RM exists.
4 Likes
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.
