OK, I figured it out.
Yes, you need to specify https or "-L" flag.
Also, if you do not have the "--compressed" flag, it fails. Unfortunately, the default Windows curl binary doesn't allow for that flag (WTH?) Tested it in linux with "--compressed", it worked. So, I retested with the curl windows binary downloaded from curl.se, specified https and the --compressed flag, and it works.
Thank you for saving my sanity. I owe you one.
XMLTV guide data
-
flexduoowner
- Posts: 1
- Joined: Tue Jun 25, 2024 8:29 pm
Re: XMLTV guide data
Would it be possible to get this guide on a Homerun Flex Duo? (HDFX-2US) I was going to buy a subscription but didn't show as supported.
Re: XMLTV guide data
All FLEX models are also supported.flexduoowner wrote: ↑Tue Jun 25, 2024 8:34 pm Would it be possible to get this guide on a Homerun Flex Duo? (HDFX-2US) I was going to buy a subscription but didn't show as supported.
Re: XMLTV guide data
Hello friends,
Every two weeks I need to launch the browser on my phone and navigate to my local HDHR device to see the device auth for the HDHR EPG API:
http://10.0.0.12/discover.json
I then go into the Tivimate settings, EPG, and update the device auth within the HDHR URL.
The OTA channels in the Tivimate guide are then updated to include programming data for the next two weeks.
How do I automate this instead of the manual task every two weeks? I wish the device auth would just remain static for my account, or change like once a year.
Every two weeks I need to launch the browser on my phone and navigate to my local HDHR device to see the device auth for the HDHR EPG API:
http://10.0.0.12/discover.json
I then go into the Tivimate settings, EPG, and update the device auth within the HDHR URL.
The OTA channels in the Tivimate guide are then updated to include programming data for the next two weeks.
How do I automate this instead of the manual task every two weeks? I wish the device auth would just remain static for my account, or change like once a year.