Posts by chewitt

[Unit]
Description=TimeCapsule Mount Script
Requires=network-online.service
After=network-online.service
Before=kodi.service

[Mount]
What=//172.16.40.100/TIMECAPSULE
Where=/storage/timecapsule
Options=username=kodi,password=kodi,sec=ntlm,vers=1.0
Type=cifs

[Install]
WantedBy=multi-user.target

Save that ^ as /storage/.config/system.d/storage.timecapsule.mount then "systemctl enable /storage/.config/system.d/storage.timecapsule.mount" and reboot, and the local mount to the device should be available to add as a new source in Kodi. It appears to be stable for me over a period of several hours. If 'mount' works the issue appears to be in smbclient or how Kodi interacts with smbclient.

Fenderman You will need to rescrape content to the library as all paths to content will change, but at least it works. It is technically possible to update the DB paths but that requires some sqlite SQL skills and I never bothered to learn those. I'm sure there's a howto somewhere.

dmesg shows no signs of an optical device being attached .. bad USB ports or cable?

wrxtasy fancy making a "droid-tools" add-on with the HK version of wiring pi ?

Yes

I've not seen issues with accessing the TC from another device (masOS sierra laptop) using SMB (not AFP) at the same time things in Kodi die and restarting Kodi from the console immediately allowed Kodi to work again for another 30 seconds so I'm not convinced it's a TC problem. I also did some experiments with longer Samba connection timeout values in advancesettings.xml but it made no difference. I might put smb debugging on in Kodi, although that mostly generates a ton of verbose crap that I don't understand so I wouldn't expect a eureka moment. I'll also play about with kernel level mounts to see if the same problem exhibits there.

Quote from donbrew

Linux people are obsessed with accounts and passwords for security, they don't understand that most home users don't care about security; Windows has ways to get around that stuff, for now.

Good advice will always be inclusive of users and will push, direct or persuade them towards better security habits. If you want to preach insecure habits we'd prefer you to keep quiet and not offer the advice. Fortunately Microsoft is also (finally) taking security more seriously. Feel free to note their current dislike of anonymous access and general direction towards everything being properly password protected, like Linux.

Sorry I thought this was some internal device, but nothing shows. Rinse/repeat with "lsusb | paste"

Kodi smbclient defaults to SMB3 so if you set minimum it will continue to attempt (and fail) with SMB3. Hence the option allows you to force the maximum protocol versionto be SMB1 which prevents SMB2/3 interfering.

client max protocol = NT1
client use spnego = no
client NTLMv2 auth = no

^ adding those to /storage/.kodi/.smb/user.conf and restarting Kodi (or rebooting) allows me to access an existing share in sources.xml although when browsing pictures in a share the connection seems to die regularly. Browsing photo's has always been partially broken in Krypton for me so I'm not sure if it's also the same with video. I'm actually surprised Apple hasn't done a firmware update to support SMB2/3 on these boxes; time to get a proper NAS!

Quote from donbrew

Add the source by typing the network path then provide user name and password. Samba browser is gone in the new version.

That is in the release notes.

^ that is wrong information for this use case.

mount -t cifs //172.16.40.100/SHARE /storage/tcshare -o user=kodi,password=kodi,sec=ntlm,vers=1.0

^ that works from the console so worst case you can use local mounts to access. I will see whether I can translate that into working smb.conf

I have remembered that my Apple router is in fact a TimeCapsule so I will play about with it and see what I can figure out. They use Apple's own interpretation of SMB protocols not Samba so there is bound to be something unusual required.

Random guess.. OE hasn't been updated since June so won't be using a current version of inputstream.adaptive. LE has a much newer version and the defaults may have changed from HLS to DASH. Go fiddle with YT settings and see swapping between them makes a difference.

I found two sites that list the AzureWave AW-NB136NF module as having a BCM43142 chip, not BCM43231.

Please run "lspci -nn | paste" and share the URL so I can see the actual device IDs.

Nothing has changed between releases and the original Kodi language packs and weather add-ons are found in the Kodi add-on repository, not the kodinerds repo. The only difference is that the Pi0W has maybe a slower loading network driver so the initial repo check fails and thus there appears to be no addons available. As Klojum already said, refreshing the Kodi repo resolves this.

I've no idea about support for data DVDs, but Kodi has no hot-plugging support so it will not detect a DVD drive connected after Kodi starts.

basically.. no

compile [LibreELEC]