1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

RPi + Other Software Hyperbian + Hyperion ng + ezcap 269

Discussion in 'Software Support' started by Tyler983, 8 September 2020.

  1. Tyler983

    Tyler983 Member

    Messages:
    110
    Hardware:
    RPi3, +PhilipsHue
    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
     
  2. Lord-Grey

    Lord-Grey Moderator Staff Member Developer

    Messages:
    204
    Hardware:
    RPi3, 32/64bit
    Hey
    Please first have the name corrected and try again.
    If then you have the timeout error again, try disabling Bluetooth.
    That is the whole point why testing on rpi3. Sorting out, if it is a rpi4 and/or Bluetooth related issue. If you change two things at a time, we do not find the root cause.

    If you have the same error, post the output from

    ls -ltr /dev/tty*
     
  3. Tyler983

    Tyler983 Member

    Messages:
    110
    Hardware:
    RPi3, +PhilipsHue
    Ok @Lord-Grey when i'll be at home i'll change the name and i'll show the log. Thx
     
  4. Awawa

    Awawa Active Member

    Messages:
    176
    Hardware:
    RPi1/Zero, RPi3, +nodeMCU/ESP8266
    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:

    Code:
    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)
     
  5. Tyler983

    Tyler983 Member

    Messages:
    110
    Hardware:
    RPi3, +PhilipsHue
    Thx a lot @Awawa in the evening i'll do it and post the result. In Boot/config.txt what i must modify?
     
  6. Awawa

    Awawa Active Member

    Messages:
    176
    Hardware:
    RPi1/Zero, RPi3, +nodeMCU/ESP8266
    For latest Raspian:
    https://www.raspberrypi.org/documentation/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:

    Code:
    [   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
    [email protected]:~ $ 
    Make sure to run
    Code:
    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.
     
    Last edited: 18 September 2020
    • Like Like x 1
  7. Tyler983

    Tyler983 Member

    Messages:
    110
    Hardware:
    RPi3, +PhilipsHue
    Please let's keep in touch, in the evening i'll let you know
     
  8. Tyler983

    Tyler983 Member

    Messages:
    110
    Hardware:
    RPi3, +PhilipsHue
    @Awawa I don't know if I made it right, but I inserted the string: dtoverlay=disable-bt in config.txt on the ssd, lunch the command
    sudo systemctl disable hciuart but nothing happened... dmesg always show the same errors.
    Did I made something wrong?
     
  9. Tyler983

    Tyler983 Member

    Messages:
    110
    Hardware:
    RPi3, +PhilipsHue
    This is my config.txt file
     

    Attached Files:

  10. Awawa

    Awawa Active Member

    Messages:
    176
    Hardware:
    RPi1/Zero, RPi3, +nodeMCU/ESP8266
    Code:
    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.
     
    Last edited: 18 September 2020
  11. Tyler983

    Tyler983 Member

    Messages:
    110
    Hardware:
    RPi3, +PhilipsHue
    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?
     

    Attached Files:

  12. Awawa

    Awawa Active Member

    Messages:
    176
    Hardware:
    RPi1/Zero, RPi3, +nodeMCU/ESP8266
    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.
     
    Last edited: 18 September 2020
  13. Tyler983

    Tyler983 Member

    Messages:
    110
    Hardware:
    RPi3, +PhilipsHue
    I will install your fork as soon as I found a right configuration for my system. Before of it I must fix delay and colors calibration.
    Do you have some suggestions to solve the delay?
     
  14. Awawa

    Awawa Active Member

    Messages:
    176
    Hardware:
    RPi1/Zero, RPi3, +nodeMCU/ESP8266
    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.
     
  15. Tyler983

    Tyler983 Member

    Messages:
    110
    Hardware:
    RPi3, +PhilipsHue
    Ok Thx a lot, I will buy a second sd to install your fork. Newly thx a lot!!!
     
  16. Tyler983

    Tyler983 Member

    Messages:
    110
    Hardware:
    RPi3, +PhilipsHue
    @Awawa i noticed that my leds stay on also if I turn off the tv. What can I do to avoid it?
     
  17. Awawa

    Awawa Active Member

    Messages:
    176
    Hardware:
    RPi1/Zero, RPi3, +nodeMCU/ESP8266
    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.
     
  18. Tyler983

    Tyler983 Member

    Messages:
    110
    Hardware:
    RPi3, +PhilipsHue
    Ok thx I will check for a solution ;)
     
  19. Tyler983

    Tyler983 Member

    Messages:
    110
    Hardware:
    RPi3, +PhilipsHue
    @Awawa i transferred the sd from the rpi3 to the rpi4 but it doesn't work. Leds are off on the rpi4
     
  20. Awawa

    Awawa Active Member

    Messages:
    176
    Hardware:
    RPi1/Zero, RPi3, +nodeMCU/ESP8266
    Post dmesg from Rpi4 and make sure that the Hyperion is working on the correct port - just in case of auto-detecting something.