LeVraiRoiDHyrule which LibreELEC version you are using (i'm using LE11 here)?
Also which HA container image ?
Alternatively ,you could use esphome bluetooth proxy ,installed on esp32 dev module (already tested here and working ).
LeVraiRoiDHyrule which LibreELEC version you are using (i'm using LE11 here)?
Also which HA container image ?
Alternatively ,you could use esphome bluetooth proxy ,installed on esp32 dev module (already tested here and working ).
I'm using docker-compose here ,but here's a snippet from the "docker-compose.yaml" file :
homeassistant:
image: homeassistant/raspberrypi4-homeassistant:stable
container_name: homeassistant
hostname: hassio
network_mode: "host"
restart: always
depends_on:
- adguardhome
- mosquitto
- zigbee2mqtt
environment:
- TZ=Europe/Rome
volumes:
- /run/dbus:/run/dbus:ro
- /etc/localtime:/etc/localtime:ro
- /storage/.config/dockers/hass-config:/config
Display More
With this configuration ,the RPi4's internal bluetooth is automatically detected in HA (check the attached screenshot ).
What's more important in this case is how much power RPi4 can provide over USB ports ,which is 1.2A MAX.
NOTE that this applies to all USB ports ,so if a device connected to an USB port requires 1.0A to work correctly ,then a second device ,connected on another USB port ,cannot/shouldn't draw more than 200mA.
Hi, thanks for your answer.
I did already, they told me to ask here. Which I find logical as the problem is more with how Libreelec handles bluetooth rather than with home assistant itself. If you can help me to find what device Libreelec uses for bluetooth, then it should be easy to mount it on docker.
EDIT : I tried to search for both the integrated bluetooth, as well as for the bluetooth dongle that I've connected. None of them seem to be visible in /dev. I don't see any new device appearing in /dev when plugging the dongle, even with it being found that I use lsusb.
Thanks in advance for any answer, have a good day.
Hi,i'm using LibreELEC 11 + Docker + HA on Rpi4 8GB and when i run "hcitool dev" in HA container's terminal,it shows the RPi4's internal bluetooth ,so no idea why it fails for you.
I will try to pair a device with it and check if Homeassistant can find it,so i will let you know .
P.S. Docker + Home Assistant (and other 12 containers like SWAG,AdGuard Home ,Zigbee2mqtt ,MQTT ,eyc) runs very well on Rpi4 .
Yes,that was for reference ,you can play it on your TV and you will notice the judder (unless you crank up de-judder to the max).
However ,i managed to force the tv's hdmi port in "hometheater" mode (that's how LG calls it) with the help of bscpylgtv and now all the motion interpolation settings are available .
Perhaps try connecting to another HDMI port on the TV?
Yeah,trying all the HDMI ports was the first thing i did,but thanks for the suggestion .
Initially i thought that it's because it was connected thru the soundbar ,so i tried the hdmi ports on the TV.
Yep ,it's enabled and i always used it.
For the most part it's smooth for me too ,but slow panning shots ,especially where there's more contrast between various object in the scene (eg. panning on bright windows ) ,are sometimes unbearable without motion interpolation.
Fir example the desert/mountain scene from this video ->
And according to some infos I've found on avsforum,it seems that the oled panel's internal refresh rate is not really in sync,even if the hdmi debug info report the correct refresh rate (in our case,24hz in case of a 24p movie).
https://www.avsforum.com/threads/2022-lg-c2-g2-owners-thread-no-price-talk.3250717/post-62197916
https://www.avsforum.com/threads/2022-l…7/post-62198740 <-- last quote is related to kodi.
I don't know on LG CX,but on LG G2 there's a lot of judder on slow panning shots and i always need to enable de-judder (i usually keep de-judder on 3-4,otherwise there will be to much SOE for my taste).
Hi guys,a few months ago i bought a new tv,an LG G2 OLED ,hooked my RPi4 to it and everything seems to work just fine ,but the RPi4 is recognized as PC so the TV activated PC MODE automatically .
The problem is that when the TV is in PC MODE,all the motion settings (Real Cinema and TruMotion settings on LG G2 ) are disabled si i'm getting a lot of judder when watching movies (24p movies).
Is there a way to force the RPi4 as a media player (or whatever it's called ) ,so i can get the motion settings back?
I'm using LibreELEC 11 and the RPi4 is connected thru the soundbar and i also tried to connect it directly to the TV,but it's always recognized as a PC.
HiassofT sorry to summon you here,but iiirc,you also have an LG OLED ,so do you have any recommendations ?Thanks you!
I switched to LE11 as daily driver ,so i will let you know if this issue will occur at some point (the bad part about being a daily driver is that i can't keep the debugging always on).
As a side note,regarding USB on Rpi4 ,I'm pretty sure i bumped into this several times -> https://github.com/raspberrypi/linux/issues/5192 <-- but in my case it was the other way around ,removing the Wi-Fi USB dongle caused a system freeze (using SSD as boot drive) .
ghtester how often it happens on your other configuration ,the one running from USB-SATA adapter ?
I'm asking because i'm testing this ,but after 24h+ the system is still running fine.
I don't have a DVB-T stick available ,but my system use a SSD (boot ) connected thru USB-SATA adapter (connected to USB3) and a Sonoff USB Dongle (Zigbee Coordinator) connected to USB2.
As the title says,i have an issue with my TV remote not working after turning the TV on (from standby).I must say that i'm trying to fiind a fix for this issue since a year or so and is present on both LE10 and LE11.So let's start with my current configuration:
OS - LibreELEC 11
Device - RPi4 8GB
TV - 40 inch Philips TV (2010 model)
Sound - Hisense HS512
Other connected devices - FireTV 4k
TV Connections :
RPi4 (HDMI0) --> Soundbar (HDMI2) --> TV (HDMI1 ARC)
FiretV 4k --> Soundbar (HDMI1) --> TV (HDMI1 ARC)
Steps to reproduce:
1) LibreELEC is running and CEC remote works
2) Power OFF the TV but don't switch to another TV input ( sounbar is also put to standby )
3) Power ON the TV ( soundbar is also powered ON )
4) Kodi UI shows up as expected and sounbar is also set to the correct input (HDMI2) but the remote control is not working
5) Opening up the TV inputs menu is showing LIVE TV as currently selected
6) Manually switching to LibreELEC input from the TV input menu fix the issue and the CEC remote control is working again
Remarks:
I tried several CEC Adapter configurations,setting the correct physical address,HDMI port,connected device.etc) but nothing worked and also noticed that the physical address value wont't always stick and is automatically changed
I thought that is caused by the soundbar ,because when it's powered ON it has a 5-8 seconds delay ,but that's not the case because on FireTV 4k everything works just fine
Another side-effect is that switching to LiveTV input is also affected,meaning that it swirch to LiveTV input just fine but audio is not switched to ARC so there's no audio output on LiveTv ( this also brings WAF to a critical level) . Switching back to LibreELEC input and back again to LiveTV will fix the issue (wife will still complain though).
Looking at the logs is seems like the active source is not set correctly,but i'm not really sure about it,so maybe you guys can spot something usefull in these logs.
Logs:
But no logs from you so far...
I'm trying to help,but if can't reproduce ,i can't get any useful logs.
I don't know what relation might be between "TV OFF" and a USB failure ,it looks more related to HDMI or CEC (and that's what i'm trying to find).
You said that CEC is disabled ,so try enabling that .
Also ,you could try switching to a different HDMI port on Rpi4 .
There's clearly a regression on the newer LE11 builds ,but without logs is almost impossible to find out what's wrong .
MatteN i tested this overnight and still no problem here,this morning LibreELEC/Kodi was still running fine.
I will try to disable CEC and test again tonight (even if an USB issue should be triggered regardless ).
MatteN do you have a spare MicroSD to test with ?
If it's an USB issue ,then it shouldn't occur when booting from MicroSD.
I'm backing up my docker containers and stuff,so i can switch to LE11 for testing .
I will try to test this overnight ,maybe 3 hours was not enough to trigger it.
I'm also using a SSD for boot,but usually ,if there's an error with the USB crapping out,then you shouldn't be able to access the device thru SSH.
That makes me think that your issue is different from the one reported by the OP.
Best thing would be to enable debug logging before powering OFF your TV,then ,after the error occurs ,grab the logs (you can do it from the SSH with the "pastekodi" command ).