I bet your Channels DVR server is not found at "local-server:8089", as that's just an example value. However you normally get to Channels is what you want to use for that value. Personally, I like to use hostnames, but most people on the forum seem to prefer IP addresses.
So my Channels DVR server can be found at http://media-server6:8089, but yours might be something like http://192.168.1.100:8089. You'll need to update that environment variable accordingly.
Feel free to post the other environment variable values you used and I'll let you know if any others look like they might not be correct.
You'll want to stop your OliveTin stack to update any env values, and then click the "Update the stack" button to launch it again.
The first seven are not OliveTin-for-Channels environment variables, so I'm not sure where those came from.
CHANNELS_DVR_ALTERNATES is only for people that have more than one CDVR server -- so delete that one, unless you do have multiple servers.
DVR_SHARE is probably wrong, as that's another example value. This should be the full path on your Synology where the "dvr" directory can be found. I believe it should be something like /volume1/.../.../.../dvr -- but you'd replace the ... parts with the actual folder names in the path from volume1 to dvr.
DVR2_SHARE is also for people with multiple Channels DVRs.
EDIT: I'm not sure /data is valid on Synology either, as I also think it should start with /volume1 -- but I'm not a Synology user.
EDIT2: There are some OliveTin Synology users though, so you can search this thread to find some relevant info like this:
I got it now, was able to generate the m3u, I'm trying to map those channel numbers. Thank you!!
1 Like
I am trying to get this setup in Unraid and the DVR_Share is failing.
I am not sure what exactly it is looking for.
My share is setup in DVR/channels-dvr
But I get the error. Not sure what to put in for DVR_SHARE.
-v '/mnt/user/DVR/channels-dvr/':'DVR_SHARE':'rw' 'bnhf/olivetin:latest'
docker: Error response from daemon: invalid volume specification: '/mnt/user/DVR/channels-dvr/:DVR_SHARE:rw': invalid mount config for type "bind": invalid mount path: 'DVR_SHARE' mount path must be absolute.
See 'docker run --help'.
This can either be a network share (which means you need to create a volume in Portainer first), or it can be a local path if OliveTin is running on the same machine as Channels DVR.
Basically, it's the path to the "dvr" folder in Channels DVR. For me, it's an SMB share:
But everyone's setup is different of course. If you need to set up a Portainer-Volume, there's some detail on that here:
I use Unraid and not Portainer.
One of the prerequisites for OliveTin is Portainer, not that you can't get it going using another container manager -- but Portainer is cross-platform, so once you know how to use it -- it works everywhere.
But back to the problem at hand, are OliveTin and Channels DVR both on your Unraid box?
Try
-v '/mnt/user/DVR/channels-dvr/:/mnt/dvr'
Yes they are. I use Unraid for all my dockers.
This is what I have for setup and it keeps throwing the same error. NO worries if it can't be set up. Just liked some of the tools.
OK, I don't use Portainer, Projects or Compose.
I was talking command line docker commands.
So you'll need another one of those container paths, like you defined for /config, but this one needs to be to /mnt/10.1.1.201-8089 and you'd be mapping it to /mnt/user/DVR/channels-dvr/dvr I would think. Check that path exists, and contains folders similar to my screenshot above.
Nope, same error. No worries I will play with it later and try to figure it out.
Thanks to both of you for helping me.
You don't need the DVR_SHARE environment variable the way you're doing it. Just add that second "Container Path".
What's your latest annotated docker compose?
Could you put it in the original post? Sorry, I see now it's already in the first post.
I'll install portainer on my Synology (should only take a minute) to play around with it.
Took less than a minute.
I just updated it with a couple of minor changes (that were in other feature-specific threads), plus I added the static-file-server container to allow hosting various files (e.g. Plex M3U/XML) from a local URL, for use in Custom Channels sources.
1 Like
Just pushed a new bnhf/olivetin:latest (aka bnhf/olivetin:2024.02.10) that includes the following:
-
When generating an M3U based on a "Channel Collection", custom channel logos are now supported as we're no longer using http://$dvr/devices/$source/channels.m3u as a starting point, but are now using JSON data from http://$dvr/devices/$source/channels. It's a slightly slower process, so it can take a couple of minutes to generate the M3U if you have a large number of channels/sources (timeout set to 180 seconds -- thanks @chDVRuser).
-
The latest and greatest version 3.x of the @mjitkop script: channels_dvr_monitor_channels.py is now included. More detail can be found here: Python script to be notified of channel lineup changes
@bnhf - I just pulled the latest and decided to try the channel lineup change notifications and set it up for sms notification on my t-mobile gateway. I was just wondering if this stdout means everything is normal and that the monitor is running fine.
1 Like
No that error would suggest you didn't supply the e-mail address and password required for this type of SMS message, which uses "SMS gateways" to send texts via SMTP:
So, if you didn't, you'd want to supply your gmail address and the app specific password you created previously. Then, I'm pretty sure your phone number needs to be in the format shown in Wikipedia, based on your carrier.