Posts by chewitt

You can use "scp" or "rsync" to securely move addon and media files to the remote Pi (use SSH key authentication and disable password auth) but you cannot install the addon without restarting Kodi and then manually enabling the automatically-disabled addon.

Once you fix the MAC address and then set connection properties for that MAC in connman (via any method) things will persist normally. There is no need for any extra logic.

Two comments:

You are free to use our project logo to indicate compatibility with our distro (fair use) but we are not your "partner" so please remove our logo and the Kodi Logo from that section of the website - or simply remove the whole section since I'm confident the Raspberry Pi Foundation and WeTek are not your partners either. I'll leave this thread for 24h to allow for changes. If no change, it will be trashed.

Also, in the world of Kodi "Wizards" are frequently associated with Piracy so it would be a good idea to provide links to sources for your addon under a FOSS license so the code can be openly inspected for security and privacy issues.

Thanks.

Connman persists connection data against the interface MAC address and you probably have a cheap USB dongle (or Android box) where the MAC address isn't preset in the factory (as the manufacturer was too cheap to buy an address range) and when there is no preset MAC most kernel drivers assign a random MAC, thus on each boot the persisted connection data doesn't match the current MAC and you need to create a "new" config again. You must also configure connman via the settings addon GUI or the connmanctl command line client. Manual edits to those files have to be made with connman stopped (in which case you will have no network) else connman can update/overwrite the files at any time.

(
sleep 10
/usr/sbin/ip link set dev wlan0 down
/usr/sbin/ip link set dev wlan0 address aa:bb:cc:dd:ee:ff  <= set a MAC address
/usr/sbin/ip link set dev wlan0 up
)&

If my hunch is correct, adding ^ that to /storage/.config/autostart.sh will overwrite the random MAC with a persistent one of your choosing on each boot. You may need to delay Kodi start in LE settings to allow for the network going down/up during startup.

It's an S905X device with Realtek Ethernet. You can grab the device-tree file from the original OS.

If the TV supports CEC you can use the TV remote (CEC is active by default) to navigate and turn SSH on; it's off by default for good reasons. If CEC isn't an option you'll need to borrow a USB keyboard from someone.

If the TV supports CEC you can use the TV remote (CEC is active by default) to navigate and turn SSH on; it's off by default for good reasons. If CEC isn't an option you'll need to borrow a USB keyboard from someone.

It's not a problem specific to RPi devices. The H.264 standard specifies 8-bit content so while it's technically possible to rip media into a 10-bit version of the format, nobody makes GPU/SoC chips that support it and all devices CPU decode it. Most Anime fans end up migrating to Intel NUC's (or similar x86_64 boxes) because lots of CPU grunt is needed to decode with all the fancy GPU based video post-processing that the Anime scene seems to like.

You know the settings addon is available under Addons > Program addons from the Home screen?

Not without either migrating code from LE Settings to Kodi core or doing major hacking to a skin.

It's not possible to PIN protect LE-Settings though, so it might be a moot point.

8GB eMMC module is enough, 16GB would be better as it allows some working space for backups to be created etc.

There's nothing exotic about your setup so as long as you're using valid credentials it should just work. No need to force to SMB1 or use legacy security as long as you're using LE 8.2 or newer as SMB2/3 are supported.

NB: If sources.xml contains Windows smb:\\server\path references I'm not sure how those are interpreted on Linux where smb://server/path is used (backslash vs. forwardslash).

I've moved the thread to the correct location in the forum.

Please provide a Kodi debug log showing a manual refresh of the repo.

If the "not working" TPLINK TN-722 is timing related you might need to add a "wait for Kodi" startup delay - in network settings in the LE settings addon. This just delays Kodi start for 'x' seconds to allow time for slow loading drivers to finish before Kodi attempts to access things on remote shares. You won't see this problem with desktop distro's but LE boots a lot faster and the slow activation of some (mostly realtek and poorly written out-of-tree) drivers can be exposed.

The ProFTPD addon in our repo (services) may support LFTP but no guarantees. If not you'll need to adapt your script to use something like scp or rsync to move files between locations.

You must do special things to your browser and OS then. For everyone else this forum has black text on a pale grey background. There is also no white text in the USB/SD creator app. PEBKAC.

If you enable SSH on the NAS and install the public SSH key for the HTPC user you can use key-based authentication between HTPC and NAS and there is no need to handle passwords or locally mount remote shares. You can create a backup script on /storage using the nano or vi text editors (via an SSH session). Run "crontab -e" to edit the cron schedules for the root user on the HTPC. There are lots of cron HOWTO's around that describe how to set things up - so I won't spoil the learning experience by doing all the work for you

The main thing to remember with cron is that you need to include the full path to any binaries you execute, e.g. /usr/bin/bash, and the full path to the script that bash will run, e.g. /storage/scripts/backup.sh