Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. ioBroker Allgemein
    4. IOBroker reagiert nicht mehr | Shelly Adapter

    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

    IOBroker reagiert nicht mehr | Shelly Adapter

    This topic has been deleted. Only users with topic management privileges can see it.
    • Thomas Braun
      Thomas Braun Most Active @dike1982 last edited by

      @dike1982

      Da kann ich dir nicht weiterhelfen, kenne den Adapter und die Hardware nicht.

      D 2 Replies Last reply Reply Quote 0
      • D
        dike1982 @Thomas Braun last edited by dike1982

        @thomas-braun
        Trotzdem schon mal danke!

        Hat sonst einer eine Idee??

        1 Reply Last reply Reply Quote 0
        • D
          dike1982 @Thomas Braun last edited by dike1982

          @thomas-braun
          Ich brauch leider nochmal Hilfe.
          Ich hab mir gedacht ich lösche den shelly-Adapter und fang mit den Shellys von vorne an.
          Das Löschen hat recht lange gedauert.

          Jetzt habe ich wieder die Time-out Warnungen auf der Oberfläche und es lässt sich quasi nicht bedienen, bzw. alles sehr langsam!!

          2024-01-14 01:36:10.647  - info: host.raspberrypi4 instance system.adapter.shelly.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
2024-01-14 01:36:10.647  - info: host.raspberrypi4 instance system.adapter.shelly.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
2024-01-14 01:37:09.511  - info: host.raspberrypi4 iobroker del shelly.0
2024-01-14 01:37:09.511  - info: host.raspberrypi4 iobroker del shelly.0
2024-01-14 01:37:40.809  - info: host.raspberrypi4 iobroker Delete instance "shelly.0"
2024-01-14 01:37:40.809  - info: host.raspberrypi4 iobroker Delete instance "shelly.0"
2024-01-14 01:37:46.555  - info: host.raspberrypi4 iobroker host.raspberrypi4 Counted 1 instances of shelly.0
2024-01-14 01:37:46.555  - info: host.raspberrypi4 iobroker host.raspberrypi4 Counted 1 instances of shelly.0
2024-01-14 01:37:51.803  - info: host.raspberrypi4 iobroker host.raspberrypi4 Counted 23 devices of shelly.0
2024-01-14 01:37:51.803  - info: host.raspberrypi4 iobroker host.raspberrypi4 Counted 23 devices of shelly.0
2024-01-14 01:37:55.733  - info: host.raspberrypi4 iobroker host.raspberrypi4 Counted 159 channels of shelly.0
2024-01-14 01:37:55.733  - info: host.raspberrypi4 iobroker host.raspberrypi4 Counted 159 channels of shelly.0
2024-01-14 01:37:59.655  - info: host.raspberrypi4 iobroker host.raspberrypi4 Counted 1360 states of shelly.0
2024-01-14 01:37:59.655  - info: host.raspberrypi4 iobroker host.raspberrypi4 Counted 1360 states of shelly.0
2024-01-14 01:38:02.245  - info: host.raspberrypi4 iobroker host.raspberrypi4 Counted 15 states of system.adapter.shelly.0
2024-01-14 01:38:02.245  - info: host.raspberrypi4 iobroker host.raspberrypi4 Counted 15 states of system.adapter.shelly.0
2024-01-14 01:38:02.906  - info: host.raspberrypi4 iobroker host.raspberrypi4 Counted 1134 states (io.shelly.0.*) from states
2024-01-14 01:38:02.906  - info: host.raspberrypi4 iobroker host.raspberrypi4 Counted 1134 states (io.shelly.0.*) from states
2024-01-14 01:38:04.894  - info: host.raspberrypi4 iobroker host.raspberrypi4 Counted 6 states (system.adapter.shelly.0.*) from states
2024-01-14 01:38:04.894  - info: host.raspberrypi4 iobroker host.raspberrypi4 Counted 6 states (system.adapter.shelly.0.*) from states
2024-01-14 01:38:11.587  - info: host.raspberrypi4 iobroker host.raspberrypi4 Counted 2 objects of shelly.0host.raspberrypi4 Deleting 1560 object(s). Be patient...
2024-01-14 01:38:11.587  - info: host.raspberrypi4 iobroker host.raspberrypi4 Counted 2 objects of shelly.0host.raspberrypi4 Deleting 1560 object(s). Be patient...
2024-01-14 01:38:49.188  - info: host.raspberrypi4 iobroker host.raspberrypi4: Only 1400 objects left to be deleted.
2024-01-14 01:38:49.188  - info: host.raspberrypi4 iobroker host.raspberrypi4: Only 1400 objects left to be deleted.
2024-01-14 01:39:59.624  - info: host.raspberrypi4 iobroker host.raspberrypi4: Only 1200 objects left to be deleted.
2024-01-14 01:39:59.624  - info: host.raspberrypi4 iobroker host.raspberrypi4: Only 1200 objects left to be deleted.
2024-01-14 01:40:21.779  - info: host.raspberrypi4 iobroker host.raspberrypi4: Only 1000 objects left to be deleted.
2024-01-14 01:40:21.779  - info: host.raspberrypi4 iobroker host.raspberrypi4: Only 1000 objects left to be deleted.
2024-01-14 01:41:30.214  - info: host.raspberrypi4 iobroker host.raspberrypi4: Only 800 objects left to be deleted.
2024-01-14 01:41:30.214  - info: host.raspberrypi4 iobroker host.raspberrypi4: Only 800 objects left to be deleted.
2024-01-14 01:41:35.629  - info: host.raspberrypi4 iobroker host.raspberrypi4: Only 600 objects left to be deleted.
2024-01-14 01:41:35.629  - info: host.raspberrypi4 iobroker host.raspberrypi4: Only 600 objects left to be deleted.
2024-01-14 01:41:50.581  - info: host.raspberrypi4 iobroker host.raspberrypi4: Only 400 objects left to be deleted.
2024-01-14 01:41:50.581  - info: host.raspberrypi4 iobroker host.raspberrypi4: Only 400 objects left to be deleted.
2024-01-14 01:44:28.905  - info: host.raspberrypi4 iobroker host.raspberrypi4: Only 200 objects left to be deleted.
2024-01-14 01:44:28.905  - info: host.raspberrypi4 iobroker host.raspberrypi4: Only 200 objects left to be deleted.
2024-01-14 01:46:34.239  - info: host.raspberrypi4 object deleted system.adapter.shelly.0
2024-01-14 01:46:34.251  - info: host.raspberrypi4 iobroker host.raspberrypi4 Deleting 1140 state(s). Be patient...
2024-01-14 01:46:34.239  - info: host.raspberrypi4 object deleted system.adapter.shelly.0
2024-01-14 01:46:34.251  - info: host.raspberrypi4 iobroker host.raspberrypi4 Deleting 1140 state(s). Be patient...
2024-01-14 01:47:44.091  - info: host.raspberrypi4 iobroker host.raspberrypi4: Only 1000 states left to be deleted.
2024-01-14 01:47:44.091  - info: host.raspberrypi4 iobroker host.raspberrypi4: Only 1000 states left to be deleted.
2024-01-14 01:48:17.714  - info: host.raspberrypi4 iobroker host.raspberrypi4: Only 800 states left to be deleted.
2024-01-14 01:48:17.714  - info: host.raspberrypi4 iobroker host.raspberrypi4: Only 800 states left to be deleted.
2024-01-14 01:49:33.382  - info: host.raspberrypi4 iobroker host.raspberrypi4: Only 600 states left to be deleted.
2024-01-14 01:49:33.382  - info: host.raspberrypi4 iobroker host.raspberrypi4: Only 600 states left to be deleted.
2024-01-14 01:49:37.528  - info: host.raspberrypi4 iobroker host.raspberrypi4: Only 400 states left to be deleted.
2024-01-14 01:49:37.528  - info: host.raspberrypi4 iobroker host.raspberrypi4: Only 400 states left to be deleted.
2024-01-14 01:52:40.727  - info: host.raspberrypi4 iobroker host.raspberrypi4: Only 200 states left to be deleted.
2024-01-14 01:52:40.727  - info: host.raspberrypi4 iobroker host.raspberrypi4: Only 200 states left to be deleted.
2024-01-14 01:53:11.244  - info: admin.0 (718) <== Disconnect system.user.admin from ::ffff:192.168.115.81 admin
2024-01-14 01:53:11.244  - info: admin.0 (718) <== Disconnect system.user.admin from ::ffff:192.168.115.81 admin
2024-01-14 01:54:05.002  - info: admin.0 (718) failed connection to socket.io from ::ffff:192.168.115.81: Passport was not initialized
2024-01-14 01:54:05.002  - info: admin.0 (718) failed connection to socket.io from ::ffff:192.168.115.81: Passport was not initialized
2024-01-14 01:54:10.253  - info: admin.0 (718) failed connection to socket.io from ::ffff:192.168.115.81: Passport was not initialized
2024-01-14 01:54:10.253  - info: admin.0 (718) failed connection to socket.io from ::ffff:192.168.115.81: Passport was not initialized
2024-01-14 01:55:26.687  - info: host.raspberrypi4 instance system.adapter.ical.0 started with pid 2971
2024-01-14 01:55:26.687  - info: host.raspberrypi4 instance system.adapter.ical.0 started with pid 2971
2024-01-14 01:55:38.919  - warn: ical.0 (2971) slow connection to objects DB. Still waiting ...
2024-01-14 01:55:38.919  - warn: ical.0 (2971) slow connection to objects DB. Still waiting ...
2024-01-14 01:56:04.379  - warn: ical.0 (2971) slow connection to states DB. Still waiting ...
2024-01-14 01:56:04.379  - warn: ical.0 (2971) slow connection to states DB. Still waiting ...
2024-01-14 01:56:48.432  - info: admin.0 (718) <== Disconnect system.user.admin from ::ffff:192.168.115.81 admin
2024-01-14 01:56:48.432  - info: admin.0 (718) <== Disconnect system.user.admin from ::ffff:192.168.115.81 admin
2024-01-14 01:57:05.853  - info: admin.0 (718) failed connection to socket.io from ::ffff:192.168.115.81: Passport was not initialized
2024-01-14 01:57:05.853  - info: admin.0 (718) failed connection to socket.io from ::ffff:192.168.115.81: Passport was not initialized
2024-01-14 01:57:41.889  - info: ical.0 (2971) starting. Version 1.13.3 in /opt/iobroker/node_modules/iobroker.ical, node: v18.19.0, js-controller: 5.0.17
2024-01-14 01:57:41.889  - info: ical.0 (2971) starting. Version 1.13.3 in /opt/iobroker/node_modules/iobroker.ical, node: v18.19.0, js-controller: 5.0.17
2024-01-14 01:57:44.516  - info: ical.0 (2971) processing URL: Müllkalender https://calendar.google.com/calendar/ical/3a2097d8a678bc40972b4f2df3a70416e549cabb23d727a3bddacc2001f63aa7%40group.calendar.google.com/private-f6d975016103767eb05b6b0c059afa62/basic.ics
2024-01-14 01:57:44.516  - info: ical.0 (2971) processing URL: Müllkalender https://calendar.google.com/calendar/ical/3a2097d8a678bc40972b4f2df3a70416e549cabb23d727a3bddacc2001f63aa7%40group.calendar.google.com/private-f6d975016103767eb05b6b0c059afa62/basic.ics
2024-01-14 01:58:13.682  - info: admin.0 (718) ==> Connected system.user.admin from ::ffff:192.168.115.81
2024-01-14 01:58:13.682  - info: admin.0 (718) ==> Connected system.user.admin from ::ffff:192.168.115.81
2024-01-14 01:58:19.894  - info: ical.0 (2971) Terminated (NO_ERROR): Without reason
2024-01-14 01:58:19.894  - info: ical.0 (2971) Terminated (NO_ERROR): Without reason
2024-01-14 01:58:21.662  - info: host.raspberrypi4 instance system.adapter.ical.0 terminated with code 0 (NO_ERROR)
2024-01-14 01:58:21.662  - info: host.raspberrypi4 instance system.adapter.ical.0 terminated with code 0 (NO_ERROR)
2024-01-14 01:59:47.928  - info: host.raspberrypi4 iobroker exit 0
2024-01-14 01:59:47.928  - info: host.raspberrypi4 iobroker exit 0
2024-01-14 02:00:00.084  - info: host.raspberrypi4 instance system.adapter.ical.0 started with pid 2990
2024-01-14 02:00:00.084  - info: host.raspberrypi4 instance system.adapter.ical.0 started with pid 2990
2024-01-14 02:00:20.340  - info: ical.0 (2990) starting. Version 1.13.3 in /opt/iobroker/node_modules/iobroker.ical, node: v18.19.0, js-controller: 5.0.17
2024-01-14 02:00:20.340  - info: ical.0 (2990) starting. Version 1.13.3 in /opt/iobroker/node_modules/iobroker.ical, node: v18.19.0, js-controller: 5.0.17
2024-01-14 02:00:33.511  - info: ical.0 (2990) processing URL: Müllkalender https://calendar.google.com/calendar/ical/3a2097d8a678bc40972b4f2df3a70416e549cabb23d727a3bddacc2001f63aa7%40group.calendar.google.com/private-f6d975016103767eb05b6b0c059afa62/basic.ics
2024-01-14 02:00:33.511  - info: ical.0 (2990) processing URL: Müllkalender https://calendar.google.com/calendar/ical/3a2097d8a678bc40972b4f2df3a70416e549cabb23d727a3bddacc2001f63aa7%40group.calendar.google.com/private-f6d975016103767eb05b6b0c059afa62/basic.ics
2024-01-14 02:01:08.408  - info: ical.0 (2990) Terminated (NO_ERROR): Without reason
2024-01-14 02:01:08.408  - info: ical.0 (2990) Terminated (NO_ERROR): Without reason
2024-01-14 02:01:09.834  - info: host.raspberrypi4 instance system.adapter.ical.0 terminated with code 0 (NO_ERROR)
2024-01-14 02:01:09.834  - info: host.raspberrypi4 instance system.adapter.ical.0 terminated with code 0 (NO_ERROR)
2024-01-14 02:02:52.339  - info: admin.0 (718) <== Disconnect system.user.admin from ::ffff:192.168.115.81 admin
2024-01-14 02:02:52.339  - info: admin.0 (718) <== Disconnect system.user.admin from ::ffff:192.168.115.81 admin
2024-01-14 02:03:06.659  - info: admin.0 (718) ==> Connected system.user.admin from ::ffff:192.168.115.81
2024-01-14 02:03:06.659  - info: admin.0 (718) ==> Connected system.user.admin from ::ffff:192.168.115.81
          D 1 Reply Last reply Reply Quote 0
          • D
            dike1982 @dike1982 last edited by

            Hat sich erledigt.
            Ich hab nochmal ein full-upgrade gemacht.

            Jetzt läuft alles inkl. Shelly.

            D 1 Reply Last reply Reply Quote 0
            • D
              dike1982 @dike1982 last edited by

              @Thomas-Braun
              Leider ist das Thema nicht erledigt.
              Der Shellyadater legt mir immer noch das System lahm.
              Ich habe deswegen ein Issue auf Github aufgemacht, der ENtwickler meinte zu mir:

              "deine Objekt- und State-DB macht Probleme"

              Keine Ahnung was das bedeutet oder wie ich das fixe.

              Würde aber dazu passen, dass ich mit einem Skript auch Probleme habe bei welchem aus einem Fensterkontakt der STATE nicht richtig ausgelesen werden kann und das Skript deswegen Fehler bringt.

              Eine Idee wie ich das löse?

              B 1 Reply Last reply Reply Quote 0
              • B
                bommel_030 @dike1982 last edited by

                @dike1982
                Schuss ins Blaue... Du hast den Device-Watcher Adapter installiert. Deaktivier den Mal... Reboot tut gut... Und dann Mal weiter beobachten. Hab die Kausalkette noch nicht durchblickt, hatte es aber schon 4-5x erfolgreich als Lösung...

                D 1 Reply Last reply Reply Quote 0
                • D
                  dike1982 @bommel_030 last edited by

                  @bommel_030
                  Device-Watcher ist tatsächlich installiert, aber gestoppt.
                  Ich hau den mal runter und mach einen reboot.

                  Wie kann ich feststellen ob die Objekt- und State-DB sauber läuft?

                  B 1 Reply Last reply Reply Quote 0
                  • B
                    bommel_030 @dike1982 last edited by

                    @dike1982
                    Oben im diag hatte ich nur gesehen dass der noch aktiv war. Ich habe noch keine Zeit gehabt das genauer zu untersuchen, daher nur Vermutung:
                    Der Shelly Adapter gibt (nach einem mir nicht ersichtlichen Schema) diese MQTT Fehlermeldungen raus. Darauf reagiert der device-watcher, darauf reagiert Shelly und darauf wieder der device-watcher und das erzeugt eine Schleife die mein System von üblicherweise 0,3 auf > 4 katapultiert hat.
                    Nach deaktivieren von device-watcher wieder 0,3. Ob dir die Überlast dein Dateisystem zerstört hat und wie das zu reparieren geht kann ich dir leider nicht beantworten.

                    D 3 Replies Last reply Reply Quote 0
                    • D
                      dike1982 @bommel_030 last edited by

                      @bommel_030
                      Alles klar ich schau mal wenn ich daheim bin!

                      1 Reply Last reply Reply Quote 0
                      • D
                        dike1982 @bommel_030 last edited by

                        @bommel_030
                        was meinst du mit 0,3 und 4?

                        B 1 Reply Last reply Reply Quote 0
                        • D
                          dike1982 @bommel_030 last edited by dike1982

                          @bommel_030
                          Könnte sein, dass das was gebracht hat.
                          Ich habe den Device-Watscher gelöscht und ein fullupgrade auf Kommandoebene gemacht.
                          Habe dann 7 von 24 Shellys wieder das MQTT aktiviert und den Shellyadapter gestartet.
                          Log ist ruhig. Lässt sich alles bedienen.
                          Host bei 9 % CPU.

                          Ich warte mal noch ein paar stunden und nehme dann die restlichen Shelly auch wieder dazu!

                          1 Reply Last reply Reply Quote 0
                          • B
                            bommel_030 @dike1982 last edited by

                            @dike1982
                            Meinte den Load average. Ganz grob, bei allem größer 1 muss irgendein Prozeß warten weil RAM, CPU etc. Ausgelastet sind.

                            D 1 Reply Last reply Reply Quote 0
                            • D
                              dike1982 @bommel_030 last edited by

                              @bommel_030
                              Nochmal blöde Frage:
                              Wo sehe ich den?
                              Sorry bin Anfänger!

                              B 1 Reply Last reply Reply Quote 0
                              • B
                                bommel_030 @dike1982 last edited by

                                @dike1982
                                Viele Wege führen nach Rom...
                                Ich nehm die Konsole und schau in htop nach.
                                Screenshot_20240115_191010_JuiceSSH.jpg
                                Je nach Betriebssystem ist das ggf. Nicht vorhanden, lässt sich aber einfach nachinstallieren oder in der Konsole top statt htop. Ist ne abgespeckte Version und eigentlich überall vorhanden.

                                D 1 Reply Last reply Reply Quote 0
                                • D
                                  dike1982 @bommel_030 last edited by

                                  @bommel_030
                                  Danke.
                                  htop klappt.

                                  habe zischen 0,20 und 0,4

                                  D 1 Reply Last reply Reply Quote 0
                                  • D
                                    dike1982 @dike1982 last edited by

                                    Also bis jetzt läuft es stabil.
                                    Vielen Dank.

                                    Aber was mach ich jetzt mit dem Device-Watcher?

                                    1 Reply Last reply Reply Quote 0
                                    • haus-automatisierung
                                      haus-automatisierung Developer Most Active @dike1982 last edited by

                                      @dike1982 sagte in IOBroker reagiert nicht mehr | Shelly Adapter:

                                      [MQTT] Unable to get mqttprefix of client with id "shelly1pmmini-543204aaa1f4"

                                      Das ist leider ein Problem mit der aktuellsten Firmware auf den Shellies. Ich konnte das bisher nur leider nicht reproduzieren.

                                      Ein paar deiner Shellies haben aber die falschen Zugangsdaten hinterlegt:

                                      [MQTT] Wrong MQTT authentification of client "shelly1pmmini-543204abcca8"

                                      D 1 Reply Last reply Reply Quote 0
                                      • D
                                        dike1982 @haus-automatisierung last edited by

                                        @haus-automatisierung
                                        Danke für die Info.
                                        Die falschen Zugangsdaten habe ich behoben. Ich bekomme jetzt keine Fehler mehr im Log, habe aber den Device-Wacher nach wie vor aus! Was etwas blöd ist!

                                        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

                                        825
                                        Online

                                        31.9k
                                        Users

                                        80.1k
                                        Topics

                                        1.3m
                                        Posts

                                        5
                                        42
                                        2155
                                        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