Shelly stops working - econnreset

[DerRene97]

Shelly device

shelly1

Protocol (CoAP / MQTT)

CoAP

The problem

Hi,

Most of the day the shelly is running fine, but somehow everyday at about the same time the adapter throws this error:

[http controlFunction] Error in function state.coap.http_cmd of state SHSW-1#68C63AFA082D#1.Relay0.Switch for 192.168.178.38 (shelly1 / shelly1-68C63AFA082D / SHSW-1#68C63AFA082D#1): Error: read ECONNRESET

After this happened, the switch stays on and i have to manually switch it off/on to get it working again.

How do i fix this?

Version of nodejs

16.17.1

Version of ioBroker js-controller

6.0.3

Version of Adapter

6.0.0

Operating system running ioBroker

Linux

Checklist of files to include below

• [X] iobroker.current.log (Please share the logs in debug mode)
• [ ] Contents of the JavaScript browser console (always include in cases of issues with the user interface)

Additional information & file uploads

[http controlFunction] Error in function state.coap.http_cmd of state SHSW-1#68C63AFA082D#1.Relay0.Switch for 192.168.178.38 (shelly1 / shelly1-68C63AFA082D / SHSW-1#68C63AFA082D#1): Error: read ECONNRESET

[Apollon77]

ECONNRESET normally means that the device itself closed the connection!

[DerRene97]

But how does this happen so frequently and only once a day? All other devices are working fine The problem appeared after updating my iobroker adapter, npm and everything

Is there a common solution for this?

[klein0r]

But how does this happen so frequently and only once a day?

Maybe the wifi connection is not stable to that specific device?

[chris299]

I have a similar issue with one shelly 2.5 (but only one out of a whole bunch of them in my network) which shows such strange behaviour: once every 10 minutes I get this error, and it is really very regular every 10 minutes.... (but mqtt though) As I can exclude the wifi-connection itself as a reason, I assume that either the shelly is broken or something else makes it stall every 10 minutes... (I also tried factory reset already, etc)

[DerRene97]

I can exlude the wifi connection as well. The shelly is about 2 meters away from the router.

I got shelly plugs and some other stuff running with iobroker without these problems.

[klein0r]

Which firmware version is installed on the devices? Everything up to date?

[chris299]

in my case it seems to be related to DHCP (for whatever reason...) after configuring the shelly to use a fixed IP it does not happen anymore. maybe I have some weird things going on in my fritzbox...

[DerRene97]

My shellys are all up to date. Version: 20220809-123240/v1.12-g99f7e0b

All my shellys use a fixed IP, so this cant be the problem for me as well.

[JuniperChris929]

I once had a similar issue - 3 days later this shelly device literally "exploded" - so my guess was, that the memory was getting corrupted before which resulted in the device sending the error and later "dying".

If it's just this very one shelly I honestly would just replace it - usually, after showing this to allterco, they will simply send you a new one. Some of them had a bad batch of resistors - maybe you got "lucky" and yours is one of the broken ones.

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs within the next 7 days. Please check if the issue is still relevant in the most current version of the adapter and tell us. Also check that all relevant details, logs and reproduction steps are included and update them if needed. Thank you for your contributions. Dieses Problem wurde automatisch als veraltet markiert, da es in letzter Zeit keine Aktivitäten gab. Es wird geschlossen, wenn nicht innerhalb der nächsten 7 Tage weitere Aktivitäten stattfinden. Bitte überprüft, ob das Problem auch in der aktuellsten Version des Adapters noch relevant ist, und teilt uns dies mit. Überprüft auch, ob alle relevanten Details, Logs und Reproduktionsschritte enthalten sind bzw. aktualisiert diese. Vielen Dank für Eure Unterstützung.

[stale[bot]]

This issue has been automatically closed because of inactivity. Please open a new issue if still relevant and make sure to include all relevant details, logs and reproduction steps. Thank you for your contributions. Dieses Problem wurde aufgrund von Inaktivität automatisch geschlossen. Bitte öffnet ein neues Issue, falls dies noch relevant ist und stellt sicher das alle relevanten Details, Logs und Reproduktionsschritte enthalten sind. Vielen Dank für Eure Unterstützung.