JSON commands for smoothing parameters
- Marxon
- Thread is marked as Resolved.
-
-
Marxon What should we do without you!
Tastes a little bit sarcastic
Switches are working now but switching takes longer every time you switch.
Restarting Hyperion does help temporally.
-
Tastes a little bit sarcastic
Sorry, I meant it seriously! No sarcasm!
I very much appreciate you testing and proactively providing feedback.
Many other just consume…
-
Switches are working now but switching takes longer every time you switch.
Restarting Hyperion does help temporally.
Hi
Is there a concrete Toggle-Switch that is slow?
Might be that the whole component overview is rendered every time by the browser and that is slow.
I toggled Smoothing rapidly.
If I look the the requests send to the backend and the updates received, they are all in a < 10 ms range.
There is only one outlier of 16ms.
Boblight is between 1-3 ms. -
Hi again,
all switches are affected.
First time switching is almost instantly.
2nd time takes 3-4 seconds.
3rd time takes about 10 seconds.
4th time takes about 30 seconds.
...
The GUI is fine, but the LED response is what takes so long.
EDIT:
I want to share my log with you but can not reproduce the issue. GIve me some minutes....
I swear, I was able to repeat this at least 5 times today, restarting several times in between but somehow all is fine now.
So I must have changed some setting which i can not remember.
We may never know. Sorry
-
exporting included effects does not work:
Fixed
-
-
Hi Marxon
The original post was about API.
I reworked the documentation in a more modern way.
You might want to have an early look at api.hyperion-project.org
This now includes the config related commands, too.
-
Hi Marxon
The original post was about API.
I reworked the documentation in a more modern way.
You might want to have an early look at api.hyperion-project.org
This now includes the config related commands, too.Lord-Grey your new Hyperion API documentation is very good!
Easy understandable and user friendly.
The code generator is awsome and helps to avoid syntax or typing errors.
Are you adding the effects api later, too? That's the only thing whats missing.
If it's desired/needed i would like to contribute a german translation somehow.
Besides: you just got your 300th forum reaction
-
Marxon Thanks for sharing feedback and great that you like it!
Many thanks for your offer on translation.
For now, I would suggest sticking to English only for now. give. Maintaining multiple languages by such a small team seems always be challenging…
If the overall community sees benefit, I am happy to revisit it. I am just hesitant to proactively start this, if there is no obvious demand.
…but maybe you would like to support creating some documentation which is currently missing?
Are you adding the effects api later, too?
Are you talking about https://docs.hyperion-project.org/effects/API.html?
In case yes, this one should not be added to the integration API.
Looks like the term API is misleading here.
I suggest changing the wording to „Effect Development Framework“ which would more clearly address that it is a toolkit for custom effect development and not an interface to Hyperion.
If you were referring to something else, please shout.
-
Are you talking about https://docs.hyperion-project.org/effects/API.html?
In case yes, this one should not be added to the integration API.Looks like the term API is misleading here.
Just thought for having all "coding-stuff" in one place.
…but maybe you would like to support creating some documentation which is currently missing?
How doing this?
Before i dive deeper, did i understood the general process correctly?
- clone the repo
- make edits
- generate documentation with doxygen
-
How doing this?
To add addition documentation items for general interest you would
a) clone https://github.com/hyperion-project/hyperion.docs
b) follow the setup instructions
c) do your updates in Markdown language; you might find additional details here what VitePress Markdown supports
d) ping me via DM or Discord if you are stuck
e) issue a Pull Request with your changes (similar the one I just did)
Hoping that gives you a good start...
-
So I was completely wrong about Doxygen
But in meanwhile I learned that Doxygen is for code documentationNevertheless editor and development server is set up and for now I just need to understand the documentations folder structure but then i can get started.
Participate now!
Don’t have an account yet? Register yourself now and be a part of our community!