Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. ioBroker Allgemein
    4. UnRAID Docker ioBroker Backitup Wiederherstellen

    NEWS

    • Wir empfehlen: Node.js 22.x

    • Neuer Blog: Fotos und Eindrücke aus Solingen

    • ioBroker goes Matter ... Matter Adapter in Stable

    UnRAID Docker ioBroker Backitup Wiederherstellen

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

      @kaese2002 sagte in UnRAID Docker ioBroker Backitup Wiederherstellen:

      system.adapter.vis.0 : vis : bed10cb58993 - disabled

      system.adapter.web.0 : web : bed10cb58993 - disabled, port: 8082, bind: 0.0.0.0, run as: admin

      Die sind noch aus !

      Auf 8082 ist VIS ..

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

        @glasfaser

        Ja hab ich jetzt gestartet, Verweis in der Instanzzeile verweist auf 8082, wie in der alten Installation.
        Aber auch auf der 8081 öffnet sich nix.

        Bildschirmfoto 2022-08-17 um 21.06.55.png Bildschirmfoto 2022-08-17 um 21.16.47.png Bildschirmfoto 2022-08-17 um 21.19.07.png

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

          @kaese2002

          Kenne so diese Einstellungen nicht .... was auf deinem System ist

          aber fehlt da nicht was 8082

          16590f7a-b011-4617-9d38-1ebc5677f850-grafik.png

          Aber auch auf der 8081 öffnet sich nix.

          ist 8082 !!

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

            @glasfaser

            OK, nach bisschen rumspielen läuft das jetzt auch.
            Was mich wundert ist, dass der Container dann trotz Xeon 6Kern und 32GB Ram fast 2min braucht, bis der iobroker erreichbar ist.
            Dann fehlen nur noch die Verbindungen zur Influx DB. Da werde ich mich morgen mit befassen.
            Danke dir nochmal und einen schönen Abend.

            Bildschirmfoto 2022-08-17 um 22.06.27.png

            Bildschirmfoto 2022-08-17 um 22.08.25.png

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

              @kaese2002 sagte in UnRAID Docker ioBroker Backitup Wiederherstellen:

              Danke dir nochmal und einen schönen Abend.

              .... sehr gerne ...

              PS: View sieht Schick aus ... & aufgeräumt

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

                @glasfaser

                Guten Abend.
                Würde nun gern mit den anderen Adaptern weiter machen...prinzipiell funktioniert noch nicht viel...
                Weder Yahka noch die Shellys krieg ich zum laufen. Yahka ist nach probieren mittlerweile soweit, dass die Instanz nicht mehr startet. InfluxDB hat ein Loginproblem...

                Anbei das Logfile

                
influxdb.0
2022-08-18 18:27:00.409	error	Error: {"code":"unauthorized","message":"unauthorized access"}

influxdb.0
2022-08-18 18:27:00.405	info	Influx DB Version used: 1.x

influxdb.0
2022-08-18 18:27:00.405	info	Connecting http://192.168.137.95:8086/ ...

influxdb.0
2022-08-18 18:26:50.404	error	Error: {"code":"unauthorized","message":"unauthorized access"}

influxdb.0
2022-08-18 18:26:50.395	info	Influx DB Version used: 1.x

influxdb.0
2022-08-18 18:26:50.395	info	Connecting http://192.168.137.95:8086/ ...

influxdb.0
2022-08-18 18:26:40.394	error	Error: {"code":"unauthorized","message":"unauthorized access"}

influxdb.0
2022-08-18 18:26:40.390	info	Influx DB Version used: 1.x

influxdb.0
2022-08-18 18:26:40.390	info	Connecting http://192.168.137.95:8086/ ...

influxdb.0
2022-08-18 18:26:30.390	error	Error: {"code":"unauthorized","message":"unauthorized access"}

influxdb.0
2022-08-18 18:26:30.386	info	Influx DB Version used: 1.x

influxdb.0
2022-08-18 18:26:30.386	info	Connecting http://192.168.137.95:8086/ ...

influxdb.0
2022-08-18 18:26:20.385	error	Error: {"code":"unauthorized","message":"unauthorized access"}

influxdb.0
2022-08-18 18:26:20.382	info	Influx DB Version used: 1.x

influxdb.0
2022-08-18 18:26:20.382	info	Connecting http://192.168.137.95:8086/ ...

influxdb.0
2022-08-18 18:26:19.154	info	Not connected to InfluxDB, try later

influxdb.0
2022-08-18 18:26:10.380	error	Error: {"code":"unauthorized","message":"unauthorized access"}

influxdb.0
2022-08-18 18:26:10.377	info	Influx DB Version used: 1.x

influxdb.0
2022-08-18 18:26:10.376	info	Connecting http://192.168.137.95:8086/ ...

influxdb.0
2022-08-18 18:26:00.377	error	Error: {"code":"unauthorized","message":"unauthorized access"}

                
yahka.0
2022-08-18 18:27:59.903	info	terminating with timeout

yahka.0
2022-08-18 18:27:58.903	warn	Terminated (UNCAUGHT_EXCEPTION): Without reason

yahka.0
2022-08-18 18:27:58.902	info	terminating

yahka.0
2022-08-18 18:27:58.289	error	Exception-Code: ERR_SOCKET_BAD_PORT: options.port should be >= 0 and < 65536. Received .

yahka.0
2022-08-18 18:27:58.288	error	RangeError: options.port should be >= 0 and < 65536. Received . at new NodeError (node:internal/errors:387:5) at validatePort (node:internal/validators:226:11) at Server.listen (node:net:1560:5) at EventedHTTPServer.listen (/opt/iobroker/node_modules/hap-nodejs/src/lib/util/eventedhttp.ts:155:20) at HAPServer.listen (/opt/iobroker/node_modules/hap-nodejs/src/lib/HAPServer.ts:316:21) at Bridge.Accessory.publish (/opt/iobroker/node_modules/hap-nodejs/src/lib/Accessory.ts:1252:18) at devicesToPublish (/opt/iobroker/node_modules/iobroker.yahka/webpack:/yahka.homekit-bridge.ts:27:31) at /opt/iobroker/node_modules/iobroker.yahka/webpack:/yahka.homekit-bridge.ts:73:41 at Array.forEach (<anonymous>) at THomeKitBridge../yahka.homekit-bridge.ts.THomeKitBridge.init (/opt/iobroker/node_modules/iobroker.yahka/webpack:/yahka.homekit-bridge.ts:73:26)

yahka.0
2022-08-18 18:27:58.103	error	unhandled promise rejection: options.port should be >= 0 and < 65536. Received .

yahka.0
2022-08-18 18:27:58.103	error	Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().

yahka.0
2022-08-18 18:27:58.067	info	publishing bridge Yahka-0 on 0.0.0.0 using ciao

yahka.0
2022-08-18 18:27:58.065	info	adding Füllstand Zisterne with UUID: 97be6285-3f20-4d86-b121-00247245d742

yahka.0
2022-08-18 18:27:58.064	info	adding Shelly 1PM Licht UG Pferdezimmer with UUID: 8f916d58-3c15-4c6c-9ff9-4b37d9144ad1

yahka.0
2022-08-18 18:27:58.062	info	adding Shelly 1PM Licht UG Technikraum with UUID: 4fbcc2c2-cfa3-4c40-88d1-2b13d550a16b

yahka.0
2022-08-18 18:27:58.061	info	adding Shelly 1PM Licht UG Flur with UUID: 62e9573f-d080-4f8f-a15d-f119d9bc5640

yahka.0
2022-08-18 18:27:58.060	info	adding Staubsaugen beenden with UUID: 9894fc51-6e1d-4d7f-8345-e83a7b4a5132

yahka.0
2022-08-18 18:27:58.059	info	adding Shelly Plug S Verstärker OG Büro with UUID: 2917b065-0e1e-47a3-91c9-8df88d4b6735

yahka.0
2022-08-18 18:27:58.058	info	adding Shelly Plug S Ladestation Garage with UUID: caa367da-b244-452b-b009-4708bc0ab2c9

yahka.0
2022-08-18 18:27:58.057	info	adding Shelly Plug S Geschirrspüler EG Küche with UUID: 8c5cb3ae-ca53-45b1-88ed-fb2f5c0a75fd

yahka.0
2022-08-18 18:27:58.055	info	adding Shelly Plug S Wäschetrockner UG Waschküche with UUID: bcae68c8-bacf-4ccd-b927-60f966d97f32

yahka.0
2022-08-18 18:27:58.054	info	adding Shelly Plug S Waschmaschine UG Waschküche with UUID: a14a781a-e5d0-45ea-b49a-e27900f0c59e

yahka.0
2022-08-18 18:27:58.053	info	adding Shelly Plug S Lüftung UG Technikraum with UUID: 532da076-0592-4c44-b92c-8b5fb6c638e8

yahka.0
2022-08-18 18:27:58.051	info	adding Shelly Plug S Heizung UG Technikraum with UUID: 05dfbde2-239d-43bb-9366-bb654a45ec72

yahka.0
2022-08-18 18:27:58.049	info	adding Shelly RGBW 2 Kallax OG Büro with UUID: 07da9a42-55db-49ca-9791-9976b7fa3951

yahka.0
2022-08-18 18:27:58.047	info	adding Shelly 1PM Licht EG Küche with UUID: 11125ba7-0dac-4fc9-9085-cce38ff2c9e2

yahka.0
2022-08-18 18:27:58.046	info	adding Shelly 1PM Licht OG Büro with UUID: efc50f8c-718b-4023-a0d7-1351d142b584

yahka.0
2022-08-18 18:27:58.044	info	adding TP-Link Steckdose copy with UUID: 6af35b33-d39a-4996-a67f-cdd77444473e

yahka.0
2022-08-18 18:27:58.043	info	adding Shelly 1PM Licht EG Toilette with UUID: 1c0a3885-b664-4c82-b729-dce8f4d20df4

yahka.0
2022-08-18 18:27:58.041	info	adding Shelly 1PM Licht EG Esszimmer with UUID: 888c4bee-1df7-48eb-baf1-c888d90c1f0a

yahka.0
2022-08-18 18:27:58.040	info	adding Shelly 1PM Licht EG Wohnzimmer with UUID: 5629937f-7061-4567-8309-761bd8563ee7

yahka.0
2022-08-18 18:27:58.038	info	adding Shelly 2.5 Rolladen rechts OG Büro with UUID: e0144602-db96-44ee-9ea1-a6fb9292492a

yahka.0
2022-08-18 18:27:58.036	info	adding Shelly 2.5 Rolladen links OG Büro with UUID: cf9e6211-60cf-4ba4-b362-1ad5af304a2b

yahka.0
2022-08-18 18:27:58.033	info	adding Shelly 2.5 Rolladen Flur OG with UUID: 05ed6412-986e-4071-9fc6-9265972d2d91

yahka.0
2022-08-18 18:27:58.031	info	adding Shelly 2.5 Rolladen rechts OG Bad with UUID: 6b50bc88-aade-420d-88a5-a99344e6839a

yahka.0
2022-08-18 18:27:58.029	info	adding Shelly 2.5 Rolladen links OG Nähzimmer with UUID: 23301a8f-f643-4c37-af69-5583401edee3

yahka.0
2022-08-18 18:27:58.026	info	adding Shelly 2.5 Rolladen rechts OG Nähzimmer with UUID: 0b139fff-550d-4946-b1fa-7a6f690fc878

yahka.0
2022-08-18 18:27:58.023	info	adding Shelly 2.5 Rolladen rechts OG Schlafzimmer with UUID: 558c1a6e-39f7-45ac-aaed-32c0e8026223

yahka.0
2022-08-18 18:27:58.021	info	adding Shelly 2.5 Rolladen links OG Schlafzimmer with UUID: 954a98dc-97ab-4b0b-ab91-52cf3995f7be

yahka.0
2022-08-18 18:27:58.019	info	adding Shelly 1PM Licht OG Schlafzimmer with UUID: 1f2f0157-8499-4151-bdf7-fd68a4c7d64b

yahka.0
2022-08-18 18:27:58.018	info	adding Shelly 1PM Licht Nähzimmer OG with UUID: beab6bee-5357-4b92-89ef-e84f63d7e533

yahka.0
2022-08-18 18:27:58.016	info	adding BYD HVS 10.2 Batteriespeicher with UUID: c9074967-8927-4a89-8347-a2321e1966c1

yahka.0
2022-08-18 18:27:58.014	info	adding Shelly 1PM Licht OG Schlafzimmer Temperatur with UUID: e84f5789-ac1d-4ef7-baea-7b4aaf381656

yahka.0
2022-08-18 18:27:58.013	info	adding Golf GTE Ölstand with UUID: f348c01c-1286-4e88-a318-401a433caa32

yahka.0
2022-08-18 18:27:58.010	info	adding Golf GTE Aussentemperatur with UUID: fff7f1d0-cc1a-4cab-b454-00743ef0687a

yahka.0
2022-08-18 18:27:58.007	info	adding Golf GTE Batterie with UUID: 0a7572a0-0ec1-4732-95f2-574b1aa0bef6

yahka.0
2022-08-18 18:27:58.003	info	adding Shelly 2.5 Rolladen groß EG Küche with UUID: d0996a75-bde1-4429-a3af-72059a9f3879

yahka.0
2022-08-18 18:27:58.000	info	adding Shelly 2.5 Rolladen groß EG Esszimmer with UUID: 8fbe49af-8445-4744-9f65-6dab3d0091f6

yahka.0
2022-08-18 18:27:57.997	info	adding Shelly 2.5 Rolladen groß EG Wohnzimmer with UUID: ff9cfc61-a0df-4375-85ff-9ec8a68d6d5c

yahka.0
2022-08-18 18:27:57.992	info	adding Shelly 2.5 Rolladen klein EG Wohnzimmer with UUID: f9cba3bf-bb49-450a-88ae-502a4a3baeba

yahka.0
2022-08-18 18:27:57.989	info	adding Shelly 1PM Kreuzschaltung EG Flur with UUID: 51662978-f5c3-4d50-9037-e2931f3666c0

yahka.0
2022-08-18 18:27:57.987	info	adding Shelly 1PM Kreuzschaltung OG Flur with UUID: cf95c1d7-30b1-4d26-8315-05c870cfe2f9

yahka.0
2022-08-18 18:27:57.978	info	adding Shelly Dimmer 2 Licht OG Bad with UUID: dd466961-fa5f-4dca-839b-b184b321159d

yahka.0
2022-08-18 18:27:57.967	info	adapter ready, checking config

yahka.0
2022-08-18 18:27:57.943	info	starting. Version 0.13.1 in /opt/iobroker/node_modules/iobroker.yahka, node: v16.17.0, js-controller: 4.0.23

                yahka.0
2022-08-18 09:38:18.682	error	Exception-Code: ERR_ASSERTION: The supplied username () is not valid (expected a format like 'XX:XX:XX:XX:XX:XX' with XX being a valid hexadecimal string). Note that, if you had this accessory already paired with the invalid username, you will need to repair the accessory and reconfigure your services in the Home app. Using an invalid username will lead to unexpected behaviour.

yahka.0
2022-08-18 09:38:18.682	error	AssertionError [ERR_ASSERTION]: The supplied username () is not valid (expected a format like 'XX:XX:XX:XX:XX:XX' with XX being a valid hexadecimal string). Note that, if you had this accessory already paired with the invalid username, you will need to repair the accessory and reconfigure your services in the Home app. Using an invalid username will lead to unexpected behaviour. at Function.AccessoryInfo.assertValidUsername (/opt/iobroker/node_modules/hap-nodejs/src/lib/model/AccessoryInfo.ts:309:12) at Function.AccessoryInfo.load (/opt/iobroker/node_modules/hap-nodejs/src/lib/model/AccessoryInfo.ts:259:19) at Bridge.Accessory.publish (/opt/iobroker/node_modules/hap-nodejs/src/lib/Accessory.ts:1143:41) at devicesToPublish (/opt/iobroker/node_modules/iobroker.yahka/webpack:/yahka.homekit-bridge.ts:27:31) at /opt/iobroker/node_modules/iobroker.yahka/webpack:/yahka.homekit-bridge.ts:73:41 at Array.forEach (<anonymous>) at THomeKitBridge../yahka.homekit-bridge.ts.THomeKitBridge.init (/opt/iobroker/node_modules/iobroker.yahka/webpack:/yahka.homekit-bridge.ts:73:26) at new THomeKitBridge (/opt/iobroker/node_modules/iobroker.yahka/webpack:/yahka.homekit-bridge.ts:20:14) at TIOBrokerAdapter../yahka.ioBroker-adapter.ts.TIOBrokerAdapter.createHomeKitBridges (/opt/iobroker/node_modules/iobroker.yahka/webpack:/yahka.ioBroker-adapter.ts:82:27) at TIOBrokerAdapter../yahka.ioBroker-adapter.ts.TIOBrokerAdapter.adapterReady (/opt/iobroker/node_modules/iobroker.yahka/webpack:/yahka.ioBroker-adapter.ts:56:14)

yahka.0
2022-08-18 09:38:18.682	error	unhandled promise rejection: The supplied username () is not valid (expected a format like 'XX:XX:XX:XX:XX:XX' with XX being a valid hexadecimal string). Note that, if you had this accessory already paired with the invalid username, you will need to repair the accessory and reconfigure your services in the Home app. Using an invalid username will lead to unexpected behaviour.

yahka.0
2022-08-18 09:38:18.681	error	Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().

                Muss ich die Bridge in Homekit löschen und neu hinzufügen?

                
shelly.0
2022-08-18 09:28:59.951	info	[CoAP Server] Listening for packets in the network

shelly.0
2022-08-18 09:28:59.756	info	Starting in CoAP mode.

shelly.0
2022-08-18 09:28:59.519	info	starting. Version 6.0.0 in /opt/iobroker/node_modules/iobroker.shelly, node: v16.17.0, js-controller: 4.0.23

shelly.0
2022-08-18 09:28:51.980	info	Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason

shelly.0
2022-08-18 09:28:51.979	info	terminating

shelly.0
2022-08-18 09:28:51.975	info	Got terminate signal TERMINATE_YOURSELF
                Glasfaser 1 Reply Last reply Reply Quote 0
                • Glasfaser
                  Glasfaser @kaese2002 last edited by

                  @kaese2002 sagte in UnRAID Docker ioBroker Backitup Wiederherstellen:

                  .prinzipiell funktioniert noch nicht viel...

                  Ports freigegeben / weitergeleitet im Container .
                  Sind die angefragten Ip´s ,vom Container aus pingbar

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

                    @glasfaser

                    Ok hab jetzt 2h gespielt und hab jetzt rausgefunden, warum der Yahka adapter permanant neustartet.
                    Da fehlt das ffmpeg-Paket im Container, was man für die Einbindung von Drittanbieter-Kameras in Homekit braucht. Das war vorher am PI4b nur einfach installiert und fehlt natürlich jetzt im Docker.
                    Schalte ich die Kameras aus, funktioniert alles....Das Log bestätigt es auch.
                    Kannst du mir helfen, das im Container zu installieren?

                    
yahka.0
2022-08-18 12:06:55.813	error	Exception-Code: ENOENT: spawn ffmpeg ENOENT

yahka.0
2022-08-18 12:06:55.812	error	Error: spawn ffmpeg ENOENT at Process.ChildProcess._handle.onexit (node:internal/child_process:283:19) at onErrorNT (node:internal/child_process:478:16) at processTicksAndRejections (node:internal/process/task_queues:83:21)

yahka.0
2022-08-18 12:06:55.810	error	uncaught exception: spawn ffmpeg ENOENT
                    K Glasfaser 2 Replies Last reply Reply Quote 0
                    • K
                      kaese2002 @kaese2002 last edited by

                      ok wird hier erklärt

                      https://forum.iobroker.net/topic/37745/iobroker-docker-ffmpeg/5

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

                        @kaese2002

                        https://forum.iobroker.net/topic/37745/iobroker-docker-ffmpeg/4

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

                          @glasfaser hahaha 🙂 ja hab ich auch grad gesehen...

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

                            @kaese2002

                            So schnell bin ich auch nicht ... hast ja dann auch gefunden !

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

                              Läuft...

                              yahka.0
2022-08-18 12:20:48.513	info	publishing camera <new camera 45> on 0.0.0.0 using ciao

yahka.0
2022-08-18 12:20:48.505	info	publishing camera Victure PC730 on 0.0.0.0 using ciao

yahka.0
2022-08-18 12:20:48.459	info	publishing bridge Yahka-0 on 0.0.0.0 using ciao

                              Um es nochmal zusammenzufassen, war mein primärer Fehler der Network Type Bridge in den Optionen.
                              Stellt man hier auf Host um, fällt der ganze Ärger mit den Portweiterleitungen flach. Schaut jetzt am Schluss so aus.

                              Bildschirmfoto 2022-08-18 um 21.24.04.png

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

                                @kaese2002 sagte in UnRAID Docker ioBroker Backitup Wiederherstellen:

                                Läuft...

                                Kannst ja diesen Thread auf "Lesezeichen" setzen ... für später mal ....

                                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

                                639
                                Online

                                32.0k
                                Users

                                80.4k
                                Topics

                                1.3m
                                Posts

                                6
                                32
                                2751
                                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