rpi-audio-receiver VS rpi-eeprom

I once installed raspberry pi’s with a Bluetooth audio receiver config. These got installed in a professional football club with each receiver having a name like ‘changing room’ , ‘bar’, ‘manager’. They gave an open connection without PIN codes and lost the active connection as soon as the current device went out of range. We tried a number of ‘real’ Bluetooth devices from Denon and similar but none offered the configurable parts of the raspberrypi’s.

Check this out, it may help you - seems to be describing close to what you're after

When I play a song on my phone/computer that is played on my speaker via bluetooth, I want the lights to be synced to music, where the ceiling and wall lights will each have different effects. I’m thinking of installing LedFx on a Raspberry Pi 4 for music syncing. Do I need https://github.com/nicokaiser/rpi-audio-receiver for this?

This may be linked to be an ongoing conflict between WiFi and Bluetooth. I bought a Hifiberry amp to explore turning a raspberry pi into a receiver, and this GitHub project is amazing for that purpose, but suggests that the RasPi's onboard bluetooth and wifi interfere with each other. I'm intending to try a USB bluetooth dongle to see if it will fix but I'm encouraged by u/AlienMajik 's post above.

Not sure if this works for you https://github.com/nicokaiser/rpi-audio-receiver

I've seen https://github.com/nicokaiser/rpi-audio-receiver but not sure how to get the input from airplay and have it pair and output to the speaker.

I do this currently with spotify, as the rpi runs rpi-audio-receiver with the spotifyd daemon. I like this because from any spotify app I can switch the device over to the rpi and the music comes out of the speakers. I don't need to access any web server running on the pi or have a separate app for playing the music there.

I don't have Pi 5 to check this, but from what I've read, it does not support PPS. And such support is required; otherwise, even with a source that supports PPS, the connection will behave in a non-PPS fashion.

Apparently, cable quality is also demonstrating itself to be a significant factor in the Pi 5 power supply environment.

Regarding both these points:

https://github.com/raspberrypi/rpi-eeprom/issues/497

I should note, I updated the eeprom, USB hub, and network firmware using the images provided from the following repository: https://github.com/raspberrypi/rpi-eeprom. So it certainly isn't a corrupted eeprom chip, and if it was I wouldn't be able to boot the old installation I pulled from my backup drive.

Its a known issue with the current Pi 4 boot firmware. The net install option is trying to look for a keyboard and gets confused with some HIDs.

I was working on a final project for my class and needed an adc. So I ordered an ADS1115 and I had to solder the pins onto it. I've never soldered before, but I tried my best. Didn't look amazing, but didn't look like any pins were getting shorted so I plugged it in to the Pi. I then noticed that my ssh disconnected and couldn't reconnect. Tried plugging in the HDMI and there was no video output. I tried flashing a new OS onto it, didn't work. Tried EEPROM recovery from here and it didn't work. So I think I killed the Pi. It doesn't feel like it's getting warmed up or anything.

See https://github.com/raspberrypi/rpi-eeprom/blob/master/firmware/release-notes.md

I try to reset the pi as factory settings (following this github advice). I use pi-imager to set my SD card to lead the pi using USB boot priority and plug a USB key with raspbian OS (no desktop) and now getting green screen when booting. Think that the pi is dead.

I think it was this one:

https://github.com/raspberrypi/rpi-eeprom/blob/master/firmwa...

I had the same problem as you, updated my eeprom and the problem was fixed

Firmware: https://github.com/raspberrypi/rpi-eeprom/releases/tag/v2020.09.03-138a1