Beiträge von spiff72

I did find that - thanks. I thought it would just be a text file, but it wasn't. I ended up just recalibrating the colors from scratch. Maybe if I get ambitious I will try copying the other file over to see if it looks any better than what I just came up with.

UPDATE: The above worked!

I did the following:

• Edit the hyperion.service file in /etc/systemd/system to add a line to the [Service] section:

User=root

• Run: sudo systemctl disable --now hyperiond@pi
• Run: sudo systemctl daemon-reload (not sure if this was necessary)
• Run: sudo reboot

After rebooting, the service hyperion was showing up under systemctl --all, and the hyperiond@pi is gone.

The web ui loads as expected, but my configuration was gone (as others have mentioned when switching to running it as root). I assume this is happening because running it as root is like starting from scratch, and the configuration files have to be recreated in the root users folder structure. My setup is simple to configure, so that was easy. Unfortunately I lost the configuration I did to the colors, so I have to figure out how to redo that. Maybe I can find the config file for the pi user and grab the values from there...

Back in business!

So I am poking around online to look at the process for starting services at boot. I see TWO .service files in my /etc/systemd/system directory. The contents are as follows:

hyperion.service

[Unit]
Description=Hyperion ambient light systemd service
After=network.target

[Service]
ExecStart=/usr/bin/hyperiond
WorkingDirectory=/usr/share/hyperion/bin
TimeoutStopSec=5
KillMode=mixed
Restart=on-failure
RestartSec=2

[Install]
WantedBy=multi-user.target

and

hyperiond@.service

[Unit]
Description=Hyperion ambient light systemd service  for user %i
After=network.target

[Service]
ExecStart=/usr/bin/hyperiond
WorkingDirectory=/usr/share/hyperion/bin
User=%i
TimeoutStopSec=5
KillMode=mixed
Restart=on-failure
RestartSec=2

[Install]
WantedBy=multi-user.target

When I run the following command immediately after boot (and before attempting to manually start a hyperion service, I get the following two entries for hyperion (sorry for the ugly formatting):

systemctl --all

  hyperion.service                                                           loaded    inactive dead      Hyperion ambient light sy
  hyperiond@pi.service                                                       loaded    inactive dead      Hyperion ambient light sy

I am not sure if there are supposed to be two of them. When I have been starting it manually, I just use the hyperion verbiage (without d), and that gets that one running successfully. The fact that both of the services after boot are "inactive dead" is odd.

My rough understanding of linux leads me to think that the hyperiond@.service can accept an argument of a user and run it as that user. However when I attempted to run:

sudo systemctl enable --now hyperiond@root

I am pretty sure I got an error about the file not existing.

I guess I might try just disabling the hyperiond@ service and editing the hyperion.service file to include a line for user=root and see if that works.

and to clarify - that hyperiond is probably running as root because I had to start it with the sudo systemctl enable command (without the d?)

i think that command MUST be run as root?

I already have my pi and WLED set up with static IPs, so that isn't the issue.

I tried running that command on mine and get this:

root       713 26.0  3.4 287100 32816 ?        Ssl  22:12  27:10 /usr/bin/hyperiond
pi         844  0.0  0.0   7480   472 pts/0    S+   23:56   0:00 grep --color=auto hyperion

Quick clarification question...

I am running into this issue as well, and upgraded from a hyperbian alpha9 raspi config to alpha10. I am not driving LEDs directly with pi GPIO - I am connecting hyperion to a WLED controller. I managed to get it running except the hyperion service won't start automatically after a reboot of the pi. Running the following via ssh will get it running again after a reboot:

sudo systemctl enable --now hyperion

If I use the commands referenced above, am I just putting a band-aid on the problem, or is it a legit fix? Or am I better off just flashing a fresh hyberbian with alpha10 (which seems to require no "fixes" like this to make it work)?

I will check into that - thanks. I had seen that issue regarding root, too, but I was thinking that since I am using the "network" WLED option (and not driving LEDs directly with the Pi), that didn't apply. The sudo requirement in my command does raise the question again, though!

Sorry if this is an obvious question, but I upgraded a hyperbian install (alpha9) to alpha10 last week, and after some fiddling (uninstalling and reinstalling hyperion via apt install), I got it working and set up fully.

However, I rebooted the Pi that it is running on today because things weren't working correctly (I think I had inadvertently changed the IP of the WLED instance that it is driving), and when it rebooted, the UI never came back up. I eventually tried running the following through an SSH connection:

sudo systemctl enable --now hyperion

and this got it running again.

So my question: is there a toggle somewhere in the UI that determines if the service starts at boot, or does this need to be manually set up by editing some files?

That was the ticket! Uninstalled, it flagged a directory that it couldn't delete (/usr/share/hyperion), so I went and deleted that directory manually, and reinstalled. UI is working now! I have to reconfigure a few things (start from scratch), but it wasn't a complex setup...

Thanks!

did you have to reflash the card, or just run the uninstall? I will give that a shot!

I had a working install of Alpha9 and wanted to give Alpha10 a try, so I followed the instructions here: https://apt.hyperion-project.org/

However, after running the commands there (and also rebooting the pi a couple of times, as well as re-running sudo apt update and sudo apt upgrade), I can't get into the web UI anymore. It's been a while since I set this up (it hasn't been used a ton), but I MAY have set it up the first time with a Hyperbian image. If I run sudo apt install hyperbian, it reports that Hyperion is already the newest version.

I am running this on a Raspberry Pi 3 (buster). Any suggestions to get this back up and running?

DON'T DO IT MY WAY!!! Web GUI goes offline every time I shut down and I can't get it back. I am planning to reimage with HyperBian at this point.

i (partially) retract my last statement. I think the settings DID carry over - I went in and just saved them again and the lights started working again. But the import of settings from alpha 8 did bork things up!

EDIT: Don't do it this way. My web GUI is unavailable every time that I removed power.

Well I tried the above - it appeared to update, but my config was apparently wiped out (acts like a fresh install - even the Web GUI password is reset). I tried importing the settings in the web gui afterward, and that borked the whole thing - couldn't connect to the GUI. I ran the dpkg command again and it came back online. I will just redo my config from scratch (it wasn't very complex).

Looking for guidance here too...would it just be the following in an ssh session (for PiZero W)?

wget https://github.com/hyperion-pr…-alpha.9-Linux-armv6l.deb
sudo dpkg -i Hyperion-2.0.0-alpha.9-Linux-armv6l.deb

I haven't tried this - just wanted to know if this was the right command!