I have my Vero4k working fine with a separate RPi running TVHeadend. It’s set up over the network and streams the channels fine.
I now have a second TVHeadend on a different RPi with a different set of channels I would like to add.
It appears the OSMC Client only supports a single IP address. Is it possible to add a second TVHeadend or not?
If it’s not possible, is the workaround to set up just one TVHeadend, but then on that RPi install, set up the second RPi as a network source and have that aggregate the streams?
What’s the best way of doing this?
TIA 
No. You can set up multiple servers in the TVheadend HTS client addon.
Thanks @grahamh but how do I do that exactly?
It looks like I can only have one instance of the add-on installed.
If I go to the add-on browser and look at the PVR clients, I already have the Tvheadend HTSP Client installed and enabled. If I go into Configuration, it only gives me the option of entering a single Tvheadend hostname or IP address.
It was a recent addition to the TVH HTSP client. You may have to update to Kodi 21.1 which is available now. My TVH client is 21.2.5.
Ahh that must be why.
My Vero 4k is running OSMC 2020.11-1 kernel 3.14.29-160-osmc
I’ll look at how to update it (apt isn’t working as the repositories are out of date)
You are running a version of OSMC that is almost four years old.
I would suggest updating. You will need to reinstall.
Thanks Sam.
I now have a new challenge - I’ve made the image on a USB stick (tried using both the OSMC installer and using Balena) but after restarting with the USB inserted, it gives me the 60 seconds before formatting, goes through with that and then upon a reboot, I get the “fatal error could not find a suitable init on the root filesystem”.
The install log that ends up on the USB drive has the following:
Sun Jan 1 00:00:13 2017 Starting OSMC installer
Sun Jan 1 00:00:16 2017 Detecting device we are running on
Sun Jan 1 00:00:16 2017 Mounting boot filesystem
Sun Jan 1 00:00:16 2017 Trying to mount to MNT_BOOT (/mnt/boot)
Sun Jan 1 00:00:16 2017 Using device->boot: /dev/mmcblk1p1 and FS: fat32
Sun Jan 1 00:00:16 2017 Trying to mount to MNT_BOOT (/mnt/boot)
Sun Jan 1 00:00:16 2017 Using device->boot: /dev/sda1 and FS: fat32
Sun Jan 1 00:00:16 2017 Filesystem defined by /mnt/boot/filesystem.tar.xz
Sun Jan 1 00:00:16 2017 No preseed file was found
Sun Jan 1 00:00:16 2017 Flash looks OK
Sun Jan 1 00:01:19 2017 Creating root partition
Sun Jan 1 00:01:21 2017 Calling fmtpart for partition /dev/vero-nand/root and fstype ext4
Sun Jan 1 00:01:22 2017 Creating filesystem with 3716096 4k blocks and 930240 inodes
Filesystem UUID: 11e46955-9e0b-4c96-a40e-e8f1bc54300b
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208
Allocating group tables: 0/114 done
Writing inode tables: 0/114 done
Creating journal (16384 blocks): done
Writing superblocks and filesystem accounting information: 0/114 done
Sun Jan 1 00:01:22 2017 From a root partition of /dev/vero-nand/root, I have deduced a base device of /dev/vero-nand/roo
Sun Jan 1 00:01:22 2017 Mounting root
Sun Jan 1 00:01:22 2017 Trying to mount to MNT_ROOT (/mnt/root)
Sun Jan 1 00:01:22 2017 Using device->root: /dev/vero-nand/root
Sun Jan 1 00:01:22 2017 Extracting files to root filesystem
Sun Jan 1 00:01:22 2017 Starting extract process ...
Sun Jan 1 00:01:22 2017 Extracting from /mnt/boot/filesystem.tar.xz
Sun Jan 1 00:01:22 2017 Halting Install. Error message was: tar: short read
Sun Jan 1 00:01:22 2017 Extraction of root filesystem completed
Sun Jan 1 00:01:22 2017 Configuring bootloader
Sun Jan 1 00:01:22 2017 Boot changed. Re-mounting the real /boot
Sun Jan 1 00:01:22 2017 Trying to unmount MNT_BOOT (/mnt/boot)
Sun Jan 1 00:01:22 2017 Trying to mount to MNT_BOOT (/mnt/boot)
Sun Jan 1 00:01:22 2017 Using device->boot: /dev/sda1 and FS: fat32
Sun Jan 1 00:01:22 2017 Configuring bootloader: moving /boot to appropriate boot partition
Sun Jan 1 00:01:22 2017 Vero 4K family: bootloader to be flashed is uboot-vero4k.bin
Sun Jan 1 00:01:22 2017 Configuring boot cmdline
Sun Jan 1 00:01:23 2017 Configuring /etc/fstab
Sun Jan 1 00:01:23 2017 Successful installation. Dumping log and rebooting system
Use another USB, that one looks corrupted
Ah yes I had missed that.
However, I wonder if I have everything.
When I used the installer, it creates just three files: dtb.img, filesystem.tar.xz and kernel.img.
The filesystem.tar.xz is zero bytes so I guess something’s wrong?
Aha! The file download https://ftp.fau.de/osmc/osmc/download//installers/diskimages/OSMC_TGT_vero3_20240825.img.gz I think is wrong. The resulting OSMC_TGT_vero3_20240825.img.gz file doesn’t have the filesystem.tar.gz file in it, or rather it’s zero bytes.
If I get the https://ftp.fau.de/osmc/osmc/download//installers/diskimages/OSMC_TGT_vero3_20240528.img.gz file, it has a 225MB sized filesystem.tar.xz.
So I think you need to check the source file on the webserver, it’s corrupt / incomplete!
I’ve triggered a rebuild of this installer just in case. It should be updated in a short while.