I am glad that you saw that the SAT>IP server was not at fault. In my experience the SAT>IP servers work very well, I have a secondary CE server based on amlogic S912 that forwards the DVB-T channels, via SAT>IP, to a main server tvheadend LE based on intel x86_64 located 300 km away, and that in turn, It can forward all TV channels (tuners: USB, SAT>IP, and IPTV) to a CE client also based on amlogic S912 located 3000 km from the main server. Well, everything works great.
Posts by elonesna
-
-
What you need is long to explain and there may be many reasons that prevent the update of the EPG on the tvheadend server. Open the address of tvheadend in a browser and type http://<tvheadend-server-ip>:9981 and study the options that refer to EPG. Without disregarding other alternatives my suggestion is:
- Use 'Internal Grabbers' exclusively and forget about 'OTA Grabbers' because they interfere with watching TV.
- Enable 'Force initial EPG grab at start-up' for 'Internal Grabbers'.
- My 'Cron multi-line' for 'Internal Grabbers' setting is "0 */6 * * *" and it causes the EPG to be updated every six hours.
In summary, study a bit the operation of the tvheadend server.
-
-
I have been using SAT>IP tuners (Digibit R1) for several years without any problem, even one of my SAT>IP tuners (Mecool KIII Pro) is 300 km away managed by the minisatip service and sent via VPN to the tvheadend server. I only see continuity errors for channel switching, but they are few and do not affect image quality. Months ago I saw many video image pixelation and continuity errors on the remote tuner when using the ZeroTier VPN. Since I have been using the WireGuard VPN, everything works perfectly. In short, I think the alarms generated by CvH are excessive.
My question is: Is LOLinger78 using a stable version of LibreELEC 9.2.X? because it is not the first time that someone with RPi complains on this forum while using a LE 10.x version.
-
I don't know where the container is saving data if it is at all. I thought it would be in addon_data.
This is easy to fix. Install docker portainer and click on "Exec console" to enter the minecraft directory tree. If you need to access a directory from LibreELEC then delete the minecraft container and run it again adding the parameter "-v <libreelec-directory>:<minecraft-directory>".
Example:
-
But I ran into problems right away following the instructions because of: "-sh: git: not found"
... and if you try this? (seems compatible with any x86_64, arm, and arm64 device)
itzg/minecraft-server: Docker Hub
-
Search the internet for "linux mount samba directories" and "libreelec cifs mount". In LibreELEC you also have the possibility to use the template "/storage/.config/system.d/cifs.mount.sample" and take into account that "/storage/.config/autostart.sh" behaves like a script that is run at startup. You will need to know SSH and SFTP to access the LibreELEC file system. Good luck!.
-
When there would be an option to use fqdn instead of an IP address? In my country, the IPs are changing every week and its awful!
If you think that WireGuard is very complicated (it really is not, although it needs the opening of router ports from the WG server network and also allows the use of DDNS in the WG clients (1) replacing the IP address) you can also try ZeroTier. The latter does not need to declare any public IP or open ports on any router.
(1) Example: myddns.duckdns.org, and you need to update the IP address of the DDNS (I do this in /storage/.config/autostart.sh of the WG server (Example: wget -qO- "$@" "https://duckdns.org/update/<myddns>/<myduckdns-token>" > /dev/null 2>&1).
-
Sorry if I have not explained myself well, I use sshfs. But this only works if the server storage allows SSH / SFTP access.
-
I have no problems although I see that Kodi access (from LibreELEC) to remote libraries with many items in the same directory via FTP or samba is a bit slow while scanning, when with android it is much faster. To solve this I am using the remote directory mount on local LibreELEC directories. This works best.
-
-
Many years ago I stopped using the robweber Backup addon in Kodi because of what you say. The backup/restore of the LibreELEC team has no problem and always works very well, you don't need any other.
-
If you want to automate the backup you can make an executable script scheduled from cron similar to this:
Bash#!/bin/sh # fullbackup.sh script tar cf /storage/backup/$(date +%Y%m%d%H%M%S).tar \ --exclude=Thumbnails --exclude=.thumbnails \ /storage/.kodi /storage/.cache /storage/.config \ /storage/.fluxbox /storage/.ssh find /storage/backup -name "*.tar" -type f -mtime +15 -exec rm -f {} \;
This script deletes backups older than 15 days. I use something like this that runs automatically every 3 days before daily reboot on my device that runs 24/7. It has saved me from some disasters.
The advantage of this method is that it is 100% compatible with the restoration of LibreELEC backups.
-
If I specifically specify the share folder
"\\192.168.1.132 \Backup" it works.
Is that correct?
But I want to see all the shares at once.
Check your samba.conf file
-
Analyze your lsusb or lspci output command after applying the drivers. In my case:
LibreELEC:~ # lsusb
Bus 001 Device 002: ID 8087:8001 Intel Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 004: ID 0bc2:ab62 Seagate RSS LLC <<<---- HARD DRIVE
Bus 003 Device 003: ID 2109:0813 VIA Labs, Inc.
Bus 003 Device 002: ID 2109:0813 VIA Labs, Inc.
Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 002 Device 005: ID 4037:2804 <<<---- MX3 AIR MOUSE
Bus 002 Device 003: ID 8087:0a2a Intel Corp.
Bus 002 Device 006: ID 18b4:1689 e3C Technologies DUTV009 <<<--- DVB-T TUNER
Bus 002 Device 008: ID 1f4d:3000 G-Tek Electronics Group <<<--- DVB-S/S2 TUNER
Bus 002 Device 007: ID 045e:02d5 Microsoft Corp. Xbox One Digital TV Tuner <<<---- DVB-T/T2 TUNER
Bus 002 Device 004: ID 2109:2813 VIA Labs, Inc.
Bus 002 Device 002: ID 2109:2813 VIA Labs, Inc.
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
My best tuners are IPTV or SAT>IP connected via ethernet and don't need drivers:
- XTi-3442 DVB-T/T2: 2 tuners
- DIGIBIT-R1 DVB-S/S2: 4 tuners
-
linuxserver/tvheadend docker container
Build for arch: x86_64
Build: 4.3-1966~g04853f0da (2021-06-09T05:05:38+0200)
Code
Display MoreOptions: pie yes ccdebug no >>>>>>>>>> cardclient yes <<<<<<<<<< cwc yes cccam yes capmt yes constcw yes linuxdvb yes satip_server yes satip_client yes hdhomerun_client yes hdhomerun_static no iptv yes tsfile yes dvbscan yes timeshift yes trace yes avahi no zlib yes libav yes ffmpeg_static no libx264 yes libx264_static no libx265 yes libx265_static no libvpx yes libvpx_static no libtheora yes libtheora_static no libvorbis yes libvorbis_static no libfdkaac no libfdkaac_static no libopus yes libopus_static no nvenc no vaapi yes mmal no omx no inotify yes epoll yes pcre no pcre2 yes uriparser yes ccache no tvhcsa yes bundle no pngquant yes kqueue no dbus_1 no android no gtimer_check no slow_memoryinfo no libsystemd_daemon no pcloud_cache yes ddci yes cclang_threadsan no gperftools no mmx yes sse2 yes W_unused_result yes f_stack_protector yes f_stack_protector_strong yes f_stack_check yes f_PIE yes strlcat yes strlcpy yes fdatasync yes getloadavg yes atomic32 yes atomic64 yes atomic_time_t yes atomic_ptr yes bitops64 yes stime yes gmtoff yes recvmmsg yes sendmmsg yes libiconv yes ifnames yes py_gzip yes bin_pkg_config yes bin_xgettext yes bin_msgmerge yes bin_gzip yes bin_bzip2 yes ssl yes linuxdvbapi yes linuxdvb_ca yes libhdhomerun yes upnp yes hwaccels yes inotify_h yes inotify_init1 yes dvbcsa yes epoll_create1 yes mpegts yes mpegts_dvb yes
-
Which stable version do you guys recommend to update Mecool Pro III S912?
I use CoreELEC 9.2.5 with Kodi 18.9 on this device. I use a minisatip service for forwarding DVB-T channels and ffmpeg together with sshfs for forwarding the stream from a surveillance camera. All this is forwarded to the LibreELEC server located in another town. Mecool KIII Pro also, like any other multimedia client, receives all TV channels, multimedia content and storage space from the server, also allows me to remotely configure the devices on this home network via VPN. Everything works very well.
The LibreELEC AMLGX 10.0 versions for this device are not yet mature but the expectations are good.
-
Zerotier, unlike others, is a VPN in which all the routing rules must be established to reach other network interfaces, the study of this allows it to be applied to other cases like yours. The basic commands that I use are:
Code
Display More# allows forwarding echo 1 > /proc/sys/net/ipv4/ip_forward # if the source address is not reachable the packet check will fail echo 2 > /proc/sys/net/ipv4/conf/all/rp_filter # default routing iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE # allow forwarding from wireguard interfaces iptables -A FORWARD -i wg+ -j ACCEPT # allow forwarding from zerotier interfaces iptables -A FORWARD -i zt+ -j ACCEPT # allow reply to unreachable interfaces iptables -A FORWARD -m conntrack --ctstate RELATED,ESTABLISHED -j ACCEPT