Raspberry Pi IP-address setting for Web Configuration

  • Hello,


    I actually try to use Hyperion again with my Rpi4. This device, as media server, is connected

    - per WIFI with my home network and

    - per Lan-cable with a 2nd raspi, my TV and my Radio.

    I installed Hyperion successfully and expected to get it with the web interface, like I can do it on my rpi3, but it does not. The reason seems to be that Hyperion did not connect the web interface to my WIFI address, but only with the LAN-Address, so I can't access it from my home network. I've read something like that in a logfile.


    Does somebody know if there is a possibility to force Hyperion to connect with my WIFI address instead of the LAN address?


    In syslog I find some lines like this

    Code
    Jan 28 15:48:36 Medienserver hyperiond[1699]: Error : incorrect HTTP headers line : "53Aid%25253Dn%2525253A14%25255Ewidth%25253Dn%2525253A68%255Eo%25253Aid%25253Dn%2525253A15%25255Ewidth%25253Dn%2525253A68%25255Ehidden%25253Db%2525253A1%255Eo%25253Aid%25253Dn%2525253A16%25255Ewidth%25253Dn%2525253A68%25255Ehidden%25253Db%2525253A1%255Eo%25253Aid%25253Dn%2525253A17%25255Ewidth%25253Dn%2525253A258%25255Ehidden%25253Db%2525253A1%255Eo%25253Aid%25253Dn%2525253A18%25255Ewidth%25253Dn%2525253A258%25255Ehidden%25253Db%2525253A1%255Eo%25253Aid%25253Dn%2525253A19%25255Ewidth%25253Dn%2525253A258%25255Ehidden%25253Db%2525253A1%255Eo%25253Aid%25253Dn%2525253A20%25255Ewidth%25253Dn%2525253A258%255Eo%25253Aid%25253Dn%2525253A21%25255Ewidth%25253Dn%2525253A258%255Eo%25253Aid%25253Dn%2525253A22%25255Ewidth%25253Dn%2525253A68%25255Ehidden%25253Db%2525253A1%5Esort%3Do%253Afield%253Ds%25253Astart_real%255Edirection%253Ds%25253AASC%5Efilters%3Do%253A\r\n"


    and I found something strange else...

    on my rpi3, where it works I see the system clock working:

    Code
    micha@raspberrypi:~ $ ps -e | grep hyp
    1282 ?        02:41:28 hyperiond
    micha@raspberrypi:~ $ ps -e | grep hyp
    1282 ?        02:41:32 hyperiond
    micha@raspberrypi:~ $ ps -e | grep hyp
    1282 ?        02:43:13 hyperiond


    on my rpi4 hyperion seems to fall into a black hole, the time goes extremly slow:

    Code
    micha@Medienserver:~$ ps -e | grep hyp
    1215 ?        00:00:02 hyperiond
    micha@Medienserver:~$ ps -e | grep hyp
    1215 ?        00:00:03 hyperiond
    micha@Medienserver:~$ ps -e | grep hyp
    1215 ?        00:00:03 hyperiond

    I tried something:

    • removed hyperion
    • reboot
    • deleted all eth0 config information
    • installed hyperion again

    Result: I get a random and public address at eth0 and hyperion connects for the web configuration to this one



    next:

    • removed hyperion
    • reboot
    • sudo ifconfig eth0 down

    now ifconfig shows no ethernet entry :)

    • installed hyperion again

    Result: Hyperion connects for the web configuration to the same public address like before:(


    From where hyperion takes the information about the rpi controllers IPv4-Address :?:

    2 Mal editiert, zuletzt von micha53 () aus folgendem Grund: Merged a post created by micha53 into this post.

  • time heals many wounds.... but not all


    today I repeated the installation of hyperion and now the installation ends with the right IPv4-address

    but my browser (Firefox, and edge does the same) still tells me that it can not establish a connection to the site.

    On that raspberry I have already Kodi and tvheadend running and I can reach the web interface of both.

    Further I have Samba and mindlna at the system running.


    The syslog message and the timing behavior at the ps command still remain.

  • systemctl status hyperion@micha shows what?

    If Hyperion was started correctly and the ports are not occupied by something else, you will also get to the WebUI with 192.168.178.43:8090 or 192.168.178.43:8091


    regards pclin

    Dreambox ONE / TWO

    dreamOS OE2.6

    Amlogic S922X - 53.000 DMIPS - 2 GB RAM - 16 GB Flash - Twin-DVB-S2X Tuner - HDR10 - HLG
    -
    AudioDSP: miniDSP 2x4HD - Amp: Pentagon - Lautsprecher ELAC / ARENDAL
    LG OLED65BX9LB (PicCap, hyperion.NG webOS)

    FireTV 4K max

    -
    hyperion (classic) & Plugin HyperionControl | hyperion-ng 2.0.16-beta.1 (dreamOS)
    Hyperion-ng (Debian bullseye)
    -
    6 x ESP32/Wemos D1 mini - WLED - SK6812 RGBW-NW 60 LEDs/m
    FeinTech VSP01201 - Grabber Macrosilicon

    LG TV Hyperion webOS & PicCap


    snoozer_likelinux_manvtkns.gif


    Ambilight for ever

  • searching around I found this thread and tried

    /usr/bin/hyperiond -d

    and got the answer

    Code
    2023-01-29T17:32:23.508 |__| MAIN              : <ERROR> The Hyperion Daemon is already running, abort start
    Access the Hyperion User-Interface for configuration and control via:
    http://169.254.190.171:8090
    http://Medienserver.local:8090

    I absolutely do not know from where the machine gets the address 169.254.190.171, but with the name of my raspi

    http://Medienserver.local:8090 I can reach the web interface.... :)


    systemctl status hyperiond@micha.service

    Unit hyperiond@micha.service could not be found.


    I think the Ports are not occupied, Kodi uses port 8080 and tvheadend uses port 9981


    and link file

    /etc/systemd/system/multi-user.target.wants/hyperion@micha.service

    exists and leads to

    /etc/systemd/system/hyperion@.service

    with this content:

    3 Mal editiert, zuletzt von micha53 () aus folgendem Grund: Merged a post created by micha53 into this post.

  • systemctl status hyperion@micha

    systemd service for user %i

    hyperiond is the binary


    Zitat von Post #2 Code
    Code
    Created symlink /etc/systemd/system/multi-user.target.wants/hyperion@micha.service → /etc/systemd/system/hyperion@.service.
    ---> Install Hyperion desktop icons
    --> systemctl start hyperion for user micha


    regards pclin

    Dreambox ONE / TWO

    dreamOS OE2.6

    Amlogic S922X - 53.000 DMIPS - 2 GB RAM - 16 GB Flash - Twin-DVB-S2X Tuner - HDR10 - HLG
    -
    AudioDSP: miniDSP 2x4HD - Amp: Pentagon - Lautsprecher ELAC / ARENDAL
    LG OLED65BX9LB (PicCap, hyperion.NG webOS)

    FireTV 4K max

    -
    hyperion (classic) & Plugin HyperionControl | hyperion-ng 2.0.16-beta.1 (dreamOS)
    Hyperion-ng (Debian bullseye)
    -
    6 x ESP32/Wemos D1 mini - WLED - SK6812 RGBW-NW 60 LEDs/m
    FeinTech VSP01201 - Grabber Macrosilicon

    LG TV Hyperion webOS & PicCap


    snoozer_likelinux_manvtkns.gif


    Ambilight for ever

    • Offizieller Beitrag

    On the 169.254.xxx IP address you might see the explanation here https://www.globalknowledge.co…x-x-ip-address-come-from/


    It is an OS generated one,.

    Anyway it is always better to use names rather than IP addresses, as you just proved…

  • On the 169.254.xxx IP address you might see

    OK, I've read and understand, Thanks



    systemctl status hyperion@micha

    systemd service for user %i

    hyperiond is the binary

    actually I get here

    Code
     systemctl status hyperion@micha
    ● hyperion@micha.service - Hyperion ambient light systemd service  for user micha
         Loaded: loaded (/etc/systemd/system/hyperion@.service; disabled; vendor preset: enabled)
         Active: inactive (dead)
           Docs: https://docs.hyperion-project.org

    still don't know why it is disabled and inactive...

    • Offizieller Beitrag

    Start hyperion from the commandline and see what the output is.

    hyperiond -d


    If it says „already running“ then do a

    pkill hyperiond


    and then start it

  • actually I have it running with wled configuration, this works quite good, still some issues with the light I am just examining


Jetzt mitmachen!

Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!