SHELLY PLUG bootet unkontrolliert alle paar Minuten

fraso

Hi,

habe div. ShellyPlugS in Betrieb. Die booten sich alle regelmäßig alle paar Minuten.

Fritz.Box

kein Repeater

Mein aktuelles "Test Shelly Plug" welches ich unter Beobachtung halte ist 4m vom Router entfernt.

Eintrag im Fritz Protokoll:

Code

10:41:55
WLAN-Gerät angemeldet (2,4 GHz), 72 Mbit/s, shellyplug-s-EF6D88, IP 192.168.178.190, MAC 3C:61:05:EF:6D:88.
12.02.22
10:41:55
WLAN-Gerät hat sich abgemeldet (2,4 GHz), shellyplug-s-EF6D88, IP 192.168.178.190, MAC 3C:61:05:EF:6D:88.

Kein Repeater dazwischen oder sonst was.

Hier das "CURRENT LOG" nachdem ich DEBUG angeschaltet. habe. Was bedeutet "minute tick"? Was genau mir das Log sagt weiß ich nicht.

Das ganze entwickelt sich hier zu einem Problem da ich eigentlich die SP2 zum Strom messen habe. Bei Reboot verliert er aber die Werte.

Code

838779928 mgos_http_server.c:180  0x3fff26e4 HTTP connection from 192.168.178.35:37806
838793694 json.c:426              RAM: 51264 total, 35324 free
840821122 mgos_http_server.c:180  0x3fff24bc HTTP connection from 192.168.178.35:37902
840860324 mgos_http_server.c:180  0x3fff18f4 HTTP connection from 192.168.178.35:37906
840902775 mgos_http_server.c:180  0x3fff26e4 HTTP connection from 192.168.178.35:37912
840919069 json.c:426              RAM: 51264 total, 35440 free
842978399 mgos_http_server.c:180  0x3fff2574 HTTP connection from 192.168.178.35:37996
843105196 mgos_http_server.c:180  0x3fff262c HTTP connection from 192.168.178.35:38008
843172793 mgos_http_server.c:180  0x3fff26e4 HTTP connection from 192.168.178.35:38016
843186932 json.c:426              RAM: 51264 total, 35440 free
845230819 mgos_http_server.c:180  0x3fff234c HTTP connection from 192.168.178.35:38096
845276706 mgos_http_server.c:180  0x3fff26e4 HTTP connection from 192.168.178.35:38102
845331363 mgos_http_server.c:180  0x3fff275c HTTP connection from 192.168.178.35:38106
845348703 json.c:426              RAM: 51264 total, 35440 free
847370796 mgos_http_server.c:180  0x3fff2404 HTTP connection from 192.168.178.35:38184
847406101 mgos_http_server.c:180  0x3fff2234 HTTP connection from 192.168.178.35:38188
847452094 mgos_http_server.c:180  0x3fff18f4 HTTP connection from 192.168.178.35:38190
847466251 json.c:426              RAM: 51264 total, 35440 free
849533559 mgos_http_server.c:180  0x3ffef94c HTTP connection from 192.168.178.35:38272
849556970 mgos_http_server.c:180  0x3fff18f4 HTTP connection from 192.168.178.35:38274
849589800 mgos_http_server.c:180  0x3fff26e4 HTTP connection from 192.168.178.35:38276
849603959 json.c:426              RAM: 51264 total, 35440 free
851622192 mgos_http_server.c:180  0x3fff24bc HTTP connection from 192.168.178.35:38370
851645411 mgos_http_server.c:180  0x3fff26e4 HTTP connection from 192.168.178.35:38376
851679328 mgos_http_server.c:180  0x3fff18f4 HTTP connection from 192.168.178.35:38378
851696597 json.c:426              RAM: 51264 total, 35440 free
853723664 mgos_http_server.c:180  0x3fff26e4 HTTP connection from 192.168.178.35:38482
853801592 mgos_http_server.c:180  0x3fff26a4 HTTP connection from 192.168.178.35:38484
853871573 mgos_http_server.c:180  0x3fff18f4 HTTP connection from 192.168.178.35:38486
853934033 json.c:426              RAM: 51264 total, 35440 free
855970482 mgos_http_server.c:180  0x3fff18f4 HTTP connection from 192.168.178.35:38592
856004982 mgos_http_server.c:180  0x3fff2e3c HTTP connection from 192.168.178.35:38594
856069488 mgos_http_server.c:180  0x3fff18f4 HTTP connection from 192.168.178.35:38596
856083688 json.c:426              RAM: 51264 total, 35440 free
858107426 mgos_http_server.c:180  0x3fff2404 HTTP connection from 192.168.178.35:38674
858140436 mgos_http_server.c:180  0x3fff18f4 HTTP connection from 192.168.178.35:38676
858194573 mgos_http_server.c:180  0x3fff27d4 HTTP connection from 192.168.178.35:38678
858208985 json.c:426              RAM: 51264 total, 35436 free
858743893 shelly_sntp.c:433       minute tick at 10:26:00
860246505 mgos_http_server.c:180  0x3fff18f4 HTTP connection from 192.168.178.35:38766
860281589 mgos_http_server.c:180  0x3fff2814 HTTP connection from 192.168.178.35:38768
860405543 mgos_http_server.c:180  0x3fff2b5c HTTP connection from 192.168.178.35:38770
860421982 json.c:426              RAM: 51264 total, 35400 free
862464463 mgos_http_server.c:180  0x3fff18f4 HTTP connection from 192.168.178.35:38856
862514891 mgos_http_server.c:180  0x3fff2ef4 HTTP connection from 192.168.178.35:38858
862580706 mgos_http_server.c:180  0x3fff2814 HTTP connection from 192.168.178.35:38864
862598001 json.c:426              RAM: 51264 total, 35440 free
864644437 mgos_http_server.c:180  0x3fff2534 HTTP connection from 192.168.178.35:38956
864660085 mgos_http_server.c:180  0x3fff262c HTTP connection from 192.168.178.64:58127
864674411 json.c:426              RAM: 51264 total, 33556 free
864711334 mgos_http_server.c:180  0x3fff18f4 HTTP connection from 192.168.178.35:38958
864779239 mgos_http_server.c:180  0x3fff26a4 HTTP connection from 192.168.178.35:38968
864835179 json.c:426              RAM: 51264 total, 35252 free
866860115 mgos_http_server.c:180  0x3fff234c HTTP connection from 192.168.178.35:39060
866891015 mgos_http_server.c:180  0x3fff2e3c HTTP connection from 192.168.178.35:39062
866976213 mgos_http_server.c:180  0x3fff262c HTTP connection from 192.168.178.35:39066
866990645 json.c:426              RAM: 51264 total, 35256 free
869020763 mgos_http_server.c:180  0x3fff2404 HTTP connection from 192.168.178.35:39168
869093365 mgos_http_server.c:180  0x3fff262c HTTP connection from 192.168.178.35:39170
869140267 mgos_http_server.c:180  0x3fff18f4 HTTP connection from 192.168.178.35:39178
869155815 json.c:426              RAM: 51264 total, 35252 free
871186797 mgos_http_server.c:180  0x3fff2d84 HTTP connection from 192.168.178.35:39232
873528566 mgos_http_server.c:180  0x3fff2d84 HTTP connection from 192.168.178.35:39268
873716599 mgos_http_server.c:180  0x3fff2b5c HTTP connection from 192.168.178.35:39296
873775712 json.c:426              RAM: 51264 total, 35800 free
874092170 mgos_http_server.c:180  0x3fff2c14 HTTP connection from 192.168.178.35:39332
875805827 mgos_http_server.c:180  0x3fff2b5c HTTP connection from 192.168.178.35:39380
877869501 mgos_http_server.c:180  0x3fff2e3c HTTP connection from 192.168.178.35:39412
877998898 mgos_http_server.c:180  0x3fff2b5c HTTP connection from 192.168.178.35:39426
878016094 json.c:426              RAM: 51264 total, 36544 free
880071635 mgos_http_server.c:180  0x3fff2aa4 HTTP connection from 192.168.178.35:39488
880098044 mgos_http_server.c:180  0x3fff18f4 HTTP connection from 192.168.178.35:39498
880191095 mgos_http_server.c:180  0x3fff2c14 HTTP connection from 192.168.178.35:39500
880205004 json.c:426              RAM: 51264 total, 36540 free
882233894 mgos_http_server.c:180  0x3fff2c14 HTTP connection from 192.168.178.35:39588
882358841 mgos_http_server.c:180  0x3fff2ccc HTTP connection from 192.168.178.35:39592
882461266 mgos_http_server.c:180  0x3fff18f4 HTTP connection from 192.168.178.35:39600
882475145 json.c:426              RAM: 51264 total, 36176 free
884500903 mgos_http_server.c:180  0x3fff2ef4 HTTP connection from 192.168.178.35:39704
884525441 mgos_http_server.c:180  0x3fff18f4 HTTP connection from 192.168.178.35:39706
884569019 mgos_http_server.c:180  0x3fff18f4 HTTP connection from 192.168.178.35:39708
884584021 json.c:426              RAM: 51264 total, 35872 free
886604772 mgos_http_server.c:180  0x3fff24bc HTTP connection from 192.168.178.35:39804
886633597 mgos_http_server.c:180  0x3fff2574 HTTP connection from 192.168.178.35:39806
886720876 mgos_http_server.c:180  0x3fff262c HTTP connection from 192.168.178.35:39808
886737686 json.c:426              RAM: 51264 total, 35504 free
888813283 mgos_http_server.c:180  0x3fff2e3c HTTP connection from 192.168.178.35:39886
888839118 mgos_http_server.c:180  0x3fff26a4 HTTP connection from 192.168.178.35:39888
888909284 mgos_http_server.c:180  0x3fff26e4 HTTP connection from 192.168.178.35:39892
888925777 json.c:426              RAM: 51264 total, 35448 free
890959923 mgos_http_server.c:180  0x3fff2aa4 HTTP connection from 192.168.178.35:39970
890989611 mgos_http_server.c:180  0x3fff18f4 HTTP connection from 192.168.178.35:39974
891102983 mgos_http_server.c:180  0x3fff26e4 HTTP connection from 192.168.178.35:39980
891117236 json.c:426              RAM: 51264 total, 35436 free
893141234 mgos_http_server.c:180  0x3fff2c14 HTTP connection from 192.168.178.35:40060
893177756 mgos_http_server.c:180  0x3fff2ccc HTTP connection from 192.168.178.35:40062
893222247 mgos_http_server.c:180  0x3fff18f4 HTTP connection from 192.168.178.35:40066
893237698 json.c:426              RAM: 51264 total, 35316 free
895313508 mgos_http_server.c:180  0x3fff2ef4 HTTP connection from 192.168.178.35:40146
895349289 mgos_http_server.c:180  0x3fff2404 HTTP connection from 192.168.178.35:40152
895444855 mgos_http_server.c:180  0x3fff26e4 HTTP connection from 192.168.178.35:40156
895461058 json.c:426              RAM: 51264 total, 35440 free
897480275 mgos_http_server.c:180  0x3fff24bc HTTP connection from 192.168.178.35:40250
897509337 mgos_http_server.c:180  0x3fff18f4 HTTP connection from 192.168.178.35:40256
897553919 mgos_http_server.c:180  0x3fff18f4 HTTP connection from 192.168.178.35:40258
897568178 json.c:426              RAM: 51264 total, 35436 free
899594898 mgos_http_server.c:180  0x3fff2e3c HTTP connection from 192.168.178.35:40356
899625308 mgos_http_server.c:180  0x3fff18f4 HTTP connection from 192.168.178.35:40358
899675506 mgos_http_server.c:180  0x3fff26e4 HTTP connection from 192.168.178.35:40360
899736839 json.c:426              RAM: 51264 total, 35440 free
901761351 mgos_http_server.c:180  0x3fff2aa4 HTTP connection from 192.168.178.35:40452
901796470 mgos_http_server.c:180  0x3fff2b5c HTTP connection from 192.168.178.35:40454
901881606 mgos_http_server.c:180  0x3fff26e4 HTTP connection from 192.168.178.35:40458
901895876 json.c:426              RAM: 51264 total, 35440 free
903924039 mgos_http_server.c:180  0x3fff2c14 HTTP connection from 192.168.178.35:40546
904002537 mgos_http_server.c:180  0x3fff2ccc HTTP connection from 192.168.178.35:40548
904066286 mgos_http_server.c:180  0x3fff275c HTTP connection from 192.168.178.35:40554
904080676 json.c:426              RAM: 51264 total, 35440 free
904234420 mgos_http_server.c:180  0x3fff279c HTTP connection from 192.168.178.35:40570
904245169 shelly_update.c:168     Starting ota from http://shelly-api-eu.shelly.cloud/firmware/SHPLG-S.zip
904794607 mgos_ota_http_clien:270 Update URL: http://shelly-api-eu.shelly.cloud/firmware/SHPLG-S.zip
904879496 mgos_ota_core.c:268     Starting, timeout 240, commit timeout 0, mem 33904
904892329 mgos_ota_core.c:652     FW: shelly-plug-s esp8266 1.0 20220209-094058/v1.11.8-g8c7bb8d sig 0x00
904897545 mgos_ota_core.c:1050    Update finished, result 1 (Version is the same as current)
904910410 shelly_update.c:111     SHOTA: success Version is the same as current
904915089 shelly_update.c:120     OTA is a success!
904920032 shelly_util.c:344       RF Start address 1fb000 4096

Alles anzeigen

Danke für jede Hilfe was ich probieren kann.

fraso

Wollte mal testweise Downgraden. Das geht auch nicht wie beschrieben. Shelly fängt an mich zu frustrieren obwohl ich davon viel Gutes gehört habe. Kann mir einer Tips geben? Danke.

http://192.168.178.190/ota?url=http://archive.shelly-support.eu/v1.11.7/SHPLG2-1_build.zip

Code

{"status":"updating","has_update":false,"new_version":"20220209-094058/v1.11.8-g8c7bb8d","old_version":"20220209-094058/v1.11.8-g8c7bb8d"}

fraso

Habe einen der nicht bootet. Der einzige Unterschied ist der Eintrag in "VERSION":

bootet dauernd: 20220209-094058/v1.11.8-g8c7bb8d

bootet nicht: 20190516-073020/master@ea1b23db

Es steht zwar auf beiden SHELLYPLUGS drauf, sind aber anscheinend andere Modelle. Bei dem welches nicht bootet wird mir auch keine neuere Firmware angeboten:

pasted-from-clipboard.png

Wie gesagt der - Downgrade zum testen ging bei dem mit 1.11.8 aber auch nicht. Sonst hätte ich das gleich mal getestet.

66er

Wovon reden wir denn nun tatsächlich?

In einem anderen Thread schreibst Du vom Shelly Plug. Hier schreibst Du im Unterforum Shelly PlugS.

Zitat

...
habe div. ShellyPlug2 in Betrieb.

Habe ich wohl verpasst, denn kenne ich nicht.

fraso

ja sorry. ShellyPlugS. Ändere das gleich.

SHELLY PLUG bootet unkontrolliert alle paar Minuten

fraso 12. Februar 2022 um 18:23

Ähnliche Themen

Shelly Plug S schalten

Shelly Plug rebootet unkontrolliert

PlugS schaltet sich (un)regelmäßig ab

Alle Shelly's plötzlich offline

Shelly Plug S plötzlich ausgeschaltet

Kann es sein, dass Smartplugs den Strom begrenzen?

Tags