using notifier app...and open patio door and get the first notification but NEVER get any more even though i have it set to 20 sec repeat....would really appreciate help,,,, tried rules machine and I could not figure out how to send repeated warnings....this app looks very clean ....but doesn't work : (
thx
tim
p.s. I read the help on the web for this app and the repeat option is not discussed...
the goal is to notify when the door opens and repeats every x time if the door is still open....is this capable of this?
I would delete and re-create this notification app instance since it's fairly simple and would probably be faster than any additional troubleshooting -- just to see if that helps. Turn on the "Enable logging" option and check the output of Logs for anything related to this app or any errors in general if it doesn't (or maybe either way if you want to try to figure out something with this).
Also note that the text in the UI is not lying to you; nothing will stop this notification, short of you going back into this app and manually hitting "Done" to re-initialize schedules, device subscriptions, etc. If you want it to stop if/when the contact sensor closes, check the "Stop repeat upon next event" option (as it is by default) or use one of the other options.
thank you so much for trying this.... I will do what you said and delete and recreate...
i'm curious what your device notification is ...
I'm trying to speak through echo speak app to alexa devices ...are you doing a text ?
The hub is at my nephews house so will check tomorrow.
My notification device was a text device. I am testing again with a TTS device...
EDIT: Odd, I don't think the repeat is working for that like it does for the notification (also only getting a single TTS announcement). Tagging @bravenel to take a look.
I have looked into this, and I can't say that I understand what I've found. As it stands, I can reproduce that spoken notifications don't repeat as they should. However, this appears to be some sort of system or driver problem because both the app and the device are logging the command to play the notification. What I discovered by messing around was that if I changed the volume of the speech device to some oddball value, then sent the speak command with the selected volume from the app, that it would repeat just fine.
I will pursue this a bit further. It doesn't make sense to me why the app should have to change the speech device volume for it to work, but that does fix it.
FWIW, repeating notifications working for me w/out issue, using similar simple test like @bertabcd1234's w/a Nest Speaker. This is on a C8-Pro, enrolled in beta so running 2.3.9.115. I open the contact and let things sit and all four announcements play as expected.
I also cannot get repeat notifications to work recently. This very notifier used to work, but I have upgraded to 2.3.8.140 and it appears to not work now.
This is quite strange with no obvious explanation. One thing you could try, which may or may not resolve this, is to clone this Notifier (gear icon in upper right of Notifier app page to App Status page, then Export/Import/Clone. Once you have the clone, open it to confirm everything, and hit Done. Disable the original Notifier for now, while you test the new one.
Pausing and resuming the notifier app - Didn't solve.
Cloning the notifier app to see if the cloned app worked - Didn't solve.
Removed the Notify Pool Heater switch restriction that I added yesterday - Didn't solve.
Cycled the triggering device (Pool Heater Enabled) off & on - SOLVED
My chain of events yesterday was that I added the switch restriction after the triggering device had already triggered the necessary state. (I was adding a feature to provide an override capability to the user interfaces.)
It seems when edits are made to a notifier app that is set for repeats, it deletes the repeat scheduled job and won't reschedule a job until the triggering device cycles again. For triggering devices that have long lifecycles for their states, this appears to stop the repeat functionality from working. You have to cycle the triggering device. This is not obvious. It may be useful to add some logic to the Done/Save of a repeating notifier app, to query the triggering device state and reschedule repeat jobs if the state warrants.
Same thoughts. Jobs are created once the notification is triggered by the trigger event.
But what @troywehrle is talking about is specific to editing a notification after the notification has been triggered and has pending jobs scheduled. He added the switch restriction to the notification while it was already active w/pending jobs. Saving the changes cleared the pending jobs.
AFAIK it would be normal/expected behavior that pending jobs would be cleared when changes are made to a notification, particularly in a case where a switch restriction blocking the notification from running in certain states was added.
I.e., if I added a restriction to a notification after it had been triggered to stop it from running during the day, and yet it kept notifying me after I saved that change, the notification would appear to be broken/not respecting my edits.
So this issue is limited to editing a notification while it is running and has pending jobs - makes sense that the notification would need to be re-triggered after the edits are saved to re-evaluate conditions and run or not run, as desired.
I actually thought the same as well, about it making sense that the trigger would need to be re-triggered.
However, the repeat jobs appear to check all the restrictions in each pass, so do they really need to be cleared. I am sure "it depends".
Using Rule Machine as a corollary, we would know if we changed the actions for a rule, we could explicitly execute its actions. We don't have that control for notification apps.
I just think it's worth noting/considering, since the level of expertise who would implement these repeats in Rule Machine versus Notifications may be different. I used to have all these notifications implemented in Rule Machine, but many years ago, simplified my setup and decided to move notification only rules to the Notification app.
At least the side effect is captured here now, for someone to search.
The good reason may be that it just keeps things simpler to clear existing jobs. 
