If your PC is not housed in a shielding enclosure and/or to near the TV, it can radiate into your antenna cable and block the TV signal. Please check the isolation of your antenna cable and the used HDMI cable, sometime also another power supply for the PC.
I had encountered a similar problem with a friend who had a Bluetooth transmitter for headphones attached directly to the back of her new TV. The SAT tuner was unable to find a transponder until I found and removed this construction.
Posts by HarryH
-
-
I have not yet made the release package for 1.1.5 available, as I am still busy converting the PRs to integrate gpiod into the official system-tools addon instead of the rpi-tools addon. Until their merge, I saw no technical necessity to use 1.1.5.
-
Please can you check if that happens too when:
- move the cabeling to the primary HDMI port of your RPi4
- use a recent LE 12 nightly
- without additional USB devices like keyboard and so on ...
- connected directly to the TV set (bypassing the DENON AVR)
Do you have an alternative power supply available for a cross check?
-
Thanks! Will the updated rpi-tools come to LibreElec Updates?
Maybe I was to ambigous or you just overlooked the known issue part of the documentation at my GitHub repo.
Some days ago I started this thread and provided the required changes, which are the base of my updated rpi-tools packages.
The workflow is started, and the 2 open pull request were already tagged. As it depends on the available time of the LE maintainers, it may take some time until someone is in the mood to review and finally merge them. Afterwards it should be general available via LE addon updates and its not required anymore to download/install the rpi-tools additional from my repo to use gpiod.
-
Version 1.1.4 released:
- added gpiod support
- use gpiod if available, as workaround against the 30 seconds delay on restart/stop of KODI with LE12+ -> reduced to 5-6 seconds
- regression with LE12/13: properly shutdown via power button of remote control possible again
This change will only take effect if rpi-tools are updated as well. Please read the known issue part, if you can't wait...
Hi firefox ,
that was really fast. To get a feedback before publishing the release package.
-
Hi mister_he1merD0ng3r ,
It is a known issue as the package provided by Argon40 is very outdated and was only intended for LibreELEC 9. The problem was already discussed by others here: RE: [RPi4B] Argon One Case Shutdown
Please use the current release 1.1.4 from here: https://github.com/HungerHa/libre…gonforty-device -
Hi chewitt ,
thanks for the review and the helpful comments. I have created another PR9592 for the master branch and updated the existing PR9591 to be able to use it as a backport for LE12. -
I have created a pull request with the needed changes. It's my first one, so please be kind if I made some mistakes and need to correct some things to make it acceptable.
rpi-tools: add gpiod support by HungerHa · Pull Request #9591 · LibreELEC/LibreELEC.tvgpiod are the official Python bindings for libgpiod. libgpiod is already part of the system tools add-on, only these Python bindings are currently missing to…github.com -
Hi QBJack ,
please can you provide the current content of your config.txt
cat /flash/config.txt
and try if the MCU of the case is detected?
i2cdetect -y 1
The output should look as follows, where 0x1a is the address assigned by the MCU:CodeLibreELEC:~ # i2cdetect -y 1 0 1 2 3 4 5 6 7 8 9 a b c d e f 00: -- -- -- -- -- -- -- -- 10: -- -- -- -- -- -- -- -- -- -- 1a -- -- -- -- -- 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 70: -- -- -- -- -- -- -- --If the MCU is not detected but the I2C working without error messages, please power cycle the case (unplug the power supply for some seconds) and try again afterwards.
A separate service shouldn't be running, The addon is running as a thread of the KODI process. You can/should enable the debug logging to get more insights what happens with the addon and please provide a link to the log:
https://wiki.libreelec.tv/support/log-files
If you have previously experimented with other solutions (argon1.sh /argonone.service ...) on your current LibreELEC installation, you should make sure that there are no fragments left that could conflict with the addon. -
Are there a chance that the Python bindings for libgpiod are official included into the virtual rpi-tools addon? libgpiod is already part of the system-tools addon, only the python bindings are currently missing.
libgpiod/bindings/python at v2.2.x · brgl/libgpiodThis is a mirror of the original repository over at kernel.org. This github page is for discussions and issue reporting only. PRs can be discussed here but the…github.com
Why?
Since LibreELEC 12 gpiozero is the main module intented to interact with the GPIO pins. But there are some ugly problems:- gpiozero takes to long to terminate (killed by KODI after 5 seconds during shutdown, may be related to the lgpio issue explained below) and doesn't frees the used GPIO ressources, so it's need to reboot instead of disable/enable the addon to get it work again
- gpiozero is slower than libgpiod because of additional abstraction layers: https://adafruit-playground.com/u/MakerMelissa…-raspberry-pi-5
- lgpio can be used without gpiozero to workaround the blocked ressource issue of gpiozero, but it seems to start some kind of threading as soon the Python module lgpio is imported. The thread with the imported lgpio module doesn't stop within 5 seconds (the hard limit for the CPythonInvoker of KODI) and prevents KODI to restart/shutdown in usual time. It takes 30 seconds to "systemctl restart kodi" or to shutdown LibreELEC if lgpio is directly or indirectly via gpiozero imported in a script addon. Therefore I think rpi-lgpio (RPi.GPIO replacement) will do have the same restriction.
For a cross-check, I compiled the rpi-tools addon for testing so that it also contains these bindings. If I use gpiod instead of gpiozero / lgpio for Argon40 Device Configuration addon the "systemctl restart kodi" takes only 4 - 6 seconds (not 30 seconds), depending how much background tasks are currently running. This will enable again an ordered shutdown, if the remote control power button is used for the case shutdown instead of the KODI menu. Another story with a firmware restriction (10 seconds limit) of the Argon40 case...
Yes, I can include the bindings in the Argon40 addon, but I would prefer a globally available gpiod Python module so that others also have the advantage of choosing the best working module for their use case. -
Theoretical it's possible, but seems depends on your existing equipment and cabeling. Within the CEC adapter settings you can configure what should happen on power on/off/standby events of KODI. The issue could be if you need to signal KODI as "active source at startup" to get the TV remote control working for CEC or to switch to the right input, this triggers some TVs to power on.
-
Wasn't there some fixes in the nightly builds released after 12.0.1 regarding some issues in conjunction with DENON AVRs?
JohnWayne111 , which version of LE do you have installed? Already tried with a recent nightly build for a cross check? -
Hey, yes, the last nightly works.
Thank you for the hint.
An no, it is a 8GB Raspberry.But yes, looks like the MCU code is similar what you wrote:
You are the first to confirm my suspicion from the linked thread that equipment variants other than the 2GiB version with this new chip version are in the wild. Nice to know.
-
It doesn't look that you have got the 8GiB version, looks more like the hardware revision 2712D0 (released with the 2GiB version). Please try a recent nightly build, which includes the needed Mesa driver patches.
Already discussed here:
[RPi5 2GB] Scrambled Display on Sony Bravia X90L
Hey, folks.
Please be patient with me as I barely pay attention to any of tech around TVs, variants of HDMI, variants of 4K/8K, etc. We are simple folks who just want to watch a digitized collection of our old movies.
I have a Bravia X90L series (55") and I just picked up a Pi5 CanaKit with all of the bells-and-whistles to double-sided tape a LibreELEC media center to the back of the TV over the fireplace. The version of LibreELEC is recent -- whatever came out of the business end of rpi-imager…
-
Only for information: There are also versions in Python3 of these scripts for Batocera, which can be adapted to LibreELEC if required.
GitHub - HungerHa/batocera_remotepi: RemotePi support for BatoceraRemotePi support for Batocera. Contribute to HungerHa/batocera_remotepi development by creating an account on GitHub.github.com -
Version 1.1.3 released:
- added Dutch translation (thanks to emv-nl)
- prevention of unnecessary I2C messages for updating the fan speed
-
I didn't want to distract. Nice to know that LE itself shouldn't be affected. It was not obvious to me whether it was mounted exclusively via LE and not via the operating system. And because I could reproduce the issue with 2 desktop linux clients in daily use too, I would only ensure that RomanHT is aware of it.
Most of the usually LE traffic is read-only (with the exception of TVheadend recordings, etc.), but he writes from LE device to NAS so that he could have been affected ...
Sure, the freeze problem itself is another topic. -
The board mentioned by popcornmix works for RPi4. You can teach a remote button of your choice to the board or use the shown button to turn it on and off. I know this because I corrected the required scripts for some people on this and another forum and got some positive feedback. But unfortunately, it's discontinued and may not be officially compatible with the RPi5 (integrated max current limit of the RemotePi board).
