IMPORTANT FOR USERS UPGRADING TO 0.3.x, 0.5.x, or 0.6.x:
- With the architectural changes made to 0.3.x or 0.5.x, a few config and set up tasks have changed. Please re-review the installation instructions for details.
- When upgrading to 0.6.x, we are now using Python 3. If you are not using Docker, please upgrade your system to Python 3.6 or newer
A Python script and Docker image to connect locast to Plex's live tv/dvr feature. Seems to work for Emby, Jellyfin, and Kodi too!
Uses ffmpeg, python, and a few awesome python modules to do most of the heavy lifting. A lot of code was inspired from telly as well.
To prevent legal issues for both Locast and myself, please do not use locast2plex to obtain channels that are outside of your general market area (i.e. in a completely different state). Thank you for understanding.
Time is limited due to other major factors (work, wife/kids), so please understand if I am not able to address all issues or pull requests. I will try my best to help though!
As always, pull requests are welcome.
Currently this is BETA, so regressions may be common in updated versions. I hope for us to be "officially" stable at v1.0
As of 0.3, are now two ways to use locast2plex -- either via a Docker container, or running as a command line/terminal program. Both options are relatively straightforward, so which option you choose would probably be based on what you're more comfortable with and your current setup.
-
Server ("always-on" computer) that is either network accessible to the Plex server, or running on the same server as Plex. Make sure the server you choose is suitable for handling video.
-
If you're using Docker, then make sure Docker is installed on the server. See here for details on getting started with Docker.
-
If you choose to run this as a command line program, the following OSs and programs are required:
- Windows (Mac and Linux probably work too, but this is untested)
- Python 3.6.x or above
- ffmpeg (if running under Mac or Linux). Mac users can usually install this via homebrew, and Linux through their distribution's respective package manager
-
A locast account that you have donated to (non donated accounts have streams that terminate after 5-10 mins, so locast2plex intentionally fails to prevent issues with non donating users and the DVR function). Also be sure you are running the server from the same physical location that you want channels for.
-
Take note of the IP address of the server or container that will 'host' the locast2plex service. This is usually the IP of the server running locast2plex, but there might be additional edge cases here for particular server setups.
Note that the ports used are:
6077
(tcp) for the hdhomerun device emulation service (and can be changed)1900
(udp) for SSDP discovery (which cannot be changed -- see troubleshooting for workarounds).
-
NEW FOR 0.5.x We now use a config.ini file to store our configuration options. Create a new file with the following content in a handy location on your computer, making sure you modify the appropriate fields to match your configuration:
[main] locast_username=<locast username> locast_password=<locast password> plex_accessible_ip=<ip found in step 1>
If you are changing port
6077
, you will need to add anplex_accessible_port
entry in the config file, like so:plex_accessible_port=<new port number>
You can also use the config_example.ini found in the source files. There's some interesting additional options commented out here that you can look at as well.
-
Choose your installation method:
-
Via Docker: Set up the Docker container. There are two options:
-
Docker Compose:
- Download the latest locast2plex release files on GitHub and extract to a folder
- Copy the newly created config file into the newly created release folder, making sure it's named
config.ini
. - Modify the
docker-compose.yml
file your liking. If you are changing port6077
, you will also need to modify the port number in the first ports option, like so:
ports: - "12345:6077"
- Run
docker-compose up
in the release folder.
-
Docker Command (no need to download anything):
Run the following command:
docker run -v <full path to config file>:/app/config/config.ini -p 6077:6077 -p 1900:1900/udp tgorg/locast2plex
If you are changing port
6077
, you will also need to modify the port number in the first-p
argument, like so:docker run -v <full path to config file>:/app/config/config.ini -p 12345:6077 -p 1900:1900/udp tgorg/locast2plex
Also, if you want Docker to start locast2plex on reboot, add
--restart unless-stopped
to the command (thanks @SJLBoulder!)
-
-
Via Terminal/Command Line:
-
Download the latest locast2plex release files on GitHub and extract to a folder
-
Copy the newly created config file into the newly created release folder, making sure it's named
config.ini
. -
Run the following command in the release folder:
python3 main.py
-
-
-
Configure Plex to use locast2plex:
-
In the Plex settings on your server or web interface, select Live TV/DVR on the left-hand menu and add a device as you would normally add a networked tuner.
-
You may need to enter the address manually as SSDP autodiscovery is buggy at the moment. The address will be the value you set as the
docker_accessible_ip
anddocker_accessible_port
(or it's default value) fields inconfig.ini
(for example 127.0.0.1:6077). -
You may or may not see a box appear showing the recognized locast2plex instance, but even if this is not the case, you should be able to use the "Continue" button on the bottom right.
-
-
Configure your channels. A few notes:
-
Make sure you have Plex using the proper "Broadcast" line up EPG for locast's broadcast location
-
Starting with 0.3, stations should have the correct channel and subchannel assignments now. If there were any that were unrecognized, check the troubleshooting list below for assistance.
-
-
Creating a service (Non Docker Users)
-
For Linux users running systemd (thanks @warrenmelnick)
The following must be performed as root (or with sudo):
- Create the user locast2plex and the group locast2plex. This way the script does not have to run as root.
- Move the file locast2plex.service into /etc/systemd/system/
- In terminal, start it with this command:
systemctl start locast2plex
- To make it auto-run on boot (also in terminal):
systemctl enable locast2plex
-
For Windows (from @tharris9d)
See https://github.com/tgorgdotcom/locast2plex/wiki/Setting-up-Locast2Plex-as-a-Windows-Service
-
For Mac... TBA
-
Sometimes locast2plex will not be able to get the correct channel/subchannel number (perhaps an outdated number or a channel number from a similarly named station outside of the market). Stations we don't recognize at all have their channel numbers assigned sequentially from 1000 on.
For now, the easiest way to fix this is to find the correct channel id by research. Usually searching the callsign via Google reveals the correct channel number (sometimes we'll see an updated callsign on a the first result as well). Wikipedia is also extremely helpful here.
In the future, I'd like to implement some additional checks and tests for better channel recognition. If you run into any problems, feel free to submit an issue so at least we can keep track of it.
SSDP is used to try to enable Plex autodetection of the locast2plex instance, but it's currently buggy at the moment. If you're using Docker, you can remove the -p 1900:1900/udp
part of the docker command like so:
docker run -v <full path to config file:/app/config/config.ini -p 6077:6077 tgorg/locast2plex
For docker-compose
users, delete the following line from docker-compose.yml
:
- "1900:1900/udp"
For now, there is no option for straight Python users to disable port 1900. Let me know in GitHub if this is an important option to implement
Additional Troubleshooting notes can be found on the Troubleshooting Wiki Page
Be sure to search the issues to see if there are any fixes found for similar issues. If you see a similar unresolved issue, please create a new issue rather than piggybacking an existing one. Most of the time people who have similar errors have different reasons for that error, necessitating a new issue.
When submitting an issue, make sure to take note of the docker or command line output, and include OS details and what method of install you have chosen (Docker, docker-compose, or via terminal). Note that logs reveal username and approximate location information (in latitude/longitude as well as Locast's Nielsen market id), so be sure to look through what you post and clear out any data you want hidden before posting.
A big THANK YOU to all who have co-developed locast2plex, and/or are answering issues in GitHub (sorry if I missed anyone!):
@CTJohnK, @diana1055, @FozzieBear, @jcastilloalonso, @dcd, @steventwheeler, @precision, @deathbybandaid, @mneumark, @ratherDashing, @tharris9d, @tri-ler, @teconmoon, @dwkane, @RedGreen007, @gogorichie, @teconmoon, @Above2, @paradxum, @rottdog32, @numchucksoe, @begunfx, @yaroz, @JimSpeedo, @toadman50, @c0deweaver, @libersongm, @dnixon1981, @patrick-GH, @Oumpa31, @seantdavidson, @scumola, @BH000, @paradxum, @warrenmelnick, @SJLBoulder, @ThomasPBrauer, @jg-24, @purduepete, @tmwebb2, @Nbr1Sniper, @mazinkhu, @cklinker