Sure but it would be nice if it mapped.
Hopefully it was easy for you to duplicate this.
I tested again today using v0.7 and still got repeated (every 5 minutes) VOD watch notifications for the same recording as I continued watching it.
Watching a channel Live only gives a single notification.
Found an issue with the recording schedules notification.
I have a pass for the show Frontline on PBS.
Tonight's episode had the generic show description, no episode title, season or episode number since it was first scheduled 15 days ago.
This morning during the daily guide update, the episode was updated to include season, episode and episode title.
ChannelWatch sent a notification saying it was cancelled using the old (probably cached) show info, then sent another notification saying it was scheduled using the same old (probably cached) show info. This notification should have included the new, updated season, episode, episode title and description.
From Channels DVR log when it was first scheduled using Old, generic show data
2025/04/21 09:18:11.032212 [DVR] Rule 'Frontline-PBS' (768) found 1 new airings (2 matching)
2025/04/21 09:18:11.071979 [DVR] queued recording job for 'Frontline' SH000017620000-1746594000 @ Tue May 6 10:00:00PM on ch=[706] (1746594000-768)
From Channels DVR log scheduled this morning using New episode data
2025/05/06 10:01:20.140798 [DVR] Rule 'Frontline-PBS' (768) found 1 new airings (2 matching)
2025/05/06 10:01:20.384528 [DVR] queued recording job for 'Frontline' EP000017620904 @ Tue May 6 10:00:00PM on ch=[706] (1746594000-768)
I have the subscribed events, CDVR log and ChannelsWatch log and activity_history if you need them, but this should be easy to duplicate.
Perhaps wait until activity "2-scheduler" is complete?
{"Type":"activities.set","Name":"1-indexer","Value":"Downloading guide data for 2025-05-06 9:30AM.","At":"2025-05-06T16:54:00Z"}
{"Type":"activities.set","Name":"1-indexer","At":"2025-05-06T17:01:19Z"}
{"Type":"guide.updated","Name":"ALL","At":"2025-05-06T17:01:19Z"}
{"Type":"activities.set","Name":"2-scheduler","Value":"Scheduling new recording jobs.","At":"2025-05-06T17:01:19Z"}
{"Type":"programs.set","Name":"SH000017620000-1746594000","At":"2025-05-06T17:01:20Z"}
{"Type":"jobs.deleted","Name":"1746594000-768","At":"2025-05-06T17:01:20Z"}
{"Type":"jobs.created","Name":"1746594000-768","UpdatedAt":1746550880310,"At":"2025-05-06T17:01:20Z"}
{"Type":"programs.set","Name":"EP000017620904","Value":"queued-1746594000-768","At":"2025-05-06T17:01:20Z"}
{"Type":"activities.set","Name":"2-scheduler","At":"2025-05-06T17:01:21Z"}
@CoderLuii Very cool, it's like Tautulli for Plex but on steroids. I've tried to install it and it finds my recording schedule but for some reason it does not catch when I am watching channels. It never shows that I am streaming.
@slampman - Thank you for clarifying - that's actually a more significant issue than I initially understood (no live stream detection at all rather than just MLB streams). This will help me pinpoint the problem better when debugging. If you could create a GitHub issue with any additional details about your setup (TunerSharing, TVE types, etc.), that would be really helpful for tracking. I'll definitely prioritize this since it affects core functionality.
ChannelWatch - GitHub Issues Page
I'm currently working on the project and the different issues people are experiencing, i should have this fix by today or tomorrow.
CoderLuii
@bnhf - Wow, that's definitely concerning! Thank you for bringing this to my attention. This kind of notification flood should absolutely never happen. I'll implement rate limiting in the next update as an urgent priority to prevent this from occurring again.
I completely understand your reluctance to restart it - that would burn through your Pushover quota quickly. If you feel comfortable, could you create a GitHub issue with this information? I'd like to understand what might have triggered this avalanche of notifications.
ChannelWatch - GitHub Issues Page
CoderLuii
@waltgrace - Welcome! I'm glad you're giving ChannelWatch a try. The streaming detection issue you're experiencing could be related to the one @slampman reported. To help me troubleshoot, could you check your ChannelWatch logs when you're watching a channel to see if any events are being detected?
If you could create a GitHub issue with some details about your setup (what client you're using to watch channels, any logs from both ChannelWatch and Channels DVR), I'd be able to investigate more systematically.
ChannelWatch - GitHub Issues Page
CoderLuii
@timstephens24 - First, thank you for adding ChannelWatch to the Unraid Appstore! That's fantastic and makes it more accessible to many users. Can you provide the link of this as well?
The TZ variable mapping is an excellent suggestion. Could you please create a feature request on GitHub? This would help me track it properly and have you test the implementation when it's ready. Having sensible environment variable defaults would definitely improve usability for everyone.
ChannelWatch - GitHub Issues Page
CoderLuii
1 Like
@chDVRuser - Thank you for your detailed reports on both the VOD notification issue and the recording schedule problems. Your feedback is incredibly valuable!
The VOD notification behavior is particularly interesting - live channels working correctly while VOD generates repeat notifications suggests a difference in session tracking between modes.
For the recording schedule issue, the sequence of events you provided points to a caching problem with guide data detection.
Since you've identified multiple specific behaviors, could you please create GitHub issues for each? This would help me properly track these unique problems, prioritize them correctly, and ensure nothing falls through the cracks. Different setups and sources can affect how these issues manifest, and your detailed reports will help improve ChannelWatch for everyone.
ChannelWatch - GitHub Issues Page
CoderLuii
I just clicked the New issue button at the website you linked to, but it wants me to sign in to my GitHub account, that I don't have.
I'm not a developer, so don't have, need or want a github account. Just a Channels DVR user who was testing the project you posted about, to provide feedback to you on this Community Forum.
Maybe someone with a github account could post a link there to this forum topic and my post? If not, i'm sure it's easy enough for anyone with a github account to duplicate the behavior I reported.
@CoderLuii, I recommend just meeting people where they are at. If you want to use the Issues area for troubleshooting and tracking, that's fine, but just go ahead and open up the items yourself. It's what I do for most stuff like this and new requests.
2 Likes
@babsonnexus - Thanks for your input. I can see where you're coming from about meeting users where they are.
For a small project like ChannelWatch that I work on in my spare time, GitHub Issues provides structure that forum posts don't - searchability, status tracking, and categorization. It helps me stay organized and efficient with the limited development time I have available.
While creating an account takes just a few minutes for users, creating and maintaining detailed GitHub issues for forum posts takes considerable time away from actual development work.
I value all feedback from the community and will continue reading forum posts, but GitHub remains my preferred method for tracking specific bugs and feature requests.
CoderLuii
1 Like
While that may be true, I don't create new accounts that I'll hardly ever use. To me, that's like someone saying there's an app for everything, why don't you just install all of them on your phone 
To each, his own.
@chDVRuser - Haha, touché with the app comparison For now, I'll do my best to track the issues you've described. If you change your mind about GitHub, the door's always open!
CoderLuii
1 Like
You should be able to find it here: Unraid | Community Apps. I couldn't find it when I searched there, but my other ones (Channels and ADBTuner) show up fine. If you search in Apps on an actual Unraid server it shows up fine as well.
Done, thanks!
Thanks for this utility - looks great. I'm glad to see on the roadmap that you have "Error alerting for system and connection issues" since that is one thing that I'd like most - to be notified if something goes wrong or my Channels DVR server goes down.
One additional feature that would be nice is a bit more granular control in the Recording Alerts. I know the Completed Alerts will indicate if the recording completed successfully or if it failed or was cancelled. I'd like to be able to select to only receive the completed notifications if it didn't complete successfully.
This would tie in with the above feature of system monitoring - to mainly only be notified if something isn't working or didn't record as expected.
Rich