Hi Hyperion-Team,
currently, you can only enable or disable Hyperion's smoothing feature via JSON.
It would be nice if you could set all the smoothing parameters (type, time, etc.) via JSON.
Best regards
Marxon
Hi Hyperion-Team,
currently, you can only enable or disable Hyperion's smoothing feature via JSON.
It would be nice if you could set all the smoothing parameters (type, time, etc.) via JSON.
Best regards
Marxon
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" ]
}
}
}'
Display More
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
}
}
}
]
}
}'
Display More
To test with the development version see here: https://docs.hyperion-project.org/user/advanced/Testing.html
Use PR1849
Thanks for your reply Lord-Grey!
This is already possible with the hyperion nightly build?
Really nice!
Because i'm watching dj-sets and concerts frequently and there i prefer different smoothing settings
than for watching movies. So i want to switch easily between two smoothing setups via remote button.
Is there a something like a nightly changelog on github too?
Best regards
Marxon
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.
That's a lot to study and test!
The installation went smoothly without problems on my LibreElec.
Let's see if mapping the remote will go like it too...
Hi again,
unfortunately the development version respondes
error: No Authorization
Creating a new token does not help
What I don't really understand is the -c option for installing the PR:
the config seems to be copied anyway when executing the PRID.sh
Best regards
Marxon
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.
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.
OK understood!
Have you checked that you run the correct Hyperion version?
Go to System/About and check the build includes the PR number.
Hyperions Dashboard shows me 2.0.17-beta.3+PR1849
How do you pass the command and the token?
Have you tried to run the command from the same host?
Yes i do so.
The getconfig command was working before on 2.0.16 with the following command:
curl -X POST -H "TOKEN" -i http://localhost:8090/json-rpc --data '{
"command": "config",
"subcommand": "getconfig",
"configFilter" : {
"global" : {
"types" : [""]
},
"instances" : {
"ids" : [],
"types" : [ "smoothing" ]
}
}
}'
EDIT:
Sorry I was wrong.
Tried the getconfig command on 2.0.16 again, result:
(ERROR) While validating schema against json data of 'JsonRpc@::ffff:192.168.1.10':[root].configFilter: no schema definition
I am such an idiot!
I left out the two words Authorization Bearer befor my token
Now everything works like excepted!
Sorry sorry sorry!
Good to hear that it is working now!!!
In case you have other findings with the development version, happy to hear.
One last question:
how to autostart the development version in kodi?
Did it.
Thanks for this Infomation Lord-Grey.
Embarrassingly i'm not getting the nightly build installed on my LibreElec.
I also tried Paulchen Panthers script with --nightly option but GibHub release installation does not support nightly releases.
What does the install command say?
Could 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
QuoteCould you share the output?
To some extent I already did This is the exact output:
Pi4:~ # curl -sSL https://releases.hyperion-project.org/install | bash -s -- --nightly
INFO : Identified distribution "libreelec"
ERROR: GibHub release installation does not support nighly releases.
Sorry, I forgot that LibreElec is not working with apt packages. My bad!
There is currently PR 1856 open.
You could test with that one benefitting from further corrections
Allright!
Hi again!
I may have found a new problem. But I'm not sure if it's related to your PR.
I'm using an Android app (Hyperion Control) that previously worked without issues, but now doesn't.
The app was also not updated in recent times, so i guess it must be related to Hyperion.
The log shows the app starting:
2025-04-27T11:13:23.027Z [WEBSOCKET] (DEBUG) (WebSocketJsonHandler.cpp:22:WebSocketJsonHandler()) New WebSocket connection from ::ffff:192.168.1.6 initiated via:
2025-04-27T11:13:23.028Z [WEBSOCKET] (INFO) JSON-API service is ready to process request
But it does not react on any changes.
Any ideas, "Mr. Lord-of Code-Grey"?
I latently applied some further fixes.
Depending when you installed the PR, there were issues.
I now merged the PR and I do not remember, if the script loads closed PR executables.
Maybe you can give it a try
I guess you mean i have to install the nightly build (scripts aborts because of closed pr), right?
Unfortunately i am using LibreElec and it is not working with apt packages.
Don’t have an account yet? Register yourself now and be a part of our community!