CTJohnK

I have several running on one machine, but not in Docker containers. I adjusted the config.ini as well as 'user_config.py' to hard code the 'reporting_friendly_name'. Sometimes when resetting Plex, those...

Given the partial Locast EPG results for DMA 501 below (listing data removed), could the issue be resolved by updating the "known_stations.json"? If so, would the listing example below be...

Looking at the code, it's not getting into the 'except' so the known_stations is not reviewed. And since the callSign is being converted into a float, the trailing zero is...

It appears removing 'float' allows the channel to process, however, I notice 3.5, 3.6, 3.8 and 3.10 show no channel label. This occurs with or without the 'float'. 

Never mind, I've experienced an ID-10T error, they are under '33.x'.

I reloaded DMA 501 on my test setup and re-installed the DVR in Plex. Guide appeared correctly, I'm able to watch and record those channels. @tgorgdotcom perhaps stationsRes[index]['channel'] = float(locast_station['callSign'].split()[0])...

Off topic, but how do you get Locast2Plex to re-scan? When I go back into the DVR config, it reports it cannot connect to Locast2Plex, but it always works, i.e....

I just checked (New York DMA 501) and see the same thing.

In 4.2 I made the "{'Content-Type': 'application/json','User-agent':'Mozilla/5.0'}" change within LocastService.py, but only in the def login. I also made the ffmpeg_proc change within main.py. I rebooted and Plex still indicates...

@biztastic Are you seeing this under "Live TV & DVR" in Settings? If so, I see the same thing, but Locast2Plex is working, the Guide is populated and I able...