Frndly TV Adds Local Stations to Streaming Lineup in 6 Markets | Next TV
1 Like
@matthuisman I am actually seeing one of these stations now... WACY. Is there anyway of getting it (and the others) associated with it's gracenote id which I believe is 32513 (frndly-111). The others which I can't test because they are not in my market are:
WHDT - 32259
KMCI - 34773
WMYD - 24050
KCDO - 54441
WFMZ - 20289
and again WACY - 32513
If you give him the FrndlyTV channel number, slug and gracenote station id, he should be able to.
Inside will be the Frndly channel number and slug.
Example: Dove Channel, the Frndly channel number is 38(channel-id="frndly-38") and the slug is dove_channel(http://192.168.1.3:8183/play/dove_channel.m3u8)
#EXTINF:-1 channel-id="frndly-38" tvg-id="frndly-38" tvg-logo="https://d229kpbsb5jevy.cloudfront.net/frndlytv/400/400/content/common/logos/channel/logos/kgiodq.png",Dove Channel
http://192.168.1.3:8183/play/dove_channel.m3u8
1 Like
101 -> WFMZ -> 20289
108 -> WMYD -> 24050
109 -> WHDT -> 32259
110 -> KMCI -> 34773
111 -> WACY -> 32513
112 -> KCDO -> 54441
added above
Turns out you can use https://frndlytv-api.revlet.net/service/api/v1/static/tvguide?channel_ids=109 even when out of region and then figure out the channels from the guide data
2 Likes
Hello, What are the working, fully functional, instructions for adding the frndly-tv to the Channels system (only inadequate instructions are provided)? (Live TV, Custom Channels? no description or instructions for what item from the Status page goes where in the Custom Channel screen.)
Using Raspberry Pi os image from getchannels.com downloaded 5-1-2024.
System has connectivity to Public Internet.
Docker has updated and is running frndlytv-for-channels.
When attempting to configure Custom Channels , receive error message:
invalid source url: failed to retrieve m3u: GET: http://dvr-server.local:8183/playlist.m3u8?gracenote=include: 500 Internal server error
Also fails using the ip address instead of the hostname.
Also fails using loopback ip address: 172.0.0.1.
Configuration page does display. http://dvr-server.local:8183/
What can be done to get this working?
What happens when you click on a link from this page? Do you see M3U data in a new browser tab?
That is the Status page for the FrndlyTV add in. As stated earlier, it does display information shown below:
Channels Source 1
Stream Format: HLS
Refresh: Daily
Source URL: http://dvr-server.local:8183/playlist.m3u8?gracenote=include
XMLTV Data URL: (Leave Blank)
Channels Source 2
Stream Format: HLS
Refresh: Daily
Source URL: http://dvr-server.local:8183/playlist.m3u8?gracenote=exclude
XMLTV Data URL: http://dvr-server.local:8183/epg.xml?gracenote=exclude
And, does a new browser tab open and display the M3U data when you click on any of the hyperlinks? (Shown in purple here)
Also make sure you supplied the container with your FrndlyTV USERNAME and PASSWORD per the setup instructions here Frndly TV for Channels
Results are:
Error: Failed to get response from url: https://frndlytv-api.revlet.net/service/api/v1/tvguide/channels?skip_tabs=0
From the Channel Source 2 information shown in prior message, I added the Source witht eh following information, since I found no description regarding which data and 'Channel' information to use:
Custom Channels
Add streams from your IP Camera, SAT>IP, Tvheadend, or other software using M3U playlists.
×Close
Nickname
frndly-tv
Stream Format
HLS
Source
URL
http://dvr-server.local:8183/playlist.m3u8?gracenote=exclude
Options
Refresh URL daily
Ignore channel-number from M3U
Starting channel number (default: 9000)
Prefer channel logos from M3U
No stream limit
XMLTV Guide Data
http://dvr-server.local:8183/epg.xml?gracenote=exclude
Thank you, yes I've added the credentials with the double quotes, as described in the Docker command instructions.
Here are my two sources
If you look at the docker container log, it might give you a clue why it's not working for you.
I still get a failure at my first login .. then it reconnects ... OLIVETIN alert below.
2024/05/13 09:00:03.214826 [ERR] Could not start stream for ANY ch2031 Great American Faith & Living: M3U: Could not fetch playlist from 192.168.50.93:8183: GET: http://192.168.50.93:8183/play/great_american_living.m3u8: 504 Gateway Time-out
2024/05/13 09:00:03.214826 [ERR] Could not start stream for ANY ch2031 Great American Faith & Living: M3U: Could not fetch playlist from 192.168.50.93:8183: GET: http://192.168.50.93:8183/play/great_american_living.m3u8: 504 Gateway Time-out
just wanted to say: Im sorry no-one cares your moving on (myself included).
3 Likes
About a week ago my frndlytv-for-channels docker install failed. I'm getting zero channels on the status page for this tuner. I ran the update steps and had the same result. Checking the logs gives me this:
Requesting: https://frndlytv-api.revlet.net/service/api/v1/tvguide/channels?skip_tabs=0
HTTPSConnectionPool(host='frndlytv-api.revlet.net', port=443): Max retries exceeded with url: /service/api/v1/tvguide/channels?skip_tabs=0 (Caused by NameResolutionError("<urllib3.connection.HTTPSConnection object at 0x7fa3ebcb5070>: Failed to resolve 'frndlytv-api.revlet.net' ([Errno -3] Temporary failure in name resolution)"))
I'm sure my DNS is working and I have tried it on different sites. Is there a workaround for this?
thanks
There are situations where DNS resolution from inside a container may not be working, when it seems fine elsewhere on your network.
To do a quick test, from a command prompt on your docker host:
docker exec -it frndlytv-for-channels apt -qq update && apt -qq install -y bind9-host && host frndlytv-api.revlet.net
And you should see output something like this if DNS resolution is working properly from inside your container:
root@channels:~# docker exec -it frndlytv-for-channels apt -qq update && apt -qq install -y bind9-host && host frndlytv-api.revlet.net
2 packages can be upgraded. Run 'apt list --upgradable' to see them.
bind9-host is already the newest version (1:9.18.24-1).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
frndlytv-api.revlet.net is an alias for frndlytv-api-new-2089997564.us-east-1.elb.amazonaws.com.
frndlytv-api-new-2089997564.us-east-1.elb.amazonaws.com has address 23.21.48.249
frndlytv-api-new-2089997564.us-east-1.elb.amazonaws.com has address 34.234.80.23
frndlytv-api-new-2089997564.us-east-1.elb.amazonaws.com has IPv6 address 2600:1f18:6257:3201:b2a3:d151:c455:8df5
frndlytv-api-new-2089997564.us-east-1.elb.amazonaws.com has IPv6 address 2600:1f18:6257:3202:9dc3:5e7d:8574:1723
1 Like
Thanks for that. I reran the container with the --dns option and it has been resolved.
1 Like
Anyone else having issues with Hallmark Drama and Hallmark Mystery? All other channels seem to be working but these two fail every time.
2024/05/30 12:09:22.421416 [ERR] Failed to start stream for ch9005: M3U: Could not fetch playlist from 10.10.10.50:8183: GET: http://10.10.10.50:8183/play/hallmark_movies___mysteries.m3u8: 500 Internal Server Error
2024/05/30 12:09:22.421502 [HLS] Couldn't generate stream playlist for ch9005-dANY-ip10.10.10.206: M3U: Could not fetch playlist from 10.10.10.50:8183: GET: http://10.10.10.50:8183/play/hallmark_movies___mysteries.m3u8: 500 Internal Server Error
2024/05/30 12:09:22.421558 [HLS] Stopping transcoder session ch9005-dANY-ip10.10.10.206 (out=0s finished=false first_seq=0 last_seq=-1)
2024/05/30 12:09:28.353463 [ERR] Failed to start stream for ch9017: M3U: Could not fetch playlist from 10.10.10.50:8183: GET: http://10.10.10.50:8183/play/hallmark_drama.m3u8: 500 Internal Server Error
2024/05/30 12:09:28.464769 [HLS] Couldn't generate stream playlist for ch9017-dANY-ip10.10.10.206: M3U: Could not fetch playlist from 10.10.10.50:8183: GET: http://10.10.10.50:8183/play/hallmark_drama.m3u8: 500 Internal Server Error
2024/05/30 12:09:28.464966 [HLS] Stopping transcoder session ch9017-dANY-ip10.10.10.206 (out=0s finished=false first_seq=0 last_seq=-1)
Yep Friendly is down XFINITY TVE is working