Reminder Feature

[bnhf]

For anyone who's interested, the reminder feature is back -- via an OliveTin-for-Channels Action.

Set things up once via the Action, then any future recordings that have 10 or 30 seconds added (configurable), will trigger a reminder.

Lots of different types of notifications supported, including an onscreen Channels client popup. Notifications are via Apprise, which has wide support.

[bnhf]

New bnhf/olivetin:latest (aka bnhf/olivetin:2025.02.28) pushed today with several enhancements to the new CDVR Event Reminder Action. Current + new feature set includes:

• Support for multiple CDVR servers.

• Support for multiple different polling intervals for matching DVR jobs.

• Support for two different "triggers" to create recordings that will generate Event Notifications (10 seconds or 30 seconds of BEFORE padding).

• Support for the entire Apprise series of notifications, plus a special channels:// value that will send back-to-back event notifications to all defined Channels clients.

• Support for keeping the DVR job, after the event notification is sent, in order to create a recording as well -- or, delete the DVR job so that no recording is ever created:

[bnhf]

@bnhf

Current + new feature set includes

A few more features added, including support for multiple space-separated notification URLs. More details here:

OliveTin for Channels: An Interface for Misc Channels DVR Scripts & Tricks

New bnhf/olivetin:latest (aka bnhf/olivetin:2025.03.01) pushed with support for a classic DVR "Reminders" feature. When this OliveTin Action is active, any DVR job created with 10 or 30 second padding added (BEFORE or AFTER), will generate one or more notifications. These notifications are via Apprise (100+ types of push, SMS, e-mail and other), or specially defined channels:// or olivetin:// values. channels:// sends an onscreen notification to all Channels clients defined in in the OliveTin e…

[mjitkop]

I understand the initial request in this thread to be reminded of an upcoming program that you want to watch live and not record.

So I'm a little bit confused: why would you want to be reminded before a recording starts?
I have nothing against it, just wondering about the use case.

[bnhf]

@mjitkop

So I'm a little bit confused: why would you want to be reminded before a recording starts?
I have nothing against it, just wondering about the use case.

It's mostly just a way to be able to trigger the notification. You have the choice in the OliveTin Action as to whether you want the DVR jobs to actually record -- or have the Action cancel the "job" after the notification is sent. It's really just a mechanism to initiate the reminder using what's already available in CDVR server and its clients.

[mjitkop]

I get it, thanks.

Great job, by the way. The Apprise service is amazing.

Could it replace the notification mechanism in the channel lineup changes action?

[bnhf]

@mjitkop

Could it replace the notification mechanism in the channel lineup changes action?

I think so. Especially for those that want to be notified by e-mail plus another service, where e-mail has the detail and the other methods are more summarized. Most of the lineup change notifications are short, but I'm not sure the longer ones would be as good via a push.

[HEHEHE69]

Setting reminders would be nice. I used to do that on my cable boxes all the time back in the day.

It would operate similar to the DVR scheduling right? Could even add it to Passes for reoccurring reminders and piggyback off that

If it runs on the server, you could choose “remind me on this device” or “all devices” right? Push notifications isn’t a big priority imo, I’d be cool without it.

[bnhf]

@HEHEHE69

It would operate similar to the DVR scheduling right? Could even add it to Passes for reoccurring reminders and piggyback off that

Yes, this should work fine with passes, just add 10 seconds of padding (BEFORE or AFTER) to the pass.

@HEHEHE69

If it runs on the server, you could choose “remind me on this device” or “all devices” right? Push notifications isn’t a big priority imo, I’d be cool without it.

You can send a notification to any or all of your Channels clients. It's also possible to get a desktop notification. E-mail, text and push notifications are possible -- and can be used in combination.

[chDVRuser]

OliveTin for Channels: An Interface for Misc Channels DVR Scripts & Tricks

I'm interested in opinions on changing the Remind Action from a 10 or 30 second padding to trigger only a reminder, to using each for a unique purpose. Ideas would include: Using a 10 second padding to generate a notification with a job delete, and 30 seconds for no job delete. Using a 30 second padding to generate a notification, and then change the channel to the notified event at its start time (though multiple concurrent reminders would be a complication). The last idea, as you mig…

[bnhf]

New bnhf/olivetin:latest (aka bnhf/olivetin:2025.03.05) pushed this morning with several enhancements to the new CDVR Guide Event Reminder Action:

The primary addition is the ability to not only send a reminder about an upcoming program in your CDVR guide, but also autotune to that channel at the event's start time:

Once you do the initial configuring of the OliveTin Action, it will continue to run as a background task. Whenever you select an event in your grid guide, and add 10 or 30 seconds padding (BEFORE or AFTER) this will trigger an on and/or off screen reminder.

However, with the autotune capability added, when you add both 10 second and 30 second padding (BEFORE and AFTER), this will trigger a channel change on the client specified in the channel_change field. You can use either the client's actual LAN hostname (not to be confused with the informal names CDVR assigns to clients which contain spaces), or the client's LAN IP address. Tailscale MagicDNS hostnames or Tailnet IP addresses work as well.

You'll see Standard Output like this when first configuring the OliveTin Action:

The other enhancement is that the interval selected will also define when the DVR job checks are performed. For example, if you select a 5 minute interval, the DVR will be checked for matching jobs every 5 minutes -- exactly on 5-minute marks [0,5,10,15,20,25,30,35,40,45,50,55]. 10, 20 and 30 minute marks are also an option.

Matching jobs set to record in the next 5 minutes (in this example) will generate a reminder, and if you have delete_jobs=true the job itself will be deleted -- so no recording is created only the reminder sent. If you've used the 10+30 second padding trigger explained above, this reminder will also include a channel change at the event's start time.