Posts by Marxon

Hi,

what exactly do you mean with "rebuilt Hyperion"?

Did you rebuild the software or your hardware setup?

Was it working before?

Is the single led fully working and controllable with hyperion?

Best regards

Marxon

Hi,

what exactly do you mean with "doesn't want to the WiFi most of the times"?

If it doesn't connect to wifi then it is for sure not because of hyperion.

Best regards

Marxon

Hi,

your problem couldt be because the voltage drop.

Try to feed the power from both sides of the stripe.

Best regards

Marxon

Hi again.

Now that there is a new Pull Request containing your feature (thanks to Lord-Grey)

i did some further tests with it and have to agree your objections.

Depending the scene the differences between the modes are more or less noticible but they really excist.

Allright!

Quote

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

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.

Hi bruteX,

for me the mean color applied to all leds mode archives exactly what you want.

I tried various scenes:

Underwater scene, all leds blue.

Desert scene, all leds orange.

Space scene, all leds black.

Woods scene, all leds green.

The led color changes only if most of the screen color does it too.

You can try to increase the smoothing time to reduce distraction.

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

I am such an idiot!

I left out the two words Authorization Bearer befor my token

Now everything works like excepted!

Sorry sorry sorry!

Quote from Lord-Grey

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!

Quote from Lord-Grey

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

Quote from Lord-Grey

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

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

2nd Update:

Setting smoothing paramaters via JSON is only available in Hyperion's Test builds for now.

See this thread: JSON commands for smoothing parameters

Topic closed

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

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

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

Update:

as a workaround i use a second instances with different smotthing settings.

Hi everybody,

i read Hyperions JSON documentation but did not find the commands for the smoothing parameters (type, time, update frequency., delay).

Aren't these parameters available?

Best rergards

Marxon

Hi everybody,

perf top

shows me multiple running hyperiond processes.

Is this normal or shoudt there be only one hyperiond at once?

Best regards
Marxon

I just un- and reinstalled Hyperion and the number of processes has not changed.

So i guess multiple hyperiond instances are normal.

Topic closed

Hi pclin,

thanks for explanation!

Although I would now like to ask the nooby question why it not could simply be copied in the graphics memory?

Afaik there is only "normal" RAM and no special GPU Memory on the Pi?

Best regards

Marxon