Skip to content
  • Home
  • Aktuell
  • Tags
  • 0 Ungelesen 0
  • Kategorien
  • Unreplied
  • Beliebt
  • GitHub
  • Docu
  • Hilfe
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Standard: (Kein Skin)
  • Kein Skin
Einklappen
ioBroker Logo

Community Forum

donate donate
  1. ioBroker Community Home
  2. Deutsch
  3. Einsteigerfragen
  4. Einbindung von Geräten
  5. Shellys per mqtt keine Verbindung

NEWS

  • UPDATE 31.10.: Amazon Alexa - ioBroker Skill läuft aus ?
    apollon77A
    apollon77
    48
    3
    8.5k

  • Monatsrückblick – September 2025
    BluefoxB
    Bluefox
    13
    1
    2.0k

  • Neues Video "KI im Smart Home" - ioBroker plus n8n
    BluefoxB
    Bluefox
    16
    1
    2.7k

Shellys per mqtt keine Verbindung

Geplant Angeheftet Gesperrt Verschoben Einbindung von Geräten
61 Beiträge 5 Kommentatoren 5.6k Aufrufe 3 Watching
  • Älteste zuerst
  • Neuste zuerst
  • Meiste Stimmen
Antworten
  • In einem neuen Thema antworten
Anmelden zum Antworten
Dieses Thema wurde gelöscht. Nur Nutzer mit entsprechenden Rechten können es sehen.
  • A Accuface

    @homoran said in Shellys per mqtt keine Verbindung:

    @accuface sagte in Shellys per mqtt keine Verbindung:

    Weil das Forum mir dass sagt.

    was?
    Du sollst ja nicht den ganzen Tag posten.

    nur die Zeilen nach Restart der Instanz

     2024-10-15 19:16:52.154 - info: admin.0 (802) <== Disconnect system.user.admin from ::ffff:192.168.178.22 admin
    2024-10-15 19:16:58.199 - info: admin.0 (802) ==> Connected system.user.admin from ::ffff:192.168.178.22
    2024-10-15 19:19:32.829 - info: admin.0 (802) <== Disconnect system.user.admin from ::ffff:192.168.178.22 admin
    2024-10-15 19:20:30.707 - info: admin.0 (802) terminating http server on port 8081
    2024-10-15 19:20:30.706 - info: host.raspberrypi5 received SIGTERM
    2024-10-15 19:20:30.710 - info: trashschedule.0 (1175) cleaned everything up...
    2024-10-15 19:20:30.716 - info: javascript.0 (864) Stopping script script.js.Skript_1
    2024-10-15 19:20:30.720 - info: backitup.0 (941) cleaned everything up...
    2024-10-15 19:20:30.728 - info: cloud.0 (959) Connection changed: disconnect
    2024-10-15 19:20:30.708 - info: host.raspberrypi5 stopInstance system.adapter.admin.0 (force=false, process=true)
    2024-10-15 19:20:30.708 - info: host.raspberrypi5 stopInstance system.adapter.javascript.0 (force=false, process=true)
    2024-10-15 19:20:30.708 - info: host.raspberrypi5 stopInstance system.adapter.scenes.0 (force=false, process=true)
    2024-10-15 19:20:30.709 - info: host.raspberrypi5 stopInstance system.adapter.sql.0 (force=false, process=true)
    2024-10-15 19:20:30.710 - info: host.raspberrypi5 stopInstance system.adapter.history.0 (force=false, process=true)
    2024-10-15 19:20:30.713 - info: host.raspberrypi5 stopInstance system.adapter.whatsapp-cmb.0 (force=false, process=true)
    2024-10-15 19:20:30.713 - info: host.raspberrypi5 stopInstance system.adapter.backitup.0 (force=false, process=true)
    2024-10-15 19:20:30.714 - info: host.raspberrypi5 stopInstance system.adapter.cloud.0 (force=false, process=true)
    2024-10-15 19:20:30.714 - info: host.raspberrypi5 stopInstance system.adapter.weatherunderground.0 (force=false, process=false)
    2024-10-15 19:20:30.714 - info: host.raspberrypi5 stopInstance system.adapter.ping.0 (force=false, process=false)
    2024-10-15 19:20:30.714 - info: host.raspberrypi5 stopInstance system.adapter.fronius.0 (force=false, process=true)
    2024-10-15 19:20:30.715 - info: host.raspberrypi5 stopInstance system.adapter.fronius.1 (force=false, process=true)
    2024-10-15 19:20:30.715 - info: host.raspberrypi5 stopInstance system.adapter.synology.0 (force=false, process=true)
    2024-10-15 19:20:30.715 - info: host.raspberrypi5 stopInstance system.adapter.ical.0 (force=false, process=false)
    2024-10-15 19:20:30.716 - info: host.raspberrypi5 stopInstance canceled schedule system.adapter.ical.0
    2024-10-15 19:20:30.716 - info: host.raspberrypi5 stopInstance system.adapter.feiertage.0 (force=false, process=false)
    2024-10-15 19:20:30.716 - info: host.raspberrypi5 stopInstance system.adapter.tankerkoenig.0 (force=false, process=true)
    2024-10-15 19:20:30.716 - info: host.raspberrypi5 stopInstance system.adapter.shelly.0 (force=false, process=true)
    2024-10-15 19:20:30.716 - info: host.raspberrypi5 stopInstance system.adapter.discovery.0 (force=false, process=true)
    2024-10-15 19:20:30.717 - info: host.raspberrypi5 stopInstance system.adapter.iot.0 (force=false, process=true)
    2024-10-15 19:20:30.717 - info: host.raspberrypi5 stopInstance system.adapter.web.0 (force=false, process=true)
    2024-10-15 19:20:30.717 - info: host.raspberrypi5 stopInstance system.adapter.vis-2.0 (force=false, process=true)
    2024-10-15 19:20:30.717 - info: host.raspberrypi5 stopInstance system.adapter.echarts.0 (force=false, process=true)
    2024-10-15 19:20:30.718 - info: host.raspberrypi5 stopInstance system.adapter.iqontrol.0 (force=false, process=false)
    2024-10-15 19:20:30.718 - info: host.raspberrypi5 stopInstance system.adapter.jarvis.0 (force=false, process=true)
    2024-10-15 19:20:30.718 - info: host.raspberrypi5 stopInstance system.adapter.fronius-solarweb.0 (force=false, process=true)
    2024-10-15 19:20:30.718 - info: host.raspberrypi5 stopInstance system.adapter.trashschedule.0 (force=false, process=true)
    2024-10-15 19:20:30.718 - info: host.raspberrypi5 stopInstance system.adapter.vis.0 (force=false, process=false)
    2024-10-15 19:20:30.719 - info: host.raspberrypi5 stopInstance system.adapter.vis-metro.0 (force=false, process=false)
    2024-10-15 19:20:30.719 - info: host.raspberrypi5 stopInstance system.adapter.dwd.0 (force=false, process=false)
    2024-10-15 19:20:30.719 - info: host.raspberrypi5 stopInstance system.adapter.vis-timeandweather.0 (force=false, process=false)
    2024-10-15 19:20:30.719 - info: jarvis.0 (1145) Adapter stopped und unloaded.
    2024-10-15 19:20:30.736 - warn: web.0 (1100) setTimeout called, but adapter is shutting down
    2024-10-15 19:20:30.766 - info: admin.0 (802) Got terminate signal TERMINATE_YOURSELF
    2024-10-15 19:20:30.767 - info: javascript.0 (864) Got terminate signal TERMINATE_YOURSELF
    2024-10-15 19:20:30.768 - info: whatsapp-cmb.0 (926) Got terminate signal TERMINATE_YOURSELF
    2024-10-15 19:20:30.769 - info: scenes.0 (880) Got terminate signal TERMINATE_YOURSELF
    2024-10-15 19:20:30.771 - info: backitup.0 (941) Got terminate signal TERMINATE_YOURSELF
    2024-10-15 19:20:30.770 - info: cloud.0 (959) Got terminate signal TERMINATE_YOURSELF
    2024-10-15 19:20:30.772 - info: fronius.1 (989) Got terminate signal TERMINATE_YOURSELF
    2024-10-15 19:20:30.772 - info: fronius.0 (974) Got terminate signal TERMINATE_YOURSELF
    2024-10-15 19:20:30.773 - info: synology.0 (1010) Got terminate signal TERMINATE_YOURSELF
    2024-10-15 19:20:30.785 - info: iot.0 (1085) Connection changed: disconnect
    2024-10-15 19:20:30.789 - info: sql.0 (895) terminating
    2024-10-15 19:20:30.790 - info: trashschedule.0 (1175) terminating
    2024-10-15 19:20:30.790 - info: javascript.0 (864) terminating
    2024-10-15 19:20:30.790 - info: admin.0 (802) terminating
    2024-10-15 19:20:30.794 - info: backitup.0 (941) terminating
    2024-10-15 19:20:30.791 - info: trashschedule.0 (1175) Terminated (NO_ERROR): Without reason
    2024-10-15 19:20:30.795 - info: backitup.0 (941) Terminated (NO_ERROR): Without reason
    2024-10-15 19:20:30.790 - info: history.0 (911) terminating
    2024-10-15 19:20:30.792 - info: sql.0 (895) Terminated (NO_ERROR): Without reason
    2024-10-15 19:20:30.798 - info: tankerkoenig.0 (1040) Got terminate signal TERMINATE_YOURSELF
    2024-10-15 19:20:30.798 - info: jarvis.0 (1145) Got terminate signal TERMINATE_YOURSELF
    2024-10-15 19:20:30.799 - info: trashschedule.0 (1175) Got terminate signal TERMINATE_YOURSELF
    2024-10-15 19:20:30.796 - info: discovery.0 (1070) Got terminate signal TERMINATE_YOURSELF
    2024-10-15 19:20:30.794 - info: fronius-solarweb.0 (1160) terminating
    2024-10-15 19:20:30.786 - info: iot.0 (1085) Connection lost
    2024-10-15 19:20:30.802 - info: tankerkoenig.0 (1040) terminating
    2024-10-15 19:20:30.793 - info: history.0 (911) Terminated (NO_ERROR): Without reason
    2024-10-15 19:20:30.800 - info: echarts.0 (1130) Got terminate signal TERMINATE_YOURSELF
    2024-10-15 19:20:30.791 - info: admin.0 (802) Terminated (NO_ERROR): Without reason
    2024-10-15 19:20:30.805 - info: vis-2.0 (1115) terminating
    2024-10-15 19:20:30.791 - info: javascript.0 (864) Terminated (NO_ERROR): Without reason
    2024-10-15 19:20:30.792 - info: synology.0 (1010) terminating
    2024-10-15 19:20:30.801 - info: shelly.0 (1286) Got terminate signal TERMINATE_YOURSELF
    2024-10-15 19:20:30.807 - info: web.0 (1100) Got terminate signal TERMINATE_YOURSELF
    2024-10-15 19:20:30.793 - info: synology.0 (1010) Terminated (NO_ERROR): Without reason
    2024-10-15 19:20:30.803 - info: iot.0 (1085) terminating
    2024-10-15 19:20:30.804 - info: iot.0 (1085) Terminated (NO_ERROR): Without reason
    2024-10-15 19:20:30.805 - info: iot.0 (1085) Got terminate signal TERMINATE_YOURSELF
    2024-10-15 19:20:30.803 - info: tankerkoenig.0 (1040) Terminated (NO_ERROR): Without reason
    2024-10-15 19:20:30.801 - info: fronius-solarweb.0 (1160) Terminated (NO_ERROR): Without reason
    2024-10-15 19:20:30.809 - info: fronius-solarweb.0 (1160) Got terminate signal TERMINATE_YOURSELF
    
    A Offline
    A Offline
    Accuface
    schrieb am zuletzt editiert von Homoran
    #21

    Hier mal ein Auszug zum Shelly

     2024-10-15 19:21:46.751  - info: host.raspberrypi5 instance system.adapter.shelly.0 in version "8.2.1" started with pid 1091
    2024-10-15 19:21:47.898  - info: shelly.0 (1091) starting. Version 8.2.1 in /opt/iobroker/node_modules/iobroker.shelly, node: v20.18.0, js-controller: 6.0.11
    2024-10-15 19:21:48.050  - info: shelly.0 (1091) Starting in MQTT mode. Listening on 0.0.0.0:1882 (QoS 0)
    2024-10-15 19:21:49.437  - info: shelly.0 (1091) [MQTT] Device with client id "shellyplus1-cc7b5c85af80" connected!
    2024-10-15 19:21:50.765  - info: host.raspberrypi5 instance system.adapter.discovery.0 in version "5.0.0" started with pid 1106
    2024-10-15 19:21:51.563  - info: discovery.0 (1106) starting. Version 5.0.0 in /opt/iobroker/node_modules/iobroker.discovery, node: v20.18.0, js-controller: 6.0.11
    2024-10-15 19:21:52.504  - info: shelly.0 (1091) [MQTT] Device with client id "shellyplus1pm-10061cca8844" connected!
    2024-10-15 19:21:52.601  - info: shelly.0 (1091) [MQTT] Device with client id "shellyplus1pm-cc7b5c0dd95c" connected!
    2024-10-15 19:21:52.692  - info: shelly.0 (1091) [MQTT] Device with client id "shellyplus1pm-10061ccb0c48" connected!
    2024-10-15 19:21:53.444  - info: shelly.0 (1091) [MQTT] Device with client id "shellyplus1pm-d4d4daeb2ddc" connected!
    2024-10-15 19:21:53.610  - info: shelly.0 (1091) [MQTT] Device with client id "shellyplus1pm-10061ccad010" connected!
    2024-10-15 19:21:54.759  - info: host.raspberrypi5 instance system.adapter.iot.0 in version "3.3.0" started with pid 1121
    2024-10-15 19:21:55.275  - info: shelly.0 (1091) [MQTT] Device with client id "shellyplus1pm-fcb46727891c" connected!
    2024-10-15 19:21:56.069  - info: iot.0 (1121) starting. Version 3.3.0 in /opt/iobroker/node_modules/iobroker.iot, node: v20.18.0, js-controller: 6.0.11
    2024-10-15 19:21:56.107  - info: iot.0 (1121) Connecting with a18wym7vjdl22g.iot.eu-west-1.amazonaws.com
    2024-10-15 19:21:56.554  - info: iot.0 (1121) Connection changed: connect "bernd_order_gmx_de"
    2024-10-15 19:21:56.966  - info: shelly.0 (1091) [MQTT] Device with client id "shellyplus1pm-d4d4da35853c" connected!
    2024-10-15 19:21:58.507  - info: shelly.0 (1091) [MQTT] Device with client id "shellyplus1pm-b0b21c1b4e14" connected!
    2024-10-15 19:21:58.750  - info: host.raspberrypi5 instance system.adapter.web.0 in version "6.2.5" started with pid 1136
    2024-10-15 19:21:59.803  - info: web.0 (1136) starting. Version 6.2.5 in /opt/iobroker/node_modules/iobroker.web, node: v20.18.0, js-controller: 6.0.11
    2024-10-15 19:22:00.220  - info: web.0 (1136) socket.io server listening on port 8082
    2024-10-15 19:22:00.223  - info: web.0 (1136) http server listening on port 8082
    2024-10-15 19:22:02.751  - info: host.raspberrypi5 instance system.adapter.vis-2.0 in version "2.9.32" started with pid 1151
    2024-10-15 19:22:03.560  - info: vis-2.0 (1151) starting. Version 2.9.32 in /opt/iobroker/node_modules/iobroker.vis-2, node: v20.18.0, js-controller: 6.0.11
    2024-10-15 19:22:03.764  - info: vis-2.0 (1151) vis-2 license is OK.
    2024-10-15 19:22:06.740  - info: host.raspberrypi5 instance system.adapter.echarts.0 in version "1.9.2" started with pid 1166
    2024-10-15 19:22:07.443  - info: echarts.0 (1166) starting. Version 1.9.2 in /opt/iobroker/node_modules/iobroker.echarts, node: v20.18.0, js-controller: 6.0.11
    2024-10-15 19:22:10.783  - info: host.raspberrypi5 instance system.adapter.jarvis.0 in version "3.1.8" started with pid 1181
    2024-10-15 19:22:12.296  - info: jarvis.0 (1181) starting. Version 3.1.8 in /opt/iobroker/node_modules/iobroker.jarvis, node: v20.18.0, js-controller: 6.0.11
    2024-10-15 19:22:12.312  - info: jarvis.0 (1181) No Backup found for layout, thus backing up initially.
    2024-10-15 19:22:12.313  - info: jarvis.0 (1181) No Backup found for scripts, thus backing up initially.
    2024-10-15 19:22:12.313  - info: jarvis.0 (1181) No Backup found for styles, thus backing up initially.
    2024-10-15 19:22:12.314  - info: jarvis.0 (1181) No Backup found for widgets, thus backing up initially.
    2024-10-15 19:22:12.365  - info: jarvis.0 (1181) Connection: WebSocket opened on port 8400 using http...
    2024-10-15 19:22:12.373  - info: jarvis.0 (1181) Found Backups for devices.
    2024-10-15 19:22:12.374  - info: jarvis.0 (1181) Found Backups for settings.
    2024-10-15 19:22:14.767  - info: host.raspberrypi5 instance system.adapter.fronius-solarweb.0 in version "0.0.3" started with pid 1196
    2024-10-15 19:22:15.644  - info: fronius-solarweb.0 (1196) starting. Version 0.0.3 in /opt/iobroker/node_modules/iobroker.fronius-solarweb, node: v20.18.0, js-controller: 6.0.11
    2024-10-15 19:22:17.092  - info: fronius-solarweb.0 (1196) Disable Pro Endpoints
    2024-10-15 19:22:17.093  - info: fronius-solarweb.0 (1196) {"responseError":3503,"responseMessage":"Not a Pro PV system."}
    2024-10-15 19:22:18.775  - info: host.raspberrypi5 instance system.adapter.trashschedule.0 in version "3.3.0" started with pid 1211
    2024-10-15 19:22:19.636  - info: trashschedule.0 (1211) starting. Version 3.3.0 in /opt/iobroker/node_modules/iobroker.trashschedule, node: v20.18.0, js-controller: 6.0.11
    2024-10-15 19:22:19.687  - info: trashschedule.0 (1211) [onReady] starting with source "ical" -> ical
    2024-10-15 19:22:19.732  - info: trashschedule.0 (1211) [ical] configured ical preview is 31 days (until 15.11.2024) - increase this value to find more events in the future
    2024-10-15 19:22:19.732  - info: trashschedule.0 (1211) [ical] found configured ical event "Vacation" without "display" flag. Activate the display flag on this entry if this is a relevant "trash event".
    2024-10-15 19:22:23.433  - info: vis.0 (1226) starting. Version 1.5.6 in /opt/iobroker/node_modules/iobroker.vis, node: v20.18.0, js-controller: 6.0.11
    2024-10-15 19:22:24.553  - info: cloud.0 (969) Trying to connect as system.user.admin to cloud
    2024-10-15 19:22:24.703  - info: cloud.0 (969) Connection changed: connect
    2024-10-15 19:22:27.486  - info: vis.0 (1226) Terminated (NO_ERROR): Without reason
    2024-10-15 19:22:28.021  - info: host.raspberrypi5 instance system.adapter.vis.0 terminated while should be started once
    2024-10-15 19:22:35.020  - info: shelly.0 (1091) [MQTT] Device with client id "shellyplus1-e465b8f46ac4" connected!
    2024-10-15 19:22:37.498  - info: shelly.0 (1091) [MQTT] Device with client id "shellyplus1pm-10061ccb9fc0" connected!
    2024-10-15 19:24:09.673  - info: host.raspberrypi5 stopInstance system.adapter.shelly.0 (force=false, process=true)
    2024-10-15 19:24:09.678  - info: shelly.0 (1091) Got terminate signal TERMINATE_YOURSELF
    2024-10-15 19:24:09.681  - info: shelly.0 (1091) terminating
    2024-10-15 19:24:09.681  - info: shelly.0 (1091) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
    2024-10-15 19:24:09.743  - info: host.raspberrypi5 stopInstance system.adapter.shelly.0 send kill signal
    2024-10-15 19:24:10.182  - info: shelly.0 (1091) terminating
    2024-10-15 19:24:10.211  - info: host.raspberrypi5 instance system.adapter.shelly.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
    2024-10-15 19:24:13.364  - info: host.raspberrypi5 instance system.adapter.shelly.0 in version "8.2.1" started with pid 1241
    2024-10-15 19:24:13.971  - debug: shelly.0 (1241) Redis Objects: Use Redis connection: 127.0.0.1:9001
    2024-10-15 19:24:13.986  - debug: shelly.0 (1241) Objects client ready ... initialize now
    2024-10-15 19:24:13.986  - debug: shelly.0 (1241) Objects create System PubSub Client
    2024-10-15 19:24:13.987  - debug: shelly.0 (1241) Objects create User PubSub Client
    2024-10-15 19:24:14.007  - debug: shelly.0 (1241) Objects client initialize lua scripts
    2024-10-15 19:24:14.010  - debug: shelly.0 (1241) Objects connected to redis: 127.0.0.1:9001
    2024-10-15 19:24:14.024  - debug: shelly.0 (1241) Redis States: Use Redis connection: 127.0.0.1:9000
    2024-10-15 19:24:14.030  - debug: shelly.0 (1241) States create System PubSub Client
    2024-10-15 19:24:14.031  - debug: shelly.0 (1241) States create User PubSub Client
    2024-10-15 19:24:14.082  - debug: shelly.0 (1241) States connected to redis: 127.0.0.1:9000
    2024-10-15 19:24:14.099  - debug: shelly.0 (1241) Plugin sentry Initialize Plugin (enabled=true)
    2024-10-15 19:24:14.294  - info: shelly.0 (1241) starting. Version 8.2.1 in /opt/iobroker/node_modules/iobroker.shelly, node: v20.18.0, js-controller: 6.0.11
    2024-10-15 19:24:14.436  - debug: shelly.0 (1241) [onlineCheck] Checking shellyplus1#cc7b5c85af80#1 on 192.168.178.29:80
    2024-10-15 19:24:14.456  - debug: shelly.0 (1241) [deviceStatusUpdate] shellyplus1#cc7b5c85af80#1: true
    2024-10-15 19:24:14.457  - debug: shelly.0 (1241) [onlineCheck] Checking shellyplus1pm#10061ccad010#1 on 192.168.178.40:80
    2024-10-15 19:24:14.467  - debug: shelly.0 (1241) [deviceStatusUpdate] shellyplus1pm#10061ccad010#1: true
    2024-10-15 19:24:14.468  - debug: shelly.0 (1241) [onlineCheck] Checking shellyplus1pm#cc7b5c0dd95c#1 on 192.168.178.33:80
    2024-10-15 19:24:14.478  - debug: shelly.0 (1241) [onlineCheck] Checking shellyplus1pm#d4d4da35853c#1 on 192.168.178.38:80
    2024-10-15 19:24:14.479  - debug: shelly.0 (1241) [onlineCheck] Checking shellyplus1pm#10061ccb9fc0#1 on 192.168.178.63:80
    2024-10-15 19:24:14.480  - debug: shelly.0 (1241) [deviceStatusUpdate] shellyplus1pm#cc7b5c0dd95c#1: true
    2024-10-15 19:24:14.483  - debug: shelly.0 (1241) [deviceStatusUpdate] Online devices: ["shellyplus1#cc7b5c85af80#1"]
    2024-10-15 19:24:14.489  - debug: shelly.0 (1241) [deviceStatusUpdate] shellyplus1pm#d4d4da35853c#1: true
    2024-10-15 19:24:14.490  - debug: shelly.0 (1241) [deviceStatusUpdate] shellyplus1pm#10061ccb9fc0#1: true
    2024-10-15 19:24:14.491  - debug: shelly.0 (1241) [onlineCheck] Checking shellyplus1pm#d4d4daeb2ddc#1 on 192.168.178.35:80
    2024-10-15 19:24:14.499  - debug: shelly.0 (1241) [deviceStatusUpdate] shellyplus1pm#d4d4daeb2ddc#1: true
    2024-10-15 19:24:14.514  - debug: shelly.0 (1241) [onlineCheck] Checking shellyplus1pm#10061ccb0c48#1 on 192.168.178.39:80
    2024-10-15 19:24:14.515  - debug: shelly.0 (1241) [deviceStatusUpdate] Online devices: ["shellyplus1#cc7b5c85af80#1","shellyplus1pm#10061ccad010#1"]
    2024-10-15 19:24:14.525  - debug: shelly.0 (1241) [deviceStatusUpdate] shellyplus1pm#10061ccb0c48#1: true
    2024-10-15 19:24:14.525  - debug: shelly.0 (1241) [onlineCheck] Checking shellyplus1pm#10061cca8844#1 on 192.168.178.32:80
    2024-10-15 19:24:14.535  - debug: shelly.0 (1241) [deviceStatusUpdate] shellyplus1pm#10061cca8844#1: true
    2024-10-15 19:24:14.537  - debug: shelly.0 (1241) [deviceStatusUpdate] Online devices: ["shellyplus1#cc7b5c85af80#1","shellyplus1pm#10061ccad010#1","shellyplus1pm#cc7b5c0dd95c#1"]
    2024-10-15 19:24:14.539  - debug: shelly.0 (1241) [onlineCheck] Checking shellyplus1pm#fcb46727891c#1 on 192.168.178.26:80
    2024-10-15 19:24:14.550  - debug: shelly.0 (1241) [deviceStatusUpdate] shellyplus1pm#fcb46727891c#1: true
    2024-10-15 19:24:14.553  - debug: shelly.0 (1241) [onlineCheck] Checking shellyplus1pm#b0b21c1b4e14#1 on 192.168.178.34:80
    2024-10-15 19:24:14.554  - debug: shelly.0 (1241) [deviceStatusUpdate] Online devices: ["shellyplus1#cc7b5c85af80#1","shellyplus1pm#10061ccad010#1","shellyplus1pm#cc7b5c0dd95c#1","shellyplus1pm#d4d4da35853c#1"]
    2024-10-15 19:24:14.556  - debug: shelly.0 (1241) [deviceStatusUpdate] Online devices: ["shellyplus1#cc7b5c85af80#1","shellyplus1pm#10061ccad010#1","shellyplus1pm#cc7b5c0dd95c#1","shellyplus1pm#d4d4da35853c#1","shellyplus1pm#10061ccb9fc0#1"]
    2024-10-15 19:24:14.557  - debug: shelly.0 (1241) [deviceStatusUpdate] Online devices: ["shellyplus1#cc7b5c85af80#1","shellyplus1pm#10061ccad010#1","shellyplus1pm#cc7b5c0dd95c#1","shellyplus1pm#d4d4da35853c#1","shellyplus1pm#10061ccb9fc0#1","shellyplus1pm#d4d4daeb2ddc#1"]
    2024-10-15 19:24:14.564  - debug: shelly.0 (1241) [deviceStatusUpdate] shellyplus1pm#b0b21c1b4e14#1: true
    2024-10-15 19:24:14.565  - debug: shelly.0 (1241) [onlineCheck] Checking shellyplus1#e465b8f46ac4#1 on 192.168.178.31:80
    2024-10-15 19:24:14.566  - info: shelly.0 (1241) Starting in MQTT mode. Listening on 0.0.0.0:1882 (QoS 0)
    2024-10-15 19:24:14.569  - debug: shelly.0 (1241) [MQTT Server] Started listener on 0.0.0.0:1882
    2024-10-15 19:24:14.571  - debug: shelly.0 (1241) [deviceStatusUpdate] shellyplus1#e465b8f46ac4#1: true
    2024-10-15 19:24:14.619  - debug: shelly.0 (1241) [deviceStatusUpdate] Online devices: ["shellyplus1#cc7b5c85af80#1","shellyplus1pm#10061ccad010#1","shellyplus1pm#cc7b5c0dd95c#1","shellyplus1pm#d4d4da35853c#1","shellyplus1pm#10061ccb9fc0#1","shellyplus1pm#d4d4daeb2ddc#1","shellyplus1pm#10061ccb0c48#1"]
    2024-10-15 19:24:14.620  - debug: shelly.0 (1241) [deviceStatusUpdate] Online devices: ["shellyplus1#cc7b5c85af80#1","shellyplus1pm#10061ccad010#1","shellyplus1pm#cc7b5c0dd95c#1","shellyplus1pm#d4d4da35853c#1","shellyplus1pm#10061ccb9fc0#1","shellyplus1pm#d4d4daeb2ddc#1","shellyplus1pm#10061ccb0c48#1","shellyplus1pm#10061cca8844#1"]
    2024-10-15 19:24:14.632  - debug: shelly.0 (1241) [deviceStatusUpdate] Online devices: ["shellyplus1#cc7b5c85af80#1","shellyplus1pm#10061ccad010#1","shellyplus1pm#cc7b5c0dd95c#1","shellyplus1pm#d4d4da35853c#1","shellyplus1pm#10061ccb9fc0#1","shellyplus1pm#d4d4daeb2ddc#1","shellyplus1pm#10061ccb0c48#1","shellyplus1pm#10061cca8844#1","shellyplus1pm#fcb46727891c#1"]
    2024-10-15 19:24:14.633  - debug: shelly.0 (1241) [deviceStatusUpdate] Online devices: ["shellyplus1#cc7b5c85af80#1","shellyplus1pm#10061ccad010#1","shellyplus1pm#cc7b5c0dd95c#1","shellyplus1pm#d4d4da35853c#1","shellyplus1pm#10061ccb9fc0#1","shellyplus1pm#d4d4daeb2ddc#1","shellyplus1pm#10061ccb0c48#1","shellyplus1pm#10061cca8844#1","shellyplus1pm#fcb46727891c#1","shellyplus1pm#b0b21c1b4e14#1"]
    2024-10-15 19:24:14.635  - debug: shelly.0 (1241) [deviceStatusUpdate] Online devices: ["shellyplus1#cc7b5c85af80#1","shellyplus1pm#10061ccad010#1","shellyplus1pm#cc7b5c0dd95c#1","shellyplus1pm#d4d4da35853c#1","shellyplus1pm#10061ccb9fc0#1","shellyplus1pm#d4d4daeb2ddc#1","shellyplus1pm#10061ccb0c48#1","shellyplus1pm#10061cca8844#1","shellyplus1pm#fcb46727891c#1","shellyplus1pm#b0b21c1b4e14#1","shellyplus1#e465b8f46ac4#1"]
    2024-10-15 19:24:15.516  - debug: shelly.0 (1241) [MQTT Server] New connection from 192.168.178.35
    2024-10-15 19:24:15.526  - debug: shelly.0 (1241) [MQTT] Client connected: {"cmd":"connect","retain":false,"qos":0,"dup":false,"length":101,"topic":null,"payload":null,"protocolId":"MQTT","protocolVersion":4,"will":{"retain":true,"qos":0,"topic":"shellyplus1pm-d4d4daeb2ddc/online","payload":{"type":"Buffer","data":[102,97,108,115,101]}},"clean":true,"keepalive":60,"clientId":"shellyplus1pm-d4d4daeb2ddc","username":"mqttuser","password":{"type":"Buffer","data":[80,97,115,115,97,116,51,53,105]}}
    2024-10-15 19:24:15.527  - info: shelly.0 (1241) [MQTT] Device with client id "shellyplus1pm-d4d4daeb2ddc" connected!
    2024-10-15 19:24:15.673  - debug: shelly.0 (1241) [createObjects] Starting object creation of (shellyplus1pm / shellyplus1pm-d4d4daeb2ddc / shellyplus1pm#d4d4daeb2ddc#1) for mode: <not set>
    2024-10-15 19:24:15.687  - debug: shelly.0 (1241) [MQTT Server] New connection from 192.168.178.32
    2024-10-15 19:24:15.688  - debug: shelly.0 (1241) [MQTT] Client connected: {"cmd":"connect","retain":false,"qos":0,"dup":false,"length":101,"topic":null,"payload":null,"protocolId":"MQTT","protocolVersion":4,"will":{"retain":true,"qos":0,"topic":"shellyplus1pm-10061cca8844/online","payload":{"type":"Buffer","data":[102,97,108,115,101]}},"clean":true,"keepalive":60,"clientId":"shellyplus1pm-10061cca8844","username":"mqttuser","password":{"type":"Buffer","data":[80,97,115,115,97,116,51,53,105]}}
    2024-10-15 19:24:15.689  - info: shelly.0 (1241) [MQTT] Device with client id "shellyplus1pm-10061cca8844" connected!
    2024-10-15 19:24:15.707  - debug: shelly.0 (1241) [MQTT Server] New connection from 192.168.178.34
    2024-10-15 19:24:15.708  - debug: shelly.0 (1241) [MQTT Server] New connection from 192.168.178.40
    2024-10-15 19:24:15.710  - debug: shelly.0 (1241) [MQTT] Client connected: {"cmd":"connect","retain":false,"qos":0,"dup":false,"length":101,"topic":null,"payload":null,"protocolId":"MQTT","protocolVersion":4,"will":{"retain":true,"qos":0,"topic":"shellyplus1pm-b0b21c1b4e14/online","payload":{"type":"Buffer","data":[102,97,108,115,101]}},"clean":true,"keepalive":60,"clientId":"shellyplus1pm-b0b21c1b4e14","username":"mqttuser","password":{"type":"Buffer","data":[80,97,115,115,97,116,51,53,105]}}
    2024-10-15 19:24:15.710  - info: shelly.0 (1241) [MQTT] Device with client id "shellyplus1pm-b0b21c1b4e14" connected!
    2024-10-15 19:24:15.712  - debug: shelly.0 (1241) [MQTT] Client connected: {"cmd":"connect","retain":false,"qos":0,"dup":false,"length":101,"topic":null,"payload":null,"protocolId":"MQTT","protocolVersion":4,"will":{"retain":true,"qos":0,"topic":"shellyplus1pm-10061ccad010/online","payload":{"type":"Buffer","data":[102,97,108,115,101]}},"clean":true,"keepalive":60,"clientId":"shellyplus1pm-10061ccad010","username":"mqttuser","password":{"type":"Buffer","data":[80,97,115,115,97,116,51,53,105]}}
    2024-10-15 19:24:15.713  - info: shelly.0 (1241) [MQTT] Device with client id "shellyplus1pm-10061ccad010" connected!
    2024-10-15 19:24:15.774  - debug: shelly.0 (1241) [createObjects] Starting object creation of (shellyplus1pm / shellyplus1pm-10061cca8844 / shellyplus1pm#10061cca8844#1) for mode: <not set>
    
    crunchipC 1 Antwort Letzte Antwort
    0
    • A Accuface

      @homoran said in Shellys per mqtt keine Verbindung:

      @accuface sagte in Shellys per mqtt keine Verbindung:

      Weil das Forum mir dass sagt.

      was?
      Du sollst ja nicht den ganzen Tag posten.

      nur die Zeilen nach Restart der Instanz

       2024-10-15 19:16:52.154 - info: admin.0 (802) <== Disconnect system.user.admin from ::ffff:192.168.178.22 admin
      2024-10-15 19:16:58.199 - info: admin.0 (802) ==> Connected system.user.admin from ::ffff:192.168.178.22
      2024-10-15 19:19:32.829 - info: admin.0 (802) <== Disconnect system.user.admin from ::ffff:192.168.178.22 admin
      2024-10-15 19:20:30.707 - info: admin.0 (802) terminating http server on port 8081
      2024-10-15 19:20:30.706 - info: host.raspberrypi5 received SIGTERM
      2024-10-15 19:20:30.710 - info: trashschedule.0 (1175) cleaned everything up...
      2024-10-15 19:20:30.716 - info: javascript.0 (864) Stopping script script.js.Skript_1
      2024-10-15 19:20:30.720 - info: backitup.0 (941) cleaned everything up...
      2024-10-15 19:20:30.728 - info: cloud.0 (959) Connection changed: disconnect
      2024-10-15 19:20:30.708 - info: host.raspberrypi5 stopInstance system.adapter.admin.0 (force=false, process=true)
      2024-10-15 19:20:30.708 - info: host.raspberrypi5 stopInstance system.adapter.javascript.0 (force=false, process=true)
      2024-10-15 19:20:30.708 - info: host.raspberrypi5 stopInstance system.adapter.scenes.0 (force=false, process=true)
      2024-10-15 19:20:30.709 - info: host.raspberrypi5 stopInstance system.adapter.sql.0 (force=false, process=true)
      2024-10-15 19:20:30.710 - info: host.raspberrypi5 stopInstance system.adapter.history.0 (force=false, process=true)
      2024-10-15 19:20:30.713 - info: host.raspberrypi5 stopInstance system.adapter.whatsapp-cmb.0 (force=false, process=true)
      2024-10-15 19:20:30.713 - info: host.raspberrypi5 stopInstance system.adapter.backitup.0 (force=false, process=true)
      2024-10-15 19:20:30.714 - info: host.raspberrypi5 stopInstance system.adapter.cloud.0 (force=false, process=true)
      2024-10-15 19:20:30.714 - info: host.raspberrypi5 stopInstance system.adapter.weatherunderground.0 (force=false, process=false)
      2024-10-15 19:20:30.714 - info: host.raspberrypi5 stopInstance system.adapter.ping.0 (force=false, process=false)
      2024-10-15 19:20:30.714 - info: host.raspberrypi5 stopInstance system.adapter.fronius.0 (force=false, process=true)
      2024-10-15 19:20:30.715 - info: host.raspberrypi5 stopInstance system.adapter.fronius.1 (force=false, process=true)
      2024-10-15 19:20:30.715 - info: host.raspberrypi5 stopInstance system.adapter.synology.0 (force=false, process=true)
      2024-10-15 19:20:30.715 - info: host.raspberrypi5 stopInstance system.adapter.ical.0 (force=false, process=false)
      2024-10-15 19:20:30.716 - info: host.raspberrypi5 stopInstance canceled schedule system.adapter.ical.0
      2024-10-15 19:20:30.716 - info: host.raspberrypi5 stopInstance system.adapter.feiertage.0 (force=false, process=false)
      2024-10-15 19:20:30.716 - info: host.raspberrypi5 stopInstance system.adapter.tankerkoenig.0 (force=false, process=true)
      2024-10-15 19:20:30.716 - info: host.raspberrypi5 stopInstance system.adapter.shelly.0 (force=false, process=true)
      2024-10-15 19:20:30.716 - info: host.raspberrypi5 stopInstance system.adapter.discovery.0 (force=false, process=true)
      2024-10-15 19:20:30.717 - info: host.raspberrypi5 stopInstance system.adapter.iot.0 (force=false, process=true)
      2024-10-15 19:20:30.717 - info: host.raspberrypi5 stopInstance system.adapter.web.0 (force=false, process=true)
      2024-10-15 19:20:30.717 - info: host.raspberrypi5 stopInstance system.adapter.vis-2.0 (force=false, process=true)
      2024-10-15 19:20:30.717 - info: host.raspberrypi5 stopInstance system.adapter.echarts.0 (force=false, process=true)
      2024-10-15 19:20:30.718 - info: host.raspberrypi5 stopInstance system.adapter.iqontrol.0 (force=false, process=false)
      2024-10-15 19:20:30.718 - info: host.raspberrypi5 stopInstance system.adapter.jarvis.0 (force=false, process=true)
      2024-10-15 19:20:30.718 - info: host.raspberrypi5 stopInstance system.adapter.fronius-solarweb.0 (force=false, process=true)
      2024-10-15 19:20:30.718 - info: host.raspberrypi5 stopInstance system.adapter.trashschedule.0 (force=false, process=true)
      2024-10-15 19:20:30.718 - info: host.raspberrypi5 stopInstance system.adapter.vis.0 (force=false, process=false)
      2024-10-15 19:20:30.719 - info: host.raspberrypi5 stopInstance system.adapter.vis-metro.0 (force=false, process=false)
      2024-10-15 19:20:30.719 - info: host.raspberrypi5 stopInstance system.adapter.dwd.0 (force=false, process=false)
      2024-10-15 19:20:30.719 - info: host.raspberrypi5 stopInstance system.adapter.vis-timeandweather.0 (force=false, process=false)
      2024-10-15 19:20:30.719 - info: jarvis.0 (1145) Adapter stopped und unloaded.
      2024-10-15 19:20:30.736 - warn: web.0 (1100) setTimeout called, but adapter is shutting down
      2024-10-15 19:20:30.766 - info: admin.0 (802) Got terminate signal TERMINATE_YOURSELF
      2024-10-15 19:20:30.767 - info: javascript.0 (864) Got terminate signal TERMINATE_YOURSELF
      2024-10-15 19:20:30.768 - info: whatsapp-cmb.0 (926) Got terminate signal TERMINATE_YOURSELF
      2024-10-15 19:20:30.769 - info: scenes.0 (880) Got terminate signal TERMINATE_YOURSELF
      2024-10-15 19:20:30.771 - info: backitup.0 (941) Got terminate signal TERMINATE_YOURSELF
      2024-10-15 19:20:30.770 - info: cloud.0 (959) Got terminate signal TERMINATE_YOURSELF
      2024-10-15 19:20:30.772 - info: fronius.1 (989) Got terminate signal TERMINATE_YOURSELF
      2024-10-15 19:20:30.772 - info: fronius.0 (974) Got terminate signal TERMINATE_YOURSELF
      2024-10-15 19:20:30.773 - info: synology.0 (1010) Got terminate signal TERMINATE_YOURSELF
      2024-10-15 19:20:30.785 - info: iot.0 (1085) Connection changed: disconnect
      2024-10-15 19:20:30.789 - info: sql.0 (895) terminating
      2024-10-15 19:20:30.790 - info: trashschedule.0 (1175) terminating
      2024-10-15 19:20:30.790 - info: javascript.0 (864) terminating
      2024-10-15 19:20:30.790 - info: admin.0 (802) terminating
      2024-10-15 19:20:30.794 - info: backitup.0 (941) terminating
      2024-10-15 19:20:30.791 - info: trashschedule.0 (1175) Terminated (NO_ERROR): Without reason
      2024-10-15 19:20:30.795 - info: backitup.0 (941) Terminated (NO_ERROR): Without reason
      2024-10-15 19:20:30.790 - info: history.0 (911) terminating
      2024-10-15 19:20:30.792 - info: sql.0 (895) Terminated (NO_ERROR): Without reason
      2024-10-15 19:20:30.798 - info: tankerkoenig.0 (1040) Got terminate signal TERMINATE_YOURSELF
      2024-10-15 19:20:30.798 - info: jarvis.0 (1145) Got terminate signal TERMINATE_YOURSELF
      2024-10-15 19:20:30.799 - info: trashschedule.0 (1175) Got terminate signal TERMINATE_YOURSELF
      2024-10-15 19:20:30.796 - info: discovery.0 (1070) Got terminate signal TERMINATE_YOURSELF
      2024-10-15 19:20:30.794 - info: fronius-solarweb.0 (1160) terminating
      2024-10-15 19:20:30.786 - info: iot.0 (1085) Connection lost
      2024-10-15 19:20:30.802 - info: tankerkoenig.0 (1040) terminating
      2024-10-15 19:20:30.793 - info: history.0 (911) Terminated (NO_ERROR): Without reason
      2024-10-15 19:20:30.800 - info: echarts.0 (1130) Got terminate signal TERMINATE_YOURSELF
      2024-10-15 19:20:30.791 - info: admin.0 (802) Terminated (NO_ERROR): Without reason
      2024-10-15 19:20:30.805 - info: vis-2.0 (1115) terminating
      2024-10-15 19:20:30.791 - info: javascript.0 (864) Terminated (NO_ERROR): Without reason
      2024-10-15 19:20:30.792 - info: synology.0 (1010) terminating
      2024-10-15 19:20:30.801 - info: shelly.0 (1286) Got terminate signal TERMINATE_YOURSELF
      2024-10-15 19:20:30.807 - info: web.0 (1100) Got terminate signal TERMINATE_YOURSELF
      2024-10-15 19:20:30.793 - info: synology.0 (1010) Terminated (NO_ERROR): Without reason
      2024-10-15 19:20:30.803 - info: iot.0 (1085) terminating
      2024-10-15 19:20:30.804 - info: iot.0 (1085) Terminated (NO_ERROR): Without reason
      2024-10-15 19:20:30.805 - info: iot.0 (1085) Got terminate signal TERMINATE_YOURSELF
      2024-10-15 19:20:30.803 - info: tankerkoenig.0 (1040) Terminated (NO_ERROR): Without reason
      2024-10-15 19:20:30.801 - info: fronius-solarweb.0 (1160) Terminated (NO_ERROR): Without reason
      2024-10-15 19:20:30.809 - info: fronius-solarweb.0 (1160) Got terminate signal TERMINATE_YOURSELF
      
      HomoranH Nicht stören
      HomoranH Nicht stören
      Homoran
      Global Moderator Administrators
      schrieb am zuletzt editiert von
      #22

      @accuface sagte in Shellys per mqtt keine Verbindung:

      host.raspberrypi5 received SIGTERM

      Hast du den Raspi oder iobroker neu gestartet?

      kein Support per PN! - Fragen im Forum stellen - es gibt fast nichts, was nicht auch für andere interessant ist.

      Benutzt das Voting rechts unten im Beitrag wenn er euch geholfen hat.

      der Installationsfixer: curl -fsL https://iobroker.net/fix.sh | bash -

      A 1 Antwort Letzte Antwort
      0
      • HomoranH Homoran

        @accuface sagte in Shellys per mqtt keine Verbindung:

        host.raspberrypi5 received SIGTERM

        Hast du den Raspi oder iobroker neu gestartet?

        A Offline
        A Offline
        Accuface
        schrieb am zuletzt editiert von Accuface
        #23

        @homoran said in Shellys per mqtt keine Verbindung:

        @accuface sagte in Shellys per mqtt keine Verbindung:

        host.raspberrypi5 received SIGTERM

        Hast du den Raspi oder iobroker neu gestartet?

        ich bin jetzt verwirrt... ich hab den Raspi auch neu gestartet, kommt drauf an wann du meinst?

        Ich sollte den doch rebooten

        Ich brauch klare ansagen wass ich wann und wie machen soll, ich hab doch null plan, schon vergessen :disappointed_relieved:

        HomoranH crunchipC 2 Antworten Letzte Antwort
        0
        • A Accuface

          @homoran said in Shellys per mqtt keine Verbindung:

          @accuface sagte in Shellys per mqtt keine Verbindung:

          host.raspberrypi5 received SIGTERM

          Hast du den Raspi oder iobroker neu gestartet?

          ich bin jetzt verwirrt... ich hab den Raspi auch neu gestartet, kommt drauf an wann du meinst?

          Ich sollte den doch rebooten

          Ich brauch klare ansagen wass ich wann und wie machen soll, ich hab doch null plan, schon vergessen :disappointed_relieved:

          HomoranH Nicht stören
          HomoranH Nicht stören
          Homoran
          Global Moderator Administrators
          schrieb am zuletzt editiert von
          #24

          @accuface sagte in Shellys per mqtt keine Verbindung:

          Ich sollte den doch rebooten

          aber doch nicht jedesmal für ein log

          kein Support per PN! - Fragen im Forum stellen - es gibt fast nichts, was nicht auch für andere interessant ist.

          Benutzt das Voting rechts unten im Beitrag wenn er euch geholfen hat.

          der Installationsfixer: curl -fsL https://iobroker.net/fix.sh | bash -

          A 1 Antwort Letzte Antwort
          0
          • HomoranH Homoran

            @accuface sagte in Shellys per mqtt keine Verbindung:

            Ich sollte den doch rebooten

            aber doch nicht jedesmal für ein log

            A Offline
            A Offline
            Accuface
            schrieb am zuletzt editiert von
            #25

            @homoran said in Shellys per mqtt keine Verbindung:

            @accuface sagte in Shellys per mqtt keine Verbindung:

            Ich sollte den doch rebooten

            aber doch nicht jedesmal für ein log

            sorry, dass muss mir doch gesagt werden. ich hab im Geschäft gelernt, lieber einmal mehr rebooten als zu wenig, sagen unsere ITler immer

            HomoranH 1 Antwort Letzte Antwort
            0
            • A Accuface

              @homoran said in Shellys per mqtt keine Verbindung:

              @accuface sagte in Shellys per mqtt keine Verbindung:

              Ich sollte den doch rebooten

              aber doch nicht jedesmal für ein log

              sorry, dass muss mir doch gesagt werden. ich hab im Geschäft gelernt, lieber einmal mehr rebooten als zu wenig, sagen unsere ITler immer

              HomoranH Nicht stören
              HomoranH Nicht stören
              Homoran
              Global Moderator Administrators
              schrieb am zuletzt editiert von
              #26

              @accuface sagte in Shellys per mqtt keine Verbindung:

              lieber einmal mehr rebooten als zu wenig,

              schadet auch nicht.
              Aber es ging doch um ein debug-log vom shrlly.
              Da nutzt das log vom reboot nichts.
              Kein Wunder dass es so viele Zeichen hat.

              kein Support per PN! - Fragen im Forum stellen - es gibt fast nichts, was nicht auch für andere interessant ist.

              Benutzt das Voting rechts unten im Beitrag wenn er euch geholfen hat.

              der Installationsfixer: curl -fsL https://iobroker.net/fix.sh | bash -

              A 1 Antwort Letzte Antwort
              0
              • HomoranH Homoran

                @accuface sagte in Shellys per mqtt keine Verbindung:

                lieber einmal mehr rebooten als zu wenig,

                schadet auch nicht.
                Aber es ging doch um ein debug-log vom shrlly.
                Da nutzt das log vom reboot nichts.
                Kein Wunder dass es so viele Zeichen hat.

                A Offline
                A Offline
                Accuface
                schrieb am zuletzt editiert von
                #27

                @homoran said in Shellys per mqtt keine Verbindung:

                @accuface sagte in Shellys per mqtt keine Verbindung:

                lieber einmal mehr rebooten als zu wenig,

                schadet auch nicht.
                Aber es ging doch um ein debug-log vom shrlly.
                Da nutzt das log vom reboot nichts.
                Kein Wunder dass es so viele Zeichen hat.

                ok, was soll ich jetzt machen?

                HomoranH 1 Antwort Letzte Antwort
                0
                • A Accuface

                  @homoran said in Shellys per mqtt keine Verbindung:

                  @accuface sagte in Shellys per mqtt keine Verbindung:

                  lieber einmal mehr rebooten als zu wenig,

                  schadet auch nicht.
                  Aber es ging doch um ein debug-log vom shrlly.
                  Da nutzt das log vom reboot nichts.
                  Kein Wunder dass es so viele Zeichen hat.

                  ok, was soll ich jetzt machen?

                  HomoranH Nicht stören
                  HomoranH Nicht stören
                  Homoran
                  Global Moderator Administrators
                  schrieb am zuletzt editiert von
                  #28

                  @accuface sagte in Shellys per mqtt keine Verbindung:

                  was soll ich jetzt machen?

                  das log mit den debug Ausgaben zum Shelly sieht soweit problemlos aus.
                  Wo liegt das Problem?

                  oder sind die entsprechenden Zeilen nicht dabei?

                  kein Support per PN! - Fragen im Forum stellen - es gibt fast nichts, was nicht auch für andere interessant ist.

                  Benutzt das Voting rechts unten im Beitrag wenn er euch geholfen hat.

                  der Installationsfixer: curl -fsL https://iobroker.net/fix.sh | bash -

                  A 2 Antworten Letzte Antwort
                  0
                  • HomoranH Homoran

                    @accuface sagte in Shellys per mqtt keine Verbindung:

                    was soll ich jetzt machen?

                    das log mit den debug Ausgaben zum Shelly sieht soweit problemlos aus.
                    Wo liegt das Problem?

                    oder sind die entsprechenden Zeilen nicht dabei?

                    A Offline
                    A Offline
                    Accuface
                    schrieb am zuletzt editiert von
                    #29

                    @homoran said in Shellys per mqtt keine Verbindung:

                    @accuface sagte in Shellys per mqtt keine Verbindung:

                    was soll ich jetzt machen?

                    Wo liegt das Problem?

                    Wenn ich das nur wüsste, müsste ich euch nicht Nerven :grimacing:

                    oder sind die entsprechenden Zeilen nicht dabei?

                    Weiß ich leider nicht. Ich weiß ja nicht wonach gesucht wird.

                    es wurde ein log verlangt, der zu lang ist, dann hab ich halt was rauskopiert.

                    1 Antwort Letzte Antwort
                    0
                    • A Accuface

                      Hier mal ein Auszug zum Shelly

                       2024-10-15 19:21:46.751  - info: host.raspberrypi5 instance system.adapter.shelly.0 in version "8.2.1" started with pid 1091
                      2024-10-15 19:21:47.898  - info: shelly.0 (1091) starting. Version 8.2.1 in /opt/iobroker/node_modules/iobroker.shelly, node: v20.18.0, js-controller: 6.0.11
                      2024-10-15 19:21:48.050  - info: shelly.0 (1091) Starting in MQTT mode. Listening on 0.0.0.0:1882 (QoS 0)
                      2024-10-15 19:21:49.437  - info: shelly.0 (1091) [MQTT] Device with client id "shellyplus1-cc7b5c85af80" connected!
                      2024-10-15 19:21:50.765  - info: host.raspberrypi5 instance system.adapter.discovery.0 in version "5.0.0" started with pid 1106
                      2024-10-15 19:21:51.563  - info: discovery.0 (1106) starting. Version 5.0.0 in /opt/iobroker/node_modules/iobroker.discovery, node: v20.18.0, js-controller: 6.0.11
                      2024-10-15 19:21:52.504  - info: shelly.0 (1091) [MQTT] Device with client id "shellyplus1pm-10061cca8844" connected!
                      2024-10-15 19:21:52.601  - info: shelly.0 (1091) [MQTT] Device with client id "shellyplus1pm-cc7b5c0dd95c" connected!
                      2024-10-15 19:21:52.692  - info: shelly.0 (1091) [MQTT] Device with client id "shellyplus1pm-10061ccb0c48" connected!
                      2024-10-15 19:21:53.444  - info: shelly.0 (1091) [MQTT] Device with client id "shellyplus1pm-d4d4daeb2ddc" connected!
                      2024-10-15 19:21:53.610  - info: shelly.0 (1091) [MQTT] Device with client id "shellyplus1pm-10061ccad010" connected!
                      2024-10-15 19:21:54.759  - info: host.raspberrypi5 instance system.adapter.iot.0 in version "3.3.0" started with pid 1121
                      2024-10-15 19:21:55.275  - info: shelly.0 (1091) [MQTT] Device with client id "shellyplus1pm-fcb46727891c" connected!
                      2024-10-15 19:21:56.069  - info: iot.0 (1121) starting. Version 3.3.0 in /opt/iobroker/node_modules/iobroker.iot, node: v20.18.0, js-controller: 6.0.11
                      2024-10-15 19:21:56.107  - info: iot.0 (1121) Connecting with a18wym7vjdl22g.iot.eu-west-1.amazonaws.com
                      2024-10-15 19:21:56.554  - info: iot.0 (1121) Connection changed: connect "bernd_order_gmx_de"
                      2024-10-15 19:21:56.966  - info: shelly.0 (1091) [MQTT] Device with client id "shellyplus1pm-d4d4da35853c" connected!
                      2024-10-15 19:21:58.507  - info: shelly.0 (1091) [MQTT] Device with client id "shellyplus1pm-b0b21c1b4e14" connected!
                      2024-10-15 19:21:58.750  - info: host.raspberrypi5 instance system.adapter.web.0 in version "6.2.5" started with pid 1136
                      2024-10-15 19:21:59.803  - info: web.0 (1136) starting. Version 6.2.5 in /opt/iobroker/node_modules/iobroker.web, node: v20.18.0, js-controller: 6.0.11
                      2024-10-15 19:22:00.220  - info: web.0 (1136) socket.io server listening on port 8082
                      2024-10-15 19:22:00.223  - info: web.0 (1136) http server listening on port 8082
                      2024-10-15 19:22:02.751  - info: host.raspberrypi5 instance system.adapter.vis-2.0 in version "2.9.32" started with pid 1151
                      2024-10-15 19:22:03.560  - info: vis-2.0 (1151) starting. Version 2.9.32 in /opt/iobroker/node_modules/iobroker.vis-2, node: v20.18.0, js-controller: 6.0.11
                      2024-10-15 19:22:03.764  - info: vis-2.0 (1151) vis-2 license is OK.
                      2024-10-15 19:22:06.740  - info: host.raspberrypi5 instance system.adapter.echarts.0 in version "1.9.2" started with pid 1166
                      2024-10-15 19:22:07.443  - info: echarts.0 (1166) starting. Version 1.9.2 in /opt/iobroker/node_modules/iobroker.echarts, node: v20.18.0, js-controller: 6.0.11
                      2024-10-15 19:22:10.783  - info: host.raspberrypi5 instance system.adapter.jarvis.0 in version "3.1.8" started with pid 1181
                      2024-10-15 19:22:12.296  - info: jarvis.0 (1181) starting. Version 3.1.8 in /opt/iobroker/node_modules/iobroker.jarvis, node: v20.18.0, js-controller: 6.0.11
                      2024-10-15 19:22:12.312  - info: jarvis.0 (1181) No Backup found for layout, thus backing up initially.
                      2024-10-15 19:22:12.313  - info: jarvis.0 (1181) No Backup found for scripts, thus backing up initially.
                      2024-10-15 19:22:12.313  - info: jarvis.0 (1181) No Backup found for styles, thus backing up initially.
                      2024-10-15 19:22:12.314  - info: jarvis.0 (1181) No Backup found for widgets, thus backing up initially.
                      2024-10-15 19:22:12.365  - info: jarvis.0 (1181) Connection: WebSocket opened on port 8400 using http...
                      2024-10-15 19:22:12.373  - info: jarvis.0 (1181) Found Backups for devices.
                      2024-10-15 19:22:12.374  - info: jarvis.0 (1181) Found Backups for settings.
                      2024-10-15 19:22:14.767  - info: host.raspberrypi5 instance system.adapter.fronius-solarweb.0 in version "0.0.3" started with pid 1196
                      2024-10-15 19:22:15.644  - info: fronius-solarweb.0 (1196) starting. Version 0.0.3 in /opt/iobroker/node_modules/iobroker.fronius-solarweb, node: v20.18.0, js-controller: 6.0.11
                      2024-10-15 19:22:17.092  - info: fronius-solarweb.0 (1196) Disable Pro Endpoints
                      2024-10-15 19:22:17.093  - info: fronius-solarweb.0 (1196) {"responseError":3503,"responseMessage":"Not a Pro PV system."}
                      2024-10-15 19:22:18.775  - info: host.raspberrypi5 instance system.adapter.trashschedule.0 in version "3.3.0" started with pid 1211
                      2024-10-15 19:22:19.636  - info: trashschedule.0 (1211) starting. Version 3.3.0 in /opt/iobroker/node_modules/iobroker.trashschedule, node: v20.18.0, js-controller: 6.0.11
                      2024-10-15 19:22:19.687  - info: trashschedule.0 (1211) [onReady] starting with source "ical" -> ical
                      2024-10-15 19:22:19.732  - info: trashschedule.0 (1211) [ical] configured ical preview is 31 days (until 15.11.2024) - increase this value to find more events in the future
                      2024-10-15 19:22:19.732  - info: trashschedule.0 (1211) [ical] found configured ical event "Vacation" without "display" flag. Activate the display flag on this entry if this is a relevant "trash event".
                      2024-10-15 19:22:23.433  - info: vis.0 (1226) starting. Version 1.5.6 in /opt/iobroker/node_modules/iobroker.vis, node: v20.18.0, js-controller: 6.0.11
                      2024-10-15 19:22:24.553  - info: cloud.0 (969) Trying to connect as system.user.admin to cloud
                      2024-10-15 19:22:24.703  - info: cloud.0 (969) Connection changed: connect
                      2024-10-15 19:22:27.486  - info: vis.0 (1226) Terminated (NO_ERROR): Without reason
                      2024-10-15 19:22:28.021  - info: host.raspberrypi5 instance system.adapter.vis.0 terminated while should be started once
                      2024-10-15 19:22:35.020  - info: shelly.0 (1091) [MQTT] Device with client id "shellyplus1-e465b8f46ac4" connected!
                      2024-10-15 19:22:37.498  - info: shelly.0 (1091) [MQTT] Device with client id "shellyplus1pm-10061ccb9fc0" connected!
                      2024-10-15 19:24:09.673  - info: host.raspberrypi5 stopInstance system.adapter.shelly.0 (force=false, process=true)
                      2024-10-15 19:24:09.678  - info: shelly.0 (1091) Got terminate signal TERMINATE_YOURSELF
                      2024-10-15 19:24:09.681  - info: shelly.0 (1091) terminating
                      2024-10-15 19:24:09.681  - info: shelly.0 (1091) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
                      2024-10-15 19:24:09.743  - info: host.raspberrypi5 stopInstance system.adapter.shelly.0 send kill signal
                      2024-10-15 19:24:10.182  - info: shelly.0 (1091) terminating
                      2024-10-15 19:24:10.211  - info: host.raspberrypi5 instance system.adapter.shelly.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
                      2024-10-15 19:24:13.364  - info: host.raspberrypi5 instance system.adapter.shelly.0 in version "8.2.1" started with pid 1241
                      2024-10-15 19:24:13.971  - debug: shelly.0 (1241) Redis Objects: Use Redis connection: 127.0.0.1:9001
                      2024-10-15 19:24:13.986  - debug: shelly.0 (1241) Objects client ready ... initialize now
                      2024-10-15 19:24:13.986  - debug: shelly.0 (1241) Objects create System PubSub Client
                      2024-10-15 19:24:13.987  - debug: shelly.0 (1241) Objects create User PubSub Client
                      2024-10-15 19:24:14.007  - debug: shelly.0 (1241) Objects client initialize lua scripts
                      2024-10-15 19:24:14.010  - debug: shelly.0 (1241) Objects connected to redis: 127.0.0.1:9001
                      2024-10-15 19:24:14.024  - debug: shelly.0 (1241) Redis States: Use Redis connection: 127.0.0.1:9000
                      2024-10-15 19:24:14.030  - debug: shelly.0 (1241) States create System PubSub Client
                      2024-10-15 19:24:14.031  - debug: shelly.0 (1241) States create User PubSub Client
                      2024-10-15 19:24:14.082  - debug: shelly.0 (1241) States connected to redis: 127.0.0.1:9000
                      2024-10-15 19:24:14.099  - debug: shelly.0 (1241) Plugin sentry Initialize Plugin (enabled=true)
                      2024-10-15 19:24:14.294  - info: shelly.0 (1241) starting. Version 8.2.1 in /opt/iobroker/node_modules/iobroker.shelly, node: v20.18.0, js-controller: 6.0.11
                      2024-10-15 19:24:14.436  - debug: shelly.0 (1241) [onlineCheck] Checking shellyplus1#cc7b5c85af80#1 on 192.168.178.29:80
                      2024-10-15 19:24:14.456  - debug: shelly.0 (1241) [deviceStatusUpdate] shellyplus1#cc7b5c85af80#1: true
                      2024-10-15 19:24:14.457  - debug: shelly.0 (1241) [onlineCheck] Checking shellyplus1pm#10061ccad010#1 on 192.168.178.40:80
                      2024-10-15 19:24:14.467  - debug: shelly.0 (1241) [deviceStatusUpdate] shellyplus1pm#10061ccad010#1: true
                      2024-10-15 19:24:14.468  - debug: shelly.0 (1241) [onlineCheck] Checking shellyplus1pm#cc7b5c0dd95c#1 on 192.168.178.33:80
                      2024-10-15 19:24:14.478  - debug: shelly.0 (1241) [onlineCheck] Checking shellyplus1pm#d4d4da35853c#1 on 192.168.178.38:80
                      2024-10-15 19:24:14.479  - debug: shelly.0 (1241) [onlineCheck] Checking shellyplus1pm#10061ccb9fc0#1 on 192.168.178.63:80
                      2024-10-15 19:24:14.480  - debug: shelly.0 (1241) [deviceStatusUpdate] shellyplus1pm#cc7b5c0dd95c#1: true
                      2024-10-15 19:24:14.483  - debug: shelly.0 (1241) [deviceStatusUpdate] Online devices: ["shellyplus1#cc7b5c85af80#1"]
                      2024-10-15 19:24:14.489  - debug: shelly.0 (1241) [deviceStatusUpdate] shellyplus1pm#d4d4da35853c#1: true
                      2024-10-15 19:24:14.490  - debug: shelly.0 (1241) [deviceStatusUpdate] shellyplus1pm#10061ccb9fc0#1: true
                      2024-10-15 19:24:14.491  - debug: shelly.0 (1241) [onlineCheck] Checking shellyplus1pm#d4d4daeb2ddc#1 on 192.168.178.35:80
                      2024-10-15 19:24:14.499  - debug: shelly.0 (1241) [deviceStatusUpdate] shellyplus1pm#d4d4daeb2ddc#1: true
                      2024-10-15 19:24:14.514  - debug: shelly.0 (1241) [onlineCheck] Checking shellyplus1pm#10061ccb0c48#1 on 192.168.178.39:80
                      2024-10-15 19:24:14.515  - debug: shelly.0 (1241) [deviceStatusUpdate] Online devices: ["shellyplus1#cc7b5c85af80#1","shellyplus1pm#10061ccad010#1"]
                      2024-10-15 19:24:14.525  - debug: shelly.0 (1241) [deviceStatusUpdate] shellyplus1pm#10061ccb0c48#1: true
                      2024-10-15 19:24:14.525  - debug: shelly.0 (1241) [onlineCheck] Checking shellyplus1pm#10061cca8844#1 on 192.168.178.32:80
                      2024-10-15 19:24:14.535  - debug: shelly.0 (1241) [deviceStatusUpdate] shellyplus1pm#10061cca8844#1: true
                      2024-10-15 19:24:14.537  - debug: shelly.0 (1241) [deviceStatusUpdate] Online devices: ["shellyplus1#cc7b5c85af80#1","shellyplus1pm#10061ccad010#1","shellyplus1pm#cc7b5c0dd95c#1"]
                      2024-10-15 19:24:14.539  - debug: shelly.0 (1241) [onlineCheck] Checking shellyplus1pm#fcb46727891c#1 on 192.168.178.26:80
                      2024-10-15 19:24:14.550  - debug: shelly.0 (1241) [deviceStatusUpdate] shellyplus1pm#fcb46727891c#1: true
                      2024-10-15 19:24:14.553  - debug: shelly.0 (1241) [onlineCheck] Checking shellyplus1pm#b0b21c1b4e14#1 on 192.168.178.34:80
                      2024-10-15 19:24:14.554  - debug: shelly.0 (1241) [deviceStatusUpdate] Online devices: ["shellyplus1#cc7b5c85af80#1","shellyplus1pm#10061ccad010#1","shellyplus1pm#cc7b5c0dd95c#1","shellyplus1pm#d4d4da35853c#1"]
                      2024-10-15 19:24:14.556  - debug: shelly.0 (1241) [deviceStatusUpdate] Online devices: ["shellyplus1#cc7b5c85af80#1","shellyplus1pm#10061ccad010#1","shellyplus1pm#cc7b5c0dd95c#1","shellyplus1pm#d4d4da35853c#1","shellyplus1pm#10061ccb9fc0#1"]
                      2024-10-15 19:24:14.557  - debug: shelly.0 (1241) [deviceStatusUpdate] Online devices: ["shellyplus1#cc7b5c85af80#1","shellyplus1pm#10061ccad010#1","shellyplus1pm#cc7b5c0dd95c#1","shellyplus1pm#d4d4da35853c#1","shellyplus1pm#10061ccb9fc0#1","shellyplus1pm#d4d4daeb2ddc#1"]
                      2024-10-15 19:24:14.564  - debug: shelly.0 (1241) [deviceStatusUpdate] shellyplus1pm#b0b21c1b4e14#1: true
                      2024-10-15 19:24:14.565  - debug: shelly.0 (1241) [onlineCheck] Checking shellyplus1#e465b8f46ac4#1 on 192.168.178.31:80
                      2024-10-15 19:24:14.566  - info: shelly.0 (1241) Starting in MQTT mode. Listening on 0.0.0.0:1882 (QoS 0)
                      2024-10-15 19:24:14.569  - debug: shelly.0 (1241) [MQTT Server] Started listener on 0.0.0.0:1882
                      2024-10-15 19:24:14.571  - debug: shelly.0 (1241) [deviceStatusUpdate] shellyplus1#e465b8f46ac4#1: true
                      2024-10-15 19:24:14.619  - debug: shelly.0 (1241) [deviceStatusUpdate] Online devices: ["shellyplus1#cc7b5c85af80#1","shellyplus1pm#10061ccad010#1","shellyplus1pm#cc7b5c0dd95c#1","shellyplus1pm#d4d4da35853c#1","shellyplus1pm#10061ccb9fc0#1","shellyplus1pm#d4d4daeb2ddc#1","shellyplus1pm#10061ccb0c48#1"]
                      2024-10-15 19:24:14.620  - debug: shelly.0 (1241) [deviceStatusUpdate] Online devices: ["shellyplus1#cc7b5c85af80#1","shellyplus1pm#10061ccad010#1","shellyplus1pm#cc7b5c0dd95c#1","shellyplus1pm#d4d4da35853c#1","shellyplus1pm#10061ccb9fc0#1","shellyplus1pm#d4d4daeb2ddc#1","shellyplus1pm#10061ccb0c48#1","shellyplus1pm#10061cca8844#1"]
                      2024-10-15 19:24:14.632  - debug: shelly.0 (1241) [deviceStatusUpdate] Online devices: ["shellyplus1#cc7b5c85af80#1","shellyplus1pm#10061ccad010#1","shellyplus1pm#cc7b5c0dd95c#1","shellyplus1pm#d4d4da35853c#1","shellyplus1pm#10061ccb9fc0#1","shellyplus1pm#d4d4daeb2ddc#1","shellyplus1pm#10061ccb0c48#1","shellyplus1pm#10061cca8844#1","shellyplus1pm#fcb46727891c#1"]
                      2024-10-15 19:24:14.633  - debug: shelly.0 (1241) [deviceStatusUpdate] Online devices: ["shellyplus1#cc7b5c85af80#1","shellyplus1pm#10061ccad010#1","shellyplus1pm#cc7b5c0dd95c#1","shellyplus1pm#d4d4da35853c#1","shellyplus1pm#10061ccb9fc0#1","shellyplus1pm#d4d4daeb2ddc#1","shellyplus1pm#10061ccb0c48#1","shellyplus1pm#10061cca8844#1","shellyplus1pm#fcb46727891c#1","shellyplus1pm#b0b21c1b4e14#1"]
                      2024-10-15 19:24:14.635  - debug: shelly.0 (1241) [deviceStatusUpdate] Online devices: ["shellyplus1#cc7b5c85af80#1","shellyplus1pm#10061ccad010#1","shellyplus1pm#cc7b5c0dd95c#1","shellyplus1pm#d4d4da35853c#1","shellyplus1pm#10061ccb9fc0#1","shellyplus1pm#d4d4daeb2ddc#1","shellyplus1pm#10061ccb0c48#1","shellyplus1pm#10061cca8844#1","shellyplus1pm#fcb46727891c#1","shellyplus1pm#b0b21c1b4e14#1","shellyplus1#e465b8f46ac4#1"]
                      2024-10-15 19:24:15.516  - debug: shelly.0 (1241) [MQTT Server] New connection from 192.168.178.35
                      2024-10-15 19:24:15.526  - debug: shelly.0 (1241) [MQTT] Client connected: {"cmd":"connect","retain":false,"qos":0,"dup":false,"length":101,"topic":null,"payload":null,"protocolId":"MQTT","protocolVersion":4,"will":{"retain":true,"qos":0,"topic":"shellyplus1pm-d4d4daeb2ddc/online","payload":{"type":"Buffer","data":[102,97,108,115,101]}},"clean":true,"keepalive":60,"clientId":"shellyplus1pm-d4d4daeb2ddc","username":"mqttuser","password":{"type":"Buffer","data":[80,97,115,115,97,116,51,53,105]}}
                      2024-10-15 19:24:15.527  - info: shelly.0 (1241) [MQTT] Device with client id "shellyplus1pm-d4d4daeb2ddc" connected!
                      2024-10-15 19:24:15.673  - debug: shelly.0 (1241) [createObjects] Starting object creation of (shellyplus1pm / shellyplus1pm-d4d4daeb2ddc / shellyplus1pm#d4d4daeb2ddc#1) for mode: <not set>
                      2024-10-15 19:24:15.687  - debug: shelly.0 (1241) [MQTT Server] New connection from 192.168.178.32
                      2024-10-15 19:24:15.688  - debug: shelly.0 (1241) [MQTT] Client connected: {"cmd":"connect","retain":false,"qos":0,"dup":false,"length":101,"topic":null,"payload":null,"protocolId":"MQTT","protocolVersion":4,"will":{"retain":true,"qos":0,"topic":"shellyplus1pm-10061cca8844/online","payload":{"type":"Buffer","data":[102,97,108,115,101]}},"clean":true,"keepalive":60,"clientId":"shellyplus1pm-10061cca8844","username":"mqttuser","password":{"type":"Buffer","data":[80,97,115,115,97,116,51,53,105]}}
                      2024-10-15 19:24:15.689  - info: shelly.0 (1241) [MQTT] Device with client id "shellyplus1pm-10061cca8844" connected!
                      2024-10-15 19:24:15.707  - debug: shelly.0 (1241) [MQTT Server] New connection from 192.168.178.34
                      2024-10-15 19:24:15.708  - debug: shelly.0 (1241) [MQTT Server] New connection from 192.168.178.40
                      2024-10-15 19:24:15.710  - debug: shelly.0 (1241) [MQTT] Client connected: {"cmd":"connect","retain":false,"qos":0,"dup":false,"length":101,"topic":null,"payload":null,"protocolId":"MQTT","protocolVersion":4,"will":{"retain":true,"qos":0,"topic":"shellyplus1pm-b0b21c1b4e14/online","payload":{"type":"Buffer","data":[102,97,108,115,101]}},"clean":true,"keepalive":60,"clientId":"shellyplus1pm-b0b21c1b4e14","username":"mqttuser","password":{"type":"Buffer","data":[80,97,115,115,97,116,51,53,105]}}
                      2024-10-15 19:24:15.710  - info: shelly.0 (1241) [MQTT] Device with client id "shellyplus1pm-b0b21c1b4e14" connected!
                      2024-10-15 19:24:15.712  - debug: shelly.0 (1241) [MQTT] Client connected: {"cmd":"connect","retain":false,"qos":0,"dup":false,"length":101,"topic":null,"payload":null,"protocolId":"MQTT","protocolVersion":4,"will":{"retain":true,"qos":0,"topic":"shellyplus1pm-10061ccad010/online","payload":{"type":"Buffer","data":[102,97,108,115,101]}},"clean":true,"keepalive":60,"clientId":"shellyplus1pm-10061ccad010","username":"mqttuser","password":{"type":"Buffer","data":[80,97,115,115,97,116,51,53,105]}}
                      2024-10-15 19:24:15.713  - info: shelly.0 (1241) [MQTT] Device with client id "shellyplus1pm-10061ccad010" connected!
                      2024-10-15 19:24:15.774  - debug: shelly.0 (1241) [createObjects] Starting object creation of (shellyplus1pm / shellyplus1pm-10061cca8844 / shellyplus1pm#10061cca8844#1) for mode: <not set>
                      
                      crunchipC Abwesend
                      crunchipC Abwesend
                      crunchip
                      Forum Testing Most Active
                      schrieb am zuletzt editiert von
                      #30

                      @accuface sagte in Shellys per mqtt keine Verbindung:

                      Starting object creation of (shellyplus1pm / shellyplus1pm-d4d4daeb2ddc / shellyplus1pm#d4d4daeb2ddc#1) for mode: <not set>

                      das kommt mir komisch vor

                      for mode: <not set>
                      

                      ansonsten steht ja überall connectet

                      umgestiegen von Proxmox auf Unraid

                      A 1 Antwort Letzte Antwort
                      1
                      • A Accuface

                        @homoran said in Shellys per mqtt keine Verbindung:

                        @accuface sagte in Shellys per mqtt keine Verbindung:

                        host.raspberrypi5 received SIGTERM

                        Hast du den Raspi oder iobroker neu gestartet?

                        ich bin jetzt verwirrt... ich hab den Raspi auch neu gestartet, kommt drauf an wann du meinst?

                        Ich sollte den doch rebooten

                        Ich brauch klare ansagen wass ich wann und wie machen soll, ich hab doch null plan, schon vergessen :disappointed_relieved:

                        crunchipC Abwesend
                        crunchipC Abwesend
                        crunchip
                        Forum Testing Most Active
                        schrieb am zuletzt editiert von
                        #31

                        @accuface sagte in Shellys per mqtt keine Verbindung:

                        Ich sollte den doch rebooten

                        hatte ich doch ...einmal neu starten, wegen

                        @crunchip sagte in Shellys per mqtt keine Verbindung:

                        code 7 (ADAPTER_ALREADY_RUNNING

                        umgestiegen von Proxmox auf Unraid

                        1 Antwort Letzte Antwort
                        0
                        • crunchipC crunchip

                          @accuface sagte in Shellys per mqtt keine Verbindung:

                          Starting object creation of (shellyplus1pm / shellyplus1pm-d4d4daeb2ddc / shellyplus1pm#d4d4daeb2ddc#1) for mode: <not set>

                          das kommt mir komisch vor

                          for mode: <not set>
                          

                          ansonsten steht ja überall connectet

                          A Offline
                          A Offline
                          Accuface
                          schrieb am zuletzt editiert von
                          #32

                          @crunchip said in Shellys per mqtt keine Verbindung:

                          @accuface sagte in Shellys per mqtt keine Verbindung:

                          Starting object creation of (shellyplus1pm / shellyplus1pm-d4d4daeb2ddc / shellyplus1pm#d4d4daeb2ddc#1) for mode: <not set>

                          das kommt mir komisch vor

                          for mode: <not set>
                          

                          ansonsten steht ja überall connectet

                          Dass ist der Shelly wo der Kühlschrank dranhängt. Der funktioniert ordnungsgemäß und wird auch unter den Objekten geführt

                          crunchipC 1 Antwort Letzte Antwort
                          0
                          • HomoranH Homoran

                            @accuface sagte in Shellys per mqtt keine Verbindung:

                            was soll ich jetzt machen?

                            das log mit den debug Ausgaben zum Shelly sieht soweit problemlos aus.
                            Wo liegt das Problem?

                            oder sind die entsprechenden Zeilen nicht dabei?

                            A Offline
                            A Offline
                            Accuface
                            schrieb am zuletzt editiert von
                            #33

                            @homoran

                            das Problem ist weiterhin, dass ich seid ..... zeitpunkt unbekannt...... keine Shellys per MQTT mehr in iob einbinden kann.

                            HomoranH Samson71S 2 Antworten Letzte Antwort
                            0
                            • A Accuface

                              @homoran

                              das Problem ist weiterhin, dass ich seid ..... zeitpunkt unbekannt...... keine Shellys per MQTT mehr in iob einbinden kann.

                              HomoranH Nicht stören
                              HomoranH Nicht stören
                              Homoran
                              Global Moderator Administrators
                              schrieb am zuletzt editiert von
                              #34

                              @accuface sagte in Shellys per mqtt keine Verbindung:

                              keine Shellys per MQTT

                              zusätzlich zum shelly Adapter?

                              bitte iob diag in der Langfassung posten

                              kein Support per PN! - Fragen im Forum stellen - es gibt fast nichts, was nicht auch für andere interessant ist.

                              Benutzt das Voting rechts unten im Beitrag wenn er euch geholfen hat.

                              der Installationsfixer: curl -fsL https://iobroker.net/fix.sh | bash -

                              A 2 Antworten Letzte Antwort
                              0
                              • A Accuface

                                @homoran

                                das Problem ist weiterhin, dass ich seid ..... zeitpunkt unbekannt...... keine Shellys per MQTT mehr in iob einbinden kann.

                                Samson71S Offline
                                Samson71S Offline
                                Samson71
                                Global Moderator
                                schrieb am zuletzt editiert von
                                #35

                                @accuface
                                Ich hab bis hier nur sporadisch gelesen/überflogen, bin aber auch mehr verwirrt was jetzt GENAU das Problem ist.

                                Vorschlag:

                                • Aktuelle Screenshots der Einstellungen EINES Shellys der aktuell nachweislich nicht einzubinden ist
                                • aktuelle Screenshots der momentanen Einstellungen des Shelly-Adapters

                                Nochmal zu meinem Verständnis. Du meinst mit MQTT aber schon den Shelly Adapter selbst und nicht zufällig den MQTT-Adapter?

                                Markus

                                Bitte beachten:
                                Hinweise für gute Forenbeiträge
                                Maßnahmen zum Schutz des Forums

                                A 1 Antwort Letzte Antwort
                                1
                                • HomoranH Homoran

                                  @accuface sagte in Shellys per mqtt keine Verbindung:

                                  keine Shellys per MQTT

                                  zusätzlich zum shelly Adapter?

                                  bitte iob diag in der Langfassung posten

                                  A Offline
                                  A Offline
                                  Accuface
                                  schrieb am zuletzt editiert von
                                  #36

                                  @homoran said in Shellys per mqtt keine Verbindung:

                                  @accuface sagte in Shellys per mqtt keine Verbindung:

                                  keine Shellys per MQTT

                                  zusätzlich zum shelly Adapter?

                                  Ich versteh die frage nicht. es lassen sich eben keine Shellys mehr in den Shelly Adapter mehr einfügen.
                                  wenn ich in einem Shelly den MQTT über die weboberfläche aktivieren und alles einstelle/eingebe und den Shelly neu starte, dann zeigt er mir in der Shelly App auf dem Iphone unter MQTT an dass er trozdem getrennt ist.
                                  in der Shelly Instanz/Objekten taucht er auch nicht auf, somit schließe ich dass irgendwo ein Problem besteht, das die Telefonate verhindert.

                                  bitte iob diag in der Langfassung posten

                                  kommt

                                  HomoranH 1 Antwort Letzte Antwort
                                  0
                                  • Samson71S Samson71

                                    @accuface
                                    Ich hab bis hier nur sporadisch gelesen/überflogen, bin aber auch mehr verwirrt was jetzt GENAU das Problem ist.

                                    Vorschlag:

                                    • Aktuelle Screenshots der Einstellungen EINES Shellys der aktuell nachweislich nicht einzubinden ist
                                    • aktuelle Screenshots der momentanen Einstellungen des Shelly-Adapters

                                    Nochmal zu meinem Verständnis. Du meinst mit MQTT aber schon den Shelly Adapter selbst und nicht zufällig den MQTT-Adapter?

                                    A Offline
                                    A Offline
                                    Accuface
                                    schrieb am zuletzt editiert von Accuface
                                    #37

                                    @samson71 said in Shellys per mqtt keine Verbindung:

                                    @accuface
                                    Ich hab bis hier nur sporadisch gelesen/überflogen, bin aber auch mehr verwirrt was jetzt GENAU das Problem ist.

                                    Vorschlag:

                                    • Aktuelle Screenshots der Einstellungen EINES Shellys der aktuell nachweislich nicht einzubinden ist
                                    • aktuelle Screenshots der momentanen Einstellungen des Shelly-Adapters

                                    ist alles in meinem ersten Post drin. erstellt gestern Abend. am Sonntagabend hab ich festgestellt dass es nicht mehr funktioniert.

                                    Nochmal zu meinem Verständnis. Du meinst mit MQTT aber schon den Shelly Adapter selbst und nicht zufällig den MQTT-Adapter?

                                    MQTT-Adapter? hatte ich Nie drauf

                                    Samson71S 1 Antwort Letzte Antwort
                                    0
                                    • A Accuface

                                      @homoran said in Shellys per mqtt keine Verbindung:

                                      @accuface sagte in Shellys per mqtt keine Verbindung:

                                      keine Shellys per MQTT

                                      zusätzlich zum shelly Adapter?

                                      Ich versteh die frage nicht. es lassen sich eben keine Shellys mehr in den Shelly Adapter mehr einfügen.
                                      wenn ich in einem Shelly den MQTT über die weboberfläche aktivieren und alles einstelle/eingebe und den Shelly neu starte, dann zeigt er mir in der Shelly App auf dem Iphone unter MQTT an dass er trozdem getrennt ist.
                                      in der Shelly Instanz/Objekten taucht er auch nicht auf, somit schließe ich dass irgendwo ein Problem besteht, das die Telefonate verhindert.

                                      bitte iob diag in der Langfassung posten

                                      kommt

                                      HomoranH Nicht stören
                                      HomoranH Nicht stören
                                      Homoran
                                      Global Moderator Administrators
                                      schrieb am zuletzt editiert von
                                      #38

                                      @accuface sagte in Shellys per mqtt keine Verbindung:

                                      Ich versteh die frage nicht.

                                      ich hatte befürchtet, wie auch @samson71, dass du zusätzlich zum Shelly Adapter auch noch den MQTT Adapter nutzen wolltest

                                      kein Support per PN! - Fragen im Forum stellen - es gibt fast nichts, was nicht auch für andere interessant ist.

                                      Benutzt das Voting rechts unten im Beitrag wenn er euch geholfen hat.

                                      der Installationsfixer: curl -fsL https://iobroker.net/fix.sh | bash -

                                      1 Antwort Letzte Antwort
                                      0
                                      • A Accuface

                                        @crunchip said in Shellys per mqtt keine Verbindung:

                                        @accuface sagte in Shellys per mqtt keine Verbindung:

                                        Starting object creation of (shellyplus1pm / shellyplus1pm-d4d4daeb2ddc / shellyplus1pm#d4d4daeb2ddc#1) for mode: <not set>

                                        das kommt mir komisch vor

                                        for mode: <not set>
                                        

                                        ansonsten steht ja überall connectet

                                        Dass ist der Shelly wo der Kühlschrank dranhängt. Der funktioniert ordnungsgemäß und wird auch unter den Objekten geführt

                                        crunchipC Abwesend
                                        crunchipC Abwesend
                                        crunchip
                                        Forum Testing Most Active
                                        schrieb am zuletzt editiert von
                                        #39

                                        @accuface war auch nicht auf den shelly bezogen, sondern generell die Meldung

                                        umgestiegen von Proxmox auf Unraid

                                        1 Antwort Letzte Antwort
                                        0
                                        • HomoranH Homoran

                                          @accuface sagte in Shellys per mqtt keine Verbindung:

                                          keine Shellys per MQTT

                                          zusätzlich zum shelly Adapter?

                                          bitte iob diag in der Langfassung posten

                                          A Offline
                                          A Offline
                                          Accuface
                                          schrieb am zuletzt editiert von Accuface
                                          #40

                                          @homoran said in Shellys per mqtt keine Verbindung:

                                          @accuface sagte in Shellys per mqtt keine Verbindung:

                                          keine Shellys per MQTT

                                          zusätzlich zum shelly Adapter?

                                          bitte iob diag in der Langfassung posten

                                          Skript v.2024-08-12
                                          
                                          *** BASE SYSTEM ***
                                          ======== Start marking the full check here =========
                                          
                                          ```bash
                                          Skript v.2024-08-12
                                          
                                          *** BASE SYSTEM ***
                                           Static hostname: raspberrypi5
                                                 Icon name: computer
                                          Operating System: Debian GNU/Linux 12 (bookworm)
                                                    Kernel: Linux 6.6.47+rpt-rpi-2712
                                              Architecture: arm64
                                          OS is similar to:
                                          
                                          Model           : Raspberry Pi 5 Model B Rev 1.0
                                          Docker          : false
                                          Virtualization  : none
                                          Kernel          : aarch64
                                          Userland        : 64 bit
                                          
                                          Systemuptime and Load:
                                           20:25:12 up  1:04,  2 users,  load average: 0.88, 0.43, 0.28
                                          CPU threads: 4
                                          
                                          
                                          *** RASPBERRY THROTTLING ***
                                          Current issues:
                                          No throttling issues detected.
                                          
                                          Previously detected issues:
                                          No throttling issues detected.
                                          
                                          *** Time and Time Zones ***
                                                         Local time: Tue 2024-10-15 20:25:12 CEST
                                                     Universal time: Tue 2024-10-15 18:25:12 UTC
                                                           RTC time: Tue 2024-10-15 18:25:12
                                                          Time zone: Europe/Berlin (CEST, +0200)
                                          System clock synchronized: yes
                                                        NTP service: active
                                                    RTC in local TZ: no
                                          
                                          *** Users and Groups ***
                                          User that called 'iob diag':
                                          Bernd
                                          HOME=/home/Bernd
                                          GROUPS=Bernd adm dialout cdrom sudo audio video plugdev games users input render netdev gpio i2c spi iobroker
                                          
                                          User that is running 'js-controller':
                                          iobroker
                                          HOME=/home/iobroker
                                          GROUPS=iobroker tty dialout audio video plugdev bluetooth gpio i2c
                                          
                                          *** Display-Server-Setup ***
                                          Display-Server: false
                                          Desktop:
                                          Terminal:       tty
                                          Boot Target:    multi-user.target
                                          
                                          *** MEMORY ***
                                                         total        used        free      shared  buff/cache   available
                                          Mem:            8.4G        1.7G        5.9G        5.4M        993M        6.7G
                                          Swap:           209M          0B        209M
                                          Total:          8.7G        1.7G        6.1G
                                          
                                          Active iob-Instances:   22
                                          
                                                   8052 M total memory
                                                   1621 M used memory
                                                   1479 M active memory
                                                    726 M inactive memory
                                                   5585 M free memory
                                                    101 M buffer memory
                                                    845 M swap cache
                                                    199 M total swap
                                                      0 M used swap
                                                    199 M free swap
                                          
                                          *** top - Table Of Processes  ***
                                          top - 20:25:12 up  1:04,  2 users,  load average: 0.88, 0.43, 0.28
                                          Tasks: 180 total,   1 running, 179 sleeping,   0 stopped,   0 zombie
                                          %Cpu(s):  0.0 us,  0.0 sy,  0.0 ni,100.0 id,  0.0 wa,  0.0 hi,  0.0 si,  0.0 st
                                          MiB Mem :   8052.3 total,   5585.5 free,   1621.4 used,    947.4 buff/cache
                                          MiB Swap:    200.0 total,    200.0 free,      0.0 used.   6430.9 avail Mem
                                          
                                          *** FAILED SERVICES ***
                                          
                                            UNIT LOAD ACTIVE SUB DESCRIPTION
                                          0 loaded units listed.
                                          
                                          *** FILESYSTEM ***
                                          Filesystem     Type      Size  Used Avail Use% Mounted on
                                          udev           devtmpfs  3.8G     0  3.8G   0% /dev
                                          tmpfs          tmpfs     806M  5.2M  801M   1% /run
                                          /dev/mmcblk0p2 ext4       29G  7.1G   21G  26% /
                                          tmpfs          tmpfs     4.0G     0  4.0G   0% /dev/shm
                                          tmpfs          tmpfs     5.0M   48K  5.0M   1% /run/lock
                                          /dev/mmcblk0p1 vfat      510M   64M  447M  13% /boot/firmware
                                          tmpfs          tmpfs     806M     0  806M   0% /run/user/1000
                                          
                                          Messages concerning ext4 filesystem in dmesg:
                                          [Tue Oct 15 19:20:45 2024] Kernel command line: reboot=w coherent_pool=1M 8250.nr_uarts=1 pci=pcie_bus_safe  smsc95xx.macaddr=2C:CF:67:56:18:0A vc_mem.mem_base=0x3fc00000 vc_mem.mem_size=0x40000000  console=ttyAMA10,115200 console=tty1 root=PARTUUID=8959849a-02 rootfstype=ext4 fsck.repair=yes rootwait cfg80211.ieee80211_regdom=DE
                                          [Tue Oct 15 19:20:48 2024] EXT4-fs (mmcblk0p2): mounted filesystem 56f80fa2-e005-4cca-86e6-19da1069914d ro with ordered data mode. Quota mode: none.
                                          [Tue Oct 15 19:20:49 2024] EXT4-fs (mmcblk0p2): re-mounted 56f80fa2-e005-4cca-86e6-19da1069914d r/w. Quota mode: none.
                                          
                                          Show mounted filesystems:
                                          TARGET           SOURCE         FSTYPE OPTIONS
                                          /                /dev/mmcblk0p2 ext4   rw,noatime
                                          `-/boot/firmware /dev/mmcblk0p1 vfat   rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,errors=remount-ro
                                          
                                          Files in neuralgic directories:
                                          
                                          /var:
                                          884M    /var/
                                          265M    /var/log/journal/9ba9919aad384e6eaaa1e9cb2eaa4832
                                          265M    /var/log/journal
                                          265M    /var/log
                                          252M    /var/cache
                                          
                                          Archived and active journals take up 264.6M in the file system.
                                          
                                          /opt/iobroker/backups:
                                          41M     /opt/iobroker/backups/
                                          
                                          /opt/iobroker/iobroker-data:
                                          1.4G    /opt/iobroker/iobroker-data/
                                          1.3G    /opt/iobroker/iobroker-data/files
                                          617M    /opt/iobroker/iobroker-data/files/javascript.admin
                                          560M    /opt/iobroker/iobroker-data/files/javascript.admin/static
                                          558M    /opt/iobroker/iobroker-data/files/javascript.admin/static/js
                                          
                                          The five largest files in iobroker-data are:
                                          38M     /opt/iobroker/iobroker-data/files/iot.admin/static/js/main.d3d286bd.js.map
                                          27M     /opt/iobroker/iobroker-data/files/tankerkoenig.admin/build/index.js.map
                                          26M     /opt/iobroker/iobroker-data/files/echarts/static/js/main.41cee985.js.map
                                          26M     /opt/iobroker/iobroker-data/files/echarts.admin/chart/static/js/main.41cee985.js.map
                                          24M     /opt/iobroker/iobroker-data/files/web.admin/static/js/main.135279a0.js.map
                                          
                                          USB-Devices by-id:
                                          USB-Sticks -  Avoid direct links to /dev/tty* in your adapter setups, please always prefer the links 'by-id':
                                          
                                          No Devices found 'by-id'
                                          
                                          
                                          
                                          
                                          *** NodeJS-Installation ***
                                          
                                          /usr/bin/nodejs         v20.18.0
                                          /usr/bin/node           v20.18.0
                                          /usr/bin/npm            10.8.2
                                          /usr/bin/npx            10.8.2
                                          /usr/bin/corepack       0.29.3
                                          
                                          
                                          nodejs:
                                            Installed: 20.18.0-1nodesource1
                                            Candidate: 20.18.0-1nodesource1
                                            Version table:
                                           *** 20.18.0-1nodesource1 1001
                                                  500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
                                                  100 /var/lib/dpkg/status
                                               20.17.0-1nodesource1 1001
                                                  500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
                                               20.16.0-1nodesource1 1001
                                                  500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
                                               20.15.1-1nodesource1 1001
                                                  500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
                                               20.15.0-1nodesource1 1001
                                                  500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
                                               20.14.0-1nodesource1 1001
                                                  500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
                                               20.13.1-1nodesource1 1001
                                                  500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
                                               20.13.0-1nodesource1 1001
                                                  500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
                                               20.12.2-1nodesource1 1001
                                                  500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
                                               20.12.1-1nodesource1 1001
                                                  500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
                                               20.12.0-1nodesource1 1001
                                                  500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
                                               20.11.1-1nodesource1 1001
                                                  500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
                                               20.11.0-1nodesource1 1001
                                                  500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
                                               20.10.0-1nodesource1 1001
                                                  500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
                                               20.9.0-1nodesource1 1001
                                                  500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
                                               20.8.1-1nodesource1 1001
                                                  500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
                                               20.8.0-1nodesource1 1001
                                                  500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
                                               20.7.0-1nodesource1 1001
                                                  500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
                                               20.6.1-1nodesource1 1001
                                                  500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
                                               20.6.0-1nodesource1 1001
                                                  500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
                                               20.5.1-1nodesource1 1001
                                                  500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
                                               20.5.0-1nodesource1 1001
                                                  500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
                                               20.4.0-1nodesource1 1001
                                                  500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
                                               20.3.1-1nodesource1 1001
                                                  500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
                                               20.3.0-1nodesource1 1001
                                                  500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
                                               20.2.0-1nodesource1 1001
                                                  500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
                                               20.1.0-1nodesource1 1001
                                                  500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
                                               20.0.0-1nodesource1 1001
                                                  500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
                                               18.19.0+dfsg-6~deb12u2 500
                                                  500 http://deb.debian.org/debian bookworm/main arm64 Packages
                                               18.19.0+dfsg-6~deb12u1 500
                                                  500 http://deb.debian.org/debian-security bookworm-security/main arm64 Packages
                                          
                                          Temp directories causing npm8 problem: 0
                                          No problems detected
                                          
                                          Errors in npm tree:
                                          
                                          *** ioBroker-Installation ***
                                          
                                          ioBroker Status
                                          iobroker is running on this host.
                                          
                                          
                                          Objects type: jsonl
                                          States  type: jsonl
                                          
                                          Core adapters versions
                                          js-controller:  6.0.11
                                          admin:          7.1.5
                                          javascript:     8.8.3
                                          
                                          nodejs modules from github:     1
                                          | +-- syno@3.0.0 (git+https://git@github.com/MeisterTR/syno.git#0104a973d33fe332aa6b1ab5be7fe8c57d3c68b0)
                                          
                                          Adapter State
                                          + system.adapter.admin.0                  : admin                 : raspberrypi5                             -  enabled, port: 8081, bind: 0.0.0.0, run as: admin
                                          + system.adapter.backitup.0               : backitup              : raspberrypi5                             -  enabled
                                          + system.adapter.cloud.0                  : cloud                 : raspberrypi5                             -  enabled
                                          + system.adapter.discovery.0              : discovery             : raspberrypi5                             -  enabled
                                            system.adapter.dwd.0                    : dwd                   : raspberrypi5                             - disabled
                                          + system.adapter.echarts.0                : echarts               : raspberrypi5                             -  enabled
                                            system.adapter.feiertage.0              : feiertage             : raspberrypi5                             - disabled
                                          + system.adapter.fronius-solarweb.0       : fronius-solarweb      : raspberrypi5                             -  enabled
                                          + system.adapter.fronius.0                : fronius               : raspberrypi5                             -  enabled
                                          + system.adapter.fronius.1                : fronius               : raspberrypi5                             -  enabled
                                          + system.adapter.history.0                : history               : raspberrypi5                             -  enabled
                                            system.adapter.ical.0                   : ical                  : raspberrypi5                             -  enabled
                                            system.adapter.icons-mfd-png.0          : icons-mfd-png         : raspberrypi5                             -  enabled
                                          + system.adapter.iot.0                    : iot                   : raspberrypi5                             -  enabled
                                            system.adapter.iqontrol.0               : iqontrol              : raspberrypi5                             - disabled
                                          + system.adapter.jarvis.0                 : jarvis                : raspberrypi5                             -  enabled, port: 8082, bind: 0.0.0.0, run as: admin
                                          + system.adapter.javascript.0             : javascript            : raspberrypi5                             -  enabled
                                            system.adapter.ping.0                   : ping                  : raspberrypi5                             - disabled
                                          + system.adapter.scenes.0                 : scenes                : raspberrypi5                             -  enabled
                                          + system.adapter.shelly.0                 : shelly                : raspberrypi5                             -  enabled, port: 1882, bind: 0.0.0.0
                                          + system.adapter.sql.0                    : sql                   : raspberrypi5                             -  enabled
                                          + system.adapter.synology.0               : synology              : raspberrypi5                             -  enabled, port: 5000
                                          + system.adapter.tankerkoenig.0           : tankerkoenig          : raspberrypi5                             -  enabled
                                          + system.adapter.trashschedule.0          : trashschedule         : raspberrypi5                             -  enabled
                                            system.adapter.vis-2-widgets-energy.0   : vis-2-widgets-energy  : raspberrypi5                             -  enabled
                                            system.adapter.vis-2-widgets-gauges.0   : vis-2-widgets-gauges  : raspberrypi5                             -  enabled
                                            system.adapter.vis-2-widgets-inventwo.0 : vis-2-widgets-inventwo: raspberrypi5                             -  enabled
                                            system.adapter.vis-2-widgets-jaeger-design.0: vis-2-widgets-jaeger-design: raspberrypi5                             -  enabled
                                            system.adapter.vis-2-widgets-material.0 : vis-2-widgets-material: raspberrypi5                             -  enabled
                                          + system.adapter.vis-2.0                  : vis-2                 : raspberrypi5                             -  enabled
                                            system.adapter.vis-metro.0              : vis-metro             : raspberrypi5                             -  enabled
                                            system.adapter.vis-timeandweather.0     : vis-timeandweather    : raspberrypi5                             -  enabled
                                            system.adapter.vis-weather.0            : vis-weather           : raspberrypi5                             -  enabled
                                            system.adapter.vis.0                    : vis                   : raspberrypi5                             -  enabled
                                            system.adapter.weatherunderground.0     : weatherunderground    : raspberrypi5                             - disabled
                                          + system.adapter.web.0                    : web                   : raspberrypi5                             -  enabled, port: 8082, bind: 0.0.0.0, run as: admin
                                          + system.adapter.whatsapp-cmb.0           : whatsapp-cmb          : raspberrypi5                             -  enabled
                                          
                                          + instance is alive
                                          
                                          Enabled adapters with bindings
                                          + system.adapter.admin.0                  : admin                 : raspberrypi5                             -  enabled, port: 8081, bind: 0.0.0.0, run as: admin
                                          + system.adapter.jarvis.0                 : jarvis                : raspberrypi5                             -  enabled, port: 8082, bind: 0.0.0.0, run as: admin
                                          + system.adapter.shelly.0                 : shelly                : raspberrypi5                             -  enabled, port: 1882, bind: 0.0.0.0
                                          + system.adapter.synology.0               : synology              : raspberrypi5                             -  enabled, port: 5000
                                          + system.adapter.web.0                    : web                   : raspberrypi5                             -  enabled, port: 8082, bind: 0.0.0.0, run as: admin
                                          
                                          ioBroker-Repositories
                                          ┌─────────┬──────────┬─────────────────────────────────────────────────────────┬──────────────┐
                                          │ (index) │ name     │ url                                                     │ auto upgrade │
                                          ├─────────┼──────────┼─────────────────────────────────────────────────────────┼──────────────┤
                                          │ 0       │ 'stable' │ 'http://download.iobroker.net/sources-dist.json'        │ false        │
                                          │ 1       │ 'beta'   │ 'http://download.iobroker.net/sources-dist-latest.json' │ false        │
                                          └─────────┴──────────┴─────────────────────────────────────────────────────────┴──────────────┘
                                          
                                          Active repo(s): stable
                                          Upgrade policy: none
                                          
                                          Installed ioBroker-Instances
                                          Used repository: stable
                                          Adapter    "admin"        : 7.1.5    , installed 7.1.5
                                          Adapter    "backitup"     : 3.0.25   , installed 3.0.22 [Updatable]
                                          Adapter    "cloud"        : 5.0.1    , installed 5.0.1
                                          Adapter    "discovery"    : 5.0.0    , installed 5.0.0
                                          Adapter    "dwd"          : 2.8.5    , installed 2.8.5
                                          Adapter    "echarts"      : 1.9.2    , installed 1.9.2
                                          Adapter    "feiertage"    : 1.2.0    , installed 1.2.0
                                          Adapter    "fronius"      : 2.1.1    , installed 2.1.1
                                          Adapter    "fronius-solarweb": 0.0.3 , installed 0.0.3
                                          Adapter    "history"      : 3.0.1    , installed 3.0.1
                                          Adapter    "ical"         : 1.15.0   , installed 1.15.0
                                          Adapter    "icons-mfd-png": 1.2.1    , installed 1.2.1
                                          Adapter    "iot"          : 3.3.0    , installed 3.3.0
                                          Adapter    "iqontrol"     : 2.3.0    , installed 2.3.0
                                          Adapter    "jarvis"       : 3.1.8    , installed 3.1.8
                                          Adapter    "javascript"   : 8.8.3    , installed 8.8.3
                                          Controller "js-controller": 6.0.11   , installed 6.0.11
                                          Adapter    "ping"         : 1.6.2    , installed 1.6.2
                                          Adapter    "scenes"       : 3.2.3    , installed 3.2.3
                                          Adapter    "shelly"       : 8.2.1    , installed 8.2.1
                                          Adapter    "simple-api"   : 2.8.0    , installed 2.8.0
                                          Adapter    "socketio"     : 6.7.1    , installed 6.7.1
                                          Adapter    "sql"          : 3.0.1    , installed 3.0.1
                                          Adapter    "synology"     : 3.1.0    , installed 3.1.0
                                          Adapter    "tankerkoenig" : 3.4.0    , installed 3.4.0
                                          Adapter    "trashschedule": 3.3.0    , installed 3.3.0
                                          Adapter    "vis"          : 1.5.6    , installed 1.5.6
                                          Adapter    "vis-2"        : 2.9.32   , installed 2.9.32
                                          Adapter    "vis-2-widgets-energy": 1.0.2, installed 1.0.2
                                          Adapter    "vis-2-widgets-gauges": 1.1.0, installed 1.1.0
                                          Adapter    "vis-2-widgets-inventwo": 0.1.11, installed 0.1.11
                                          Adapter    "vis-2-widgets-jaeger-design": 1.2.7, installed 1.2.7
                                          Adapter    "vis-2-widgets-material": 1.4.10, installed 1.4.10
                                          Adapter    "vis-metro"    : 1.2.0    , installed 1.2.0
                                          Adapter    "vis-timeandweather": 1.2.2, installed 1.2.2
                                          Adapter    "vis-weather"  : 2.5.9    , installed 2.5.9
                                          Adapter    "weatherunderground": 3.7.0, installed 3.7.0
                                          Adapter    "web"          : 6.2.5    , installed 6.2.5
                                          Adapter    "whatsapp-cmb" : 0.3.0    , installed 0.3.0
                                          Adapter    "ws"           : 2.6.2    , installed 2.6.2
                                          
                                          Objects and States
                                          Please stand by - This may take a while
                                          Objects:        5608
                                          States:         4481
                                          
                                          *** OS-Repositories and Updates ***
                                          Hit:1 http://deb.debian.org/debian bookworm InRelease
                                          Hit:2 http://deb.debian.org/debian-security bookworm-security InRelease
                                          Hit:3 http://archive.raspberrypi.com/debian bookworm InRelease
                                          Hit:4 http://deb.debian.org/debian bookworm-updates InRelease
                                          Hit:5 https://deb.nodesource.com/node_20.x nodistro InRelease
                                          Reading package lists...
                                          Pending Updates: 0
                                          
                                          *** Listening Ports ***
                                          Active Internet connections (only servers)
                                          Proto Recv-Q Send-Q Local Address           Foreign Address         State       User       Inode      PID/Program name  
                                          tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN      0          5626       777/sshd: /usr/sbin
                                          tcp        0      0 0.0.0.0:8400            0.0.0.0:*               LISTEN      1001       7833       1181/io.jarvis.0  
                                          tcp        0      0 127.0.0.1:9001          0.0.0.0:*               LISTEN      1001       6380       766/iobroker.js-con
                                          tcp        0      0 127.0.0.1:9000          0.0.0.0:*               LISTEN      1001       7383       766/iobroker.js-con
                                          tcp        0      0 0.0.0.0:1882            0.0.0.0:*               LISTEN      1001       43171      1414/io.shelly.0  
                                          tcp6       0      0 :::8082                 :::*                    LISTEN      1001       7749       1136/io.web.0     
                                          tcp6       0      0 :::8081                 :::*                    LISTEN      1001       7422       812/io.admin.0    
                                          tcp6       0      0 :::22                   :::*                    LISTEN      0          5628       777/sshd: /usr/sbin
                                          udp        0      0 0.0.0.0:48252           0.0.0.0:*                           104        6279       655/avahi-daemon: r
                                          udp        0      0 0.0.0.0:5353            0.0.0.0:*                           104        6277       655/avahi-daemon: r
                                          udp6       0      0 :::60397                :::*                                104        6280       655/avahi-daemon: r
                                          udp6       0      0 fe80::dc25:f03d:c31:546 :::*                                0          6638       738/NetworkManager
                                          udp6       0      0 :::5353                 :::*                                104        6278       655/avahi-daemon: r
                                          
                                          *** Log File - Last 25 Lines ***
                                          
                                          2024-10-15 20:25:25.325  - debug: shelly.0 (1414) [MQTT] Publish: 192.168.178.34 (shellyplus1pm / shellyplus1pm-b0b21c1b4e14 / shellyplus1pm#b0b21c1b4e14#1) - topic: shellyplus1pm-b0b21c1b4e14/events/rpc, qos: 1, payload: {"src":"shellyplus1pm-b0b21c1b4e14","dst":"shellyplus1pm-b0b21c1b4e14/events","method":"NotifyStatus","params":{"ts":1729016724.29,"switch:0":{"id":0,"apower":3.9}}}
                                          2024-10-15 20:25:25.340  - debug: shelly.0 (1414) [MQTT] Publish: 192.168.178.34 (shellyplus1pm / shellyplus1pm-b0b21c1b4e14 / shellyplus1pm#b0b21c1b4e14#1) - topic: shellyplus1pm-b0b21c1b4e14/status/switch:0, qos: 1, payload: {"id":0, "source":"SHC", "output":true, "apower":4.5, "voltage":228.5, "current":0.047, "aenergy":{"total":550.191,"by_minute":[71.439,80.471,65.280],"minute_ts":1729016700},"temperature":{"tC":54.1, "tF":129.4}}
                                          2024-10-15 20:25:25.340  - debug: shelly.0 (1414) [MQTT] State change 192.168.178.34 (shellyplus1pm / shellyplus1pm-b0b21c1b4e14 / shellyplus1pm#b0b21c1b4e14#1): shellyplus1pm-b0b21c1b4e14/status/switch:0 -> state: shellyplus1pm#b0b21c1b4e14#1.Relay0.Power, value: 4.5
                                          2024-10-15 20:25:25.341  - debug: shelly.0 (1414) [MQTT] State change 192.168.178.34 (shellyplus1pm / shellyplus1pm-b0b21c1b4e14 / shellyplus1pm#b0b21c1b4e14#1): shellyplus1pm-b0b21c1b4e14/status/switch:0 -> state: shellyplus1pm#b0b21c1b4e14#1.Relay0.Voltage, value: 228.5
                                          2024-10-15 20:25:25.341  - debug: shelly.0 (1414) [MQTT] State change 192.168.178.34 (shellyplus1pm / shellyplus1pm-b0b21c1b4e14 / shellyplus1pm#b0b21c1b4e14#1): shellyplus1pm-b0b21c1b4e14/status/switch:0 -> state: shellyplus1pm#b0b21c1b4e14#1.Relay0.Current, value: 0.047
                                          2024-10-15 20:25:25.341  - debug: shelly.0 (1414) [MQTT] State change 192.168.178.34 (shellyplus1pm / shellyplus1pm-b0b21c1b4e14 / shellyplus1pm#b0b21c1b4e14#1): shellyplus1pm-b0b21c1b4e14/status/switch:0 -> state: shellyplus1pm#b0b21c1b4e14#1.Relay0.Energy, value: 550.191
                                          2024-10-15 20:25:26.819  - debug: shelly.0 (1414) [httpIoBrokerState] State change 192.168.178.31 (shellyplus1 / shellyplus1-e465b8f46ac4 / shellyplus1#e465b8f46ac4#1): state: shellyplus1#e465b8f46ac4#1.uptime, value: 1238126
                                          2024-10-15 20:25:26.844  - debug: shelly.0 (1414) [httpIoBrokerState] State change 192.168.178.63 (shellyplus1pm / shellyplus1pm-10061ccb9fc0 / shellyplus1pm#10061ccb9fc0#1): state: shellyplus1pm#10061ccb9fc0#1.uptime, value: 775665
                                          2024-10-15 20:25:27.125  - debug: shelly.0 (1414) [httpIoBrokerState] State change 192.168.178.26 (shellyplus1pm / shellyplus1pm-fcb46727891c / shellyplus1pm#fcb46727891c#1): state: shellyplus1pm#fcb46727891c#1.uptime, value: 1238125
                                          2024-10-15 20:25:27.179  - debug: shelly.0 (1414) [httpIoBrokerState] State change 192.168.178.39 (shellyplus1pm / shellyplus1pm-10061ccb0c48 / shellyplus1pm#10061ccb0c48#1): state: shellyplus1pm#10061ccb0c48#1.uptime, value: 1238125
                                          2024-10-15 20:25:27.179  - debug: shelly.0 (1414) [httpIoBrokerState] State change 192.168.178.39 (shellyplus1pm / shellyplus1pm-10061ccb0c48 / shellyplus1pm#10061ccb0c48#1): state: shellyplus1pm#10061ccb0c48#1.rssi, value: -58
                                          2024-10-15 20:25:27.241  - debug: shelly.0 (1414) [httpIoBrokerState] State change 192.168.178.29 (shellyplus1 / shellyplus1-cc7b5c85af80 / shellyplus1#cc7b5c85af80#1): state: shellyplus1#cc7b5c85af80#1.uptime, value: 994761
                                          2024-10-15 20:25:27.261  - debug: shelly.0 (1414) [httpIoBrokerState] State change 192.168.178.34 (shellyplus1pm / shellyplus1pm-b0b21c1b4e14 / shellyplus1pm#b0b21c1b4e14#1): state: shellyplus1pm#b0b21c1b4e14#1.uptime, value: 1238121
                                          2024-10-15 20:25:27.261  - debug: shelly.0 (1414) [httpIoBrokerState] State change 192.168.178.34 (shellyplus1pm / shellyplus1pm-b0b21c1b4e14 / shellyplus1pm#b0b21c1b4e14#1): state: shellyplus1pm#b0b21c1b4e14#1.rssi, value: -73
                                          2024-10-15 20:25:31.322  - debug: shelly.0 (1414) [MQTT] Publish: 192.168.178.34 (shellyplus1pm / shellyplus1pm-b0b21c1b4e14 / shellyplus1pm#b0b21c1b4e14#1) - topic: shellyplus1pm-b0b21c1b4e14/events/rpc, qos: 1, payload: {"src":"shellyplus1pm-b0b21c1b4e14","dst":"shellyplus1pm-b0b21c1b4e14/events","method":"NotifyStatus","params":{"ts":1729016726.29,"switch:0":{"id":0,"apower":4.7}}}
                                          2024-10-15 20:25:31.332  - debug: shelly.0 (1414) [MQTT] Publish: 192.168.178.34 (shellyplus1pm / shellyplus1pm-b0b21c1b4e14 / shellyplus1pm#b0b21c1b4e14#1) - topic: shellyplus1pm-b0b21c1b4e14/status/switch:0, qos: 1, payload: {"id":0, "source":"SHC", "output":true, "apower":5.6, "voltage":228.4, "current":0.061, "aenergy":{"total":550.200,"by_minute":[71.439,80.471,65.280],"minute_ts":1729016700},"temperature":{"tC":54.0, "tF":129.3}}
                                          2024-10-15 20:25:31.332  - debug: shelly.0 (1414) [MQTT] State change 192.168.178.34 (shellyplus1pm / shellyplus1pm-b0b21c1b4e14 / shellyplus1pm#b0b21c1b4e14#1): shellyplus1pm-b0b21c1b4e14/status/switch:0 -> state: shellyplus1pm#b0b21c1b4e14#1.Relay0.temperatureC, value: 54
                                          2024-10-15 20:25:31.332  - debug: shelly.0 (1414) [MQTT] State change 192.168.178.34 (shellyplus1pm / shellyplus1pm-b0b21c1b4e14 / shellyplus1pm#b0b21c1b4e14#1): shellyplus1pm-b0b21c1b4e14/status/switch:0 -> state: shellyplus1pm#b0b21c1b4e14#1.Relay0.temperatureF, value: 129.3
                                          2024-10-15 20:25:31.332  - debug: shelly.0 (1414) [MQTT] State change 192.168.178.34 (shellyplus1pm / shellyplus1pm-b0b21c1b4e14 / shellyplus1pm#b0b21c1b4e14#1): shellyplus1pm-b0b21c1b4e14/status/switch:0 -> state: shellyplus1pm#b0b21c1b4e14#1.Relay0.Power, value: 5.6
                                          2024-10-15 20:25:31.332  - debug: shelly.0 (1414) [MQTT] State change 192.168.178.34 (shellyplus1pm / shellyplus1pm-b0b21c1b4e14 / shellyplus1pm#b0b21c1b4e14#1): shellyplus1pm-b0b21c1b4e14/status/switch:0 -> state: shellyplus1pm#b0b21c1b4e14#1.Relay0.Voltage, value: 228.4
                                          2024-10-15 20:25:31.332  - debug: shelly.0 (1414) [MQTT] State change 192.168.178.34 (shellyplus1pm / shellyplus1pm-b0b21c1b4e14 / shellyplus1pm#b0b21c1b4e14#1): shellyplus1pm-b0b21c1b4e14/status/switch:0 -> state: shellyplus1pm#b0b21c1b4e14#1.Relay0.Current, value: 0.061
                                          2024-10-15 20:25:31.332  - debug: shelly.0 (1414) [MQTT] State change 192.168.178.34 (shellyplus1pm / shellyplus1pm-b0b21c1b4e14 / shellyplus1pm#b0b21c1b4e14#1): shellyplus1pm-b0b21c1b4e14/status/switch:0 -> state: shellyplus1pm#b0b21c1b4e14#1.Relay0.Energy, value: 550.2
                                          2024-10-15 20:25:31.786  - debug: shelly.0 (1414) [httpIoBrokerState] State change 192.168.178.35 (shellyplus1pm / shellyplus1pm-d4d4daeb2ddc / shellyplus1pm#d4d4daeb2ddc#1): state: shellyplus1pm#d4d4daeb2ddc#1.uptime, value: 1238120
                                          2024-10-15 20:25:32.606  - debug: shelly.0 (1414) [httpIoBrokerState] State change 192.168.178.33 (shellyplus1pm / shellyplus1pm-cc7b5c0dd95c / shellyplus1pm#cc7b5c0dd95c#1): state: shellyplus1pm#cc7b5c0dd95c#1.uptime, value: 1238132
                                          2024-10-15 20:25:33.444  - debug: shelly.0 (1414) [httpIoBrokerState] State change 192.168.178.38 (shellyplus1pm / shellyplus1pm-d4d4da35853c / shellyplus1pm#d4d4da35853c#1): state: shellyplus1pm#d4d4da35853c#1.uptime, value: 1238128
                                          
                                          

                                          1 Antwort Letzte Antwort
                                          0
                                          Antworten
                                          • In einem neuen Thema antworten
                                          Anmelden zum Antworten
                                          • Älteste zuerst
                                          • Neuste zuerst
                                          • Meiste Stimmen


                                          Support us

                                          ioBroker
                                          Community Adapters
                                          Donate

                                          766

                                          Online

                                          32.4k

                                          Benutzer

                                          81.4k

                                          Themen

                                          1.3m

                                          Beiträge
                                          Community
                                          Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen | Einwilligungseinstellungen
                                          ioBroker Community 2014-2025
                                          logo
                                          • Anmelden

                                          • Du hast noch kein Konto? Registrieren

                                          • Anmelden oder registrieren, um zu suchen
                                          • Erster Beitrag
                                            Letzter Beitrag
                                          0
                                          • Home
                                          • Aktuell
                                          • Tags
                                          • Ungelesen 0
                                          • Kategorien
                                          • Unreplied
                                          • Beliebt
                                          • GitHub
                                          • Docu
                                          • Hilfe