I have docker container for Channels DVR.
Is it possible to set up channels DVR server to use PushOver notifications?
https://pushover.net/
Examples of Alerts, I'd like to set up if possible:
When someone starts watching a channel
When someone starts recording
When someone schedules a recording for the future
When the recording is complete or gets completed
When recording is stopped or manually stopped
You can do e-mail log alerts now with OliveTin-for-Channels, which could be setup to notify on the events you're interested in.
I also have other OliveTin Actions setup to notify via Apprise -- which supports Pushover. So, it wouldn't be difficult to add notifications via Apprise to the Log Alerts Action.
So, I propose this:
Setup OliveTin-for-Channels and test out the Log Alerts Action, and if it works for you with e-mail alerts, I'll add Apprise support to it.
Any plans to have apprise alongside the email alerts instead of either/or? I have a private discord feed on hand so having 2 different places for alerts would be fine
I would add the ability to specify multiple alerts -- just like I did with Reminders. So, there'd be olivetin:// (alert e-mails), channels:// (Channels client onscreen notifications), and the 100+ services supported by Apprise.
That would be great.
Currently experiencing notification issues with some apps (like Apple Mail) on iOS 18 (only works when the iPhone is plugged into power).
Would prefer Pushover for all notifications.
Is there a guide you recommend for the setup?
There's a thread regarding OliveTin-for-Channels where you can get many questions answered using search, and you can post questions there of course.
Also, I did this video awhile back:
I was going to wait to hear back from the OP once he had OliveTin installed, but it seems like there's enough interest (me included), to move ahead with this enhancement now.
I'm tweaking a few things in ah4c atm, but I'll circle back and do this soon.
@chDVRuser @Jean0987654321 @CoderLuii
New bnhf/olivetin:latest (aka bnhf/olivetin:2025.03.15) pushed today with support for Apprise-based notifications (which includes Pushover) and Channels Client onscreen notifications for the OliveTin E-Mail Log Alerts Action.
This is in addition to the previous e-mail only support. Channels client notifications will show just the "filters" used, and not the log lines -- due to space concerns. Pushover notifications (and I'm sure others at varying counts) are limited to 1024 characters.
Also, I've added a couple of extra standard filter fields (now 5 in total), along with a field for specifying the notification methods you'd like to use.
Be sure to kill any existing E-Mail Log Alerts you have set up, by using the standard frequency=0 method, as it's now necessary to specify the way you want to be notified. Use of the default olivetin:// will function in the same manner as the original version of this Action.
Looks like this:
Ok, that seem to work. Any plans to add that to the Lineup Changes notifications too?
That's up to @mjitkop, since it's his script -- but he's already expressed interest in offering an Apprise option in the future.
I gave the script a bit more time and its not filitering anything. Im getting these notifications which i dont want. I just wanted the errors
2025/03/15 17:06:58.588294 [HTTP] | 200 | 2.333686584s | [192.168.1.64](http://192.168.1.64/) | GET "/dvr/files?raw=false"
2025/03/15 17:06:58.588294 [HTTP] | 200 | 2.333686584s | [192.168.1.64](http://192.168.1.64/) | GET "/dvr/files?raw=false"
2025/03/15 17:06:58.588294 [HTTP] | 200 | 2.333686584s | [192.168.1.64](http://192.168.1.64/) | GET "/dvr/files?raw=false"
2025/03/15 17:06:59.963123 [HTTP] | 200 | 3.120465ms | [192.168.1.64](http://192.168.1.64/) | GET "/dvr/jobs"
2025/03/15 17:06:59.963123 [HTTP] | 200 | 3.120465ms | [192.168.1.64](http://192.168.1.64/) | GET "/dvr/jobs"
2025/03/15 17:06:59.963123 [HTTP] | 200 | 3.120465ms | [192.168.1.64](http://192.168.1.64/) | GET "/dvr/jobs"
2025/03/15 17:06:59.973532 [HTTP] | 200 | 1.803858ms | [192.168.1.64](http://192.168.1.64/) | GET "/dvr/rules"
2025/03/15 17:06:59.973532 [HTTP] | 200 | 1.803858ms | [192.168.1.64](http://192.168.1.64/) | GET "/dvr/rules"
2025/03/15 17:06:59.973532 [HTTP] | 200 | 1.803858ms | [192.168.1.64](http://192.168.1.64/) | GET "/dvr/rules"'
What does your grep filter look like?
EDIT: Also, I'm not seeing any lines in my log that looks like those. Could you maybe run the OliveTin Post-Install HealthCheck -- just to be sure your LOGS_SHARE value is pointing at the right place?
EDIT2: OK, I get it now, you have HTTP logging enabled. So you're looking to grep anything that's not a 200?
A while back, I started to rewrite parts of my script for channel lineup changes notifications, and so far I haven't had enough time to sit down and put my head back in it to finish it.
When I am finally able to get back to it, I'll look into adding support for Apprise too.
@bnhf - Thank you for sharing this solution. I found the setup process quite complex due to the number of environment variables needed in the config file. I spent about 6 hours trying to understand each variable and figure out how to configure Pushover, but found it challenging to navigate without additional guidance. For what I'm trying to achieve, this solution feels more complex than necessary, and would likely require extensive back-and-forth communication to implement correctly.
While I understand that OliveTin offers various use cases beyond what I'm looking for, I may try a simpler approach. Previously, I created a script for qBittorrent notifications using Pushover that alerted me when a torrent was completed or when a new torrent was added. I might develop something similar just for alerts with this system. The main challenge will be understanding the logging system, but I hope to create a script that can notify me when:
If I'm able to create a working solution for any of these notification types, I'll share it here in this thread.
Appreciate your help with this 
I'm just looking to grep "[DVR] Error" and thats it
Assuming you have Docker and Portainer installed, the env vars aren't too difficult. Not every value is required by every user, and the basic values you'd need to provide are the same ones you'd need to know in order to be able to develop a script.
You can get a working OliveTin installation up-an-running, by knowing the answers to only a few questions:
What URL do you use to access the CDVR WebUI?
What is the path to your CDVR recordings?
What is the path to your CDVR executables?
What is your timezone in standard linux format?
Where would you like to store your persistent OliveTin data (needs to be a writable path)?
What local domain name is used on your LAN? localdomain or something else?
Answer those 6 questions, and I'll post a set of env vars here, and you can be up-and-running with OliveTin in a few minutes. Project One-Click and a few other things won't work immediately, but you can add those values later.
EDIT: Don't get discouraged by the occasional user that has needed extra hand-holding to get OliveTin going. There have been something like 25K downloads of the project -- so most need little or no assistance.
Are you saying the default [DVR] Error value is matching the log lines you posted?
Yeah...I think so. Either that or its not filtering those log lines out.
Could you post the contents of your *logalerts.running file from the directory where you're storing your OliveTin data? Redact tokens or other sensitive info from the last argument shown.