Shellys per mqtt keine Verbindung

[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

[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>

[Homoran]

@accuface sagte in Shellys per mqtt keine Verbindung:

host.raspberrypi5 received SIGTERM

Hast du den Raspi oder iobroker neu gestartet?

[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

[Homoran]

@accuface sagte in Shellys per mqtt keine Verbindung:

Ich sollte den doch rebooten

aber doch nicht jedesmal für ein log

[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

[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.

[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?

[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?

[Accuface]

@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

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.

[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

[crunchip]

@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

[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

[Accuface]

@homoran

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

[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

[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?

[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

[Accuface]

@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

[Homoran]

@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

[crunchip]

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