Posts by jbinkley60

    I did some additional debugging and the issue appears to be related to urllib within LibreElec. I created a simple script and ran it from the Python REP under Python on Windows and Python on LibreElec :


    Python 3.7.7 (tags/v3.7.7:d7c567b08f, Mar 10 2020, 10:41:24) [MSC v.1900 64 bit (AMD64)] on win32


    import urllib.request, urllib.parse, urllib.error


    arg1 = "?contentdirectory=http://192.168.0.34:53168/ContentDirectory/control;mode=server;objectID=taz1l0z1l13"

    args = urllib.parse.parse_qs(arg1)


    print(arg1)

    ?contentdirectory=http://192.168.0.34:53168/ContentDirectory/control;mode=server;objectID=taz1l0z1l13

    print(str(args))

    {'?contentdirectory': ['http://192.168.0.34:53168/ContentDirectory/control'], 'mode': ['server'], 'objectID': ['taz1l0z1l13']}


    Python 3.8.8 (default, Mar 11 2021, 14:17:31) [GCC 10.2.0] on linux


    import urllib.request, urllib.parse, urllib.error


    arg1 = "?contentdirectory=http://192.168.0.34:53168/ContentDirectory/control;mode=server;objectID=taz1l0z1l13"

    args = urllib.parse.parse_qs(arg1)


    print(arg1)

    ?contentdirectory=http://192.168.0.34:53168/ContentDirectory/control;mode=server;objectID=taz1l0z1l13

    print(str(args))

    {'?contentdirectory': ['http://192.168.0.34:53168/ContentDirectory/control;mode=server;objectID=taz1l0z1l13']}


    On LibreElec arg1 is not parsed to a dictionary. Under Python on Windows it is.



    Jeff

    I just upgraded my Raspberry Pi 4 from LE 9.2.6 to 10.0b1 . With 9.2.6 I was running the autoexec.py for automatically starting my addon. With Kodi 19 this method was deprecated in favor of a service.autoexec approach. I converted a Windows 10 machine running Kodfi 19 and my Raspberry Pi 4 running LE 10.0b1 to the service.autoexec solution. With Kodi on Windows it works perfectly. With LE on the Raspberry Pi I am not seeing the arguments on my ActivateWindow command being parsed properly. I instrumented the addon to see what is being passed.


    Here's the autoexec.py file which service.autoexec is calling:


    import xbmc


    xbmc.sleep(2000)

    xbmc.log('Kodi Autoexec Service Started.', xbmc.LOGINFO)


    xbmc.executebuiltin("ActivateWindow(10025,plugin://plugin.video.mezzmo/?contentdirectory=http://192.168.0.34:53168/ContentDirectory/control;mode=server;objectID=taz1l0z1l13)")



    Here's what the addon is seeing under Kodi on Windows and LE 10.


    Kodi on Windows:


    Addon args. {'contentdirectory': ['http://192.168.0.34:53168/ContentDirectory/control'], 'mode': ['server'], 'objectID': ['taz1l0z1l13']}


    LE 10:


    Addon args {'contentdirectory': ['http://192.168.0.34:53168/ContentDirectory/control;mode=server;objectID=taz1l0z1l13']}


    LibreElec isn't parsing beyond the first argument.


    My apologies in advance if I posted this in the wrong forum. if so, can the moderator move it ?



    Thanks,


    Jeff

    I rebuilt my Raspberry Pi 4 with a new SD chip. Everything working fine except autoexec.py doesn't seem to be working. It is the same one which was on my 9.2.6 build.


    import xbmc


    xbmc.executebuiltin("ActivateWindow(10025,plugin://plugin.video.mezzmo/?contentdirectory=http://192.168.0.34:53168/ContentDirectory/control;mode=server;objectID=taz1l0z1l13)")


    The window isn't opening on restart.


    Jeff

    If you look in your /etc folder do you see these entries ?


    lrwxrwxrwx 1 root root 27 Sep 2 22:04 rc_keymaps -> /storage/.config/rc_keymaps

    -rw-r--r-- 1 root root 6594 Sep 2 22:04 rc_maps.cfg


    Actually I get the same output when I run the ir-keytable command on my Intel NUC running the latest beta. It actually looks like lircd is running vs. ir-keytable. Maybe there was a change between releases ? I thought prior releases were running ir-keytable but I never looked that closely.

    I upgraded my NUC 8i7BEH to 9.1.002 / 9.2 earlier today. So far no issues across all media types. I'll keep an eye on memory usage since this version is supposed to fix the memory usage issues in earlier releases.

    It's been awhile since I've updated this thread. I worked with the splitter folks and they provided some new software but I still wasn't able to pass bitstream audio through the splitter using my NUC and LibreElec, just with my Vero 4K and OSMC. I decided to treat myself to a new AVR and bought a Yamaha RX-A3080, which is a much newer model than my older Yamaha RX-A3020. With the new AVR I was able to remove the splitter and go full HDMI 2.0 with 4K @ 60 fps. That solved the problem. I am now getting 4K @ 60 fps with bitstream audio. It also allows my streaming TV, which is running through a Roku Ultra into my AVR to run 4K too vs. being limited to 1080P. It was an expensive solution but something I had been planning to do at sometime.

    My issue is resolved. I was behind 2 versions of the PVR addon running version 2.0.1 . The bug was fixed in 2.02:


    v2.0.2 (2019.05.08)


    - Update SQLite database engine to version 3.28.0

    - Prevent multiple Kodi threads from simultaneously requesting EPG data

    - Prevent individually malformed EPG data request results from aborting all remaining requests

    - Fix bug that allowed extraneous EPG entries to be transferred to Kodi

    - Fix bug that prevented successfully setting channel visibility flags

    - Fix bug in database layer that could cause unhandled exceptions processing NULL column values


    I've updated to 2.03 and the issue is resolved.

    Ok, so I answered my own question. I found the kodi.FAILED folder. I deleted both the HDHomeRun addon and the unofficial HDHomeRun PVR addon and things stabilized. I reinstalled both one at a time and Kodi started crashing again once I installed the unofficial PVR client and it started processing the guide. I've placed a note in the HDHomerun foorum where the author closely monitors: Right now I am leaving the PVR client removed and things are stable.

    I am convinced the HDHomeRun PVR Addon is likely causing the issue because the reboots occur while the EPG is being updated as soon a Kodi comes up. How were you able to disable the addon because in Safe mode it isn't installed and thus is stable ? I am stuck in a loop where the reboots and Kodi restarts occur faster than I can do anything in normal mode.


    The 3 Addons which were automatically updated yesterday were:


    Universal Artist Scraper

    Universal Album Scraper

    The Movie Database

    I am seeing the same thing on my Intel NUC. It started a couple of hours ago. I haven't done any troubleshooting yet but it's been rock solid and never booted into safe mode until now. I had the same behavior, multiple reboots and then boot into safe mode. At a causal glance I see where some add-ons automatically updated today. I'll watch this thread and see what comes of this before doing anything else.