Beiträge von TimJW

I don't think anything has changed, but in the last few days, Hyperion has started occasionally toggling WLED off and on again every few seconds - this is quite disruptive as the "default" WLED orange pops on for a second before reverting to the correct screen captured colour.

I was running a 2.0.15 beta, but I've reverted to 2.0.14 with no difference. The logs just show hyperion turning WLED off and then on again, but don't explain WHY it's doing it - anyone have ideas?

Hyperion System Summary Report (My Hyperion Config), Reported instance: unknown

< ----- System information -------------------- >

Hyperion Server:

- Build: (HEAD detached at 2.0.14) (LordGrey-c9a1c88/b109703-1669566414)

- Build time: Nov 27 2022 17:44:02

- Git Remote: https://github.com/hyperion-project/hyperion.ng

- Version: 2.0.14

- UI Lang: en (BrowserLang: en-GB)

- UI Access: advanced

- Avail Screen Cap.: qt,dx

- Avail Video Cap.: v4l2

- Avail Services: boblight,effectengine,forwarder,flatbuffer,protobuffer,mDNS,SSDP,borderdetection

- Config path: C:/Users/Admin/.hyperion

- Database: read/write

Hyperion Server OS:

- Distribution: Windows 10 Version 2009

- Architecture: x86_64

- Kernel: winnt (10.0.19044 (WS: 64))

- Root/Admin: true

- Qt Version: 5.15.2

- Python Version: 3.11.0

- Browser: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/109.0

< ----- Configured Instances ------------------ >

0: First LED Hardware instance Running: true

< ----- This instance's priorities ------------ >

110: VISIBLE! (PROTOSERVER) Owner: undefined

250: (GRABBER) Owner: undefined

priorities_autoselect: true

< ----- This instance components' status ------->

ALL - true

SMOOTHING - true

BLACKBORDER - true

FORWARDER - false

BOBLIGHTSERVER - false

GRABBER - true

V4L - false

LEDDEVICE - true

< ----- Current Log --------------------------- >

2023-01-29T16:50:09.657Z [EFFECTFILES] (INFO) 40 effects loaded from directory :/effects/

2023-01-29T16:50:09.659Z [EFFECTFILES] (INFO) 22 effect schemas loaded from directory :/effects/schema/

2023-01-29T16:50:09.659Z [EFFECTFILES] (INFO) 0 effects loaded from directory C:/Users/Admin/.hyperion/custom-effects/

2023-01-29T16:50:09.670Z [DAEMON] (INFO) DirectX grabber created

2023-01-29T16:50:09.672Z [MAIN] (INFO) Start Systray menu

2023-01-29T16:50:09.672Z [LEDDEVICE|First LED Hardware instance] (INFO) Start LedDevice 'wled'.

2023-01-29T16:50:09.673Z [EFFECTENGINE|First LED Hardware instance] (INFO) Run effect "Rainbow swirl fast" on channel 1

2023-01-29T16:50:09.674Z [FLATBUFSERVER] (INFO) Started on port 19400

2023-01-29T16:50:09.674Z [HYPERION|First LED Hardware instance] (INFO) Initial foreground effect 'Rainbow swirl fast' started

2023-01-29T16:50:09.674Z [PROTOSERVER] (INFO) Started on port 19445

2023-01-29T16:50:09.880Z [HYPERION-INSTMGR] (INFO) Hyperion instance 'First LED Hardware instance' has been started

2023-01-29T16:50:09.882Z [JSONSERVER] (INFO) Started on port 19444

2023-01-29T16:50:09.885Z [WEBSERVER] (INFO) 'Hyperion http-Webserver' started on port 8090

2023-01-29T16:50:09.896Z [WEBSERVER] (INFO) 'Hyperion https-Webserver' started on port 8092

2023-01-29T16:50:10.170Z [LEDDEVICE|First LED Hardware instance] (INFO) Resolved service [wled-4f9f42._wled._tcp.local] to mDNS hostname [wled-4f9f42.local.], service port [80]

2023-01-29T16:50:10.170Z [LEDDEVICE|First LED Hardware instance] (INFO) Resolved hostname (wled-4f9f42._wled._tcp.local) to IP-address (192.168.1.187)

2023-01-29T16:50:10.179Z [LEDDEVICE|First LED Hardware instance] (INFO) Resolved service [wled-4f9f42._wled._tcp.local] to mDNS hostname [wled-4f9f42.local.], service port [80]

2023-01-29T16:50:10.179Z [LEDDEVICE|First LED Hardware instance] (INFO) Resolved hostname (wled-4f9f42._wled._tcp.local) to IP-address (192.168.1.187)

2023-01-29T16:50:10.179Z [LEDDEVICE|First LED Hardware instance] (INFO) Stream UDP data to 192.168.1.187 port: 4048

2023-01-29T16:50:10.179Z [LEDDEVICE|First LED Hardware instance] (INFO) Switching device wled ON

2023-01-29T16:50:10.326Z [LEDDEVICE|First LED Hardware instance] (INFO) Device wled is ON

2023-01-29T16:50:10.326Z [LEDDEVICE|First LED Hardware instance] (INFO) LedDevice 'wled' enabled

2023-01-29T16:50:12.685Z [LEDDEVICE|First LED Hardware instance] (INFO) Switching device wled OFF

2023-01-29T16:50:12.751Z [LEDDEVICE|First LED Hardware instance] (INFO) Device wled is OFF

2023-01-29T16:50:12.752Z [EFFECTENGINE|First LED Hardware instance] (INFO) Effect [Rainbow swirl fast] finished

2023-01-29T16:50:19.536Z [LEDDEVICE|First LED Hardware instance] (INFO) Switching device wled ON

2023-01-29T16:50:19.631Z [LEDDEVICE|First LED Hardware instance] (INFO) Device wled is ON

2023-01-29T16:50:35.788Z [LEDDEVICE|First LED Hardware instance] (INFO) Switching device wled OFF

2023-01-29T16:50:35.852Z [LEDDEVICE|First LED Hardware instance] (INFO) Device wled is OFF

2023-01-29T16:50:35.872Z [LEDDEVICE|First LED Hardware instance] (INFO) Switching device wled ON

2023-01-29T16:50:35.979Z [LEDDEVICE|First LED Hardware instance] (INFO) Device wled is ON

2023-01-29T16:50:38.786Z [LEDDEVICE|First LED Hardware instance] (INFO) Switching device wled OFF

2023-01-29T16:50:38.852Z [LEDDEVICE|First LED Hardware instance] (INFO) Device wled is OFF

2023-01-29T16:50:38.860Z [LEDDEVICE|First LED Hardware instance] (INFO) Switching device wled ON

2023-01-29T16:50:39.006Z [LEDDEVICE|First LED Hardware instance] (INFO) Device wled is ON

2023-01-29T16:50:51.664Z [LEDDEVICE|First LED Hardware instance] (INFO) Switching device wled OFF

2023-01-29T16:50:51.726Z [LEDDEVICE|First LED Hardware instance] (INFO) Device wled is OFF

2023-01-29T16:50:51.758Z [LEDDEVICE|First LED Hardware instance] (INFO) Switching device wled ON

2023-01-29T16:50:51.853Z [LEDDEVICE|First LED Hardware instance] (INFO) Device wled is ON

2023-01-29T16:50:55.664Z [LEDDEVICE|First LED Hardware instance] (INFO) Switching device wled OFF

2023-01-29T16:50:55.752Z [LEDDEVICE|First LED Hardware instance] (INFO) Device wled is OFF

2023-01-29T16:50:55.768Z [LEDDEVICE|First LED Hardware instance] (INFO) Switching device wled ON

2023-01-29T16:50:55.884Z [LEDDEVICE|First LED Hardware instance] (INFO) Device wled is ON

2023-01-29T16:50:58.912Z [LEDDEVICE|First LED Hardware instance] (INFO) Switching device wled OFF

2023-01-29T16:50:58.951Z [LEDDEVICE|First LED Hardware instance] (INFO) Device wled is OFF

2023-01-29T16:50:58.958Z [LEDDEVICE|First LED Hardware instance] (INFO) Switching device wled ON

2023-01-29T16:50:59.079Z [LEDDEVICE|First LED Hardware instance] (INFO) Device wled is ON

Just as an update in case anyone else struggles with this - I couldn't get Hyperion to reliably work after sleep, and I also ran into a problem with HyperionScreenCap stopping capture after sleep and not resuming.

Rather than spend any more time, I just used a quick powershell script to terminate and relaunch Hyperion and HyperionScreenCap, and set it as a scheduled task, triggered on workstation unlock (as I have my PC set to lock on sleep). This is now working fine for me, although hopefully Hyperion will become more reliable at suspend/resume over time and it will be unnecessary in the future!

I just encountered another crash when resuming from sleep... but annoyingly, running hyperion with the "-c -d" from the command line, it still creates its own window and writes all the logs to that, so when the app crashes, the window vanishes together with all the log details.

I'm struggling to think of a way to capture this - a quick google suggests that adding "/k" as a parameter to the console window should keep it open, or alternatively a flag to capture log writes to a file would be an option? If it happens again, I'll try to make sure the hyperion window is on top so I can watch it, but I suspect the crash will occur quickly enough that I won't get a chance to see any error messages...

EDIT: just had a slightly different crash, it's come out of sleep but hyperion isn't responding at all, and the context menu isn't working. The log window is still up, but the most recent log is a few seconds after the initial startup, so nothing was written either entering or leaving sleep. Killing the process and restarting works fine, expected.

Followup (sorry for the spam) - this time Hyperion slept, woke up fine, but didn't seem to be able to control or see the LED strip (no output). Quitting and restarting Hyperion corrected the problem, as usual. I've put the logs into pastebin rather than clogging up this thread: https://pastebin.com/s6Dd5tka

Thanks, that's perfect - I just (predictably) slept and woke five times and everything worked perfectly, but I'll keep launching with the debug flag set and try to test more tomorrow!

Windows logs show me this:

Faulting application name: hyperiond.exe, version: 2.0.15.0, time stamp: 0x63b45622

Faulting module name: Qt5Core.dll, version: 5.15.2.0, time stamp: 0x5fa4dd3b

Exception code: 0xc0000005

Fault offset: 0x00000000001f307b

Faulting process ID: 0x337c

Faulting application start time: 0x01d921eab9d30beb

Faulting application path: C:\Utilities\Hardware\Hyperion\bin\hyperiond.exe

Faulting module path: C:\Utilities\Hardware\Hyperion\bin\Qt5Core.dll

Report ID: bf5d7662-2d84-4885-b5e7-aa91fd3ba5a2

Faulting package full name:

Faulting package-relative application ID:

EventData:

hyperiond.exe

2.0.15.0

63b45622

Qt5Core.dll

5.15.2.0

5fa4dd3b

c0000005

00000000001f307b

337c

01d921eab9d30beb

C:\Utilities\Hardware\Hyperion\bin\hyperiond.exe

C:\Utilities\Hardware\Hyperion\bin\Qt5Core.dll

bf5d7662-2d84-4885-b5e7-aa91fd3ba5a2

I'm guessing this isn't much help, though!

Ah - thank you! Just downloaded and slept / woke three times - it worked perfectly twice (with a delay of about 20 seconds after waking before coming to life), but on one occasion hyperion crashed - does it log to disk so it's possible to see what went wrong? (And thanks again for taking the time to add this functionality and point me at the dev builds to test it.)

Hi, I'm running Hyperion with WLED (just started setting it up this morning). All working well, except that when the PC sleeps and then wakes, Hyperion stops working. The LEDs correctly go blank when the PC sleeps, but they don't come back on when woken.

I've checked the logs, and after sleep / wake, it shows this:

< ----- Current Log --------------------------- >

2023-01-06T14:16:43.066Z [LEDDEVICE|First LED Hardware instance] (ERROR) Device disabled, device 'wled' signals error: 'Power-off request failed with error: 'Host unreachable''

2023-01-06T14:16:43.066Z [LEDDEVICE|First LED Hardware instance] (WARNING) Failed switching device wled OFF

Which perhaps means that Hyperion thinks it has lost connection to the WLED controller and can't access it any more?

After waking, if I tell hyperion to "identify" the LED controller, the lights all flash correctly, so the connection is fine. Also, if I just restart Hyperion it all starts working again - but obviously having to restart manually each time the PC sleeps is a bit irritating! Does anyone have any idea why this is happening and whether it can be resolved?

Thanks in advance!