It's on the deprecated page in OliveTin, but should still work, if you want to install it.
It was strange situation with the developer from the start, as he was brand new to this forum and brand new to GitHub, along with everything he was doing being AI generated. His code, his forum posts, you name it.
I used his container for bit, despite concerns, and spent a a fair amount of time keeping it working with OliveTin through various breaking changes. Ultimately though, when his code pushed thousands of notifications out through my Pushover account (with no explanation), I personally pulled the plug.
Since he hasn't posted here in the last 9+ months, the code hasn't been touched in almost a year, and he's done nothing else on GitHub during that period -- it seemed like time to move it to the back burner, at least as far as OliveTin-for-Channels is concerned.
The dev bailed. It's been doormat for a year. Darn shame tho as it was a promising tool but yeah
Gotcha - yeah the ai stuff was pretty obvious - was my first indication that vibe based projects were becoming a thing - first indication seems to be mostly feature complete on version 1 and the ui design is a lot better than most v1 projects
Its just been working for me so i didn't notice it has been abandoned - thanks
would it be possible to get an olivetin adb action to reboot an androidtv client &or one to kill the cdvr client app (cdvr beta)
It could be done, but that would mean configuring ADB connections for all of your Channels client devices (or at least the ones you want to be able to reboot). Other than that requirement, OliveTin already has all the tools and info it needs to do it.
There would be a dropdown that would have each of the CHANNELS_CLIENTS you've defined, and then the Action could send an adb connect to that client, which you'd need to approve the first time (you would have had to already enabled developer mode and USB debugging of course).
This would not work with any device that can't be used with ah4c or ADBTuner, like the CCwGTV (Android 14+) for example.
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 