JSON commands for smoothing parameters

  • 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

    Pi4 | LibreElec | Hyperion 2.0.17-beta.3+PR1860 | Rudihorn DRM-VC4-Grabber | SN75174 Driver | SN75176 Receiver | WS2812

  • Marxon

    Changed the title of the thread from “JSON commandsfor smoothing parameters” to “JSON commands for smoothing parameters”.
    • Best Answer
    • Official Post

    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



    Assume you would like to update the smoothing configuration for instance 0 you can achieve this by sending


    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? :huh:

    Really nice! :thumbup:

    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

    Pi4 | LibreElec | Hyperion 2.0.17-beta.3+PR1860 | Rudihorn DRM-VC4-Grabber | SN75174 Driver | SN75176 Receiver | WS2812

    • Official Post

    In the unreleased section you find the changes included in the nightly build.

    hyperion.ng/CHANGELOG.md at master · hyperion-project/hyperion.ng
    The successor to Hyperion aka Hyperion Next Generation - hyperion-project/hyperion.ng
    github.com


    The PR I was referring to has some additional corrections. For details see here:

    Diverse Refactoring, error fixing and new features by Lord-Grey · Pull Request #1849 · hyperion-project/hyperion.ng
    Summary Added Support to freely select source and target instances to be used by forwarder Systray: Support multiple instances UI: Validate that key ports do…
    github.com


    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...

    Pi4 | LibreElec | Hyperion 2.0.17-beta.3+PR1860 | Rudihorn DRM-VC4-Grabber | SN75174 Driver | SN75176 Receiver | WS2812

  • Marxon

    Selected a post as the best answer.
  • 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

    Pi4 | LibreElec | Hyperion 2.0.17-beta.3+PR1860 | Rudihorn DRM-VC4-Grabber | SN75174 Driver | SN75176 Receiver | WS2812

    Edited once, last by Marxon ().

    • Official Post

    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

    Pi4 | LibreElec | Hyperion 2.0.17-beta.3+PR1860 | Rudihorn DRM-VC4-Grabber | SN75174 Driver | SN75176 Receiver | WS2812

    Edited once, last by Marxon: Ein Beitrag von Marxon mit diesem Beitrag zusammengefügt. ().

  • I am such an idiot!

    I left out the two words Authorization Bearer befor my token :rolleyes: :cursing: :rolleyes:

    Now everything works like excepted!

    Sorry sorry sorry!

    Pi4 | LibreElec | Hyperion 2.0.17-beta.3+PR1860 | Rudihorn DRM-VC4-Grabber | SN75174 Driver | SN75176 Receiver | WS2812

  • One last question:

    how to autostart the development version in kodi?


    Did it.

    1. createt this hyperion.service file:
      [Unit]
      Description=Hyperion ambient light systemd service for user %i
      Requisite=network.target
      Wants=network-online.target
      After=network-online.target
      After=systemd-resolved.service
      [Service]
      ExecStart=/storage/hyperion_pr1849/bin/hyperiond --userdata /storage/.hyperion --service
      WorkingDirectory=/storage/hyperion_pr1849/bin
      User=%i
      TimeoutStopSec=5
      KillMode=mixed
      Restart=on-failure
      RestartSec=2
      [Install]
      WantedBy=multi-user.target
    2. Copied this file to /storage/.config/system.d/
    3. Run systemctl enable hyperion.service

    Pi4 | LibreElec | Hyperion 2.0.17-beta.3+PR1860 | Rudihorn DRM-VC4-Grabber | SN75174 Driver | SN75176 Receiver | WS2812

    Edited 3 times, last by Marxon: Ein Beitrag von Marxon mit diesem Beitrag zusammengefügt. ().

    • Official Post

    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.

  • 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.

    Pi4 | LibreElec | Hyperion 2.0.17-beta.3+PR1860 | Rudihorn DRM-VC4-Grabber | SN75174 Driver | SN75176 Receiver | WS2812

    • New
    • Official Post

    What does the install command say?


    Code
    curl -sSL https://releases.hyperion-project.org/install | bash -s -- --nightly


    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


    Code
    curl -sSL https://releases.hyperion-project.org/install | bash -s -- --remove
  • Quote

    Could you share the output?

    To some extent I already did 8o 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.

    Pi4 | LibreElec | Hyperion 2.0.17-beta.3+PR1860 | Rudihorn DRM-VC4-Grabber | SN75174 Driver | SN75176 Receiver | WS2812

    • New
    • Official Post

    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 :)

  • 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"? :saint:

    Pi4 | LibreElec | Hyperion 2.0.17-beta.3+PR1860 | Rudihorn DRM-VC4-Grabber | SN75174 Driver | SN75176 Receiver | WS2812

    • New
    • Official Post

    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.

    Pi4 | LibreElec | Hyperion 2.0.17-beta.3+PR1860 | Rudihorn DRM-VC4-Grabber | SN75174 Driver | SN75176 Receiver | WS2812

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!