Posts by Da Flex

Does it start when you enter this line?

/storage/hyperion/bin/hyperiond.sh

That's because the path to the Hyperion start command is somewhere else in LibreELEC. Let's find it. Please post the output of this command from SSH login:

find / -name "hyperion*" -print

Excellent, that's it!

If you only have a Win10 PC, you can edit the files by SSH login (use PuTTY).

If you have a Linux PC, simply remove the MicroSD card, and plug it into the PC.

Create the directory "/storage/hyperion/scripts" for the scripts.

On SSH:

mkdir /storage/hyperion
mkdir /storage/hyperion/scripts

Copy "ledon.py" and "ledoff.py" into that folder.

Insert this code into autostart.sh, if you want to start Hyperion by default:

#!/bin/sh

(
    python /storage/hyperion/scripts/ledon.py
) &

Copy "remote.xml" into the "/storage/.kodi/userdata/keymaps" folder, if you want to switch it on and off by red and green remote buttons.

Tell us, if it works!

Quote from kogbok

I try with Rapsberry 2 and Amp+ and last LibreElec.

In this configuration, everything is good.

This indicates a PSU issue, too. The RasPi 3B+ needs more wattage by default. In case you are using WiFi for NFS access, I'm very sure that it's a PSU issue. WiFi transmission needs more wattage, compared to Ethernet.

It's better to remove all unnecessary hardware to find the bug. Just use the RasPi and the MicroSD card.

OK, I will have a look at the LibreELEC add-on repository. If I find it, I can install it to see what shell commands it provides. Maybe adding the right command to autostart.sh is all you need.

Is "hyperion creator" part of an add-on? If yes, is it an official add-on from the LibreELEC repository? What's the name of the add-on?

PS: I'm asking because there are two ways to install Hyperion: By using HyperCon (Win10) installer, or by using a LibreELEC add-on.

How do you usually start Hyperion after you have been plugged in the power cable for RasPi / Hyperion?

The autostart.sh calls a Python script. The Python script will set electrical levels to specific GPIO pins. A device, connected to GPIO (Hyperion), will listen to those level changes at GPIO. That's usually the way to start or reset connected RasPi hardware.

When I have some time, I will have a look at the Hyperion project.

I can help you to adapt the scripts, but I need the necessary infos for Hyperion GPIO events.

English is not my mother language. "Outage" means an electrical accident, and no power for a short time, right?

After that outage, the RasPi and LibreELEC will start. You can trigger the fitting GPIO signals by using autostart. In the Python script (see link above), you can learn how to set GPIO levels. I don't know the right pins / signals to start Hyperion. That's not part of LibreELEC. Can you do a research for this?

Quote from xevipc1

I could handle cutting off the power with smart plug or whatever, but I found out that if I cut power (I am powering Rpi through Leds via Gpio), hyperion does not start automatically when I power on again. Leds remain off.

I wouldn't do that. It's better not to cut the power for the RasPi. Use a RasPi power button instead. That should keep Hyperion in a defined state, and should power it on with the RasPi when the power button is pressed. You can use PuTTY on Win10 to add the necessary scripts to RasPi.

For the installation of the button, you may have some space between the RasPi Ethernet port and the upper part of the RasPi case. If you have enough space there, you can just lay the button on the Ethernet port without mounting it permanently. Then you just have to drill a hole over the Ethernet port, insert the button and close the case to fix it.

Here is the button that I use: 10x tact push buttons. With some cables and basic soldering skills everybody can do it.

I still don't understand your setup, especially "I am powering Rpi through Leds via Gpio".

Generally, you can have an on/off button on the RPi, you can autostart scripts when LibreELEC starts, and you can trigger scripts by GPIO events. Does any of those options solve the problem?

Marry Christmas, robmcc83!

It's definitely possible to make your case work with LE. I did an on/off button (see here) and a status LED (see here).

You just have to adapt the pin numbering for your needs. Take care about the difference of GPIO and pin numbering system.

Adding a reset function to the Python script should be no problem, too (use the "reboot" command).

Da Flex

Still no interest to fix your bug? Do you need help?

Downgrading will produce more trouble than it solves. Use the current stable LibreELEC, and find out what happens when you go deep into file hierarchy.

Create the file advancedsettings.xml at .kodi/userdata, and add this lines:

<advancedsettings>
  <loglevel>1</loglevel>
</advancedsettings>

When you get those blackouts, grab the kodi.log (now set to log level 1) from .kodi/temp, and analyze it with us.

Most people explain, what they want to run on LibreELEC. But you don't. Why?

The log looks OK to me. Watch out for changes inside the XML "videoscreen.whitelist" tag at guisettings.xml:

<setting id="videoscreen.whitelist">

When your computer wakes up, it maybe gets a different whitelist, compared to the state before standby. That will change the guisettings.xml (the content of XML "videoscreen.whitelist" tag), and the GUI will ask you to save it. The whitelist stores all possible resolutions / vertical frequencies available for the display device.

HiassofT:

How do you disable the internal Bluetooth? I think that's the solution for most users to re-enable "full UART".