-
-
Notifications
You must be signed in to change notification settings - Fork 370
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
LEDs are not turning black after deactivating Protocol Buffers Stream and no active source is left #828
Comments
@b1rdhous3 schau mal in den slack vorbei bitte :-) |
Should be fine
Should work, this fires black but just once. |
Same issues with 2.0.0 alpha 6 |
I've had this issue intermittently through all the 2.0 alphas. Sometimes it clears the lights, sometimes 1, 2, or 3 instances will fail to go to black and stay on last colors. Inputs are from protocol buffer (Mediaportal add-in), 3 devices (APA102 led strip, nanoleaf, nanoleaf panels). I tried to set the idle color to black as a workaround, but that doesn't seem to fix reliably, either. |
@ncmilhouse I can follow the expectations raised, but unfortunately hyperion does not support switching-off LEDs yet, when no further input streams are available. I will consider it as an enhancement request for the backlog. For now, I could only suggest, you either disable hyperion's instances or the LED devices via WebSockets or the UI. |
I don't expect the nanolead devices to actually shut off, I am fine with streaming black. But it isn't even doing that. If I stop the source in Mediaportal I would expect all the lights (led strips and nanoleafs) to go dark. But many times at least 1 is still showing the last color. |
The devices will only go black, if there is no source any longer. Nanoleaf devices should go off and streaming is to be stopped. Otherwise there is unnecessary network traffic. |
Bug report
I am using a protocol buffers stream for my LEDs. In previous alphas the LEDs turned black if i deactivated the stream and the source disappears from the input selection on remote control.
Now the source disappears as well and no source is left but the LEDs are representing the last LED state. I manually have to disable and enable LED Hardware on Remote Tab to turn off the LEDs.
Steps to reproduce
I just figured out that this isn't only the case with protocol buffers. At least Effect have the same Problem.
What is expected?
What is actually happening?
System
Hyperion Server:
Hyperion Server OS:
Log:
[hyperiond WEBSOCKET] (DEBUG) (JsonAPI.cpp:102:handleInstanceSwitch()) Client '::ffff:192.168.178.xx' switch to Hyperion instance 0 [hyperiond PROTOSERVER] (DEBUG) (ProtoClientConnection.cpp:75:disconnected()) Socket Closed [hyperiond HYPERION] (DEBUG) (PriorityMuxer.cpp:255:clearInput()) Removed source priority 129 [hyperiond HYPERION] (DEBUG) (PriorityMuxer.cpp:333:setCurrentTime()) Set visible priority to 255 [hyperiond LEDDEVICE] (DEBUG) (LedDeviceAdalight.cpp:83:receivedData()) >>received 4 bytes data [hyperiond LEDDEVICE] (DEBUG) (LedDeviceAdalight.cpp:83:receivedData()) Previous line repeats 7 times [hyperiond PROTOSERVER] (DEBUG) (ProtoServer.cpp:68:newConnection()) New connection from ::ffff:192.168.178.xx [hyperiond HYPERION] (DEBUG) (PriorityMuxer.cpp:158:registerInput()) Register new input 'Proto@::ffff:192.168.178.xx/PROTOSERVER' with priority 129 as inactive [hyperiond HYPERION] (DEBUG) (PriorityMuxer.cpp:238:setInputImage()) Priority 129 is now active [hyperiond HYPERION] (DEBUG) (PriorityMuxer.cpp:333:setCurrentTime()) Set visible priority to 129 [hyperiond LEDDEVICE] (DEBUG) (LedDeviceAdalight.cpp:83:receivedData()) >>received 4 bytes data [hyperiond LEDDEVICE] (DEBUG) (LedDeviceAdalight.cpp:83:receivedData()) Previous line repeats 9 times [hyperiond HYPERION] (DEBUG) (PriorityMuxer.cpp:255:clearInput()) Removed source priority 129 [hyperiond HYPERION] (DEBUG) (PriorityMuxer.cpp:333:setCurrentTime()) Set visible priority to 255 [hyperiond PROTOSERVER] (DEBUG) (ProtoClientConnection.cpp:75:disconnected()) Socket Closed [hyperiond LEDDEVICE] (DEBUG) (LedDeviceAdalight.cpp:83:receivedData()) >>received 4 bytes data [hyperiond LEDDEVICE] (DEBUG) (LedDeviceAdalight.cpp:83:receivedData()) Previous line repeats 2 times [hyperiond EFFECTENGINE] (INFO) Run effect "Fire" on channel 1 [hyperiond EFFECTENGINE] (DEBUG) (EffectEngine.cpp:183:runEffectScript()) Start the effect: name [Fire], smoothCfg [2] [hyperiond HYPERION] (DEBUG) (PriorityMuxer.cpp:158:registerInput()) Register new input 'Web Configuration@::ffff:192.168.178xx/EFFECT' with priority 1 as inactive [hyperiond HYPERION] (DEBUG) (PriorityMuxer.cpp:238:setInputImage()) Priority 1 is now active [hyperiond HYPERION] (DEBUG) (PriorityMuxer.cpp:333:setCurrentTime()) Set visible priority to 1 [hyperiond HYPERION] (DEBUG) (PriorityMuxer.cpp:255:clearInput()) Removed source priority 1 [hyperiond HYPERION] (DEBUG) (PriorityMuxer.cpp:333:setCurrentTime()) Set visible priority to 255 [hyperiond EFFECTENGINE] (INFO) effect finished [hyperiond LEDDEVICE] (DEBUG) (LedDeviceAdalight.cpp:83:receivedData()) >>received 4 bytes data [hyperiond LEDDEVICE] (DEBUG) (LedDeviceAdalight.cpp:83:receivedData()) Previous line repeats 68 times [hyperiond WEBSOCKET] (DEBUG) (JsonAPI.cpp:1035:handleLoggingCommand()) log streaming activated for client ::ffff:192.168.178xx [hyperiond WEBSOCKET] (DEBUG) (JsonAPI.cpp:1035:handleLoggingCommand()) log streaming activated for client ::ffff:192.168.178xx
The text was updated successfully, but these errors were encountered: