Lightning-guy77 Screengrabbers do not have an encoding format...
Posts by Lord-Grey
-
-
I also asked myself, why asks the system for Hardware LED count when it claims a value that is the sum of the LEDs on the 4 sides I have to fill in at the LED layout? This better can be an information output than an input field.
The Hardware LED count should give what the LED device is capable of.
The Layout define how you use the provided hardware LEDs.
It is perfectly fine, if you define a layout for less than the number HW LEDs.
To have some device working, one needs to update all HW LEDs and fill the missing ones not provided in the Layout.
Your case is just a subset, of what is required out there…
Hoping that clarifies.
-
Just looking at all the code, the 256 seems just to be a default value and not a maximum one. It should be the number of LEDs, if I am not mistaken. Why Hardware LED count is not used, might be because of legacy reasons.
If there are hard limits per device type, the UI would not allow to overwrite them.
Lightning-guy77 The WLED limit of 490 does not apply anymore, if you select the DDP protocol.
-
You might try the latest nightly build. There a close suspend/resume integration is available.
-
Have a look here: https://docs.hyperion-project.org/en/json/Subscribe.html
If I am not mistaken HA already has a Hyperion plug-in. Maybe it provides certain events already to.
The capture preview in HA is using the subscriptions, as far as I understand…
-
-
Those commands are changing the state temporarily. They are not changing the configuration items.
Edit: The persistent configuration API is currently not exposed publicly.
-
-
I am currently in the process to add a dominant color feature.
The transition between sectors seems to be a conflicting requirement.
First you would like to group and then have a differentiation on individual LEDs again..
-
Do you have an LED strip where 3 LEDs are treated as one?
Then you need only to configure 1/3 of the number of LEDs
-
Hi ajs
a) You might need to revisit your assumption that this will reduce traffic.
Even if you logical group LEDs. Every LED needs getting a color assigned; i.e. the overall processing required will not change.b) Currently, you can achieve grouping via a custom setup.
In your sample case you would
1. Switch Settings level to Expert
2. Define 20 LEDs on the top (Classic Layout)
3. Click "Generated/Current LED Configuration"
4. Copy all curly bracket elements "{}" five times (add a comma between them)
5. Click Update Preview
6. The Total LED number should say 100 in the Layout Preview
7. Save
Here is as ample for 1 group of 5 LEDs -
Das WLED Device kann über das Netzwerk nicht richtig angesprochen werden. Operation Cancelled weist auf einen Timeout hin.
Entweder
- WLED ist nicht gestartet
- hat mittlerweile eine andere IP
- versuche mal Wifi Sleep im WLED Netzwerk Screen zu deaktivieren.
Zusätzlich könntest Du noch versuchen den Restore State auszuschalten, dann wird das Kommando nicht geschickt.
-
Please excuse my ignorance: where do I find the "click/update rate"?
I meant: "Do not click that often/quick or move around the cursor on the color-selector"
Every click or move creates a request....
-
Try to lower the "click/update rate".
Hyperion currently has problems, if too many requests are issued via API...
This is a known issue.
-
Die Baurate ist immer gleich.
Du hast die Sperrzeit beim Device allerdings auf eins gesetzt.
Die Sperrzeit ist die Zeit, die die LEDs zwischen zwei Updates brauchen.
Wenn Du sie zu klein setzt und viele Updates in kurzer Zeit machst, funktionieren sie halt nicht. Die Speerzeit (latchtime) findest Du im Datenblatt der LEDs.
Je nach Effekt ist die fps/Updateanzahl gering.
Die Zeit zwischen den Updates ist groß genug und darum gehen die Updates durch und die LEDs leuchten.
Beim Grabber hast Du wahrscheinlich eine hohe fps Zahl und es gibt zu viele Updates -> die LEDs leuchten nicht.
-
Change the Settings level to „Expert“ and check, if you can then see the device.
-
Ok. Das ist Hyperion Classic.
Da wird schon lange nicht mehr weiterentwickelt...
Wenn Du auf Hyperion.NG wechselst, stelle bitte sicher, dass das "alte" komplett entfernt wurde.
-
-
Unfortunately, it does not provide enough details…
If you would like to do me a favor, you could start hyperiond.exe with „-c -d“ as options via the command-line or by creating a shortcut with command line properties.
Then full debug output will be printed.
In case the error occurs again, we might find some pointers to what happened before the abort.
Many thanks already in advance!
-
Unfortunately, on Windows I am not aware that there is system logging.
On linux it is different ...