I think a recents list would be good and when adding one maybe the cdvr api could give a list of the servers clients. otherwise a link to that settings page to quickly find the IP
edit; just realize I steped up the level there a bit.. any little bit still helps!
The dropdown would list the devices you defined in CHANNELS_CLIENTS, which is an OliveTin-for-Channels env var that's also used to send onscreen messages to clients. Those clients can be defined by resolvable hostname or IP address. I always use hostnames myself for easy identification.
What I'm hoping to do here is use values, tools and methods already available in OliveTin to achieve what you're requesting. 
no, I appreciate any and all effort! I forgot about the other client tool.
for some reason on my setup there's a docker to localhost connection that doesn't ^ always resolve the host names for me.
Do you use Tailscale? Have you established a domain name for your LAN (most decent routers support this) -- like localdomain or lan?
OliveTin has a DOMAIN variable, and you can set your LAN and Tailnet domain names there.
unless i'm missing something this is the closest i can get with a cheep router. I just saw I can change it, but it's been set to that the whole time, so unless case matters, the router should know the name. also, I am running a pi-hole.
With Pi-hole, that should be your DNS server in order for it to do anything. Go into your Pi-hole WebUI, and create local DNS records for whatever. E.G. shaggy-mancave could be assigned to 192.168.x.x. Then you could set CHANNELS_CLIENTS=shaggy-mancave, or CHANNELS_CLIENTS=shaggy-mancave shaggy-hometheater shaggy-snoozespot, to expand on the concept.
I might be the only one using this action, but can you update the stalexmlalerter.sh script to have curl follow redirects, curl -sL ...
Done. Pushed as bnhf/olivetin:latest (aka bnhf/olivetin:2026.03.26). Untested, so if you could confirm it works, that'd be appreciated.
Thanks. Working now.
I tried the OliveTin function to "Manually Add a Recording" just now but the time assignment isn't translating properly. I want it to record at 4 PM so I enter 16:00 in the field as instructed but then when I check the DVR schedule I see that recording is scheduled instead for 9 AM, which is in the past. What am I doing wrong?
It looks like the latest version of Debian (13 aka Trixie), has dropped support for time zones in the Country/Timezone format, and is now insisting on the Continent/City form. So, stop your OliveTin-for-Channels stack and change:
TZ=US/Pacific
to:
TZ=America/Los_Angeles
and you should be good to go.
Thanks for reporting this.
I think I'm running ubuntu, but I'll change mine to, I suppose Central to Chicago
The OliveTin container is running on Debian.
Choose the Canonical (primary, preferred zone) name for your zone.
Thanks for the quick fix! I changed my TZ setting, tested a manual recording just now and it's working fine. Much appreciated 
Looks like some changes to the CDVR API's require updating your Remove Comskip Markers from a Recording action
marknocommercials.sh
Change line 18 from
curl -s -XPOST "http://$dvr/dvr/files/$fileID/comskip/edit?source=local" --data-raw "[]" >> $logFile
to
curl -s -XPOST "http://$dvr/dvr/files/$fileID/comskip/edit?source=standard" --data-raw "[]" >> $logFile
Change line 22 from
curl -s -XPUT "http://$dvr/dvr/files/$fileID/m3u8" >> $logFile
to
curl -s -XPUT "http://$dvr/dvr/files/$fileID/fingerprint" >> $logFile
No problem. I'll do that now, and let you know when it's published.
@chDVRuser Pushed just now as bnhf/olivetin:latest (aka bnhf/olivetin:2026.05.23). Thanks for making it super easy!
Thanks, That was quick!