What does the install command say?
curl -sSL https://releases.hyperion-project.org/install | bash -s -- --nightlyCould you share the output?
Note: If you have already installed hyperion, you need to remove that one first.
… but that is reported by the install script
curl -sSL https://releases.hyperion-project.org/install | bash -s -- --removesioux Those should be the commands.
Note: You MUST use an authentication (aka bearer) token for Admin commands.
{
"command": "config",
"subcommand": "getconfig",
"configFilter" : {
"global" : {
"types" : [ "grabberV4L2" ]
},
"instances" : {
"types" : [ "" ]
}
}
}
{
"command": "config",
"subcommand": "setconfig",
"config" :
{
"global": {
"settings": {
"grabberV4L2": your updated config
}
}
}
}
All fields of a configuration set…
It might not properly work in 2.0.16 anyway...
Besides that your script is also producing a wrong configuration.
config = response.json()
includes the whole response, but you would need only the object provided by info.
In addition, you should check, if the response indicates a successful execution of the request before doing a setconfig
Otherwise you might see "strange" behaviours...
2.0.17-beta should be more advanced and it is more clear on errors.
In addition, you can now just get and manipulate the v42l grabber config only without updating the whole configuration.
Which version are you running, 2.0.17-beta3?
I think there is currently a general issue when the grabber stopps/restarts and you see this effect.
Marxon We did some further corrections and the development version and now publish it via the Nightly Build channel.
So you could run and test it without modifying the systemd service file.
Good to hear that it is working now!!!
In case you have other findings with the development version, happy to hear.
What I don't really understand is the -c option for installing the PR:
The -c option allows you to specify the directory where your current’s hyperion configuration file sits.
This configuration will be copied to the PR directory created during installation and used when you start via the PR script.
That only happens if the directory provided exits. See https://github.com/hyperion-pr…cripts/install_pr.sh#L258
If you do without -c a default configuration will be created.
version respondes
error: No Authorization
Creating a new token does not help
Have you checked that you run the correct Hyperion version?
Go to System/About and check the build includes the PR number.
How do you pass the command and the token?
Have you tried to run the command from the same host?
Just to be on the save side. The token is not the GitHub one, but one you need to create in Hyperion under Network.
In the unreleased section you find the changes included in the nightly build.
The PR I was referring to has some additional corrections. For details see here:
Would be great, if you could test against the PR.
You can install the PR version next to an existing one and remove it after testing.
Hi
with the current development version you can update the configuration too.
As these are Admin commands you need to create an API Token under Network.
Replace "HyperionToken" in the command below via your token.
In case you are executing the command on a different host, replace localhost by the DNS or IP of the host Hyperion runs on.
You can query your current smoothing configuration via
curl -X POST -H 'Authorization: Bearer HyperionToken ' -i http://localhost:8090/json-rpc --data '{
"command": "config",
"subcommand": "getconfig",
"configFilter" : {
"global" : {
"types" : [""]
},
"instances" : {
"ids" : [],
"types" : [ "smoothing" ]
}
}
}'Assume you would like to update the smoothing configuration for instance 0 you can achieve this by sending
curl -X POST -H 'Authorization: Bearer HyperionToken' -i http://localhost:8090/json-rpc --data '{
"command":"config",
"subcommand":"setconfig",
"config":{
"instances":[
{
"id":0,
"settings":{
"smoothing":{
"decay":1,
"dithering":false,
"enable":true,
"interpolationRate":25,
"time_ms":150,
"type":"linear",
"updateDelay":0,
"updateFrequency":25
}
}
}
]
}
}'To test with the development version see here: https://docs.hyperion-project.org/user/advanced/Testing.html
Use PR1849
Mal schauen, ob die Konfig noch gespeichert ist. Hatte zuletzt das Phänomen, dass die Einstellung der Segmente nicht gespeichert bleibt.
Auf welcher Version hast Du das getestet?
Könntest Du es auf Basis von PR1849 testen?
Artifakte zum runterladen findest Du hier:
Gibt es eine Möglichkeit nur das mittlere Segment des Streifens mit der Instanz anzusteuern?
Ja. Das geht mit Hyperion.
Mambojambo Du kannst für ein WLED entweder zu einem! Segment streamen oder an den ganzen Strip.
Damit das Segment Streaming geht, musst Du es in WLED aktivieren.
Siehe https://docs.hyperion-project.…ml#wled-segment-streaming
Best is using the easy install script.
First remove Hyperion, then install the nightly build.
You need to install the current beta version
The error this different from the scenario I shared.
Can you share a screenshot of the about page that we see which hyperion Version you are running and what macOS version you use?
m4r35z Check, if you see warnings in the log as described in
Die Fernbedienung ist nur um temporäre Änderungen zu testen und ja, aktuell ändert sie nur Profil 1
Do you see any other errors in the log
When you press the link button ?
You need to enter a userid and a Client key.
Is your need to only bind to the localhost adapter or to ensure that only local addresses can access the port?
The latter you can already configure under Networks
How does your Authorization header look like?
Does in include the „token “ prefix for the actual token?
In addition, what Hyperion Version are you running?
