Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

error: shelly.0 (2903) Exception: Error: No reply in 247s #106

Closed
HGlab01 opened this issue Dec 20, 2019 · 1 comment
Closed

error: shelly.0 (2903) Exception: Error: No reply in 247s #106

HGlab01 opened this issue Dec 20, 2019 · 1 comment

Comments

@HGlab01
Copy link
Contributor

HGlab01 commented Dec 20, 2019

Describe the bug
Since today 03:54:37 in the morning I find the line
error: shelly.0 (2903) Exception: Error: No reply in 247s
in the log.
I did not change something in my configuration and I am still on Shelly version 1.5.6
Have others the same issue?


2019-12-20 03:54:37.438 - error: shelly.0 (2903) Exception: Error: No reply in 247s
--
2019-12-20 03:54:37.457 - info: host.ioBroker instance system.adapter.shelly.0 terminated with code 0 (NO_ERROR)
2019-12-20 03:54:37.458 - info: host.ioBroker Restart adapter system.adapter.shelly.0 because enabled
2019-12-20 03:55:07.479 - info: host.ioBroker instance system.adapter.shelly.0 started with pid 2976
2019-12-20 03:55:08.413 - info: shelly.0 (2976) starting. Version 3.1.1 in /opt/iobroker/node_modules/iobroker.shelly, node: v10.17.0
2019-12-20 03:55:08.443 - info: shelly.0 (2976) Stating Shelly adapter in CoAP modus.
2019-12-20 03:55:08.526 - info: shelly.0 (2976) Listening for Shelly packets in the network

Versions:

  • Adapter version: 3.1.1
  • JS-Controller version: 2.1.1
  • Node version: v10.17.0
  • Operating system: Linux, x64
@schmupu
Copy link
Contributor

schmupu commented Dec 20, 2019

I can not help you. It is a problem with the CoAP API. See Issue #71

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants