Trying to narrow down this issue where I see random periodic reboots of my Shelly 2.5 controlling 2 channels of kitchen lights, here in the U.S. (120V)
Shelly 2.5 on firmware version:
20211109-125214/v1.11.7-g682a0dwhere Channel 1 is powering 27W lights and Channel 2 is powering 13W light.
Steps I take to reproduce:
1. Turn on both channel lights
2. Go to http://[DEVICE IP]/ and click around normally, or leave the browser open. Sometimes 2a), the URL page hangs with the page loading spinner
3. The Shelly 2.5 randomly reboots and I observe my channel lights turn off then back on
3a) Alternatively, calling the status URL every few seconds directly in browser also randomly reboots it. A few sample captures of status results with a low uptime value confirm that the device indeed rebooted (did not crash). Here are some sample returns that do not indicate any Power overloading, weak WIFI, low RAM, or over temperature issues and show what I see before it crashes randomly:
{"wifi_sta":{"connected":true,"ssid":"[redacted]","ip":"192.168.86.27","rssi":-50},"cloud":{"enabled":false,"connected":false},"mqtt":{"connected":false},"time":"09:56","unixtime":1638802607,"serial":1,"has_update":false,"mac":"3C6105E54B78","cfg_changed_cnt":0,"actions_stats":{"skipped":0},"relays":[{"ison":true,"has_timer":false,"timer_started":0,"timer_duration":0,"timer_remaining":0,"overpower":false,"overtemperature":false,"is_valid":true,"source":"input"},{"ison":true,"has_timer":false,"timer_started":0,"timer_duration":0,"timer_remaining":0,"overpower":false,"overtemperature":false,"is_valid":true,"source":"input"}],"meters":[{"power":27.24,"overpower":0.00,"is_valid":true,"timestamp":1638784607,"counters":[0.000, 0.000, 0.000],"total":0},{"power":13.85,"overpower":0.00,"is_valid":true,"timestamp":1638784607,"counters":[0.000, 0.000, 0.000],"total":0}],"inputs":[{"input":0,"event":"","event_cnt":0},{"input":1,"event":"","event_cnt":0}],"temperature":65.60,"overtemperature":false,"tmp":{"tC":65.60,"tF":150.09, "is_valid":true},"temperature_status":"Normal","update":{"status":"unknown","has_update":false,"new_version":"","old_version":"20211109-125214/v1.11.7-g682a0db"},"ram_total":49944,"ram_free":36812,"fs_size":233681,"fs_free":130771,"voltage":124.16,"uptime":16}{"wifi_sta":{"connected":true,"ssid":"[redacted]","ip":"192.168.86.27","rssi":-52},"cloud":{"enabled":false,"connected":false},"mqtt":{"connected":false},"time":"10:04","unixtime":1638803087,"serial":1,"has_update":false,"mac":"3C6105E54B78","cfg_changed_cnt":0,"actions_stats":{"skipped":0},"relays":[{"ison":true,"has_timer":false,"timer_started":0,"timer_duration":0,"timer_remaining":0,"overpower":false,"overtemperature":false,"is_valid":true,"source":"input"},{"ison":true,"has_timer":false,"timer_started":0,"timer_duration":0,"timer_remaining":0,"overpower":false,"overtemperature":false,"is_valid":true,"source":"input"}],"meters":[{"power":27.49,"overpower":0.00,"is_valid":true,"timestamp":1638785087,"counters":[27.343, 27.390, 27.175],"total":81},{"power":13.91,"overpower":0.00,"is_valid":true,"timestamp":1638785087,"counters":[13.883, 13.882, 13.763],"total":41}],"inputs":[{"input":0,"event":"","event_cnt":0},{"input":1,"event":"","event_cnt":0}],"temperature":65.60,"overtemperature":false,"tmp":{"tC":65.60,"tF":150.09, "is_valid":true},"temperature_status":"Normal","update":{"status":"idle","has_update":false,"new_version":"20211109-125214/v1.11.7-g682a0db","old_version":"20211109-125214/v1.11.7-g682a0db"},"ram_total":49944,"ram_free":37572,"fs_size":233681,"fs_free":130771,"voltage":124.23,"uptime":253}When I turn off either of the channels, or both, I cannot reproduce this reset issue. This problem only occurs when both channels are powered.
I assume this is firmware as this is a second replacement Shelly 2.5 and it's only caused by my active URL requests (or from the web UI page). If I close the browser window, I don't see these issues.
Now, I don't plan to use the Web UI frequently, and instead plan to use local MQTT with Home Assistant. But am a bit concerned that just some regular page loads of the Web UI are indicative of a bigger problem where the Shelly 2.5 server code is unable to handle any load.
Any one have seen similar issues?
Thanks