gave up and bought the govee immersion kit 2
dealing with HDR, Dolby Vision, Atmos, passthrough, ARC and broken leds I cant figure out was too much
Posts by Borja
-
-
-
I tested the GPIO 18 and there are 1.643V up the the connector of the leds.
the black and red wire have 5V and the power supply is giving 5V correctly to the Pi and the leds.
measured at the leds, between ground and 5v the multimeter reads 5v.
I can only think that the leds are blown out. is there a way to test them?
how could that have happened?
I tried with GPIO12 too but it doesn't seem to be a Pi issue.
loose joints around the led shouldn't be an issue, I have corner joints that act up and that makes the led lines after the funny join not light up or flash weird. the first one should always light up.
I tested the wires from the power supply and Pi up to the 3 wire connector right before the start of the led strip.
inside the led strip I also read 5V and some small value jumping around between ground and the PWM
-
follow your tip
What configs did you change and which GPIO did you use?
-
thanks!
I'm still learning what EDID etc do
-
Thanks for the quick reply !
I tried the GPIO 12 but no luck.
I’ll check all the wirings tomorrow.
It was working last night and not today after unplugging and plugging back in the microusb ??♂️
-
https://xolorspace.com/collect…th-downscaler-4k-to-1080p
this is the one i have now, very happy with it.what settings do you have on the splitter pins?
-
I'm really sorry to create another thread but I'm losing my mind.
I unplugged by working raspberry pi 3 B
it had homebridge, hyperion alpha 7 I think and pi hole
I removed homebridge and pihole and updated hyperion
now the leds do not work.
I have tried a lot of commands
a couple of clean installs
now I did a full Hyperbian install and the leds are not coming on anymore.
When I run sudo updateHyperionUser -u root it says already under root, no updates required.
I don't know what else to do.
Wiring was working on the GPIO-18 before and now it doesn't
is there a way to check that it is the raspberry failing?
here is the debug log from hyperbian
config.txt has dtparam=spi=on and dtparam=audio=off
