Hallo an alle,
ich habe seit einiger Zeit das Problem dass wenn ich mein Shelly plus Plug S, egal ob über Gerätetaste, App oder GUI einschalte, es sich nach kurzer Zeit wieder deaktiviert. Es liegt auch keine Last an, der plus Plug S ist somit im Leerlauf.
Die Firmware ist auf dem neusten Stand: 20240726-114505/1.4.0-gb2aeadb
Es gibt keine Schaltzeiten oder ähnliches.
Und die “Input/Output settings” sind auf: “Restore last known state of output/relay”
Jetzt habe ich mal bei den Diagnostics den “device log” aktiviert und sehe dass irgendjemand immer den Shelly abschaltet:
im Log ist zu sehen dass ich ihn
- mit der GUI eingeschaltet habe, dann ist der aus.
- mit der App eingeschaltet habe, dann ist der aus.
- am Taster eingeschaltet habe, dann ist der aus.
shos_rpc_inst.c:242 switch.toggle via WS_in 192.168.178.37:62435
09:05:20
shelly_notification:162 Status change of switch:0: {"id":0,"output":true,"source":"WS_in"}
09:05:20
shelly_notification:162 Status change of switch:0: {"id":0,"voltage":233.5}
09:05:26
shelly_notification:162 Status change of switch:0: {"id":0,"aenergy":{"by_minute":[0.000,0.000,0.000],"minute_ts":1723273560,"total":261037.038}}
09:06:00
shos_rpc_inst.c:242 Switch.Set via SHC 34.76.136.111:6022
09:06:03
shelly_notification:162 Status change of switch:0: {"id":0,"apower":0,"current":0,"output":false,"source":"SHC","voltage":0}
09:06:03
shos_rpc_inst.c:242 shelly.getdeviceinfo via WS_in 192.168.178.63:44812
09:06:32
shos_rpc_inst.c:242 shelly.getcomponents via WS_in 192.168.178.63:44812
09:06:38
shos_init.c:94 New min heap free: 119232
09:06:38
shos_rpc_inst.c:242 switch.Set via HTTP_in POST 192.168.178.63:45324
09:06:38
shelly_notification:162 Status change of switch:0: {"id":0,"output":true,"source":"HTTP_in"}
09:06:38
shos_rpc_inst.c:242 shelly.getcomponents via WS_in 192.168.178.63:44812
09:06:38
shelly_debug.cpp:236 Streaming logs to 192.168.178.63:45328
09:06:38
shos_rpc_inst.c:242 schedule.list via WS_in 192.168.178.63:44812
09:06:38
shos_rpc_inst.c:242 shelly.listmethods via WS_in 192.168.178.63:44812
09:06:38
shos_rpc_inst.c:242 webhook.list via WS_in 192.168.178.63:44812
09:06:38
shos_rpc_inst.c:242 webhook.listsupported via WS_in 192.168.178.63:44812
09:06:38
shos_init.c:94 New min heap free: 118496
09:06:38
shos_rpc_inst.c:242 kvs.getmany via WS_in 192.168.178.63:44812
09:06:39
shos_rpc_inst.c:242 schedule.list via WS_in 192.168.178.63:44812
09:06:39
shos_init.c:94 New min heap free: 118368
09:06:39
shelly_debug.cpp:236 Streaming logs to 192.168.178.63:45330
09:06:39
shos_init.c:94 New min heap free: 118040
09:06:39
shos_init.c:94 New min heap free: 117580
09:06:39
shos_init.c:94 New min heap free: 117412
09:06:39
shelly_notification:162 Status change of switch:0: {"id":0,"voltage":234.4}
09:06:44
shos_init.c:94 New min heap free: 116768
09:06:53
shelly_notification:162 Status change of switch:0: {"id":0,"aenergy":{"by_minute":[0.000,0.000,0.000],"minute_ts":1723273620,"total":261037.038}}
09:07:00
shos_rpc_inst.c:242 Switch.Set via SHC 34.76.136.111:6022
09:07:03
shelly_notification:162 Status change of switch:0: {"id":0,"apower":0,"current":0,"output":false,"source":"SHC","voltage":0}
09:07:03
shos_time.c:54 Setting time from SNTP (1723273628.706 delta -3.286)
09:07:08
shelly_sys.cpp:217 Time set to 516023.912930 from 1
09:07:08
shelly_notification:162 Status change of switch:0: {"id":0,"output":true,"source":"button"}
09:07:17
shelly_notification:162 Status change of switch:0: {"id":0,"voltage":233.0}
09:07:23
shelly_notification:162 Status change of switch:0: {"id":0,"aenergy":{"by_minute":[0.000,0.000,0.000],"minute_ts":1723273680,"total":261037.038}}
09:08:00
shos_rpc_inst.c:242 Switch.Set via SHC 34.76.136.111:6022
09:08:00
shelly_notification:162 Status change of switch:0: {"id":0,"apower":0,"current":0,"output":false,"source":"SHC","voltage":0}
09:08:00
shos_init.c:94 New min heap free: 115964
09:08:00
shos_init.c:94 New min heap free: 114912
09:08:00
shos_init.c:94 New min heap free: 113520
09:08:00
shos_init.c:94 New min heap free: 111464
09:08:00
shelly_notification:162 Status change of switch:0: {"id":0,"aenergy":{"by_minute":[0.000,0.000,0.000],"minute_ts":1723273740,"total":261037.038}}
09:09:00
shos_rpc_inst.c:242 Switch.Set via SHC 34.76.136.111:6022
09:09:00
shelly_notification:162 Status change of switch:0: {"id":0,"aenergy":{"by_minute":[0.000,0.000,0.000],"minute_ts":1723273800,"total":261037.038}}
09:10:00
shos_rpc_inst.c:242 Switch.Set via SHC 34.76.136.111:6022
09:10:00
shelly_notification:162 Status change of switch:0: {"id":0,"aenergy":{"by_minute":[0.000,0.000,0.000],"minute_ts":1723273860,"total":261037.038}}
09:11:00
shos_rpc_inst.c:242 Switch.Set via SHC 34.76.136.111:6022
09:11:00
shelly_notification:162 Status change of switch:0: {"id":0,"aenergy":{"by_minute":[0.000,0.000,0.000],"minute_ts":1723273920,"total":261037.038}}
09:12:00
shos_rpc_inst.c:242 Switch.Set via SHC 34.76.136.111:6022
09:12:00
shelly_notification:162 Status change of switch:0: {"id":0,"aenergy":{"by_minute":[0.000,0.000,0.000],"minute_ts":1723273980,"total":261037.038}}
09:13:00
shos_rpc_inst.c:242 Switch.Set via SHC 34.76.136.111:6022
09:13:00
Nachdem ich die Cloud deaktiviert habe, bleibt der Schaltzustand stabil.
Ich hätte den schon gern in der Shelly App.
Sobald ich die Cloud wieder aktiviere, beginnt wieder die Abschaltung.
hat den jemand gehackt, oder was ist das Problem?
Kennt jemand das Problem?
