Closed gregwa1953 closed 2 years ago
Phrede
commented
2 years ago Having same problems on a Windows install on both Kodi 19.1 and 19.3. HDHomerun/SiliconDust changed API to https: today. Nick said there is a redirect but it doesn't appear to be working here. Notice the URL for recording_rules.
gregwa1953
commented
2 years ago Thanks @Phrede .
Yes, I did notice.
It's bad enough that there's no version of Zuki for Raspian higher than 18.9 so I can't move forward to Matrix and now this happens. I'm not blaming Nick. Just very frustrated right now.
solfrio
commented
2 years ago I'm running CoreELEC and I'm facing the same predicament. I tried to uninstall and reinstall the add-on but that makes it worse. It can't find my Hdhomerun tuners afterwards.
djp952
commented
2 years ago Hi! Sorry I was away on vacation/holiday this past week while this happened. As mentioned by @Phrede, the backend apparently switched to requiring https:. Given how I build/package this addon, mainly for the GNU Linux flavors, https: was problematic to support in the past.
There are two paths forward and I'm afraid neither will be done overnight.
Path 1 is cook back in https: support natively into libCURL, which is easy on Windows and Android but unless I learn a new trick is hard for everything else. Before I was trying to build/link against libssl, maybe I can just set a flag for CURL saying "just load it from the OS", Kodi uses it so it should be there on all the GNU systems.
Path 2 is to just pivot away from using the libCURL I compile for these requests and route them through Kodi. I don't like this option for a few reasons that aren't super important to go into, but if this is how it needs to go, that's what we'll do!
I'm sorry I don't have a quick-fix for everyone, this caught me by complete surprise as well. If there are multiple Issues opened that come back around to this, I may create an overarching one and close/link these individual ones.
On it, but will not have a solution immediately.
gregwa1953
commented
2 years ago Thank you for the update!
djp952
commented
2 years ago Hi! I have test builds available that should fix everything: https://onedrive.live.com/?authkey=%21AISo7jpF%5FU1t9mc&id=BEDA187345100601%21203410&cid=BEDA187345100601
These are marked as "alpha1" but the feedback so far has been positive, so I may just push this out this evening and mop up any untested platform-specific issues with a follow-on release. Note that installing an alpha/beta build does not break auto-update, once the non-alpha/beta goes out Kodi will update to that automatically.
Any feedback you can provide would be greatly appreciated!
solfrio
commented
2 years ago Thanks for the update. Working fine on both Android TV and CoreELEC.
gregwa1953
commented
2 years ago Just downloaded and installed. Set up for a temporary record in 20 minutes.
Looks good.
Is there any chance that you'll be able to make a raspbian version for Matrix soon?
Greg
djp952
commented
2 years ago You shouldn't need a custom Raspbian build for Matrix anymore, that is actually an "ARMv6" build behind the scenes (as opposed to ARMv7). You should be able to use linux-armel or linux-armhf. Besides, Matrix won't compile with the old Raspberry Pi compiler anymore :)
I have 2 Pi 3s and a Pi 4 that I can use to test this out for you, what Operating System are you using, and what hardware device? I can make sure it's all on the up and up and let you know which linux build is "right"?
gregwa1953
commented
2 years ago Thank you.
LibreELEC 10.0 (Kodi 19.3) RPi 4 (at least 4 Gig)
I haven't tried LibreELEC Matrix on the PI yet, since I didn't know there was a version of Zuki for RPi Matrix yet.
Thank you again!
On Mon, Jan 31, 2022 at 1:55 PM Michael Brehm @.***> wrote:
You shouldn't need a custom Raspbian build for Matrix anymore, that is actually an "ARMv6" build behind the scenes (as opposed to ARMv7). You should be able to use linux-armel or linux-armhf. Besides, Matrix won't compile with the old Raspberry Pi compiler anymore :)
I have 2 Pi 3s and a Pi 4 that I can use to test this out for you, what Operating System are you using, and what hardware device? I can make sure it's all on the up and up and let you know which linux build is "right"?
— Reply to this email directly, view it on GitHub https://github.com/djp952/pvr.hdhomerundvr/issues/88#issuecomment-1026151179, or unsubscribe https://github.com/notifications/unsubscribe-auth/AEKEQMJVLSFA6IWJ34CYEL3UY3SLBANCNFSM5M7O5GMQ . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you authored the thread.Message ID: @.***>
-- To be forewarned is to be forearmed. To be forearmed means you can't buy off the rack.
Greg Walters
djp952
commented
2 years ago Yeah, I can totally set that up this evening (I may actually already have Libre 10 on that!). I think it will be the "linux-armel" version but will confirm.
gregwa1953
commented
2 years ago Thank you Michael!. I'm looking forward to hearing which version I should use.
On Mon, Jan 31, 2022 at 2:06 PM Michael Brehm @.***> wrote:
Yeah, I can totally set that up this evening (I may actually already have Libre 10 on that!). I think it will be the "linux-armel" version but will confirm.
— Reply to this email directly, view it on GitHub https://github.com/djp952/pvr.hdhomerundvr/issues/88#issuecomment-1026160743, or unsubscribe https://github.com/notifications/unsubscribe-auth/AEKEQMKT5C67FFVFNDUIWRDUY3TVVANCNFSM5M7O5GMQ . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you authored the thread.Message ID: @.***>
-- To be forewarned is to be forearmed. To be forearmed means you can't buy off the rack.
Greg Walters
solfrio
commented
2 years ago I just noticed that Hdhomerun released another update to it's tuners and recording engine (20220128). Hopefully this new update doesn't break the add-on again.
gregwa1953
commented
2 years ago I threw together a quick SD card of Libre 10.0 (for some reason 10.1 failed to run) and I used the "linux-armhf". The armel wouldn't install.
Right now, "linux-armhf" seems to be working well. I had to try to remember the last configuration settings the best I could, and now it seems to be working very well.
THANK YOU MICHAEL!!!!!!!!!!!!!!! Once again, you are a ROCK STAR!
I'll leave the issue open for a few days for anyone else to comment, then I'll close it out.
djp952
commented
2 years ago I've added a TODO to actually sit down and document this for everyone: https://github.com/djp952/pvr.hdhomerundvr/issues/99
In honor of you doing it for me, I added your scenario as the sample :)
gregwa1953
commented
2 years ago Thank you Michael. Still testing, but looks very good!
On Mon, Jan 31, 2022 at 9:08 PM Michael Brehm @.***> wrote:
I've added a TODO to actually sit down and document this for everyone: #99 https://github.com/djp952/pvr.hdhomerundvr/issues/99
In honor of you doing it for me, I added your scenario as the sample :)
— Reply to this email directly, view it on GitHub https://github.com/djp952/pvr.hdhomerundvr/issues/88#issuecomment-1026436072, or unsubscribe https://github.com/notifications/unsubscribe-auth/AEKEQMJF5V6XRX36LXKH7O3UY5FBJANCNFSM5M7O5GMQ . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you authored the thread.Message ID: @.***>
-- To be forewarned is to be forearmed. To be forearmed means you can't buy off the rack.
Greg Walters
gregwa1953
commented
2 years ago The only complaint (not really a complaint, but question) is that when I go to the EPG, it defaults to HEVC channels rather than All Channels.
Right now, we live in a fringe area where OTA signals are fair at best (if there are no weather fronts in the area) and while HDHR does recognize that there are a few HEVC channels in the area, none of them come through.
I'd rather that when I switch to EPG, it shows all channels rather than HEVC channels by default. I'm guessing that there is a setting that I missed. Could you point me to that setting?
Thank you in advance,
Greg
djp952
commented
2 years ago Kodi should default to All Channels at first and then remember what the last channel group you had set was and default to that on the next run. No setting I am aware of, maybe LibreELEC customized this in their build (not sure why they would do that, though)
You can make sure you have PVR & LIve TV / General / Synchronise channel groups with backend(s) enabled and maybe execute a Clear Data to wipe out anything stuck in Kodi's database? I know of a number of ways to break Channel Groups in Matrix, nuking them with the Clear Data always cleans them up, maybe it will for you?
gregwa1953
commented
2 years ago As always, your suggestion to Clear Data fixed it. Sync was already enabled.
Thank you again!
On Tue, Feb 1, 2022 at 8:05 AM Michael Brehm @.***> wrote:
Kodi should default to All Channels at first and then remember what the last channel group you had set was and default to that on the next run. No setting I am aware of, maybe LibreELEC customized this in their build (not sure why they would do that, though)
You can make sure you have PVR & LIve TV / General / Synchronise channel groups with backend(s) enabled and maybe execute a Clear Data to wipe out anything stuck in Kodi's database? I know of a number of ways to break Channel Groups in Matrix, nuking them with the Clear Data always cleans them up, maybe it will for you?
— Reply to this email directly, view it on GitHub https://github.com/djp952/pvr.hdhomerundvr/issues/88#issuecomment-1026879396, or unsubscribe https://github.com/notifications/unsubscribe-auth/AEKEQMP4RDQYVCH2SKMGUIDUY7SDXANCNFSM5M7O5GMQ . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you authored the thread.Message ID: @.***>
-- To be forewarned is to be forearmed. To be forearmed means you can't buy off the rack.
Greg Walters
gregwa1953
commented
2 years ago No one has added anything for a while, so everything looks good for this issue.
I'm going to close it.
Thank you once again Michael!
Error log says... 2022-01-27 18:44:38.653 T:2552226624 NOTICE: AddOnLog: HDHomeRun DVR PVR Client: discover_episodes: initiated recording rule episode discovery 2022-01-27 18:44:38.826 T:2552226624 ERROR: AddOnLog: HDHomeRun DVR PVR Client: scheduled task failed due to an exception: HTTP 301: Moved Permanently (1) 2022-01-27 18:44:38.829 T:2552226624 NOTICE: AddOnLog: HDHomeRun DVR PVR Client: update_listings_task: listing discovery skipped; data is less than 18 hours old 2022-01-27 18:44:38.952 T:2543833920 NOTICE: PVR Manager: Started 2022-01-27 18:44:40.902 T:2870932288 NOTICE: EPG thread started 2022-01-27 18:44:55.373 T:2881561408 ERROR: CCurlFile::Stat - Failed: HTTP response code said error(22) for https://www.thetvdb.com/banners/ 2022-01-27 18:45:13.343 T:3011921280 ERROR: AddOnLog: HDHomeRun DVR PVR Client: AddTimer failed due to an exception: http post request on [http://api.hdhomerun.com/api/recording_rules] failed with cURL error: Unsupported protocol (1) 2022-01-27 18:45:13.344 T:3011921280 ERROR: AddTimer: Add-on 'zuki.pvr.hdhomerundvr:api.hdhomerun.com' returned an error: the command failed 2022-01-27 18:45:39.348 T:3011921280 ERROR: AddOnLog: HDHomeRun DVR PVR Client: AddTimer failed due to an exception: http post request on [http://api.hdhomerun.com/api/recording_rules] failed with cURL error: Unsupported protocol (1) 2022-01-27 18:45:39.348 T:3011921280 ERROR: AddTimer: Add-on 'zuki.pvr.hdhomerundvr:api.hdhomerun.com' returned an error: the command failed
What's going on? This just started tonight. My subscription is good, so why can't I set any new timers?