multilightpack results in errors/warnings #505
Labels
Comments
|
The error re: serial numbers isn’t an error - it should be marked as info. How many leds do you have configured ? |
|
I have 30 LEDs configured I have the three packs, the usb capture device and flirc connected to a powered usb hub which is then connected to the pi this was one of the good examples where it detected all three packs (even though only one actually turned on), it quite often gives a LIBUSB_ERROR_PIPE or something along those lines when it runs through its detection routine and wont return all the serial numbers, the current stable version of hyperion does this too occasionally but restarting the service (quite often multiple times) usually fixes it If I configure it to run just one pack, it'll actually work and wont spam that warning regarding no more led data available |
Lord-Grey
added a commit
to Lord-Grey/hyperion.ng
that referenced
this issue
Jun 29, 2020
Paulchen-Panther
pushed a commit
that referenced
this issue
Jul 12, 2020
* Refactor LedDevices - Initial version * Small renamings * Add WLED as own device * Lpd8806 Remove open() method * remove dependency on Qt 5.10 * Lpd8806 Remove open() method * Update WS281x * Update WS281x * Update WS2812SPI * Add writeBlack for WLED powerOff * WLED remove extra bracket * Allow different Nanoleaf panel numbering sequence (Feature req.#827) * Allow different Nanoleaf panel numbering sequence (Feature req.#827) * build(deps): bump websocket-extensions from 0.1.3 to 0.1.4 in /docs (#826) Bumps [websocket-extensions](https://github.com/faye/websocket-extensions-node) from 0.1.3 to 0.1.4. - [Release notes](https://github.com/faye/websocket-extensions-node/releases) - [Changelog](https://github.com/faye/websocket-extensions-node/blob/master/CHANGELOG.md) - [Commits](faye/websocket-extensions-node@0.1.3...0.1.4) Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> * Fix typos * Nanoleaf clean-up * Yeelight support, generalize wizard elements * Update Yeelight to handle quota in music mode * Yeelight extend rage for extraTimeDarkness for testing * Clean-up - Add commentary, Remove development debug statements * Fix brightnessSwitchOffOnMinimum typo and default value * Yeelight support restoreOriginalState, additional Fixes * WLED - Remove UDP-Port, as it is not configurable * Fix merging issue * Remove QHostAddress::operator=(const QString&)' is deprecated * Windows compile errors and (Qt 5.15 deprecation) warnings * Fix order includes * LedDeviceFile Support Qt5.7 and greater * Windows compatibility and other Fixes * Fix Qt Version compatability * Rs232 - Resolve portname from unix /dev/ style, fix DMX sub-type support * Disable WLED Wizard Button (until Wizard is available) * Yeelight updates * Add wrong log-type as per #505 * Fixes and Clean-up after clang-tidy report * Fix udpe131 not enabled for generated CID * Change timer into dynamic for Qt Thread-Affinity * Hue clean-up and diyHue workaround * Updates after review feedback by m-seker * Add "chrono" includes * Add "chrono" includes * Revert "Merge branch 'master' into Refactor_LedDevices" This reverts commit 978ac75, reversing changes made to aa346ed. Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Paulchen-Panther
pushed a commit
that referenced
this issue
Jul 12, 2020
* Refactor LedDevices - Initial version * Small renamings * Add WLED as own device * Lpd8806 Remove open() method * remove dependency on Qt 5.10 * Lpd8806 Remove open() method * Update WS281x * Update WS2812SPI * Add writeBlack for WLED powerOff * WLED remove extra bracket * Allow different Nanoleaf panel numbering sequence (Feature req.#827) * build(deps): bump websocket-extensions from 0.1.3 to 0.1.4 in /docs (#826) * Bumps [websocket-extensions](https://github.com/faye/websocket-extensions-node) from 0.1.3 to 0.1.4. - [Release notes](https://github.com/faye/websocket-extensions-node/releases) - [Changelog](https://github.com/faye/websocket-extensions-node/blob/master/CHANGELOG.md) - [Commits](faye/websocket-extensions-node@0.1.3...0.1.4) * Fix typos * Nanoleaf clean-up * Yeelight support, generalize wizard elements * Update Yeelight to handle quota in music mode * Yeelight extend rage for extraTimeDarkness for testing * Clean-up - Add commentary, Remove development debug statements * Fix brightnessSwitchOffOnMinimum typo and default value * Yeelight support restoreOriginalState, additional Fixes * WLED - Remove UDP-Port, as it is not configurable * Fix merging issue * Remove QHostAddress::operator=(const QString&)' is deprecated * Windows compile errors and (Qt 5.15 deprecation) warnings * Fix order includes * LedDeviceFile Support Qt5.7 and greater * Windows compatibility and other Fixes * Fix Qt Version compatability * Rs232 - Resolve portname from unix /dev/ style, fix DMX sub-type support * Disable WLED Wizard Button (until Wizard is available) * Yeelight updates * Add wrong log-type as per #505 * Fixes and Clean-up after clang-tidy report * Fix udpe131 not enabled for generated CID * Change timer into dynamic for Qt Thread-Affinity * Hue clean-up and diyHue workaround * Updates after review feedback by m-seker * Add "chrono" includes
|
Closed, as no feedback by @Sp0rks |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi,
I have 3 light packs connected to a Rasberry PI 2.0 (running Stretch) and after spending longer than I care to admit trying to compile Hyperion.NG I finally got it working but am experiencing issues where it throws various errors and warnings regarding the packs, doesn't always detect the 3 of them and even if it does, throws errors regardless and a majority of the time only 1 (if I'm lucky 2) of the packs will actually light up.
This is what it gives me when running in verbose
and it'll spam that WARNING about no more led data until I kill it.
I completely understand this is still in ALPHA but thought I'd play around with it
The text was updated successfully, but these errors were encountered: