Posts by rcrh

  • Can't access SMB share on LE after upgrade to 8.1.1

    Quote from M3Rocket

    I also migrated to 8.1.1 from 8.0.2 and am using Windows 10 Creators Update to access Samba shares. Windows 10 Creators Update has SMB1 disabled by default, so changing the option within LE is pointless. But make sure you enable SMB password in the LE Settings addon and use the name and password listed there when logging into the Samba shares.

    Also backup the old samba.conf. Then copy the samba.conf.sample to samba.conf and reboot LE. In my setup, the previous samba.conf from 8.0.2 did not work at all with 8.1.1.

    All of this plus a couple of reboots of both LE & Windows and now everything is working.

    Thanks M3Rocket!

  • Can't access SMB share on LE after upgrade to 8.1.1

    Update:

    I'm back on the 8.1.1 version of LE and I can't access my SMB shares from Windows 10.

    I've read the info on the blog post:

    • The Kodi SMB client sometimes fails to negotiate SMB3 with old Samba versions. There is a new option in Kodi Settings > Services > SMB client > that allows SMB2 or SMB1 connections to be forced for compatibility with legacy SMB servers.

    I can't find this new option.

    There's also a note on updating samba.conf but no info how do to this.

    • Samba 3.x /storage/.config/samba.conf configurations must be updated to use the new Samba 4.x template (samba.conf.sample) as some Samba 3.x configuration is incompatible. The embedded Samba server may fail to start until this is done.

    Can anyone point me to some instructions to get past this SMB issue?

  • Can't access SMB share on LE after upgrade to 8.1.1

    I've been running LE for a while on 8.0.1 and wanted to update my install to pick up the patches in Kodi 17.4. I upgraded from 8.0.1 to 8.1.1 and everything went fine until I tried to access my LE box to view TVH recordings. I can't access the SMB shares from Windows 10 or from various android devices.

    I tried rolling back to 8.1.0 and had the same error so i went back to 8.0.2. Everything is now fine.

    But I'm now back to a RC of Kodi.

    Does something in my configuration need to be changed with the move from 8.0.x to 8.1.x?

    Thanks in advance.

    ****

    OK, I just saw the release notes on the 8.1.1 blog post. I'll have to look at them in the AM to see if I can get LE, Android & Windows 10 all on the same page.

  • Schedules Direct for Tvheadend addon

    Quote from edit4ever

    The log shows an error in trying to grab a specific station schedule...it seems that the date format got messed up - which is weird.

    Nothing on the schedules direct site has indicated that they made a change. I will do some testing.

    Can you provde the zip and name of the lineup that you are using so I can check the data?

    I'm at 28203 and I'm using the antenna listings. But I made these changes (from the initial post) and things seem to be working now.

    If you have an HDHomerun setup

    select Discover or IP in the HDHomerun Channel Filter

    Discover - should find your device on the network

    IP - if you know the hdhomerun ip address you can enter it here

    Disable the File Based Channel Filter setting

    I also changed the days to 1 and ran it.

    Now I'm getting ten days of schedule.

    Sorry for the possible false alarm.

    Could you explain why I had to configure it for my HDHOMERUN?

  • Schedules Direct for Tvheadend addon

    I'm having an issue with this addon. It doesn't seem to be picking up anything.

    I ran the addon on my backend computer and set all of the options. I then reboot my backend three or four times.

    I then went into TVH and set TV_GRAB_SD4TVH as the only active grabber and set it's priority to 1.

    I then reboot the backend a couple of more times.

    Back in TVH when I look at the log I see this:

    2017-06-17 09:20:48.000 xmltv: /storage/.kodi/addons/script.module.sd4tvh/bin/tv_grab_sd4tvh: grab /storage/.kodi/addons/script.module.sd4tvh/bin/tv_grab_sd4tvh

    2017-06-17 09:20:48.007 spawn: Executing "/storage/.kodi/addons/script.module.sd4tvh/bin/tv_grab_sd4tvh"

    2017-06-17 09:20:51.125 spawn: cat: can't open 'xmltv.xml': No such file or directory

    2017-06-17 09:20:51.126 xmltv: /storage/.kodi/addons/script.module.sd4tvh/bin/tv_grab_sd4tvh: no output detected

    2017-06-17 09:20:51.126 xmltv: /storage/.kodi/addons/script.module.sd4tvh/bin/tv_grab_sd4tvh: grab returned no data

    If I look at EPG grabber channels I only see my old zap2xml channels.

    I'm kinda stuck.

    ***update***

    I found the sd4tvh.log. Here it is

    2017-06-17 09:35:47,248 sd4tvh INFO Getting SchedulesDirect token.

    2017-06-17 09:35:47,546 sd4tvh INFO Getting SchedulesDirect status.

    2017-06-17 09:35:47,682 sd4tvh WARNING Account will expire on 2017-06-24 12:38:38 (6 days).

    2017-06-17 09:35:47,682 sd4tvh INFO SchedulesDirect last update at 2017-06-17 06:18:47 (7 hours 17 minutes ago).

    2017-06-17 09:35:47,683 sd4tvh INFO Message: No known issues.

    2017-06-17 09:35:47,684 sd4tvh INFO Getting station/channel mappings for 1 lineups.

    2017-06-17 09:35:47,698 root WARNING Key(s) not processed for Station: stationLogo

    2017-06-17 09:35:47,699 root WARNING Key(s) not processed for Station: stationLogo

    2017-06-17 09:35:47,699 root WARNING Key(s) not processed for Station: stationLogo

    2017-06-17 09:35:47,700 root WARNING Key(s) not processed for Station: stationLogo

    2017-06-17 09:35:47,701 root WARNING Key(s) not processed for Station: stationLogo

    2017-06-17 09:35:47,701 root WARNING Key(s) not processed for Station: stationLogo

    2017-06-17 09:35:47,702 root WARNING Key(s) not processed for Station: stationLogo

    2017-06-17 09:35:47,704 root WARNING Key(s) not processed for Station: stationLogo

    2017-06-17 09:35:47,705 root WARNING Key(s) not processed for Station: stationLogo

    2017-06-17 09:35:47,706 root WARNING Key(s) not processed for Station: stationLogo

    2017-06-17 09:35:47,707 root WARNING Key(s) not processed for Station: stationLogo

    2017-06-17 09:35:47,708 root WARNING Key(s) not processed for Station: stationLogo

    2017-06-17 09:35:47,709 root WARNING Key(s) not processed for Station: stationLogo

    2017-06-17 09:35:47,711 root WARNING Key(s) not processed for Station: stationLogo

    2017-06-17 09:35:47,712 root WARNING Key(s) not processed for Station: stationLogo

    2017-06-17 09:35:47,713 root WARNING Key(s) not processed for Station: stationLogo

    2017-06-17 09:35:47,714 root WARNING Key(s) not processed for Station: stationLogo

    2017-06-17 09:35:47,714 root WARNING Key(s) not processed for Station: stationLogo

    2017-06-17 09:35:47,715 root WARNING Key(s) not processed for Station: stationLogo

    2017-06-17 09:35:47,716 root WARNING Key(s) not processed for Station: stationLogo

    2017-06-17 09:35:47,716 root WARNING Key(s) not processed for Station: stationLogo

    2017-06-17 09:35:47,717 root WARNING Key(s) not processed for Station: stationLogo

    2017-06-17 09:35:47,717 root WARNING Key(s) not processed for Station: stationLogo

    2017-06-17 09:35:47,718 root WARNING Key(s) not processed for Station: stationLogo

    2017-06-17 09:35:47,719 root WARNING Key(s) not processed for Station: stationLogo

    2017-06-17 09:35:47,719 root WARNING Key(s) not processed for Station: stationLogo

    2017-06-17 09:35:47,720 root WARNING Key(s) not processed for Station: stationLogo

    2017-06-17 09:35:47,720 root WARNING Key(s) not processed for Station: stationLogo

    2017-06-17 09:35:47,721 root WARNING Key(s) not processed for Station: stationLogo

    2017-06-17 09:35:47,722 root WARNING Key(s) not processed for Station: stationLogo

    2017-06-17 09:35:47,722 root WARNING Key(s) not processed for Station: stationLogo

    2017-06-17 09:35:47,723 root WARNING Key(s) not processed for Station: stationLogo

    2017-06-17 09:35:47,723 root WARNING Key(s) not processed for Station: stationLogo

    2017-06-17 09:35:47,724 root WARNING Key(s) not processed for Station: stationLogo

    2017-06-17 09:35:47,725 root WARNING Key(s) not processed for Station: stationLogo

    2017-06-17 09:35:47,725 root WARNING Key(s) not processed for Station: stationLogo

    2017-06-17 09:35:47,726 root WARNING Key(s) not processed for Station: stationLogo

    2017-06-17 09:35:47,727 root WARNING Key(s) not processed for Station: stationLogo

    2017-06-17 09:35:47,727 root WARNING Key(s) not processed for Station: stationLogo

    2017-06-17 09:35:47,728 root WARNING Key(s) not processed for Station: stationLogo

    2017-06-17 09:35:47,728 root WARNING Key(s) not processed for Station: stationLogo

    2017-06-17 09:35:47,729 root WARNING Key(s) not processed for Station: stationLogo

    2017-06-17 09:35:47,730 root WARNING Key(s) not processed for Station: stationLogo

    2017-06-17 09:35:47,730 root WARNING Key(s) not processed for Station: stationLogo

    2017-06-17 09:35:47,731 root WARNING Key(s) not processed for Station: stationLogo

    2017-06-17 09:35:47,732 root WARNING Key(s) not processed for Station: stationLogo

    2017-06-17 09:35:47,732 root WARNING Key(s) not processed for Station: stationLogo

    2017-06-17 09:35:47,755 sd4tvh INFO Getting schedule hashes...

    Traceback (most recent call last):

    File "/storage/.kodi/addons/script.module.sd4tvh/sd4tvh.py", line 407, in <module>

    main()

    File "/storage/.kodi/addons/script.module.sd4tvh/sd4tvh.py", line 403, in main

    app.process()

    File "/storage/.kodi/addons/script.module.sd4tvh/sd4tvh.py", line 112, in process

    schedule_hash_list = self._sd.get_schedule_hash_list(station_ids)

    File "/storage/.kodi/addons/script.module.sd4tvh/libschedulesdirect/schedulesdirect.py", line 201, in get_schedule_hash_list

    schedule_hash_list = [(station_id, parse_date(date), result[station_id][date]["md5"]) for station_id in result for date in result[station_id]]

    File "/storage/.kodi/addons/script.module.sd4tvh/libschedulesdirect/__init__.py", line 17, in parse_date

    return date(*map(int, d_str.split(u"-")))

    TypeError: Required argument 'month' (pos 2) not found

  • two versions on one PC

    Quote from chewitt


    Invest the time and update everything to 17.1, because although it's technically possible to do some kind of dual-boot arrangement on a box to allow booting between LE 7/8 - it's one of those topics where "if you have to ask how it's done?" it will take considerably longer to figure that out (there is no pretty howto guide anywhere) than the effort of updating, which most users understand.

    It's not a question of investing time; One of my boxes runs SPMC and the current version is still on the 16.1 library. Until Koying updates I'm stuck with both versions.
    So my choices are to dump SPMC and loose DTS passthrough or keep running both versions.
    I wish I had stayed with 16.1 but I can't do that either because another box is running MRMC and I can't downgrade it.
    [sigh].

  • two versions on one PC

    I'm using LE to update my shared mysql library. Unfortunately I've ended up with some clients on 16.1 & some on 17.1. I'm wondering if its possible to run both versions of LE so that both kodi libraries can be updated.
    I'm pretty sure they can't run at the same time but perhaps one could start up, update the library and then quit... repeated by the second version.

    Any thoughts?