For almost all the docker containers that I have on my LibreELEC server that interact with the operating system, I use the following parameters for docker creation command in their creation as the 'root' user:
...
-e PUID=0 \
-e PGID=0 \
...
either
...
--user 0:0 \
...
My experience with Digibit Twin tells me that it is unable to tune to some HD channels, verified with Hellas 39ºE satellite.
Although it is not exactly what you are looking for, it may help you find the solution. I try to reboot a remote TV Box when it loses internet connection in the following way:
cron command:
# check every hour
10 */1 * * * /storage/.config/reboot_noip.sh
script /storage/.config/reboot_noip.sh:
#!/usr/bin/env sh
IP=$(curl -s checkip.amazonaws.com)
A=`echo "$IP" | awk '/^([0-9]{1,3}[.]){3}([0-9]{1,3})$/{print $1}'`
if [ -z $A ]
then
# echo "not ok"
reboot
sleep 15s
exit 1
fi
# echo "okay"
exit 0
maybe some expert can give us better alternatives
It is difficult to have an explanation for your problem because you tell us almost nothing. So, I will explain what I do and I assure you that it works perfectly:
My system consists of three drives, 'sda' is the LE drive, and 'sdb' and 'sdc' are my USB storage drives, in these conditions I run the following commands in /storage/.config/autostart.sh :
/storage/.kodi/addons/virtual.system-tools/bin/hd-idle -a sdb -i 300 -l /storage/hd-idle.log
/storage/.kodi/addons/virtual.system-tools/bin/hd-idle -a sdc -i 300 -l /storage/hd-idle.log
For two and a half years I have a self-powered usb 3.0 hub running that powers a 5TB hard drive and six months ago I added a second 5TB hard drive, it also powers some tuners. Well, I have no problem. What is the secret?:
(1) The hub is connected to an i5 mini PC with LibreELEC 9.2.6 that works as a server 24/7 and is never turned off even though it automatically restarts every day at seven in the morning. The hard drives automatically power off when not in use for three minutes, and the only hard drive left permanently working is the internal 256GB SSD.
(2) The external disks are formatted in EXT4 because it works very well with Linux in general and with LE in particular.
(3) I never disconnect hard drives and access is done via the network, usually with SFTP protocol for reading/writing, and WebDAV for reading, FOR ALL DEVICES, including smartphones, TV boxes, smart TVs, and PCs with Windows or Linux . All the management of users, quotas and permissions is carried out by the drakkan/sftpgo docker service running within LE for network access, or directly by LE for internal access (backup services, remote synchronization, etc.).
(4) Once or twice a year I check and repair the hard drives on a Linux PC but have never encountered any problems.
I do not have enough knowledge to comment on the virtues of the NTFS format but what I do know is that Windows plays havoc with hard drives and I am not surprised that you suffer massive corruptions; Solomon's solution is to disallow direct hard drive access to Windows, and allow this only via network sharing.
Regarding exFAT I know enough to tell you not to use this, it is very very very bad.
Good luck!
This is my SSH command for install transmission for docker:
docker run -d \
--name=9091-transmission \
--net=host \
--cpus=0.5 \
-e PUID=0 \
-e PGID=0 \
-e TZ=Europe/Paris \
-e USER=transmission \
-e PASS=libreelec \
-e DOCKER_MODS=linuxserver/mods:universal-wait-for-internet \
-p 9091:9091 \
-p 51413:51413 \
-p 51413:51413/udp \
-v /storage/.config/dockers/transmission/config:/config \
-v /media/5TB-HDD/.transmission/downloads:/downloads \
-v /storage/.config/dockers/transmission/watch:/watch \
-v /media:/media \
--restart unless-stopped \
linuxserver/transmission
replace 5TB-HDD with de name of your partition on external disk
sobralbr :
Are you sure that access to the Thoradia repository is not working?
Yes, all linux shells I know of and use understand the backslash '\' as 'script continues on next line'
I'm swatting flies but it works, in modern IPTV HLS streams with ads, in playlists for tvheadend, I pass the URL of each channel through streamlink+ffmpeg+cvlc using a personal tvhdecode.sh script... and it works .
I sense that now many TV streams or other, include DRM codes that need specific hardware/software in which linux is excluded or license burned in of the SoC itself, and only work well in major browsers or android applications, or some certified devices.
Now I'm testing with Jellyfin clients that receive streams from the server from the playlists generated by tvheadend and the tests are interesting, with Android you can use the processing with the internal player based on ExoPlayer!.
I hope I didn't bore you!
I agree with you, I only use tvheadend with FTA channels, and we allow ourselves the license to record TV shows when we feel like it, although this is also not legal since ..., 2005?
Display MoreThanks for your responses. I am not familiar with this Sat>IP technology at all. Currently, the Wetek box works as a headless tvheadend server. A couple of LNBs are connected to the two input ports via DISEqC switches. It also runs Oscam for decrypting channels. There are some tvheadend clients configured. The number of concurrent subscriptions is generally low, however the box can serve more than two subscriptions if the requested channels located on same DVB muxes. If I understand well, an Sat>IP server transports only selected channel and not a complete mux. In this sense a twin Sat>IP server could provide less capacity than a conventional twin tuner setup, could it?
If I go for a Sat>IP server
- can it manage DISEqC switches and multiple LNBs?
- do I still need a tvheadend server for decrypting and serving multiple Kodi clients?
- I could feed a 4 port Sat>IP server. Digibit R1 price is comparable with an USB twin tuner + an RPi4. The Vbox android gateway does not seem good choice for a headless server use
If I understand well, an Sat>IP server transports only selected channel and not a complete mux: Sat>IP allow full mux RX mode support
can it manage DISEqC switches and multiple LNBs?: yes
do I still need a tvheadend server for decrypting and serving multiple Kodi clients?: yes
The Vbox android gateway does not seem good choice for a headless server use: false, is the same as Sat>IP
The main differences between Sat>IP and VBox are:
For tvheadend Sat>IP is another automatically recognized tuner that does not allow handling any satellite dish motor.
For tvheadend VBox is an IPTV playlist and can't group channels from the same mux, although VBox does.
If you use an enigma2 player as a tuner, then tvheadend also sees it as an IPTV playlist.
Windows always makes hard drives unusable for other operating systems when it goes to sleep or shuts down using techniques called 'Windows Fast Boot or Power Saver'.
I don't know if this happens to you using samba access from Windows to your LibreELEC hard drive, if this is the case then unmount the drive when you're done.
Warning: My little experience with DIGIBIT Twin has been bad, there is no problem with SD channels and a single TV client, but on Hellas Sat 39ºE satellites it is unable to recognize some HD channels that DIGIBIT R1 recognizes without problems. Another alternative to consider is https://vboxcomm.com/product/vbox-a…-for-satellite/ (I have a XTi-3442 2xDVBT/T2 device working fine for almost ten years).
You are correct, system backups do not include the .cache directory and this allows the restore to be done on another device.
My custom backups are run from the 'cron' service every three days and include everything:
cd /media/<my-external-hdd>/.backups/le-backup/ && tar -cvf $(date +%Y%m%d%H%M%S).tar \
--exclude=Thumbnails --exclude=.thumbnails --exclude=.acestream_cache --exclude=temp --exclude=tmp \
/storage/.kodi /storage/.cache /storage/.config /storage/.fluxbox /storage/.ssh
You just need to look at the source:
(I think the name of the docker image is wrong and you should replace 'http://ghcr.io/home-assistant/home-assistant:stable' with 'homeassistant/home-assistant' as it appears on https://localhost, check this yourself)
Very important warning: Before installing a new docker Home Assistant container, remove the previous ones installed. If you don't know docker, study a little starting here https://docs.docker.com/
Mounting a network drive with 'sshfs' is a bit more difficult than 'curlftpfs', however 'sshfs' is supported in LE and 'curlftpfs' is not.
Previous commands that must be executed on a LE/CE client device only once before executing 'sshfs' to a LibreELEC or CoreELEC server:
ssh-keygen -f "/storage/.ssh/known_hosts" -R "[192.168.xxx.yyy]:22"
echo n | ssh-keygen -t rsa -f /storage/.ssh/id_rsa
ssh [email protected] "mkdir -p /storage/.ssh"
cat /storage/.ssh/id_rsa.pub | ssh [email protected] "cat >> /storage/.ssh/authorized_keys"
# where 192.168.xxx.yyy is the IP address of the LibreELEC or CoreELEC SSH serveronly from now on will 'sshfs' mount commands always work.
I don't know what you're doing. LE is able to recognize very few things but recognizes my bluetooth hardware with no problem, tries to find out the hardware can be recognized on your device.
##############################################
# LibreELEC #
# https://libreelec.tv #
##############################################
LibreELEC (official): 9.2.6 (Generic.x86_64)
LibreELEC:~ # bluetoothctl list
Controller B8:9A:xx:xx:81 LibreELEC [default]
LibreELEC:~ #
One other thing: I have installed and uninstalled the 'Home Assistant' docker service twice. The reason: Too complex and heavy 1.5GB, and CPU demanding even for my LE x86_64 server that needs to run the fans. I would never recommend HA for an arm device like RPi4.
As a substitute for 'Home Assistant', I use the real-time android applications 'XMEye' for surveillance cameras, and 'Smart Life', for remote connection and disconnection of electrical devices. LE records the cameras 24 hours a day.