search

hyperion-project / hyperion.ng

The successor to Hyperion aka Hyperion Next Generation
https://hyperion-project.org/
MIT License
3.02k stars 375 forks source link

Forwader BUG - Client LEDS do not illuminate until web UI is accessed #823

Closed RKF-FKR closed 3 years ago

RKF-FKR commented 4 years ago

Bug report

Using Hyperion NG to forward Proto and JSON (or either). LED's on the target screen do not become active until the WEB UI is accessed (or refreshed) After that, Hyperion works flawlessly.

Steps to reproduce

Start Pi4 containing the V4L2 grabber and the forwarder port details. (eg 192.168.1.200) Start Pi Zero W containing the client ports. (eg 192.168.1.300) Wait for splash screen of client > OK Wait for Hyperion to commence on client (192.168.1.300) > fail Using Mac Safari - access 192.168.1.200:8090 - hit enter Hyperion UI opens - lights illuminate on 192.168.1.300

What is expected?

Previous Hyperion forwarder and client Pi's boot up, then as soon as client connects with forwarder Hyperion LED's commence.

What is actually happening?

Strangely I need to open a web UI for the client lights to commence - happens whether I use LAN cable or Wifi for the Hyperion forwarder Pi

System

Hyperion Server:

Hyperion Server OS:

Paulchen-Panther commented 4 years ago

Which LEDs do you use on your Pi Zero W?

RKF-FKR commented 4 years ago

I use APA102 (BTW without problems on the old version).

direk commented 4 years ago

Looks like the same issue I've noticed... https://github.com/hyperion-project/hyperion.ng/issues/813

RKF-FKR commented 4 years ago

@direk Indeed - seems like a duplication on my part.

RKF-FKR commented 4 years ago

@Paulchen-Panther - I can also report that the LEDs on server Pi - connected to Pi pins 19 and 23 (also APA102) will also remain on the boot colours until the UI is opened. Once the UI web page is opened. So that means forwarder and server LEDS seem to suffer the same symptoms.

m-seker commented 4 years ago

@RKF-FKR @direk Do you have the possibility to build hyperion with debug symbols ? If yes, running the hyperion in gdb and providing the stack trace (ctrl + c, thread apply all bt) before accesing WebUI would make a good start towards understanding the issue.

RKF-FKR commented 4 years ago

@m-seker I'd love to try your suggestion. I am not at your level of expertise. Happy to download and try a compiled version that contains your suggested changes though.

mstuebner commented 3 years ago

Same issue using WS2812 led on GPIO18 of an PI3b+

Hyperion Status: An
Plattform: Raspberry Pi
Steuerungstyp: ws281x
Instanz: GPIO-18
Ports (flat|proto): 19400 | 19445
Deine Hyperion Version: 2.0.0-alpha.6
Ausgewählter Versionszweig: Stable
Aktuellste Hyperion Version: 2.0.0-alpha.8
direk commented 3 years ago

Sorry, I moved to RPi4 with adalight USB device to drive leds and alpha.8 version. The problem disappeared.

RKF-FKR commented 3 years ago

Indeed my problems have vanished with Alpha 8 as well using the classic wired configuration for the primary TV and then all other LED’s are via Instance configurations (udpe131 and WLED). No further issues to report from me.

tpmodding commented 3 years ago

so this can be closed?

RKF-FKR commented 3 years ago

From my perspective, yes. But I noticed that @mstuebner is still using Alpha 6 and has the problem. Otherwise yes I believe with the current version it should be fine.

mstuebner commented 3 years ago

Moved to alpha 8 today and can confirm that this is gone