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.

Sign up for GitHub

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

Jump to bottom

shelly adapter loops #96

Closed
smarti2019 opened this issue Oct 12, 2019 · 11 comments
Closed

shelly adapter loops #96

smarti2019 opened this issue Oct 12, 2019 · 11 comments
Assignees
@schmupu

Comments

@smarti2019
Copy link

The shelly adapter is constantly restarts. what can this be?

shelly.0 2019-10-12 10:46:21.070 info (1490) Stating Shelly adapter in CoAP modus.
shelly.0 2019-10-12 10:46:21.041 info (1490) starting. Version 3.1.1 in /opt/iobroker/node_modules/iobroker.shelly, node: v10.16.3
shelly.0 2019-10-12 10:45:49.775 info (1473) Stating Shelly adapter in CoAP modus.
shelly.0 2019-10-12 10:45:49.752 info (1473) starting. Version 3.1.1 in /opt/iobroker/node_modules/iobroker.shelly, node: v10.16.3
shelly.0 2019-10-12 10:45:18.567 info (1458) Stating Shelly adapter in CoAP modus.
shelly.0 2019-10-12 10:45:18.534 info (1458) starting. Version 3.1.1 in /opt/iobroker/node_modules/iobroker.shelly, node: v10.16.3
@schmupu
Copy link
Contributor

schmupu commented Oct 12, 2019

Unfortunatly the Logfile does not help, because there are no errors recognizable.
Please could you change the logfile to the debug Modus and send me this one.

since when is it like this? What did you change? Network Changes, Adapter update, js-contoller update, new Shelly devices, IP address changes, ...? I need more information to find the cause.

@schmupu schmupu self-assigned this Oct 12, 2019
@smarti2019
Copy link
Author

smarti2019 commented Oct 12, 2019 •
edited by schmupu

i changed only the nodejs version from 8x to 10.16.3
so, the log modus is now in debug mode:


2019-10-12 13:36:01.429  - debug: shelly.0 (6990) Redis Objects: Use Redis connection: 127.0.0.1:9001
2019-10-12 13:36:01.450  - debug: shelly.0 (6990) objectDB connected
2019-10-12 13:36:01.452  - debug: shelly.0 (6990) Redis States: Use Redis connection: 127.0.0.1:6379
2019-10-12 13:36:01.453  - debug: shelly.0 (6990) Objects connected to redis: 127.0.0.1:9001
2019-10-12 13:36:01.456  - debug: shelly.0 (6990) statesDB connected
2019-10-12 13:36:01.465  - debug: shelly.0 (6990) States connected to redis: 127.0.0.1:6379
2019-10-12 13:36:01.864  - info: shelly.0 (6990) starting. Version 3.1.1 in /opt/iobroker/node_modules/iobroker.shelly, node: v10.16.3
2019-10-12 13:36:01.884  - info: shelly.0 (6990) Stating Shelly adapter in CoAP modus.
2019-10-12 13:36:01.902  - info: host.iobroker instance system.adapter.shelly.0 terminated with code 0 (NO_ERROR)
2019-10-12 13:36:01.902  - info: host.iobroker Restart adapter system.adapter.shelly.0 because enabled
2019-10-12 13:36:31.908  - info: host.iobroker instance system.adapter.shelly.0 started with pid 7005
2019-10-12 13:36:32.417  - debug: shelly.0 (7005) Redis Objects: Use Redis connection: 127.0.0.1:9001
2019-10-12 13:36:32.436  - debug: shelly.0 (7005) Objects connected to redis: 127.0.0.1:9001
2019-10-12 13:36:32.439  - debug: shelly.0 (7005) objectDB connected
2019-10-12 13:36:32.440  - debug: shelly.0 (7005) Redis States: Use Redis connection: 127.0.0.1:6379
2019-10-12 13:36:32.443  - debug: shelly.0 (7005) statesDB connected
2019-10-12 13:36:32.449  - debug: shelly.0 (7005) States connected to redis: 127.0.0.1:6379
2019-10-12 13:36:33.112  - info: shelly.0 (7005) starting. Version 3.1.1 in /opt/iobroker/node_modules/iobroker.shelly, node: v10.16.3
2019-10-12 13:36:33.138  - info: shelly.0 (7005) Stating Shelly adapter in CoAP modus.
2019-10-12 13:36:33.154  - info: host.iobroker instance system.adapter.shelly.0 terminated with code 0 (NO_ERROR)
2019-10-12 13:36:33.154  - info: host.iobroker Restart adapter system.adapter.shelly.0 because enabled
2019-10-12 13:37:03.160  - info: host.iobroker instance system.adapter.shelly.0 started with pid 7021
2019-10-12 13:37:03.661  - debug: shelly.0 (7021) Redis Objects: Use Redis connection: 127.0.0.1:9001
2019-10-12 13:37:03.679  - debug: shelly.0 (7021) Objects connected to redis: 127.0.0.1:9001
2019-10-12 13:37:03.682  - debug: shelly.0 (7021) objectDB connected
2019-10-12 13:37:03.683  - debug: shelly.0 (7021) Redis States: Use Redis connection: 127.0.0.1:6379
2019-10-12 13:37:03.686  - debug: shelly.0 (7021) statesDB connected
2019-10-12 13:37:03.693  - debug: shelly.0 (7021) States connected to redis: 127.0.0.1:6379
2019-10-12 13:37:04.418  - info: shelly.0 (7021) starting. Version 3.1.1 in /opt/iobroker/node_modules/iobroker.shelly, node: v10.16.3
2019-10-12 13:37:04.447  - info: shelly.0 (7021) Stating Shelly adapter in CoAP modus.
2019-10-12 13:37:04.464  - info: host.iobroker instance system.adapter.shelly.0 terminated with code 0 (NO_ERROR)
2019-10-12 13:37:04.464  - info: host.iobroker Restart adapter system.adapter.shelly.0 because enabled

@Apollon77
Copy link
Member

You change nodejs version? How? Followed update instructions like https://forum.iobroker.net/topic/22867/how-to-node-js-f%C3%BCr-iobroker-richtig-updaten ??

@smarti2019
Copy link
Author

yes, exactly after the instructions. All adapters work afterwards, only the shelly adapter makes loops
even deleting the adapter and reinstalling does not change anything

@schmupu
Copy link
Contributor

schmupu commented Oct 12, 2019

There is no error evident in the logfile. I think, the error has something to do with your nodejs update. I would recover the ioBroker system from your last backup. I have no idea how I can help you, because the shelly adapter does not show any error in the logfile.

@schmupu
Copy link
Contributor

schmupu commented Oct 12, 2019

I have one idea. We had a similar error, because in instances of the Shelly adapter, the restarting of the adapter was scheduled (Neu starten).

@smarti2019
Copy link
Author

I can not see a planned restart of the adapter. nothing is configured to that effect

@schmupu
Copy link
Contributor

schmupu commented Oct 12, 2019

Try following. Stop the shelly adapter in ioBroker under instances. Go on your ioBroker system into the shelly directory and start the shelly adapter in debug modus. What do you see?

cd /opt/iobroker/node_modules/iobroker.shelly
node shelly.js --debug

@smarti2019
Copy link
Author

smarti2019 commented Oct 12, 2019 •
edited by schmupu 

2019-10-12 17:27:05.215  - debug: shelly.0 (2459) Redis Objects: Use Redis connection: 127.0.0.1:9001
2019-10-12 17:27:05.237  - debug: shelly.0 (2459) objectDB connected
2019-10-12 17:27:05.238  - debug: shelly.0 (2459) Redis States: Use Redis connection: 127.0.0.1:6379
2019-10-12 17:27:05.240  - debug: shelly.0 (2459) Objects connected to redis: 127.0.0.1:9001
2019-10-12 17:27:05.242  - debug: shelly.0 (2459) statesDB connected
2019-10-12 17:27:05.249  - debug: shelly.0 (2459) States connected to redis: 127.0.0.1:6379
2019-10-12 17:27:05.931  - error: shelly.0 (2459) adapter disabled
2019-10-12 17:27:05.932  - info: shelly.0 (2459) starting. Version 3.1.1 in /opt/iobroker/node_modules/iobroker.shelly, node: v10.16.3
2019-10-12 17:27:05.951  - info: shelly.0 (2459) Stating Shelly adapter in CoAP modus.
Exception: TypeError: xmlserializer.Builder is not a constructor/TypeError: xmlserializer.Builder is not a constructor
2019-10-12 17:27:05.960  - error: shelly.0 (2459) Exception: TypeError: xmlserializer.Builder is not a constructor
2019-10-12 17:27:05.961  - info: shelly.0 (2459) Closing Adapter

@Apollon77
Copy link
Member

jetzt kommen wir der Sache näher. Da hat es eine Library bei Dir zerbröselt.
Schau mal bitte hier ... hilft das? https://forum.iobroker.net/topic/17306/shelly-adapter-errors-im-log

@smarti2019
Copy link
Author

@Apollon77 , exakt das hat das Problem gelöst, du bist mein Held , super danke, läuft alles wieder perfekt!

@schmupu schmupu mentioned this issue Jun 24, 2020
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@schmupu schmupu

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@Apollon77 @schmupu @smarti2019