Posts by HiassofT

Can you test if this rpi-tools addon version works?

virtual.rpi-tools-9.1.901.107.zip

It includes the RPi.GPIO 0.7.0 update update RPi.GPIO to 0.7.0 by HiassofT · Pull Request #3871 · LibreELEC/LibreELEC.tv · GitHub

so long,

Hias

The journal shows that hyperion can't connect to Kodi. Please change the kodi check address in your hyperion config from

192.168.2.14 to 127.0.0.1.

In addition to that you may also need to enable "Allow remote control from applications on other systems" in Settings->Services->Control (IIRC older kodi versions had a bug that even local connections to 127.0.0.1 didn't work unless this was enabled - could well be that this has been resolved, though).

so long,

Hias

Yes, you need to do that with putty. It might be easiest if you change to the "pictures" directory first, then you can simply grab and view the screenshot.png via the "Pictures" share on your PC:

cd pictures
hyperion-dispmanx --width 320 --height 180 --screenshot

Then repeat the hyperion-dispmanx (just press "cursor-up" to recall it, then return) while you view different pictures on your RPi and check the screenshot.png on your PC.

While you're at it it would be good to grab some info about your system. Please run the following commands and post the URLs:

journalctl -a | paste
paste /flash/config.txt
paste /storage/.kodi/temp/kodi.log
paste /storage/.kodi/userdata/addon_data/service.hyperion/hyperion.config.json

so long,

Hias

Can you please do the dispmanx grabber tests as I described in post 4? Hyperion hypercon problem no green and white lights

so long,

Hias

As I already wrote use multiple times use hypercon for that. Go to ssh tab, connect, choose your hyperion.config.json with "Local Config Path" and click on "Send Config". Then reboot so hyperion picks up the file.

so long,

Hias

Yes, exactly. I highly recommend using hypercon (the LibreELEC version) to manage hyperion config, that's a lot easier.

so long,

Hias

If you manually install hyperion-config.json you need to copy it to .kodi/userdata/addon_data/service.hyperion/hyperion.config.json, NOT .config. Or use the LibreELEC hypercon version (from our wiki) to do that, using "Send Config" in the ssh tab.

Without the config file in place hyperion won't start.

So far it looks like you are still running the official hyperion version and this one seem to have problems with LibreELEC and the RPi4. There's probably nothing wrong with your RPi4.

so long,

Hias

It looks like the issue is triggered by the vfs.sftp addon

2019-09-17 20:48:04.305 T:1937068048 ERROR: Unable to load /storage/.kodi/addons/vfs.sftp/vfs.sftp.so.1.0.1, reason: libcrypto.so.1.0.0: cannot open shared object file: No such file or directory

On LE 9.2 several crypto libraries were changed and the one used by vfs.sftp on LE9.0 is no longer available on LE 9.2.

Can you try uninstalling that addon, then upgrade to LE 9.2 beta 2? If that succeeded you can install the LE 9.2 vfs.sftp addon which should then work as befoe.

so long,

Hias

This is very odd. Just did a test here with white, green, blue and red images and it looks fine (RPi4 with Arduino/Adalight).

Could you do a test with this hyperion addon? service.hyperion-9.1.901.112.zip

I fixed screenshot grabbing not working on the command line so you can check if the dispmanx grabber works. ssh in and then run

hyperion-dispmanx --width 320 --height 180 --screenshot

This will save a 320x180 pixel screenshot to "screenshot.png" in the current directory. Copy that over to your PC and verify that it's matching what you have on screen (especially the colors).

so long,

Hias

If you downloaded hypercon from the hyperion website and used that to install hyperion you are running the wrong version.

In that case try to remove whatever hypercon changed on the LibreELEC installation (or just start with a fresh LibreELEC installation, that might be easier) and install hyperion from the LibreELEC addon repository - that'll be the correct version to use.

You can then use hypercon from here Hypercon [LibreELEC.wiki] to configure hyperion on LibreELEC.

Read also here for more information: Hyperion [LibreELEC.wiki]

so long,

Hias

Check your TV settings, on quite a lot of sets you need to manually enable "Ultra Deep Colour" or some similar setting on the HDMI port you're using. Had to do that on my LG 55C8, otherwise 4:4:4 subsampling isn't enabled and 4kp60 isn't available.

so long,

Hias

This has nothing to do with textures or GUI. If you look at the log you'll see that kodi is crashing because it couldn't load the german language file

FATAL: SetLanguage: CLangInfo: failed to load resource.language.de_de language information

Search the forums, this has been reported multiple times (sorry, can't remember the workaround/solution right now).

so long,

Hias

In general it's best to avoid USB DACs on RPi0-3, the USB controller isn't too great and we are still seeing occasional reports of crackling audio etc.

If you want something small and well supported then use one of the plenty I2S audio cards / hats. eg pHAT DAC, Hifiberry, Justboom or IQaudio.

so long,

Hias

After looking a bit it turned out there are tools available for that in the lirc distribution and some of them are already included in LibreELEC.

With "irsimsend" (which is available in LE) you can convert a lircd.conf file to a raw file with pulse/space codes. It's a very simple test tool and writes the raw codes always to simsend.out. By default it'll dump all codes (which isn't too useful), but you can tell it to only dump a single button.

eg with your lircd.conf file saved to panasonic.conf you can do

irsimsend -k KEY_POWER panasonic.conf
mv simsend.out power.raw
irsimsend -k KEY_VOLUMEUP panasonic.conf
mv simsend.out volumeup.raw
...

In the lirc source code I found a "pronto2lirc" python script, it's not installed in LE and by default wants Python3, but also works with Python2. I've attached that script (in a zip) and checked that it works on LE.

You need to create a file with the pronto hex codes of each button all in one line and put the button name followed by a colon at the beginning of each line. eg create a file panasonic.pronto:

poweron:0000 0071 0000 0032 0080 003F 0010 0010 0010 0030 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0030 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0030 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0030 0010 0030 0010 0030 0010 0030 0010 0030 0010 0010 0010 0010 0010 0010 0010 0030 0010 0030 0010 0030 0010 0030 0010 0030 0010 0010 0010 0030 0010 0A98
poweroff:0000 0071 0000 0032 0080 003F 0010 0010 0010 0030 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0030 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0030 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0030 0010 0030 0010 0030 0010 0030 0010 0030 0010 0030 0010 0010 0010 0010 0010 0030 0010 0030 0010 0030 0010 0030 0010 0030 0010 0030 0010 0010 0010 0030 0010 0A98

And then run that through pronto2lirc.py

./pronto2lirc.py panasonic.pronto

That'll create a lircd.conf file in the current directory and you can then use irsimsend (with -k poweron, -k poweroff) to create raw files.

so long,

Hias

Quote from MattGarrett

GitHub - kusticM/rpi: rpi files

config.txt looks fine but according to dmesg communication with wm8804 fails:

[ 7.844393] wm8804 1-003b: Failed to read device ID: -121
 [ 7.844554] wm8804: probe of 1-003b failed with error -121

Are you sure the card isn't defective or plugged in wrong?

I did a test with my justboom digi card (no config.txt changes required as it has a HAT eeprom onboard) on RPi4 running LE 9.1.002 and it worked just fine

[ 9.267296] wm8804 1-003b: revision E
[ 9.274108] snd-rpi-wm8804 soc:sound: wm8804-spdif <-> fe203000.i2s mapping ok

so long,

Hias

Please post your config.txt and dmesg and the exact model info (eg link to vendor webpage) of your audio card. It's hard to help without having any details.

paste /flash/config.txt
dmesg | paste

so long,

Hias

It could be that you need to transmit the IR code multiple times - my old Panasonic CRT TV only powered up if the power button was held down for about 0.5-1 seconds.

You could try something like this:

ir-ctl -g 75000 --send=button-power--send=button-power--send=button-power--send=button-power--send=button-power

"-g 75000" sets the gap / pause between IR signals to 75ms - that's about the value I see with my panasonic remote. You can also try other values in the range of (about) 50000 to 100000.

To add more repeats just add --send... more often - maybe try with 10 instead of 5 if it doesn't work.

It's a bit odd though that the TV didn't blink when you sent the code (IIRC my old CRT TV blinked shortly, multiple times when powering up).

It could be that the recorded signals aren't accurate enough - MCEUSB has 50µs resolution and this page Description of the panasonic infrared protocol (REC-80) says the intervals are about 420µs in USA and 450 in europe (not sure if that's correct, different lengths are quite odd).

so long,

Hias

The easiest way to do that with ir-ctl would be to capture the raw signals to a file and then send those. for example:

record a button to file "tv-power"

ir-ctl -1 --receive=tv-power

transmit the signal:

ir-ctl --send=tv-power

An alternative would be to use lircd if you can find a lircd.conf with the signals/codes for your TV.

Converting those various "ir codes" you find on the net to a format suitable for ir-ctl or lircd isn't easy as there's no real standard for them.

so long,

Hias