Shelly 2.5 In Client Mode with Both Channels "off" Goes into Reboot Loop

  • Hi,

    (apologies for a previous version of this post named "WiFi Issues" - the problem turns out not to be a WiFi issue, turned out to be a mis-diagnosis)

    I'm evaluating Shelly products for home use, so I purchased a few different products and am experimenting with them.

    I'm seeing a rather weird issue with the 2.5 switch. It's running the latest (1.10.4) firmware but the problem seems to have been there with the stock (2019) firmware as well.

    When I connect to the 2.5 in AP mode, everything works well. Immediate web UI response, instantaneous operation (on/off/readout/configuration) - the works.

    When I configure it to join my WiFi LAN, problems begin. The switch joins the network, but its response time is abysmal. Can take two minutes to draw an initial web UI screen (if it does at all). "ping" to it shows massive (over 40%) packet loss, and the responses that do get back take like 2000-3000ms (good reason for slow response...).

    Investigating it I found that the switch goes into a reboot loop. It just keeps rebooting every few seconds. Extracting "uptime" from the API via curl shows it clearly.

    Factory reset, reconfigure - same story.

    What seems to resolve the issue is powering one of the channels on. Once at least one of the channels is "on" - the switch stops rebooting and becomes still and responsive. Both set to "off"- reboot loop resumes.

    Any help will be greatly appreciated. Thanks!

    2 Mal editiert, zuletzt von doron (28. Juni 2021 um 13:07)

  • doron 28. Juni 2021 um 13:07

    Hat den Titel des Themas von „WiFi issues with Shelly 2.5“ zu „Shelly 2.5 In Client Mode with Both Channels "off" Goes into Reboot Loop“ geändert.
  • Some more data to try to shed light on this - here's what I get in the debug log:

    This is when I turn the last channel that was "on" to "off" (could be done via the switch connected to "sw" or via web UI - same behavior). For some reason the WiFi station immediately disconnects, and the devices reboots - only to keep doing this in a loop.

    Set one of the channels to "on" - everything is stable again.