Hyperbian + Hyperion ng + ezcap 269

Quote from Tyler983

Hi @Awawa do you have a command line to disable Bluetooth? I tried through cyber duck but with no luck. Ok for the port setting

Modify boot/config.txt to be sure it'll remain unloaded.
If you dont want use editor (I recommend mc and its internal editor for beginners) on Rpi3 you can achieve it using commands from internet, but I havent test it:

echo "dtoverlay=pi3-disable-bt" | sudo tee -a /boot/config.txt
sudo systemctl disable hciuart
sudo reboot

And save dmesg and Hyperion and ls -ltr /dev/tty* logs after each step (1 after modifying port configuration, 2 after modifying port configuration + disabled Bluetooth to see if something has changed)

For latest Raspian:
https://www.raspberrypi.org/do…ion/configuration/uart.md
dtoverlay=disable-bt
fol older:
dtoverlay=pi3-disable-bt
Check dmesg to see if helped
Definatelly you dont want to see that lines as in your latest log at the end:

[   13.705520] Bluetooth: Core ver 2.22
[   13.705620] NET: Registered protocol family 31
[   13.705631] Bluetooth: HCI device and connection manager initialized
[   13.705662] Bluetooth: HCI socket layer initialized
[   13.705681] Bluetooth: L2CAP socket layer initialized
[   13.705711] Bluetooth: SCO socket layer initialized
[   13.727224] Bluetooth: HCI UART driver ver 2.3
[   13.727240] Bluetooth: HCI UART protocol H4 registered
[   13.727309] Bluetooth: HCI UART protocol Three-wire (H5) registered
[   13.727529] Bluetooth: HCI UART protocol Broadcom registered
[   14.017506] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[   14.017519] Bluetooth: BNEP filters: protocol multicast
[   14.017539] Bluetooth: BNEP socket layer initialized
pi@HyperBian:~ $

Make sure to run

sudo systemctl disable hciuart

And restart.

If it doesnt help then I'm out of ideas and propable that Lightberry USB converter isnt compatible with Rpi or it needs some special settings for example: custom COM speed.

sudo systemctl disable hciuart
sudo reboot

remove it from that file. you were supposed to run it from command line after editing config.txt
and check dmesg if bluetooth disappeared and released uart.

Quote from Tyler983

I GOT IT!!!!!! thhhhhhxxxxx @Awawa !!! Leds are finally going. dmesg errors are still there but leds are going. I can see a bit of delay response, I need to calibrate them.
Do you think I can connect rpi4 now or better not?

Great Seems the Bluetooth was the root of the problem (and port misconfiguration at some point) as suggested by @Lord-Grey . If you're going to use ezcap 269 then give Rpi4 a try: quality with YUY2 encoding is better than MJPEG but it requires USB3.0 so Rpi4 is necessary.

Check CPU usage for current setup (command top, then press 1). MJPEG can easily take over the whole cpu's core and then high framerate by ezcap can cause the system to meld down.

Try size decimation but the output quality for MJPEG could be terrible (I know we don't take screenshots to admire but it affects LED). Check CPU usage from previous post. If you switch to my fork the problem with lag should disappear.

I prefer to shutdown whole LED&Rpi system with Power Cube Remote (my raspbian system is on the read-only image so it's safe). There is a signal detection in Hyperion but dont know how to setup it.

Post dmesg from Rpi4 and make sure that the Hyperion is working on the correct port - just in case of auto-detecting something.