LoxBerry V4.0.0 PRE-RELEASE

Einklappen
X
 
  • Zeit
  • Anzeigen
Alles löschen
neue Beiträge
  • BlackSoll
    Dumb Home'r
    • 16.09.2022
    • 29

    #31
    I just install latest commit and after a reboot when I hit the ip, the login form appears. I type username & pass and then just white page. SSH works, apache is running, audio server docker is running fine and players from Loxone app works. The loxberry ui is just blank. Eventually the browser goes to 504 gateway timeout. Can I do anything from ssh to restore or reinstall ? Running loxberry at a x86 with latest trixie !
    Zuletzt geändert von BlackSoll; vor 2 Tagen.

    Kommentar


    • BlackSoll
      BlackSoll kommentierte
      Kommentar bearbeiten
      Never mind. Solved it. With systemctl restart loxberry
      systemctl restart apache2 , ui restarted and gave me enough time to go to prerelease 4.0.0.7. Now everything working as expected !😊
  • Prof.Mobilux
    Supermoderator
    • 25.08.2015
    • 5374

    #32
    Latest is for developers only.
    🇺🇦 Hilfe für die Menschen der Ukraine: https://www.loxforum.com/forum/proje...Cr-die-ukraine


    LoxBerry - Beyond the Limits

    Kommentar

    • christian288
      Dumb Home'r
      • 29.12.2015
      • 24

      #33
      Hi,

      I wanted to ask whether it will be possible to install it on Proxmox in the future. According to the guide here:

      https://wiki.loxberry.de/installatio...xberry/proxmox

      this procedure can no longer be used because the DietPi version it relies on is outdated.

      Kommentar


      • Prof.Mobilux
        Prof.Mobilux kommentierte
        Kommentar bearbeiten
        Just use the latest DietPi version. It works on Proxmox.
    • BlackSoll
      Dumb Home'r
      • 16.09.2022
      • 29

      #34
      Mqtt v2 works ok and values are sent normally to ms, in ui the value, ms,sent,time are empty. Is it only in my installation or is not finished yet ? I'm on version 4.0.0.7


      Klicke auf die Grafik für eine vergrößerte Ansicht

Name: Screenshot 2026-06-05 215447.png
Ansichten: 50
Größe: 68,3 KB
ID: 485702

      Kommentar


      • Prof.Mobilux
        Prof.Mobilux kommentierte
        Kommentar bearbeiten
        Is this behaviour also there after a reboot of loxberry and waiting until new data from your devices arrive?

      • BlackSoll
        BlackSoll kommentierte
        Kommentar bearbeiten
        Ok. After 4.0.0.8 works. One more question: When I go to file manager or to Mqtt asks for pin, I type it, hit enter and enters. In plugin installation, I type pin and hit enter nothing happens. I have to manually hit the button.
    • duncan
      LoxBus Spammer
      • 28.08.2015
      • 353

      #35
      i tried an update of a runnning loxberry to 4.0.0.7
      pi4, dietpi 9.11.2, bullseye

      got a couple of errors:

      <INFO> Executing command 'python3 -m venv '/opt/loxberry/system/python_venv/mqttgateway''...
      <ERROR> ERROR executing command - Exitcode 1
      The virtual environment was not created successfully because ensurepip is not
      available. On Debian/Ubuntu systems, you need to install the python3-venv
      package using the following command.

      apt-get install python3-venv

      You may need to use sudo with that command. After installing the python3-venv
      package, recreate your virtual environment.

      Failing command: ['/opt/loxberry/system/python_venv/mqttgateway/bin/python3', '-Im', 'ensurepip', '--upgrade', '--default-pip']

      <INFO> Executing command ''/opt/loxberry/system/python_venv/mqttgateway/bin/pip' install -q aiomqtt aiohttp'...
      <ERROR> ERROR executing command - Exitcode 127

      <INFO> Executing command 'chown -R loxberry:loxberry '/opt/loxberry/system/python_venv/mqttgateway''...
      <OK> Command executed successfully. - Exitcode 0

      <OK> MQTT Gateway venv created.
      <OK> Update script /opt/loxberry/sbin/loxberryupdate/update_v4.0.0.6.pl finished.
      17:55:51.939 <INFO> exec_perl_script /opt/loxberry/sbin/loxberryupdate/update_v4.0.0.6.pl release=v4.0.0.7 logfilename=/opt/loxberry/log/system/loxberryupdate/20260605_175546_413_update.log cron= updatedir=/tmp/loxberryupdate/mschlenstedt-Loxberry-9841038 with user - errcode 0
      17:55:51.942 <OK> Update scripts executed successful.
      17:55:51.942 <INFO> Migrating configuration settings from default config...
      17:55:52.311 <OK> LoxBerry config settings updated successfully.
      17:55:52.311 <INFO> Updating LoxBerry legacy templates...
      17:55:53.123 <OK> LoxBerry legacy template successfully updated.
      17:55:53.124 <INFO> Updating Skels for Logfolders...
      17:55:54.092 <OK> Skels for Logfolders successfully updated.
      17:55:54.093 <INFO> LoxBerry's config version is updated from v3.0.1.3 to v4.0.0.7
      17:55:54.100 <INFO> Cleaning up temporary download folder
      17:55:54.237 <INFO> All procedures finished.
      17:55:54.258 <OK> Loxberry Update WAS SUCCESSFUL!
      <LOGEND> LoxBerry Update processing finished.
      <LOGEND> 05.06.2026 17:55:54 TASK FINISHED

      i dont know whether this is important as everything seems to be working

      Kommentar

    • Tweeet
      Dumb Home'r
      • 01.03.2018
      • 29

      #36
      Pi-Version gemäss 'cat /proc/cpuinfo': Raspberry Pi 3 Model B Rev 1.2.
      Distribution Debian 13 (trixie).
      LB-Version 4.0.0.7

      Backup/Restore funktioniert tip top. Allerdings erhalte ich beim öffnen des Widgets immer eine Fehlermeldung (siehe Anhang).

      'showpitype' ergibt "nopi". Das löst wohl auch die Fehlermeldung aus. Wenn ich das richtig verstehe, erkennt das Script meine CPUs nicht korrekt. Auch bei den LB-System Informationen erhalte ich bei den CUPs 'unknown'.

      Kann ich das bei mir korrigieren oder ist das ein bug?
      Angehängte Dateien

      Kommentar


      • Prof.Mobilux
        Prof.Mobilux kommentierte
        Kommentar bearbeiten
        Das ist ein Bug. Kannst Du mir bitte die komplette Ausgabe von "ls -l /boot/firmware" und "cat /boot/dietpi/.hw_model" schicken. Danke.
    • Tweeet
      Dumb Home'r
      • 01.03.2018
      • 29

      #37
      Vielen Dank für deine rasche Rückmeldung. Anbei die gewünschten Ausgaben.
      Angehängte Dateien

      Kommentar

      • Prof.Mobilux
        Supermoderator
        • 25.08.2015
        • 5374

        #38
        Das ist wirklich interessant - DietPi erkannet den gar nicht als Raspberry. Unser eigenes Skript showpitype ja auch nicht (die Erkennungen hatte ich auch mal irgendwoher "geklaut").

        Code:
        cat /boot/dietpi/.hw_model
        
        root@loxberry11:~# cat /boot/dietpi/.hw_model
        G_HW_MODEL=22
        G_HW_MODEL_NAME='Generic Device (aarch64)'
        G_HW_ARCH=3
        G_HW_ARCH_NAME='aarch64'
        G_HW_CPUID=0
        G_HW_CPU_CORES=4
        G_DISTRO=8
        G_DISTRO_NAME='trixie'
        G_ROOTFS_DEV='/dev/mmcblk0p2'
        G_HW_UUID='b9605029-bdf1-435f-8eef-5cb28740145f'
        Das solltest Du mal mit der Ausgabe von cat /proc/cpuinfo an DietPi als Issue melden: https://github.com/MichaIng/DietPi/issues

        🇺🇦 Hilfe für die Menschen der Ukraine: https://www.loxforum.com/forum/proje...Cr-die-ukraine


        LoxBerry - Beyond the Limits

        Kommentar

        • <Andreas>
          LoxBus Spammer
          • 07.03.2023
          • 431

          #39
          In LoxMqttRealy wurde die Möglichkeit geschaffen User Properties zu verwenden

          vielleicht wäre es ja für das MQTT Gateway V2 auch eine Überlegung wert

          Kommentar


          • Prof.Mobilux
            Prof.Mobilux kommentierte
            Kommentar bearbeiten
            Müsste ich mir anschauen. Wozu braucht man das?
        • duncan
          LoxBus Spammer
          • 28.08.2015
          • 353

          #40
          Zitat von duncan
          i tried an update of a runnning loxberry to 4.0.0.7
          pi4, dietpi 9.11.2, bullseye

          got a couple of errors:

          Executing command 'python3 -m venv '/opt/loxberry/system/python_venv/mqttgateway''...
          ERROR executing command - Exitcode 1
          The virtual environment was not created successfully because ensurepip is not
          available. On Debian/Ubuntu systems, you need to install the python3-venv
          package using the following command.

          apt-get install python3-venv

          You may need to use sudo with that command. After installing the python3-venv
          package, recreate your virtual environment.

          Failing command: ['/opt/loxberry/system/python_venv/mqttgateway/bin/python3', '-Im', 'ensurepip', '--upgrade', '--default-pip']

          Executing command ''/opt/loxberry/system/python_venv/mqttgateway/bin/pip' install -q aiomqtt aiohttp'...
          ERROR executing command - Exitcode 127

          Executing command 'chown -R loxberry:loxberry '/opt/loxberry/system/python_venv/mqttgateway''...
          Command executed successfully. - Exitcode 0

          MQTT Gateway venv created.
          Update script /opt/loxberry/sbin/loxberryupdate/update_v4.0.0.6.pl finished.
          17:55:51.939 exec_perl_script /opt/loxberry/sbin/loxberryupdate/update_v4.0.0.6.pl release=v4.0.0.7 logfilename=/opt/loxberry/log/system/loxberryupdate/20260605_175546_413_update.log cron= updatedir=/tmp/loxberryupdate/mschlenstedt-Loxberry-9841038 with user - errcode 0
          17:55:51.942 Update scripts executed successful.
          17:55:51.942 Migrating configuration settings from default config...
          17:55:52.311 LoxBerry config settings updated successfully.
          17:55:52.311 Updating LoxBerry legacy templates...
          17:55:53.123 LoxBerry legacy template successfully updated.
          17:55:53.124 Updating Skels for Logfolders...
          17:55:54.092 Skels for Logfolders successfully updated.
          17:55:54.093 LoxBerry's config version is updated from v3.0.1.3 to v4.0.0.7
          17:55:54.100 Cleaning up temporary download folder
          17:55:54.237 All procedures finished.
          17:55:54.258 Loxberry Update WAS SUCCESSFUL!
          LoxBerry Update processing finished.
          05.06.2026 17:55:54 TASK FINISHED

          i dont know whether this is important as everything seems to be working
          im not sure if the fix is already in the latest dev - i tried again, same pi4, diepi 9 / bullseye

          E: Failed to fetch https://deb.debian.org/debian-securi...11u3_arm64.deb 404 Not Found [IP: 151.101.2.132 443]
          E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?

          CRITICAL: Error installing python3-venv - Error 100

          INFO: Creating MQTT Gateway venv at /opt/loxberry/system/python_venv/mqttgateway...

          INFO: Executing command 'python3 -m venv '/opt/loxberry/system/python_venv/mqttgateway''...

          ERROR: ERROR executing command - Exitcode 1
          The virtual environment was not created successfully because ensurepip is not
          available. On Debian/Ubuntu systems, you need to install the python3-venv
          package using the following command.

          apt-get install python3-venv

          You may need to use sudo with that command. After installing the python3-venv
          package, recreate your virtual environment.

          Failing command: ['/opt/loxberry/system/python_venv/mqttgateway/bin/python3', '-Im', 'ensurepip', '--upgrade', '--default-pip']


          INFO: Executing command 'chown -R loxberry:loxberry '/opt/loxberry/system/python_venv/mqttgateway''...

          OK: Command executed successfully. - Exitcode 0


          ERROR: Update script /opt/loxberry/sbin/loxberryupdate/update_v4.0.0.6.pl finished with errors.

          16:21:59.513 INFO: exec_perl_script /opt/loxberry/sbin/loxberryupdate/update_v4.0.0.6.pl release=v4.0.0.9 logfilename=/opt/loxberry/log/system/loxberryupdate/20260606_162147_017_update.log cron= updatedir=/tmp/loxberryupdate/Loxberry-master with user - errcode 2

          16:21:59.513 ERROR: Update-Script update_v4.0.0.6 returned errorcode 2. Despite errors loxberryupdate.pl will continue.

          16:21:59.514 INFO: Setting update script update_v4.0.0.6 as failed in general configuration.

          16:21:59.514 INFO: Script version: v4.0.0.8

          16:21:59.514 INFO: Running update script for v4.0.0.8...

          i tried running "apt-get install python3-venv" as root from a telnet session and get a lot of 404 not found errors
          After this operation, 458 kB of additional disk space will be used.
          Do you want to continue? [Y/n] y
          Err:1 https://deb.debian.org/debian-security bullseye-security/main arm64 python 3.9-dev arm64 3.9.2-1+deb11u3
          404 Not Found [IP: 151.101.194.132 443]
          Err:2 https://deb.debian.org/debian-security bullseye-security/main arm64 libpyt hon3.9-dev arm64 3.9.2-1+deb11u3
          404 Not Found [IP: 151.101.194.132 443]
          Err:3 https://deb.debian.org/debian-security bullseye-security/main arm64 libpyt hon3.9 arm64 3.9.2-1+deb11u3
          404 Not Found [IP: 151.101.194.132 443]
          Err:4 https://deb.debian.org/debian-security bullseye-security/main arm64 python 3.9 arm64 3.9.2-1+deb11u3
          404 Not Found [IP: 151.101.194.132 443]
          Err:5 https://deb.debian.org/debian-security bullseye-security/main arm64 libpyt hon3.9-stdlib arm64 3.9.2-1+deb11u3
          404 Not Found [IP: 151.101.194.132 443]
          Err:6 https://deb.debian.org/debian-security bullseye-security/main arm64 python 3.9-minimal arm64 3.9.2-1+deb11u3
          404 Not Found [IP: 151.101.194.132 443]
          Err:7 https://deb.debian.org/debian-security bullseye-security/main arm64 libpyt hon3.9-minimal arm64 3.9.2-1+deb11u3
          404 Not Found [IP: 151.101.194.132 443]
          Err:8 https://deb.debian.org/debian-security bullseye-security/main arm64 python 3.9-venv arm64 3.9.2-1+deb11u3
          404 Not Found [IP: 151.101.194.132 443]
          E: Failed to fetch https://deb.debian.org/debian-securi...ates/main/p/py thon3.9/python3.9-dev_3.9.2-1%2bdeb11u3_arm64.deb 404 Not Found [IP: 151.101.1 94.132 443]
          E: Failed to fetch https://deb.debian.org/debian-securi...ates/main/p/py thon3.9/libpython3.9-dev_3.9.2-1%2bdeb11u3_arm64.deb 404 Not Found [IP: 151.10 1.194.132 443]
          E: Failed to fetch https://deb.debian.org/debian-securi...ates/main/p/py thon3.9/libpython3.9_3.9.2-1%2bdeb11u3_arm64.deb 404 Not Found [IP: 151.101.19 4.132 443]
          E: Failed to fetch https://deb.debian.org/debian-securi...ates/main/p/py thon3.9/python3.9_3.9.2-1%2bdeb11u3_arm64.deb 404 Not Found [IP: 151.101.194.1 32 443]
          E: Failed to fetch https://deb.debian.org/debian-securi...ates/main/p/py thon3.9/libpython3.9-stdlib_3.9.2-1%2bdeb11u3_arm64.deb 404 Not Found [IP: 151 .101.194.132 443]
          E: Failed to fetch https://deb.debian.org/debian-securi...ates/main/p/py thon3.9/python3.9-minimal_3.9.2-1%2bdeb11u3_arm64.deb 404 Not Found [IP: 151.1 01.194.132 443]
          E: Failed to fetch https://deb.debian.org/debian-securi...ates/main/p/py thon3.9/libpython3.9-minimal_3.9.2-1%2bdeb11u3_arm64.deb 404 Not Found [IP: 15 1.101.194.132 443]
          E: Failed to fetch https://deb.debian.org/debian-securi...ates/main/p/py thon3.9/python3.9-venv_3.9.2-1%2bdeb11u3_arm64.deb 404 Not Found [IP: 151.101. 194.132 443]
          E: Unable to fetch some archives, maybe run apt-get update or try with --fix-mis sing?
          Zuletzt geändert von duncan; vor 2 Stunden.

          Kommentar

          • duncan
            LoxBus Spammer
            • 28.08.2015
            • 353

            #41
            after a bit of reading it seems the following is necessary on this older version of dietpi

            After adding deb http://security.ubuntu.com/ubuntu focal-security main universe in /etc/apt/sources.list,
            run apt update

            then the 4.0.0.9 update script rins without errors

            Kommentar

            Lädt...