Beiträge von djh144

    For anyone else who landed on this thread. I had the same issue and fixed it with the above suggestion. Really nice to have all the new hyperion features so i recommend it.

    Explicitly...

    1. cut the two signal lines coming out of the light berry controller. You can identify them by opening up the controller box. The circuit board has the wires labeled.
    2. cut the rj45 signal wires. Leave the power/ground connected. For me, this was green and black, but you can see it by looking at the wire trace on the board.
    3. connect the signal wires to each other- bypassing the controller. I didn't bother trying to figure out which was the data vs clock. 50/50 shot and doesn't do any harm if you get it wrong.


    Things I like about this solution.

    • I get to maintain my separate power supply for the LEDs via the lightberry controller. My thought is that this increases the longevity of the pi by not running additional power through the pi. It also has a separate protection circuit. It's also nice because I use a smart plug to turn the LED's on/off without powering off the pi. I know you can do it in software too.
    • By keeping the same wire ground connections through the controller, I maintain a common ground which should prevent a ground mismatch. In theory, a ground mismatch would cause the LEDs to flash/flicker.

    Ugh.. I'm in the same spot.

    My RPi 1 B+ I had running lightberry for YEARS died this week (power module).
    I managed to save the old hyperion config file.

    I have another RPi 3 running a HomeAssistant docker on RaspOS that I tried to install Hyperion. My Lightberry is old and connects on SPI GPIO pins.

    Frame grabber seems to be working but I'm getting no lights, only a baud rate warning. Considering rolling back to a previous hyperion on openelec when I can find another RPi in stock, unless someone knows some setup issues.


    Oh this thread is interesting:


    Am I double SPI'ing my system?