Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. ioBroker Allgemein
    4. Yahka Adapter in iobroker im Docker Container

    NEWS

    • Neuer Blog: Fotos und Eindrücke aus Solingen

    • ioBroker@Smart Living Forum Solingen, 14.06. - Agenda added

    • ioBroker goes Matter ... Matter Adapter in Stable

    Yahka Adapter in iobroker im Docker Container

    This topic has been deleted. Only users with topic management privileges can see it.
    • T
      Tomme @Glasfaser last edited by

      @glasfaser sagte in Yahka Adapter in iobroker im Docker Container:

      Schau mal auf der PI wer Besitzer deines Ordners

      opt/iobroker

      ist und ob dort etwas vorhanden ist .

      ja ist da und voll wie bei stand alone installation und besitzer ist pi

      @dockerpi:/opt $ ls -l
      insgesamt 16
      drwx--x--x 4 root root 4096  6. Mai 11:05 containerd
      drwxrwxr-x 8 pi   pi   4096  7. Mai 15:20 iobroker
      drwxr-xr-x 3 root root 4096  3. Mai 05:00 pigpio
      drwxr-xr-x 3 root root 4096  3. Mai 04:58 WidevineCdm
      pi@dockerpi:/opt $
      
      
      Glasfaser 1 Reply Last reply Reply Quote 0
      • Glasfaser
        Glasfaser @Tomme last edited by

        @tomme sagte in Yahka Adapter in iobroker im Docker Container:

        und besitzer ist pi

        und das ist dann falsch , deshalb hast du damit Probleme !

        aber @ThomasK1966 kann dir bestimmt mehr dazu schreiben , denn ich habe keine Pi
        und er hat dir den Ordner dazu vorgeschlagen .

        T 1 Reply Last reply Reply Quote 0
        • T
          Tomme @Glasfaser last edited by Tomme

          @glasfaser achso müsste iobroker stehen?

          kann sein das ich den gestern irgendwann zwischendurch mal selbst angelegt hatte aber eigentlich hatte ich den auch wieder gelöscht ...
          das kann ich aber glaube mit chown ... überschreiben muss ich mal nachschauen

          T 1 Reply Last reply Reply Quote 0
          • T
            ThomasK1966 @Tomme last edited by

            @tomme
            Bei mir gehört der Ordner dem User „iobroker“. Das ist der Standarduser mit dem eine ioBroker-Installation läuft. Da lokal auch schon eine ioBroker-Installation gelaufen ist, gibt es diesen User auch im Host-System.

            Ich weiß aber nicht, ob das wirklich das Problem ist. Schreiben kann der ioBroker ja in dem Ordner. Sonst gäbe es ganz andere Probleme.

            Gruß Thomas

            T 1 Reply Last reply Reply Quote 0
            • T
              Tomme @ThomasK1966 last edited by

              @thomask1966
              ja kann ich trozdem ordentlich machen ... wenn mal thomasbraun drauf guckt kriege ich gleich wieder ne ansage 😄 das ist ja ne "kleinigkeit"

              T 1 Reply Last reply Reply Quote 0
              • T
                Tomme @Tomme last edited by Tomme

                @ThomasK1966

                oder doch nicht ...

                pi@dockerpi:/opt $ chown -v -R iobroker:iobroker /opt/iobroker
                chown: ungültiger Benutzer: „iobroker:iobroker“
                pi@dockerpi:/opt $ 
                

                mit sudo geht es auch nicht

                aber ich kann doch nochmal den container raus werfen und den ordner löschen und dann mit dem stack im portainer wieder anlegen oder? wird der dann neu erstellt?
                ich hatte meinen neu aufgesetzt vorher daher hab ich den user bestimmt nicht oder?

                T 2 Replies Last reply Reply Quote 0
                • T
                  ThomasK1966 @Tomme last edited by

                  @tomme

                  Ja, der Ordner würde neu angelegt werden.
                  Allerdings fängst Du dann quasi noch mal von vorne an, einschließlich dem Einspielen der Backups etc,
                  Du könntest den Ordner auch einfach mal umbenennen und dann mit einem leeren neu anfangen. Vorher aber den Container stoppen.
                  Dann siehst Du, mit welchem User der neue Ordner angelegt wird auf Deinem System.
                  Danach dann den alten Ordner entsprechend anpassen und wieder zurück umbenennen.

                  Ich kann aber keine Garantie geben, dass das funktioniert. Habe ich selber auch noch nicht gemacht und ist halt ein bisschen gefummel.

                  Gruß Thomas

                  T 1 Reply Last reply Reply Quote 0
                  • T
                    ThomasK1966 @Tomme last edited by

                    @tomme
                    Ich habe gerade zum Thema User noch etwas in der Image-Beschreibung gelesen:

                    IMG_0030.jpeg

                    Daraus entnehme ich, dass der Container mit dem User „iobroker“ läuft. Dazu muss dieser auf dem Host die SETUID = 1000 haben.

                    Hast Du einen User „iobroker“ auf Deinem Host und welche SETUID hat der?

                    Gruß Thomas

                    T 1 Reply Last reply Reply Quote 0
                    • T
                      Tomme @ThomasK1966 last edited by

                      @thomask1966 kein ding zur not mache ich das neu einprägen kommt von wiederholen ... ich probiere es vorher mit dem container

                      1 Reply Last reply Reply Quote 0
                      • T
                        Tomme @ThomasK1966 last edited by

                        @thomask1966 sagte in Yahka Adapter in iobroker im Docker Container:

                        Du einen User „iobroker“ auf Deinem Host und welche SETUID hat der?

                        öhm ich weiß nicht

                        T 1 Reply Last reply Reply Quote 0
                        • T
                          ThomasK1966 @Tomme last edited by

                          @tomme
                          Auf die Schnelle habe ich diese Seite gefunden. Da steht wie man das über die Konsole rausbekommt:
                          https://www.giga.de/downloads/linux-mint/tipps/linux-gruppen-und-benutzer-anzeigen-so-gehts/#:~:text=So zeigt ihr Gruppen und,jeweils%2C welche Benutzer drin stecken.

                          Gruß Thomas

                          T 1 Reply Last reply Reply Quote 0
                          • T
                            Tomme @ThomasK1966 last edited by Tomme

                            @thomask1966

                            pi@dockerpi:/ $ cut -d: -f1 /etc/passwd
                            root
                            daemon
                            bin
                            sys
                            sync
                            games
                            man
                            lp
                            mail
                            news
                            uucp
                            proxy
                            www-data
                            backup
                            list
                            irc
                            gnats
                            nobody
                            _apt
                            systemd-network
                            systemd-resolve
                            pi
                            systemd-timesync
                            messagebus
                            _rpc
                            sshd
                            statd
                            avahi
                            dnsmasq
                            lightdm
                            rtkit
                            pulse
                            saned
                            colord
                            hplip
                            systemd-coredump
                            pi@dockerpi:/ $
                            
                            pi@dockerpi:/ $ sudo cat /etc/shadow
                            root:*:19480:0:99999:7:::
                            daemon:*:19480:0:99999:7:::
                            bin:*:19480:0:99999:7:::
                            sys:*:19480:0:99999:7:::
                            sync:*:19480:0:99999:7:::
                            games:*:19480:0:99999:7:::
                            man:*:19480:0:99999:7:::
                            lp:*:19480:0:99999:7:::
                            mail:*:19480:0:99999:7:::
                            news:*:19480:0:99999:7:::
                            uucp:*:19480:0:99999:7:::
                            proxy:*:19480:0:99999:7:::
                            www-data:*:19480:0:99999:7:::
                            backup:*:19480:0:99999:7:::
                            list:*:19480:0:99999:7:::
                            irc:*:19480:0:99999:7:::
                            gnats:*:19480:0:99999:7:::
                            nobody:*:19480:0:99999:7:::
                            _apt:*:19480:0:99999:7:::
                            systemd-network:*:19480:0:99999:7:::
                            systemd-resolve:*:19480:0:99999:7:::
                            pi:$5$M4L2UEJ8O5$nu8APjrF6ue1ruNoyO1uMwq9KopuBv4z4QWiiyftHL3:19480:0:99999:7:::
                            systemd-timesync:*:19480:0:99999:7:::
                            messagebus:*:19480:0:99999:7:::
                            _rpc:*:19480:0:99999:7:::
                            sshd:*:19480:0:99999:7:::
                            statd:*:19480:0:99999:7:::
                            avahi:*:19480:0:99999:7:::
                            dnsmasq:*:19480:0:99999:7:::
                            lightdm:*:19480:0:99999:7:::
                            rtkit:*:19480:0:99999:7:::
                            pulse:*:19480:0:99999:7:::
                            saned:*:19480:0:99999:7:::
                            colord:*:19480:0:99999:7:::
                            hplip:*:19480:0:99999:7:::
                            systemd-coredump:!*:19480::::::
                            pi@dockerpi:/ $
                            
                            

                            also kein user da ... die frage ist ob er den user nicht hätte anlegen müssen wenn man den bräuchte? abgesehen davon wer jetzt den Ordner lokal angelegt hat
                            ist schon erschreckend wieviele user da überhaupt drauf sind bei der "nackigen" installation

                            T Thomas Braun 2 Replies Last reply Reply Quote 0
                            • T
                              ThomasK1966 @Tomme last edited by

                              @tomme
                              Hmm, nach dem was in der Image-Beschreibung steht nutzt der Container standardmäßig die UID 1000.
                              Das wäre bei Dir sehr wahrscheinlich der User „pi“. Der wird ja bei einer Neuinstallation automatisch als erster User angelegt.
                              Ob das für ioBroker ein Problem ist, dass der User nicht „iobroker“ heißt, weiß ich nicht.
                              Der Ordner und alle Unterordner und Dateien in /opt/iobroker sollten in Deinem Fall dem User „pi“ und der entsprechenden Gruppe zugeordnet sein.

                              Gruß Thomas

                              T 1 Reply Last reply Reply Quote 0
                              • T
                                Tomme @ThomasK1966 last edited by

                                @thomask1966
                                ich denke mal im container wird das schon stimmig sein der ist ja frisch erstellt ist halt nur der gemappte ordner im lokalen pfad ... bisher sehe ich da nix was fehler schmeisst außer node-red ... das startet nicht zuverlässig ich weiß nicht ob das auch an der homebridge geschichte liegt ...

                                der iobroker startet ordentlich die warnungen von lg kann man übersehen der adapter meckert wie ein rohrspatz aber die daten sind da und das war auch so bei der stand alone installation
                                unten drunter sind die fehler von node-red die jedes mal auftreten wenn ich versuche das web ui zu öffnen und er bleibt dann da iwo stehen beim einlesen des Flows

                                2023-05-07 15:21:29.638 - info: host.iobroker iobroker.js-controller version 4.0.24 js-controller starting
                                2023-05-07 15:21:29.644 - info: host.iobroker Copyright (c) 2014-2022 bluefox, 2014 hobbyquaker
                                2023-05-07 15:21:29.645 - info: host.iobroker hostname: iobroker, node: v18.16.0
                                2023-05-07 15:21:29.646 - info: host.iobroker ip addresses: 192.168.7.39 2a01:598:b1ae:5fa:cda9:f7e8:4f52:b0ae fe80::d1ed:ac40:eb70:1818 172.17.0.1 fe80::42:ff:fea8:f9dc 169.254.109.96 fe80::dc28:b3ff:fe26:53e2 169.254.233.119 fe80::6111:bcc0:a1c7:a2b1 169.254.246.52 fe80::88ee:4aff:fed1:1f0e
                                2023-05-07 15:21:31.814 - info: host.iobroker connected to Objects and States
                                2023-05-07 15:21:31.902 - info: host.iobroker added notifications configuration of host
                                2023-05-07 15:21:32.697 - info: host.iobroker Delete state "system.host.iobroker.versions.nodeCurrent"
                                2023-05-07 15:21:32.700 - info: host.iobroker 53 instances found
                                2023-05-07 15:21:32.771 - info: host.iobroker starting 43 instances
                                2023-05-07 15:21:32.784 - warn: host.iobroker startInstance cannot find adapter "yahka@0.17.0". Try to install it... 1 attempt
                                2023-05-07 15:21:32.785 - info: host.iobroker iobroker install yahka@0.17.0 using installedFrom
                                2023-05-07 15:21:32.967 - info: host.iobroker Delete state "system.host.iobroker.versions.nodeNewest"
                                2023-05-07 15:21:33.009 - info: host.iobroker instance system.adapter.admin.0 started with pid 175
                                2023-05-07 15:21:33.031 - info: host.iobroker Delete state "system.host.iobroker.versions.nodeNewestNext"
                                2023-05-07 15:21:33.054 - info: host.iobroker Delete state "system.host.iobroker.versions.npmCurrent"
                                2023-05-07 15:21:33.120 - info: host.iobroker Delete state "system.host.iobroker.versions.npmNewest"
                                2023-05-07 15:21:33.139 - info: host.iobroker Delete state "system.host.iobroker.versions.npmNewestNext"
                                2023-05-07 15:21:33.157 - info: host.iobroker Some obsolete host states deleted.
                                2023-05-07 15:21:36.478 - info: admin.0 (175) starting. Version 6.3.5 in /opt/iobroker/node_modules/iobroker.admin, node: v18.16.0, js-controller: 4.0.24
                                2023-05-07 15:21:36.549 - info: admin.0 (175) requesting all states
                                2023-05-07 15:21:36.550 - info: admin.0 (175) requesting all objects
                                2023-05-07 15:21:37.118 - info: host.iobroker instance system.adapter.influxdb.0 started with pid 198
                                2023-05-07 15:21:38.449 - info: host.iobroker iobroker npm-install: NPM version: 9.5.1Installing iobroker.yahka@0.17.0... (System call)
                                2023-05-07 15:21:39.336 - info: admin.0 (175) received all objects
                                2023-05-07 15:21:39.880 - info: admin.0 (175) Request actual repository...
                                2023-05-07 15:21:39.920 - info: admin.0 (175) http server listening on port 8081
                                2023-05-07 15:21:39.921 - info: admin.0 (175) Use link "http://localhost:8081" to configure.
                                2023-05-07 15:21:39.937 - info: admin.0 (175) socket.io server listening on port 8081
                                2023-05-07 15:21:40.529 - info: host.iobroker Updating repository "stable" under "http://download.iobroker.net/sources-dist.json"
                                2023-05-07 15:21:41.021 - info: host.iobroker instance system.adapter.javascript.0 started with pid 252
                                2023-05-07 15:21:42.442 - info: influxdb.0 (198) starting. Version 3.2.0 in /opt/iobroker/node_modules/iobroker.influxdb, node: v18.16.0, js-controller: 4.0.24
                                2023-05-07 15:21:42.538 - info: influxdb.0 (198) No stored data from last exit found
                                2023-05-07 15:21:42.541 - info: influxdb.0 (198) Connecting http://localhost:8086/ ...
                                2023-05-07 15:21:42.544 - info: influxdb.0 (198) Influx DB Version used: 2.x
                                2023-05-07 15:21:42.696 - info: influxdb.0 (198) Applying retention policy for iobroker to 31536000 seconds. Shard Group Duration (calculated): 604800 seconds
                                2023-05-07 15:21:42.798 - info: influxdb.0 (198) Connected!
                                2023-05-07 15:21:42.904 - info: admin.0 (175) ==> Connected system.user.admin from ::ffff:192.168.7.1
                                2023-05-07 15:21:43.842 - info: admin.0 (175) Repository received successfully.
                                2023-05-07 15:21:45.409 - info: host.iobroker instance system.adapter.node-red.0 started with pid 263
                                2023-05-07 15:21:47.828 - info: javascript.0 (252) starting. Version 6.1.4 in /opt/iobroker/node_modules/iobroker.javascript, node: v18.16.0, js-controller: 4.0.24
                                2023-05-07 15:21:49.249 - info: host.iobroker instance system.adapter.telegram.0 started with pid 282
                                2023-05-07 15:21:49.845 - info: node-red.0 (263) starting. Version 4.0.0 in /opt/iobroker/node_modules/iobroker.node-red, node: v18.16.0, js-controller: 4.0.24
                                2023-05-07 15:21:51.375 - info: javascript.0 (252) requesting all states
                                2023-05-07 15:21:51.377 - info: javascript.0 (252) requesting all objects
                                2023-05-07 15:21:54.644 - info: node-red.0 (263) Starting node-red: --max-old-space-size=128 /opt/iobroker/node_modules/node-red/red.js -v --settings /opt/iobroker/iobroker-data/node-red/settings.js
                                2023-05-07 15:21:55.062 - info: host.iobroker instance system.adapter.whatsapp-cmb.0 started with pid 328
                                2023-05-07 15:21:55.205 - info: javascript.0 (252) received all objects
                                2023-05-07 15:21:55.590 - info: javascript.0 (252) received all states
                                2023-05-07 15:21:55.881 - info: javascript.0 (252) Start javascript script.js.Blockly
                                2023-05-07 15:21:55.991 - info: javascript.0 (252) script.js.Blockly: registered 3 subscriptions, 0 schedules, 0 messages, 0 logs and 0 file subscriptions
                                2023-05-07 15:21:57.014 - info: host.iobroker instance scheduled system.adapter.ical.0 0,30 * * * *
                                2023-05-07 15:21:57.096 - info: host.iobroker instance system.adapter.ical.0 started with pid 335
                                2023-05-07 15:21:57.165 - info: telegram.0 (282) starting. Version 1.15.2 in /opt/iobroker/node_modules/iobroker.telegram, node: v18.16.0, js-controller: 4.0.24
                                2023-05-07 15:22:01.032 - info: host.iobroker instance system.adapter.loxone.0 started with pid 369
                                2023-05-07 15:22:01.504 - info: whatsapp-cmb.0 (328) starting. Version 0.2.3 in /opt/iobroker/node_modules/iobroker.whatsapp-cmb, node: v18.16.0, js-controller: 4.0.24
                                2023-05-07 15:22:02.406 - info: ical.0 (335) starting. Version 1.13.2 in /opt/iobroker/node_modules/iobroker.ical, node: v18.16.0, js-controller: 4.0.24
                                2023-05-07 15:22:03.770 - info: ical.0 (335) processing URL: AbfallPM https://apm.wastebox.gemos-management.de/Gemos/WasteBox/Frontend/TourSchedule/Raw/Name/2023/year/155989/1427,1429,1431,1433,1434,1435,1436,1437/180/Print/ics/Default/Abfuhrtermine.ics
                                2023-05-07 15:22:04.856 - error: host.iobroker iobroker npm-install: host.iobroker Cannot install iobroker.yahka@0.17.0: 1
                                2023-05-07 15:22:05.058 - info: host.iobroker instance system.adapter.ping.0 started with pid 388
                                2023-05-07 15:22:05.863 - info: loxone.0 (369) starting. Version 3.0.1 in /opt/iobroker/node_modules/iobroker.loxone, node: v18.16.0, js-controller: 4.0.24
                                2023-05-07 15:22:05.985 - info: host.iobroker iobroker npm-install: exit 25
                                2023-05-07 15:22:06.508 - warn: node-red.0 (263) 7 May 15:22:06 - [warn] [RED.events] Deprecated use of "nodes-started" event from "/opt/iobroker/iobroker-data/node-red/node_modules/connect-nodes/ipc/ipc.js:66:20". Use "flows:started" instead.
                                2023-05-07 15:22:06.512 - warn: node-red.0 (263) 7 May 15:22:06 - [warn] [RED.events] Deprecated use of "nodes-stopped" event from "/opt/iobroker/iobroker-data/node-red/node_modules/connect-nodes/ipc/ipc.js:67:20". Use "flows:stopped" instead.
                                2023-05-07 15:22:07.072 - warn: host.iobroker startInstance cannot find adapter "yahka@0.17.0". Try to install it... 2 attempt
                                2023-05-07 15:22:07.073 - info: host.iobroker iobroker install yahka@0.17.0 using installedFrom
                                2023-05-07 15:22:07.292 - info: loxone.0 (369) Trying to connect
                                2023-05-07 15:22:07.499 - warn: node-red.0 (263) 7 May 15:22:07 - [warn] [RED.events] Deprecated use of "nodes-started" event from "/opt/iobroker/iobroker-data/node-red/node_modules/connect-nodes/nodes/connect-system/connect-system.js:17:16". Use "flows:started" instead.
                                2023-05-07 15:22:08.241 - info: loxone.0 (369) got structure file; last modified on 2023-05-02 15:35:08
                                2023-05-07 15:22:08.741 - info: loxone.0 (369) Unsupported device control AudioZoneV2
                                2023-05-07 15:22:09.054 - info: host.iobroker instance system.adapter.rpi2.0 started with pid 423
                                2023-05-07 15:22:09.115 - info: ical.0 (335) Terminated (NO_ERROR): Without reason
                                2023-05-07 15:22:09.372 - info: ping.0 (388) starting. Version 1.5.3 in /opt/iobroker/node_modules/iobroker.ping, node: v18.16.0, js-controller: 4.0.24
                                2023-05-07 15:22:10.042 - info: host.iobroker instance system.adapter.ical.0 terminated with code 0 (NO_ERROR)
                                2023-05-07 15:22:10.382 - warn: node-red.0 (263) 7 May 15:22:10 - [warn] Projekte deaktiviert: editorTheme.projects.enabled=false
                                2023-05-07 15:22:12.950 - info: host.iobroker instance system.adapter.samsung.0 started with pid 456
                                2023-05-07 15:22:13.315 - info: rpi2.0 (423) starting. Version 1.3.2 in /opt/iobroker/node_modules/iobroker.rpi2, node: v18.16.0, js-controller: 4.0.24
                                2023-05-07 15:22:14.825 - info: host.iobroker iobroker npm-install: NPM version: 9.5.1
                                2023-05-07 15:22:14.831 - info: host.iobroker iobroker npm-install: Installing iobroker.yahka@0.17.0... (System call)
                                2023-05-07 15:22:15.991 - info: loxone.0 (369) Unsupported device control IntercomV2
                                2023-05-07 15:22:16.367 - info: loxone.0 (369) Unsupported device control NfcCodeTouch
                                2023-05-07 15:22:16.938 - info: host.iobroker instance scheduled system.adapter.weatherunderground.0 9 * * * *
                                2023-05-07 15:22:16.990 - info: host.iobroker instance system.adapter.weatherunderground.0 started with pid 510
                                2023-05-07 15:22:17.386 - info: loxone.0 (369) Unsupported device control AudioZoneV2
                                2023-05-07 15:22:19.912 - info: samsung.0 (456) starting. Version 0.5.11 in /opt/iobroker/node_modules/iobroker.samsung, node: v18.16.0, js-controller: 4.0.24
                                2023-05-07 15:22:20.964 - info: host.iobroker instance scheduled system.adapter.weatherunderground.1 33 * * * *
                                2023-05-07 15:22:21.015 - info: host.iobroker instance system.adapter.weatherunderground.1 started with pid 534
                                2023-05-07 15:22:22.744 - info: weatherunderground.0 (510) starting. Version 3.4.2 in /opt/iobroker/node_modules/iobroker.weatherunderground, node: v18.16.0, js-controller: 4.0.24
                                2023-05-07 15:22:23.526 - info: loxone.0 (369) Unsupported device control Irrigation
                                2023-05-07 15:22:24.979 - info: host.iobroker instance system.adapter.discovery.0 started with pid 561
                                2023-05-07 15:22:26.200 - info: weatherunderground.1 (534) starting. Version 3.4.2 in /opt/iobroker/node_modules/iobroker.weatherunderground, node: v18.16.0, js-controller: 4.0.24
                                2023-05-07 15:22:27.306 - info: loxone.0 (369) Unsupported device control Heatmixer
                                2023-05-07 15:22:27.422 - info: loxone.0 (369) Unsupported device control Sequential
                                2023-05-07 15:22:27.930 - info: loxone.0 (369) Unsupported device control PulseAt
                                2023-05-07 15:22:28.987 - info: host.iobroker instance system.adapter.backitup.0 started with pid 576
                                2023-05-07 15:22:29.233 - info: loxone.0 (369) Unsupported device control SteakThermo
                                2023-05-07 15:22:30.395 - info: discovery.0 (561) starting. Version 3.1.0 in /opt/iobroker/node_modules/iobroker.discovery, node: v18.16.0, js-controller: 4.0.24
                                2023-05-07 15:22:31.919 - info: loxone.0 (369) Unsupported device control AudioZoneV2
                                2023-05-07 15:22:33.097 - info: host.iobroker instance system.adapter.alarm.0 started with pid 591
                                2023-05-07 15:22:33.918 - info: loxone.0 (369) Unsupported device control LightsceneRGB
                                2023-05-07 15:22:34.500 - info: backitup.0 (576) starting. Version 2.6.19 in /opt/iobroker/node_modules/iobroker.backitup, node: v18.16.0, js-controller: 4.0.24
                                2023-05-07 15:22:34.859 - info: backitup.0 (576) [iobroker] backup will be activated at 02:40 every 7 day(s)
                                2023-05-07 15:22:36.654 - info: loxone.0 (369) Unsupported device control Ventilation
                                2023-05-07 15:22:36.874 - error: backitup.0 (576) Error: Command failed: sudo mount -t cifs -o username=Tomme,password=****,rw,uid=iobroker,gid=iobroker,file_mode=0777,dir_mode=0777 //192.168.7.1/BackItUp/ /opt/iobroker/backups
                                sudo: /etc/sudo.conf is world writable
                                sudo: /usr/bin/sudo must be owned by uid 0 and have the setuid bit set
                                2023-05-07 15:22:36.932 - info: host.iobroker instance scheduled system.adapter.awattar.0 0 15 * * *
                                2023-05-07 15:22:38.538 - info: loxone.0 (369) Unsupported device control AudioZoneV2
                                2023-05-07 15:22:39.616 - info: alarm.0 (591) starting. Version 3.3.11 in /opt/iobroker/node_modules/iobroker.alarm, node: v18.16.0, js-controller: 4.0.24
                                2023-05-07 15:22:39.646 - info: loxone.0 (369) Unsupported device control LightsceneRGB
                                2023-05-07 15:22:39.922 - info: loxone.0 (369) Unsupported device control SteakThermo
                                2023-05-07 15:22:40.268 - info: loxone.0 (369) Unsupported device control AudioZoneV2
                                2023-05-07 15:22:40.712 - error: host.iobroker iobroker npm-install: host.iobroker Cannot install iobroker.yahka@0.17.0: 1
                                2023-05-07 15:22:40.864 - info: host.iobroker instance scheduled system.adapter.birthdays.0 0 0 * * *
                                2023-05-07 15:22:40.911 - info: host.iobroker instance system.adapter.birthdays.0 started with pid 626
                                2023-05-07 15:22:41.777 - info: host.iobroker iobroker npm-install: exit 25
                                2023-05-07 15:22:42.740 - info: loxone.0 (369) Unsupported device control Heatmixer
                                2023-05-07 15:22:42.778 - warn: host.iobroker startInstance cannot find adapter "yahka@0.17.0". Try to install it... 3 attempt
                                2023-05-07 15:22:42.778 - info: host.iobroker iobroker install yahka@0.17.0 using installedVersion
                                2023-05-07 15:22:42.882 - info: loxone.0 (369) Unsupported device control Ventilation
                                2023-05-07 15:22:44.952 - info: host.iobroker instance system.adapter.bmw.0 started with pid 644
                                2023-05-07 15:22:45.322 - info: birthdays.0 (626) starting. Version 2.2.0 in /opt/iobroker/node_modules/iobroker.birthdays, node: v18.16.0, js-controller: 4.0.24
                                2023-05-07 15:22:45.627 - error: birthdays.0 (626) No birthdays found in any configured source - please check configuration and retry
                                2023-05-07 15:22:45.790 - info: birthdays.0 (626) Terminated (NO_ERROR): Without reason
                                2023-05-07 15:22:46.015 - info: weatherunderground.1 (534) WUnderground API returned 204, no data available. The configured station might be offline
                                2023-05-07 15:22:46.450 - info: host.iobroker instance system.adapter.birthdays.0 terminated with code 0 (NO_ERROR)
                                2023-05-07 15:22:46.594 - error: weatherunderground.1 (534) No current observation data found in response
                                2023-05-07 15:22:47.821 - info: loxone.0 (369) Unsupported device control Heatmixer
                                2023-05-07 15:22:49.052 - info: host.iobroker instance system.adapter.cloud.0 started with pid 667
                                2023-05-07 15:22:49.845 - info: host.iobroker iobroker npm-install: NPM version: 9.5.1Installing iobroker.yahka@0.17.0... (System call)
                                2023-05-07 15:22:50.144 - info: bmw.0 (644) starting. Version 2.5.7 in /opt/iobroker/node_modules/iobroker.bmw, node: v18.16.0, js-controller: 4.0.24
                                2023-05-07 15:22:51.665 - info: loxone.0 (369) Unsupported device control Webpage
                                2023-05-07 15:22:51.936 - info: bmw.0 (644) Start getting bmw vehicles
                                2023-05-07 15:22:52.721 - info: loxone.0 (369) Unsupported device control PulseAt
                                2023-05-07 15:22:52.928 - info: host.iobroker instance scheduled system.adapter.daswetter.0 */15 * * * *
                                2023-05-07 15:22:52.980 - info: host.iobroker instance system.adapter.daswetter.0 started with pid 701
                                2023-05-07 15:22:53.364 - info: bmw.0 (644) Found 1 bmw vehicles
                                2023-05-07 15:22:55.556 - info: cloud.0 (667) starting. Version 4.3.0 in /opt/iobroker/node_modules/iobroker.cloud, node: v18.16.0, js-controller: 4.0.24
                                2023-05-07 15:22:56.793 - info: cloud.0 (667) Connecting with https://iobroker.net:10555 with "tommede@t-online.de_9ebe9420-d07e-11ed-90e5-93e0bcbc3923"
                                2023-05-07 15:22:56.955 - info: host.iobroker instance scheduled system.adapter.dwd.0 */5 * * * *
                                2023-05-07 15:22:57.034 - info: host.iobroker instance system.adapter.dwd.0 started with pid 728
                                2023-05-07 15:22:57.281 - info: cloud.0 (667) Trying to connect as system.user.admin to cloud
                                2023-05-07 15:22:57.642 - info: cloud.0 (667) Adapter redirected temporally to "https://iobroker.net:10556" in one minute. Reason: command from server
                                2023-05-07 15:22:57.650 - info: cloud.0 (667) Connection changed: disconnect
                                2023-05-07 15:22:59.025 - info: loxone.0 (369) Unsupported device control EFM
                                2023-05-07 15:22:59.753 - info: loxone.0 (369) Unsupported device control EnergyManager2
                                2023-05-07 15:22:59.830 - info: daswetter.0 (701) starting. Version 3.1.8 in /opt/iobroker/node_modules/iobroker.daswetter, node: v18.16.0, js-controller: 4.0.24
                                2023-05-07 15:23:00.973 - info: host.iobroker instance system.adapter.fahrplan.0 started with pid 739
                                2023-05-07 15:23:01.371 - info: loxone.0 (369) Unsupported device control LoadManager
                                2023-05-07 15:23:01.904 - info: weatherunderground.0 (510) WUnderground API returned 204, no data available. The configured station might be offline
                                2023-05-07 15:23:02.524 - error: weatherunderground.0 (510) No current observation data found in response
                                2023-05-07 15:23:04.833 - info: host.iobroker instance scheduled system.adapter.feiertage.0 0 0 * * *
                                2023-05-07 15:23:04.955 - info: host.iobroker instance system.adapter.feiertage.0 started with pid 750
                                2023-05-07 15:23:05.944 - info: dwd.0 (728) starting. Version 2.8.3 in /opt/iobroker/node_modules/iobroker.dwd, node: v18.16.0, js-controller: 4.0.24
                                2023-05-07 15:23:07.382 - info: daswetter.0 (701) Terminated (ADAPTER_REQUESTED_TERMINATION): All data handled, adapter stopped until next scheduled moment
                                2023-05-07 15:23:07.948 - info: daswetter.0 (701) cleaned everything up...
                                2023-05-07 15:23:08.115 - info: host.iobroker instance system.adapter.daswetter.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
                                2023-05-07 15:23:09.050 - info: host.iobroker instance system.adapter.homeconnect.0 started with pid 765
                                2023-05-07 15:23:10.291 - info: fahrplan.0 (739) starting. Version 1.2.3 in /opt/iobroker/node_modules/iobroker.fahrplan, node: v18.16.0, js-controller: 4.0.24
                                2023-05-07 15:23:10.373 - info: dwd.0 (728) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
                                2023-05-07 15:23:10.441 - info: fahrplan.0 (739) Adapter started, Updates every 5 minutes
                                2023-05-07 15:23:11.142 - info: host.iobroker instance system.adapter.dwd.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
                                2023-05-07 15:23:11.756 - info: feiertage.0 (750) starting. Version 1.1.0 in /opt/iobroker/node_modules/iobroker.feiertage, node: v18.16.0, js-controller: 4.0.24
                                2023-05-07 15:23:12.500 - info: feiertage.0 (750) Next holiday: Tag der Befreiung (neue Bundesländer) is in 1 days on 08.05.2023
                                2023-05-07 15:23:12.621 - info: feiertage.0 (750) adapter feiertage objects written
                                2023-05-07 15:23:12.693 - info: loxone.0 (369) Unsupported device control ClimateControllerUS
                                2023-05-07 15:23:12.963 - info: weatherunderground.1 (534) Terminated (NO_ERROR): Without reason
                                2023-05-07 15:23:13.011 - info: host.iobroker instance system.adapter.homekit-controller.0 started with pid 802
                                2023-05-07 15:23:13.195 - info: feiertage.0 (750) Terminated (NO_ERROR): Without reason
                                2023-05-07 15:23:13.755 - info: host.iobroker instance system.adapter.weatherunderground.1 terminated with code 0 (NO_ERROR)
                                2023-05-07 15:23:14.389 - info: host.iobroker instance system.adapter.feiertage.0 terminated with code 0 (NO_ERROR)
                                2023-05-07 15:23:15.486 - info: homeconnect.0 (765) starting. Version 1.1.1 in /opt/iobroker/node_modules/iobroker.homeconnect, node: v18.16.0, js-controller: 4.0.24
                                2023-05-07 15:23:16.450 - error: homeconnect.0 (765) refresh token failed
                                2023-05-07 15:23:16.455 - error: homeconnect.0 (765) AxiosError: Request failed with status code 401
                                2023-05-07 15:23:16.456 - error: homeconnect.0 (765) {"error":"invalid_client","error_description":"client has limited user list - user not assigned to client"}
                                2023-05-07 15:23:16.457 - error: homeconnect.0 (765) Start relogin in 10min
                                2023-05-07 15:23:16.980 - info: homeconnect.0 (765) Found 1 devices
                                2023-05-07 15:23:17.043 - info: host.iobroker instance system.adapter.lg-thinq.0 started with pid 849
                                2023-05-07 15:23:19.740 - info: homeconnect.0 (765) 013010426226000339/programs/active: There is no program active.
                                2023-05-07 15:23:20.017 - info: homeconnect.0 (765) 013010426226000339/programs/active/options: There is no program active.
                                2023-05-07 15:23:20.405 - error: host.iobroker iobroker npm-install: host.iobroker Cannot install iobroker.yahka@0.17.0: 1
                                2023-05-07 15:23:21.164 - info: host.iobroker instance system.adapter.net-tools.0 started with pid 864
                                2023-05-07 15:23:21.575 - info: host.iobroker iobroker npm-install: exit 25
                                2023-05-07 15:23:21.687 - info: homekit-controller.0 (802) starting. Version 0.5.8 in /opt/iobroker/node_modules/iobroker.homekit-controller, node: v18.16.0, js-controller: 4.0.24
                                2023-05-07 15:23:22.067 - info: homekit-controller.0 (802) IP-0E:34:37:9C:2A:37 (homebridge-loxone-proxy 8C29) found without pairing data but available for pairing: Create basic objects
                                2023-05-07 15:23:22.581 - warn: host.iobroker startInstance cannot find adapter "yahka@0.17.0". Try to install it... 4 attempt
                                2023-05-07 15:23:22.582 - info: host.iobroker iobroker install yahka@0.17.0 using installedVersion
                                2023-05-07 15:23:23.420 - info: lg-thinq.0 (849) starting. Version 0.1.4 in /opt/iobroker/node_modules/iobroker.lg-thinq, node: v18.16.0, js-controller: 4.0.24
                                2023-05-07 15:23:23.472 - warn: homekit-controller.0 (802) IP-0E:AC:47:0C:28:ED Could not initialize device: M4: Error: 2 Error: M4: Error: 2
                                at PairingProtocol.parsePairVerifyM4 (/opt/iobroker/node_modules/hap-controller/src/protocol/pairing-protocol.ts:718:19)
                                at /opt/iobroker/node_modules/hap-controller/src/transport/ip/http-client.ts:381:40
                                at processTicksAndRejections (node:internal/process/task_queues:95:5)
                                2023-05-07 15:23:23.475 - info: homekit-controller.0 (802) IP-0E:C9:E6:E1:F3:03 (homebridge-loxone-connect 9AC9) found without pairing data but available for pairing: Create basic objects
                                2023-05-07 15:23:25.078 - info: host.iobroker instance system.adapter.nina.0 started with pid 890
                                2023-05-07 15:23:26.605 - info: net-tools.0 (864) starting. Version 0.2.0 in /opt/iobroker/node_modules/iobroker.net-tools, node: v18.16.0, js-controller: 4.0.24
                                2023-05-07 15:23:26.837 - info: net-tools.0 (864) Scanning for open ports (20, 21, 22, 23, 25, 53, 80, 110, 119, 123, 143, 161, 162, 194, 443, 445, 3306, 3389, 5900, 6379, 8080, 8443, 9090, 9200, 9999) at localhost, please wait
                                2023-05-07 15:23:27.046 - info: lg-thinq.0 (849) Login successful
                                2023-05-07 15:23:28.104 - info: fahrplan.0 (739) Updated 2 routes, 2 enabled and 0 disabled
                                2023-05-07 15:23:28.784 - info: lg-thinq.0 (849) Found: 1 devices
                                2023-05-07 15:23:29.055 - info: host.iobroker instance scheduled system.adapter.odl.0 59 33 * * * *
                                2023-05-07 15:23:29.146 - info: net-tools.0 (864) Port scan finished
                                2023-05-07 15:23:29.118 - info: host.iobroker instance system.adapter.odl.0 started with pid 921
                                2023-05-07 15:23:29.225 - warn: lg-thinq.0 (849) State value to set for "lg-thinq.0.0a8df99a-dbe2-1300-9bc0-805b65694fe3.snapshot.washerDryer.remainTimeMinute" has value "199" greater than max "59"
                                2023-05-07 15:23:30.472 - warn: lg-thinq.0 (849) Please create an issue on https://github.com/TA2k/ioBroker.lg-thinq/issues with: missing AUTO_DETERGENT_OFF
                                2023-05-07 15:23:30.473 - warn: lg-thinq.0 (849) Please create an issue on https://github.com/TA2k/ioBroker.lg-thinq/issues with: missing AUTO_DETERGENT_ON
                                2023-05-07 15:23:30.474 - warn: lg-thinq.0 (849) Please create an issue on https://github.com/TA2k/ioBroker.lg-thinq/issues with: missing GPLUS_BEST_WASH_NO_SELECT
                                2023-05-07 15:23:30.475 - warn: lg-thinq.0 (849) Please create an issue on https://github.com/TA2k/ioBroker.lg-thinq/issues with: missing GPLUS_BEST_WASH_NORMAL
                                2023-05-07 15:23:30.476 - warn: lg-thinq.0 (849) Please create an issue on https://github.com/TA2k/ioBroker.lg-thinq/issues with: missing GPLUS_BEST_WASH_INTENSIVE
                                2023-05-07 15:23:30.478 - warn: lg-thinq.0 (849) Please create an issue on https://github.com/TA2k/ioBroker.lg-thinq/issues with: missing GPLUS_BEST_WASH_TURBOWASH
                                2023-05-07 15:23:30.479 - warn: lg-thinq.0 (849) Please create an issue on https://github.com/TA2k/ioBroker.lg-thinq/issues with: missing GPLUS_BEST_WASH_TIMESAVE
                                2023-05-07 15:23:30.481 - warn: lg-thinq.0 (849) Please create an issue on https://github.com/TA2k/ioBroker.lg-thinq/issues with: missing STEAM_1_LEVEL
                                2023-05-07 15:23:30.482 - warn: lg-thinq.0 (849) Please create an issue on https://github.com/TA2k/ioBroker.lg-thinq/issues with: missing STEAM_2_LEVEL
                                2023-05-07 15:23:30.483 - warn: lg-thinq.0 (849) Please create an issue on https://github.com/TA2k/ioBroker.lg-thinq/issues with: missing STEAM_3_LEVEL
                                2023-05-07 15:23:30.484 - warn: lg-thinq.0 (849) Please create an issue on https://github.com/TA2k/ioBroker.lg-thinq/issues with: missing STEAM_8_LEVEL
                                2023-05-07 15:23:30.501 - warn: lg-thinq.0 (849) Please create an issue on https://github.com/TA2k/ioBroker.lg-thinq/issues with: missing SOILWASH_LIGHT
                                2023-05-07 15:23:30.503 - warn: lg-thinq.0 (849) Please create an issue on https://github.com/TA2k/ioBroker.lg-thinq/issues with: missing SOILWASH_HEAVY
                                2023-05-07 15:23:30.505 - warn: lg-thinq.0 (849) Please create an issue on https://github.com/TA2k/ioBroker.lg-thinq/issues with: missing RINSE_HOLD
                                2023-05-07 15:23:30.507 - warn: lg-thinq.0 (849) Please create an issue on https://github.com/TA2k/ioBroker.lg-thinq/issues with: missing DRYLEVEL_30MIN
                                2023-05-07 15:23:30.508 - warn: lg-thinq.0 (849) Please create an issue on https://github.com/TA2k/ioBroker.lg-thinq/issues with: missing DRYLEVEL_60MIN
                                2023-05-07 15:23:30.511 - warn: lg-thinq.0 (849) Please create an issue on https://github.com/TA2k/ioBroker.lg-thinq/issues with: missing DRYLEVEL_90MIN
                                2023-05-07 15:23:30.512 - warn: lg-thinq.0 (849) Please create an issue on https://github.com/TA2k/ioBroker.lg-thinq/issues with: missing DRYLEVEL_120MIN
                                2023-05-07 15:23:30.513 - warn: lg-thinq.0 (849) Please create an issue on https://github.com/TA2k/ioBroker.lg-thinq/issues with: missing PROOFING_OFF
                                2023-05-07 15:23:30.514 - warn: lg-thinq.0 (849) Please create an issue on https://github.com/TA2k/ioBroker.lg-thinq/issues with: missing PROOFING_ON
                                2023-05-07 15:23:30.517 - warn: lg-thinq.0 (849) Please create an issue on https://github.com/TA2k/ioBroker.lg-thinq/issues with: missing SOFTENER_OFF
                                2023-05-07 15:23:30.518 - warn: lg-thinq.0 (849) Please create an issue on https://github.com/TA2k/ioBroker.lg-thinq/issues with: missing SOFTENER_ON
                                2023-05-07 15:23:30.519 - warn: lg-thinq.0 (849) Please create an issue on https://github.com/TA2k/ioBroker.lg-thinq/issues with: missing DETERGENT_OFF
                                2023-05-07 15:23:30.520 - warn: lg-thinq.0 (849) Please create an issue on https://github.com/TA2k/ioBroker.lg-thinq/issues with: missing DETERGENT_ON
                                2023-05-07 15:23:30.522 - warn: lg-thinq.0 (849) Please create an issue on https://github.com/TA2k/ioBroker.lg-thinq/issues with: missing DETERGENT_REMAINING_NO
                                2023-05-07 15:23:30.523 - warn: lg-thinq.0 (849) Please create an issue on https://github.com/TA2k/ioBroker.lg-thinq/issues with: missing DETERGENT_REMAINING_YES
                                2023-05-07 15:23:30.526 - warn: lg-thinq.0 (849) Please create an issue on https://github.com/TA2k/ioBroker.lg-thinq/issues with: missing DETERGENT_BOX_OFF
                                2023-05-07 15:23:30.530 - warn: lg-thinq.0 (849) Please create an issue on https://github.com/TA2k/ioBroker.lg-thinq/issues with: missing DETERGENT_BOX_ON
                                2023-05-07 15:23:30.531 - warn: lg-thinq.0 (849) Please create an issue on https://github.com/TA2k/ioBroker.lg-thinq/issues with: missing MINI_PAIRING_OFF
                                2023-05-07 15:23:30.532 - warn: lg-thinq.0 (849) Please create an issue on https://github.com/TA2k/ioBroker.lg-thinq/issues with: missing MINI_PAIRING_ON
                                2023-05-07 15:23:30.534 - warn: lg-thinq.0 (849) Please create an issue on https://github.com/TA2k/ioBroker.lg-thinq/issues with: missing pickerOffset
                                2023-05-07 15:23:30.535 - warn: lg-thinq.0 (849) Please create an issue on https://github.com/TA2k/ioBroker.lg-thinq/issues with: missing BLOOD
                                2023-05-07 15:23:30.535 - warn: lg-thinq.0 (849) Please create an issue on https://github.com/TA2k/ioBroker.lg-thinq/issues with: missing CHOCOLATE
                                2023-05-07 15:23:30.536 - warn: lg-thinq.0 (849) Please create an issue on https://github.com/TA2k/ioBroker.lg-thinq/issues with: missing COCOA
                                2023-05-07 15:23:30.537 - warn: lg-thinq.0 (849) Please create an issue on https://github.com/TA2k/ioBroker.lg-thinq/issues with: missing COFFEE
                                2023-05-07 15:23:30.538 - warn: lg-thinq.0 (849) Please create an issue on https://github.com/TA2k/ioBroker.lg-thinq/issues with: missing COLA
                                2023-05-07 15:23:30.539 - warn: lg-thinq.0 (849) Please create an issue on https://github.com/TA2k/ioBroker.lg-thinq/issues with: missing CURRY
                                2023-05-07 15:23:30.540 - warn: lg-thinq.0 (849) Please create an issue on https://github.com/TA2k/ioBroker.lg-thinq/issues with: missing EGG
                                2023-05-07 15:23:30.541 - warn: lg-thinq.0 (849) Please create an issue on https://github.com/TA2k/ioBroker.lg-thinq/issues with: missing FATOIL
                                2023-05-07 15:23:30.542 - warn: lg-thinq.0 (849) Please create an issue on https://github.com/TA2k/ioBroker.lg-thinq/issues with: missing FRUIT_STAIN
                                2023-05-07 15:23:30.543 - warn: lg-thinq.0 (849) Please create an issue on https://github.com/TA2k/ioBroker.lg-thinq/issues with: missing GRASS
                                2023-05-07 15:23:30.544 - warn: lg-thinq.0 (849) Please create an issue on https://github.com/TA2k/ioBroker.lg-thinq/issues with: missing GREASE
                                2023-05-07 15:23:30.545 - warn: lg-thinq.0 (849) Please create an issue on https://github.com/TA2k/ioBroker.lg-thinq/issues with: missing KETCHUP
                                2023-05-07 15:23:30.545 - warn: lg-thinq.0 (849) Please create an issue on https://github.com/TA2k/ioBroker.lg-thinq/issues with: missing LIPSTICK
                                2023-05-07 15:23:30.546 - warn: lg-thinq.0 (849) Please create an issue on https://github.com/TA2k/ioBroker.lg-thinq/issues with: missing MAKE_UP
                                2023-05-07 15:23:30.546 - warn: lg-thinq.0 (849) Please create an issue on https://github.com/TA2k/ioBroker.lg-thinq/issues with: missing MUD
                                2023-05-07 15:23:30.547 - warn: lg-thinq.0 (849) Please create an issue on https://github.com/TA2k/ioBroker.lg-thinq/issues with: missing PEPPER
                                2023-05-07 15:23:30.548 - warn: lg-thinq.0 (849) Please create an issue on https://github.com/TA2k/ioBroker.lg-thinq/issues with: missing RED_WINE
                                2023-05-07 15:23:30.548 - warn: lg-thinq.0 (849) Please create an issue on https://github.com/TA2k/ioBroker.lg-thinq/issues with: missing RUST
                                2023-05-07 15:23:30.549 - warn: lg-thinq.0 (849) Please create an issue on https://github.com/TA2k/ioBroker.lg-thinq/issues with: missing SHOE_POLISH
                                2023-05-07 15:23:30.550 - warn: lg-thinq.0 (849) Please create an issue on https://github.com/TA2k/ioBroker.lg-thinq/issues with: missing SPINACH
                                2023-05-07 15:23:30.550 - warn: lg-thinq.0 (849) Please create an issue on https://github.com/TA2k/ioBroker.lg-thinq/issues with: missing SOY_SAUCE
                                2023-05-07 15:23:30.551 - warn: lg-thinq.0 (849) Please create an issue on https://github.com/TA2k/ioBroker.lg-thinq/issues with: missing TEA
                                2023-05-07 15:23:30.553 - warn: lg-thinq.0 (849) Please create an issue on https://github.com/TA2k/ioBroker.lg-thinq/issues with: missing TOMATOSAUCE
                                2023-05-07 15:23:30.554 - warn: lg-thinq.0 (849) Please create an issue on https://github.com/TA2k/ioBroker.lg-thinq/issues with: missing VEGATABLE_STAIN
                                2023-05-07 15:23:30.555 - warn: lg-thinq.0 (849) Please create an issue on https://github.com/TA2k/ioBroker.lg-thinq/issues with: missing COURSE_TYPE_COURSE
                                2023-05-07 15:23:30.556 - warn: lg-thinq.0 (849) Please create an issue on https://github.com/TA2k/ioBroker.lg-thinq/issues with: missing COURSE_TYPE_MYPATTERN
                                2023-05-07 15:23:30.557 - warn: lg-thinq.0 (849) Please create an issue on https://github.com/TA2k/ioBroker.lg-thinq/issues with: missing COURSE_TYPE_RECENT
                                2023-05-07 15:23:30.557 - warn: lg-thinq.0 (849) Please create an issue on https://github.com/TA2k/ioBroker.lg-thinq/issues with: missing COURSE_TYPE_DOWNLOADCYCLE
                                2023-05-07 15:23:31.720 - info: host.iobroker iobroker npm-install: NPM version: 9.5.1Installing iobroker.yahka@0.17.0... (System call)
                                2023-05-07 15:23:32.320 - warn: homekit-controller.0 (802) IP-D8:BE:54:E7:06:F8 Could not initialize device: connect ECONNREFUSED 127.0.0.1:33531 Error: connect ECONNREFUSED 127.0.0.1:33531
                                at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1494:16)
                                2023-05-07 15:23:32.419 - info: lg-thinq.0 (849) Found MQTT Host
                                2023-05-07 15:23:32.468 - info: homekit-controller.0 (802) IP-0E:34:37:9C:2A:37 (homebridge-loxone-proxy 8C29) found without pairing data but available for pairing: Create basic objects
                                2023-05-07 15:23:32.472 - info: homekit-controller.0 (802) IP-0E:C9:E6:E1:F3:03 (homebridge-loxone-connect 9AC9) found without pairing data but available for pairing: Create basic objects
                                2023-05-07 15:23:32.619 - info: lg-thinq.0 (849) Found AWS CER
                                2023-05-07 15:23:32.654 - info: homekit-controller.0 (802) IP-7A:0C:6C:53:B1:DF (Bungalow) found without known pairing data and already paired: ignoring
                                2023-05-07 15:23:32.784 - warn: homekit-controller.0 (802) IP-0E:AC:47:0C:28:ED Could not initialize device: M4: Error: 2 Error: M4: Error: 2
                                at PairingProtocol.parsePairVerifyM4 (/opt/iobroker/node_modules/hap-controller/src/protocol/pairing-protocol.ts:718:19)
                                at /opt/iobroker/node_modules/hap-controller/src/transport/ip/http-client.ts:381:40
                                at processTicksAndRejections (node:internal/process/task_queues:95:5)
                                2023-05-07 15:23:33.178 - info: host.iobroker instance scheduled system.adapter.pegelalarm.0 */15 * * * *
                                2023-05-07 15:23:33.225 - info: host.iobroker instance system.adapter.pegelalarm.0 started with pid 951
                                2023-05-07 15:23:33.238 - info: fahrplan.0 (739) Updated 2 departure timetables, 2 enabled and 0 disabled
                                2023-05-07 15:23:33.245 - info: nina.0 (890) starting. Version 0.0.25 in /opt/iobroker/node_modules/iobroker.nina, node: v18.16.0, js-controller: 4.0.24
                                2023-05-07 15:23:33.488 - info: lg-thinq.0 (849) Create certification done
                                2023-05-07 15:23:33.629 - info: nina.0 (890) Found AGS for: Potsdam-Mittelmark
                                2023-05-07 15:23:34.298 - info: lg-thinq.0 (849) Start MQTT Connection
                                2023-05-07 15:23:35.193 - info: lg-thinq.0 (849) MQTT connected to: t20/op/1e29198491d36f7258b1d98a1f0b90cc3ce83e4f610c72aa161e846b8226e903/inbox
                                2023-05-07 15:23:35.698 - info: odl.0 (921) starting. Version 2.0.5 in /opt/iobroker/node_modules/iobroker.odl, node: v18.16.0, js-controller: 4.0.24
                                2023-05-07 15:23:37.164 - info: host.iobroker instance system.adapter.pvforecast.0 started with pid 974
                                2023-05-07 15:23:38.509 - info: weatherunderground.0 (510) Terminated (NO_ERROR): Without reason
                                2023-05-07 15:23:38.890 - info: pegelalarm.0 (951) starting. Version 1.3.0 in /opt/iobroker/node_modules/iobroker.pegelalarm, node: v18.16.0, js-controller: 4.0.24
                                2023-05-07 15:23:39.278 - info: host.iobroker instance system.adapter.weatherunderground.0 terminated with code 0 (NO_ERROR)
                                2023-05-07 15:23:39.599 - info: odl.0 (921) Terminated (NO_ERROR): Without reason
                                2023-05-07 15:23:40.276 - info: host.iobroker instance system.adapter.odl.0 terminated with code 0 (NO_ERROR)
                                2023-05-07 15:23:41.031 - info: host.iobroker instance system.adapter.reolink.0 started with pid 1001
                                2023-05-07 15:23:42.052 - info: pvforecast.0 (974) starting. Version 2.3.0 in /opt/iobroker/node_modules/iobroker.pvforecast, node: v18.16.0, js-controller: 4.0.24
                                2023-05-07 15:23:42.170 - info: pvforecast.0 (974) using system latitude: 52.34774765 longitude: 12.701417707138479
                                2023-05-07 15:23:45.121 - info: host.iobroker instance system.adapter.reolink.1 started with pid 1016
                                2023-05-07 15:23:46.480 - info: pvforecast.0 (974) Starting update cron (every 15 Minutes) for timezone: Europe/Berlin
                                2023-05-07 15:23:47.195 - info: reolink.0 (1001) starting. Version 0.1.1 (non-npm: aendue/ioBroker.reolink#b78aab6744cdb81b360fd947a9c6e2fd6808bab1) in /opt/iobroker/node_modules/iobroker.reolink, node: v18.16.0, js-controller: 4.0.24
                                2023-05-07 15:23:47.259 - info: reolink.0 (1001) Reolink adapter has started
                                2023-05-07 15:23:47.266 - info: reolink.0 (1001) Current IP: 192.168.7.241
                                2023-05-07 15:23:47.419 - info: reolink.0 (1001) State value to set for "reolink.0.network.channel" has to be type "number" but received type "string"
                                2023-05-07 15:23:48.977 - info: host.iobroker instance system.adapter.reolink.2 started with pid 1031
                                2023-05-07 15:23:50.067 - info: reolink.0 (1001) State value to set for "reolink.0.RAW.Email" has to be stringified but received type "object"
                                2023-05-07 15:23:50.265 - info: pegelalarm.0 (951) Terminated (NO_ERROR): Without reason
                                2023-05-07 15:23:51.069 - info: host.iobroker instance system.adapter.pegelalarm.0 terminated with code 0 (NO_ERROR)
                                2023-05-07 15:23:51.115 - info: reolink.1 (1016) starting. Version 0.1.1 (non-npm: aendue/ioBroker.reolink#b78aab6744cdb81b360fd947a9c6e2fd6808bab1) in /opt/iobroker/node_modules/iobroker.reolink, node: v18.16.0, js-controller: 4.0.24
                                2023-05-07 15:23:51.182 - info: reolink.1 (1016) Reolink adapter has started
                                2023-05-07 15:23:51.189 - info: reolink.1 (1016) Current IP: 192.168.7.241
                                2023-05-07 15:23:53.009 - info: host.iobroker instance system.adapter.reolink.3 started with pid 1046
                                2023-05-07 15:23:54.041 - info: reolink.1 (1016) State value to set for "reolink.1.RAW.Email" has to be stringified but received type "object"
                                2023-05-07 15:23:54.772 - info: reolink.2 (1031) starting. Version 0.1.1 (non-npm: aendue/ioBroker.reolink#b78aab6744cdb81b360fd947a9c6e2fd6808bab1) in /opt/iobroker/node_modules/iobroker.reolink, node: v18.16.0, js-controller: 4.0.24
                                2023-05-07 15:23:54.859 - info: reolink.2 (1031) Reolink adapter has started
                                2023-05-07 15:23:54.872 - info: reolink.2 (1031) Current IP: 192.168.7.241
                                2023-05-07 15:23:55.837 - error: host.iobroker iobroker npm-install: host.iobroker Cannot install iobroker.yahka@0.17.0: 1
                                2023-05-07 15:23:56.970 - info: host.iobroker iobroker npm-install: exit 25
                                2023-05-07 15:23:57.082 - info: host.iobroker instance system.adapter.reolink.4 started with pid 1072
                                2023-05-07 15:23:57.689 - info: cloud.0 (667) Trying to connect as system.user.admin to cloud
                                2023-05-07 15:23:57.991 - info: cloud.0 (667) Connection changed: connect
                                2023-05-07 15:23:58.105 - error: host.iobroker Cannot download and install adapter "yahka@0.17.0". To retry it disable/enable the adapter or restart host. Also check the error messages in the log!
                                2023-05-07 15:23:58.326 - info: reolink.2 (1031) State value to set for "reolink.2.RAW.Email" has to be stringified but received type "object"
                                2023-05-07 15:23:59.356 - info: reolink.3 (1046) starting. Version 0.1.1 (non-npm: aendue/ioBroker.reolink#b78aab6744cdb81b360fd947a9c6e2fd6808bab1) in /opt/iobroker/node_modules/iobroker.reolink, node: v18.16.0, js-controller: 4.0.24
                                2023-05-07 15:23:59.440 - info: reolink.3 (1046) Reolink adapter has started
                                2023-05-07 15:23:59.448 - info: reolink.3 (1046) Current IP: 192.168.7.241
                                2023-05-07 15:24:00.933 - info: host.iobroker instance system.adapter.simple-api.0 started with pid 1087
                                2023-05-07 15:24:01.630 - info: reolink.3 (1046) State value to set for "reolink.3.RAW.Email" has to be stringified but received type "object"
                                2023-05-07 15:24:02.092 - info: reolink.4 (1072) starting. Version 0.1.1 (non-npm: aendue/ioBroker.reolink#b78aab6744cdb81b360fd947a9c6e2fd6808bab1) in /opt/iobroker/node_modules/iobroker.reolink, node: v18.16.0, js-controller: 4.0.24
                                2023-05-07 15:24:02.173 - info: reolink.4 (1072) Reolink adapter has started
                                2023-05-07 15:24:02.179 - info: reolink.4 (1072) Current IP: 192.168.7.241
                                2023-05-07 15:24:04.755 - info: reolink.4 (1072) State value to set for "reolink.4.RAW.Email" has to be stringified but received type "object"
                                2023-05-07 15:24:04.792 - info: host.iobroker instance scheduled system.adapter.solarwetter.0 17 5 * * *
                                2023-05-07 15:24:04.834 - info: host.iobroker instance system.adapter.solarwetter.0 started with pid 1102
                                2023-05-07 15:24:05.564 - info: simple-api.0 (1087) starting. Version 2.7.2 in /opt/iobroker/node_modules/iobroker.simple-api, node: v18.16.0, js-controller: 4.0.24
                                2023-05-07 15:24:05.640 - info: simple-api.0 (1087) simpleAPI server listening on port 8087
                                2023-05-07 15:24:05.642 - info: simple-api.0 (1087) Allow states only when user is owner: false
                                2023-05-07 15:24:05.668 - info: simple-api.0 (1087) http server listening on port 8087
                                2023-05-07 15:24:08.252 - info: solarwetter.0 (1102) starting. Version 1.0.2 (non-npm: motuditli/ioBroker.solarwetter#c5d340e2b3e021951a88c44a89f6219624c97a15) in /opt/iobroker/node_modules/iobroker.solarwetter, node: v18.16.0, js-controller: 4.0.24
                                2023-05-07 15:24:08.344 - info: solarwetter.0 (1102) Postcode: 147
                                2023-05-07 15:24:08.348 - info: solarwetter.0 (1102) 4-Tage-Prognose für: Berlin
                                2023-05-07 15:24:08.351 - info: solarwetter.0 (1102) Leistung eigene Anlage: 20 kWp
                                2023-05-07 15:24:08.365 - info: solarwetter.0 (1102) objects written
                                2023-05-07 15:24:08.901 - info: host.iobroker instance system.adapter.tankerkoenig.0 started with pid 1121
                                2023-05-07 15:24:12.159 - info: tankerkoenig.0 (1121) starting. Version 3.3.7 in /opt/iobroker/node_modules/iobroker.tankerkoenig, node: v18.16.0, js-controller: 4.0.24
                                2023-05-07 15:24:12.236 - info: tankerkoenig.0 (1121) Adapter is already in daemon mode
                                2023-05-07 15:24:12.239 - info: tankerkoenig.0 (1121) Sync time set to 15 minutes or 900000 ms
                                2023-05-07 15:24:12.954 - info: host.iobroker instance system.adapter.text2command.0 started with pid 1148
                                2023-05-07 15:24:17.026 - info: host.iobroker instance system.adapter.trashschedule.0 started with pid 1197
                                2023-05-07 15:24:17.632 - info: text2command.0 (1148) starting. Version 2.3.0 in /opt/iobroker/node_modules/iobroker.text2command, node: v18.16.0, js-controller: 4.0.24
                                2023-05-07 15:24:20.989 - info: host.iobroker instance system.adapter.worx.0 started with pid 1212
                                2023-05-07 15:24:23.038 - info: trashschedule.0 (1197) starting. Version 2.2.0 in /opt/iobroker/node_modules/iobroker.trashschedule, node: v18.16.0, js-controller: 4.0.24
                                2023-05-07 15:24:24.077 - info: trashschedule.0 (1197) [ical] configurured ical preview is 14 days - increase this value to find more events in the future
                                2023-05-07 15:24:24.219 - warn: trashschedule.0 (1197) no events matches type "Restabfalltonne" with match "Restabfall" (exact match)
                                2023-05-07 15:24:24.269 - warn: trashschedule.0 (1197) no events matches type "Wertstofftonne" with match "Wertstoff" (exact match)
                                2023-05-07 15:24:24.375 - warn: trashschedule.0 (1197) no events matches type "Biotonne" with match "Bio" (exact match)
                                2023-05-07 15:24:24.492 - warn: trashschedule.0 (1197) no events matches type "Papiertonne" with match "Papier" (exact match)
                                2023-05-07 15:24:24.676 - warn: trashschedule.0 (1197) (5) next has no entries. Check configuration of ical (increase preview) and trashschedule!
                                2023-05-07 15:24:24.758 - warn: trashschedule.0 (1197) (5) nextAfter has no entries. Check configuration of ical (increase preview) and trashschedule!
                                2023-05-07 15:24:26.070 - info: tankerkoenig.0 (1121) Start first request
                                2023-05-07 15:24:26.279 - info: worx.0 (1212) starting. Version 2.1.3 in /opt/iobroker/node_modules/iobroker.worx, node: v18.16.0, js-controller: 4.0.24
                                2023-05-07 15:24:26.384 - info: worx.0 (1212) Login to worx
                                2023-05-07 15:24:27.848 - info: worx.0 (1212) Connected to worx server
                                2023-05-07 15:24:28.227 - info: worx.0 (1212) Found 1 devices
                                2023-05-07 15:24:28.228 - info: worx.0 (1212) Found device M hinten with id 2021302672090025823D
                                2023-05-07 15:24:29.610 - info: worx.0 (1212) Create product folder and states for WR165E
                                2023-05-07 15:24:30.011 - info: worx.0 (1212) No payload found
                                2023-05-07 15:24:30.014 - info: worx.0 (1212) Start MQTT connection
                                2023-05-07 15:24:30.049 - warn: lg-thinq.0 (849) State value to set for "lg-thinq.0.0a8df99a-dbe2-1300-9bc0-805b65694fe3.snapshot.washerDryer.remainTimeMinute" has value "197" greater than max "59"
                                2023-05-07 15:25:00.068 - info: host.iobroker instance system.adapter.dwd.0 started with pid 1266
                                2023-05-07 15:25:03.489 - info: dwd.0 (1266) starting. Version 2.8.3 in /opt/iobroker/node_modules/iobroker.dwd, node: v18.16.0, js-controller: 4.0.24
                                2023-05-07 15:25:06.325 - info: dwd.0 (1266) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
                                2023-05-07 15:25:06.863 - info: host.iobroker instance system.adapter.dwd.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
                                2023-05-07 15:25:08.367 - info: solarwetter.0 (1102) force terminating adapter after 1 minute
                                2023-05-07 15:25:08.875 - info: solarwetter.0 (1102) Terminated (NO_ERROR): Without reason
                                2023-05-07 15:25:09.490 - info: host.iobroker instance system.adapter.solarwetter.0 terminated with code 0 (NO_ERROR)
                                2023-05-07 15:25:30.164 - warn: lg-thinq.0 (849) State value to set for "lg-thinq.0.0a8df99a-dbe2-1300-9bc0-805b65694fe3.snapshot.washerDryer.remainTimeMinute" has value "196" greater than max "59"
                                
                                
                                node-red.0
                                2023-05-07 16:07:52.336	warn	Error: ENOENT: no such file or directory, stat '/opt/iobroker/node_modules/iobroker.node-red/.node-red/node_modules/connect-nodes/editor/components/image-select/src/js/image-select.js'
                                
                                node-red.0
                                2023-05-07 16:07:52.335	warn	Error: ENOENT: no such file or directory, stat '/opt/iobroker/node_modules/iobroker.node-red/.node-red/node_modules/connect-nodes/editor/lib/lib.js'
                                
                                node-red.0
                                2023-05-07 16:07:52.297	warn	Error: ENOENT: no such file or directory, stat '/opt/iobroker/node_modules/iobroker.node-red/.node-red/node_modules/connect-nodes/editor/node-editor-controllers/node-editor-controllers.js'
                                
                                node-red.0
                                2023-05-07 16:07:52.293	warn	Error: ENOENT: no such file or directory, stat '/opt/iobroker/node_modules/iobroker.node-red/.node-red/node_modules/connect-nodes/editor/block-configs/block-configs.js'
                                
                                node-red.0
                                2023-05-07 16:07:52.278	warn	Error: ENOENT: no such file or directory, stat '/opt/iobroker/node_modules/iobroker.node-red/.node-red/node_modules/connect-nodes/editor/components/block-config-select/src/js/block-config-select.js'
                                

                                den Pfad mit ..../.node-red/ gibt es nicht davor sind die ordner da aber ab .node-red fehlen die ordner und unter /opt/iobroker/node_modules/ sind die auch nicht zu finden

                                T 1 Reply Last reply Reply Quote 0
                                • T
                                  Tomme @Tomme last edited by

                                  ich habe gerade mal versucht das node-red backup das ich habe zurückzuspielen und das geht auch nicht der zeigt jetzt auch keine backups an ...
                                  heißt ich setze den container nochmal neu auf und lösche vorher den /opt/iobroker Ordner
                                  das mit dem backitup möchte ich so nicht haben ...
                                  ich übernehme aber alles so wie gestern besprochen und stelle das backup wieder her ... ich halte euch auf dem laufenden ...

                                  T 1 Reply Last reply Reply Quote 0
                                  • T
                                    Tomme @Tomme last edited by

                                    (Re)setting permissions (This might take a while! Please be patient!)... Done.

                                    Fixing "sudo-bug" by replacing sudo with gosu... Done.

                                    was heißt n das eigentlich? gosu gibt es hab ich auch schon mal mit rumprobiert aber wie man das anstelle sudo obwohl man ja schon root ist in der konsole anwendet keine ahnung

                                    Glasfaser 1 Reply Last reply Reply Quote 0
                                    • Glasfaser
                                      Glasfaser @Tomme last edited by

                                      @tomme sagte in Yahka Adapter in iobroker im Docker Container:

                                      was heißt n das eigentlich?

                                      ist im Startscript enthalten .

                                      https://github.com/buanet/ioBroker.docker/blob/main/debian/scripts/iobroker_startup.sh#L234

                                      1 Reply Last reply Reply Quote 0
                                      • Thomas Braun
                                        Thomas Braun Most Active @Tomme last edited by

                                        @tomme sagte in Yahka Adapter in iobroker im Docker Container:

                                        ist schon erschreckend wieviele user da überhaupt drauf sind bei der "nackigen" installation

                                        Warum? Sind halt für den Betrieb der einzelnen Services erforderlich. Linux ist halt als MultiUser-System designed.

                                        T 1 Reply Last reply Reply Quote 1
                                        • T
                                          Tomme @Thomas Braun last edited by

                                          @thomas-braun moin großmeister!

                                          ja aber damit hab ich nicht gerechnet ehrlich gesagt ...

                                          T 1 Reply Last reply Reply Quote 0
                                          • T
                                            Tomme @Tomme last edited by

                                            so container ist mit 2 handgriffen erstellt und gestartet
                                            iob im hintergrund installiert
                                            admin gestartet und testbackup gemacht
                                            kann man auch im admin wiederherstellen
                                            jetzt suche ich den gemappten ordner und spiele mein backup wieder rein und hoffe das er das dann auch findet

                                            T 1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post

                                            Support us

                                            ioBroker
                                            Community Adapters
                                            Donate
                                            FAQ Cloud / IOT
                                            HowTo: Node.js-Update
                                            HowTo: Backup/Restore
                                            Downloads
                                            BLOG

                                            532
                                            Online

                                            31.7k
                                            Users

                                            79.9k
                                            Topics

                                            1.3m
                                            Posts

                                            6
                                            255
                                            21914
                                            Loading More Posts
                                            • Oldest to Newest
                                            • Newest to Oldest
                                            • Most Votes
                                            Reply
                                            • Reply as topic
                                            Log in to reply
                                            Community
                                            Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen
                                            The ioBroker Community 2014-2023
                                            logo