My setup consists of a dedicated Channels server and Shield devices at each entertainment center.

Outside, at the pool area, I use a super cheap Roku TV (wireless) to watch Emby (local channels only via the HDHomerun). While I'm not a fan of Roku devices, it was the only TV, when I purchased it, that was small and allowed me to move it from the closet to outdoor easily.

My imagination got the better of me and I ended up writing a python program that calls a Channels DVR endpoint that provides channel information for TVE. The program creates a m3u file based on this endpoint with all of the live stations that Channels is serving up.

In Emby, I setup a new "TV Source" and pointed to the m3u file. For guide data I'm using iptv-epg.com.

This configuration works great on the Roku using the Emby App. The only issue I'm having is accurate guide data. iptv-epg provides guide data to all of the channels BUT the whole timezone the TVE feed is based on is driving me insane which leaves me to believe I don't understand everything going on.

FX and FXP I configured by setting a time offset in the guide. But this doesn't appear to work for all channels. USA does not return guide data that is even close + or - n-timeshift with what is actually airing.

My question: is there a guide source I can use that is ready-made that matches the Channels DVR guide? If not, any suggestions on understanding where live tv feeds base their guide data. I can always exclude the problem channels, but want to seek help first. Thanks -- Mike

Channels' guide data is provided by Gracenote. Gracenote runs the Zap2It website, so the listings there will be the same as Channels'.

Also, you can get guide data from Schedules Direct (which also uses Gracenote's data) from the xmltv utilities, such as the tv_grab_zz_sdjson and tv_grab_zz_sdjson_sqlite, and then feed the resulting xmltv files to Emby.

Thanks @racameron. I was thinking about going in that direction. I wasn't sure if I would have the same issue. The only negative is I would have to transform the channel numbers to avoid mapping each channel in Emby. iptv-epg does this easily. But right now I have a lot of time on my hands.

Thanks @tmm1 I tried the roku app prior, but buffering was an issue. I created the program (instead of the built-in generator) so I could transform channel numbers for easier mapping. If I go with Schedules Direct, I'll need to transform the numbers for automatic mapping in Emby.

Just added this to my Roku 3 and it still works! There is no guide, but “on now” will still pull the live channels. Looks like all of my recorded movies are there too. The TV recordings are limited to “up next”, no option for all recordings.

The Locast device name is LOCAST-### where "###" is your broadcast market. For example, the LA broadcast market is 803, so my Locast device in Channels is at the /devices/LOCAST-803/channels.m3u endpoint.

I started this thread and thought I would close out my part by posting what I found. This was my first attempt in creating m3u files and working with guide data, so this may be simple to you. I had a lot to learn. Seriously.

The idea seemed simple, use Emby to play live TV from Channels DVR on an old Roku TV that didn’t handle the beta Channels DVR App very well.

In the end I was able to accomplish exactly what I wanted with the added benefit of having all the channels in the order I wanted them (grouped by news, movies, locals, etc.).

I abandoned the iptv-epg service (service quality was the primary issue. I experienced, slow updates to my configuration and the quality of guide data was less than what Channels provides.

I read and tried a lot of tips from various internet sites related to Emby and proper m3u configurations. I found more out-of-date/inaccurate information than answers. I did figure out the key elements of the m3u setup that work with Emby per my implementation goals.

The m3u file needs to provide the exact call sign for a channel, otherwise Emby required lots of channel mapping. That’s a pain. To place the channels in the guide in the order I wanted, I found that using the channel-id tag allowed me to the order the channels in the Emby guide according to my preferences.

I used the built-in Emby guide for tv/show listings, but I had to use several guide sources to get East vs Pacific channels to work without resorting to time-shifting the m3u per channel. I did not have to map any channels in the Emby guide setup, everything just worked. I simply added the m3u source and added the guides.

There may a more direct route to this end, but where I lacked any knowledge, I perhaps took the long route.

Question for you, how exactly did you get the Pacific channels to lineup? I added my local Guide source (i.e. DISH Network) for all non-Pacific channels and then a second Guide Source using a California zip code and mapped ONLY the "P" channels and they aren't quite matching up right, they are essentially showing the exact same lineup, with no time offsets.

Your approach is the same as what I implemented in my setup. To get guide data for all of the channels, I have 4 different Emby Guide sources:

Local for my area

Direct TV New York - Satellite (zip: 10001)

Charter Spectrum - Digital Compton (zip: 90001)

Direct TV - Los Angeles - Satellite (zip: 90001)

I had to use that order to get everything to work.

You will need to normalize the channel names. For example, Channels reports FreeForm as FREEFORM and FREEFORMP. The channel names are FREFMHD and FREFRMP. Once i changed all of the channel names to match the standard name, everything just worked.

Posting part of my m3u file below. As this was my first attempt I can't tell you it is 100% right. It does work however.