[Bug]: [MQTT] Unable to get mqttprefix of client with id "shellyplus2pm-e

[dike1982]

I'm sure that

• [X] This issue is still present in the current beta version of this adapter
• [X] There is no other (open) issue with the same topic (use the search!)
• [X] This issue is not described in the adapter documentation / FAQ (read the docs!)

Shelly device

shelly1pmmini, shellyplus2pm,

Shelly firmware version

1.1.0

Protocol

MQTT

The problem

Das Log de Iobroker wird mit den Meldungen zugemüllt was dann den ganzen iobroker lahmlegt. Nach einem: echo -e "Package: nodejs\nPin: origin deb.nodesource.com\nPin-Priority: 1001" | sudo tee /etc/apt/preferences.d/nodejs.pref

  | sudo apt update   | iob stop   | sudo apt full-upgrade   | sudo reboot

Läuft es wieder fehlerfrei. Allerdings nur für einen tag und dann fängt es an die Fehler zu werfen und immer mehr.

iobroker.current.log (in debug mode!)

2024-01-14 19:28:36.535 - error: shelly.0 (957) [MQTT] Unable to get mqttprefix of client with id "shelly1pmmini-543204aa1ae0" 2024-01-14 19:28:36.536 - error: shelly.0 (957) [MQTT] Unable to get mqttprefix of client with id "shelly1pmmini-543204aa1ae0" 2024-01-14 19:28:36.546 - error: shelly.0 (957) [MQTT] Unable to get mqttprefix of client with id "shelly1pmmini-543204ab95d8" 2024-01-14 19:28:36.547 - error: shelly.0 (957) [MQTT] Unable to get mqttprefix of client with id "shelly1pmmini-543204ad6264" 2024-01-14 19:28:36.548 - error: shelly.0 (957) [MQTT] Unable to get mqttprefix of client with id "shelly1pmmini-543204aa8d5c" 2024-01-14 19:28:39.490 - error: shelly.0 (957) [MQTT] Unable to get mqttprefix of client with id "shelly1pmmini-543204addca8" 2024-01-14 19:28:39.497 - error: shelly.0 (957) [MQTT] Unable to get mqttprefix of client with id "shellyplus2pm-e465b8604d6c" 2024-01-14 19:28:39.499 - error: shelly.0 (957) [MQTT] Unable to get mqttprefix of client with id "shelly1pmmini-543204aaa1f4" 2024-01-14 19:28:40.061 - info: shelly.0 (957) [MQTT] Client Close: (shelly1pmmini / shelly1pmmini-543204aa80e8 / shelly1pmmini#543204aa80e8#1) (false) 2024-01-14 19:28:41.427 - error: shelly.0 (957) [MQTT] Unable to get mqttprefix of client with id "shellyplus2pm-e465b8604d6c" 2024-01-14 19:28:41.429 - error: shelly.0 (957) [MQTT] Unable to get mqttprefix of client with id "shelly1pmmini-543204aaa1f4" 2024-01-14 19:28:43.000 - info: shelly.0 (957) [MQTT] Device with client id "shelly1pmmini-543204acaf70" connected! 2024-01-14 19:28:44.911 - error: shelly.0 (957) [MQTT] Unable to get mqttprefix of client with id "shellyplus2pm-e465b893c4d0" 2024-01-14 19:28:44.914 - error: shelly.0 (957) [MQTT] Unable to get mqttprefix of client with id "shellyplus2pm-a0a3b3684114" 2024-01-14 19:28:44.914 - error: shelly.0 (957) [MQTT] Unable to get mqttprefix of client with id "shellyplus2pm-e465b893c4d0" 2024-01-14 19:28:44.915 - error: shelly.0 (957) [MQTT] Unable to get mqttprefix of client with id "shelly1pmmini-543204aa8d5c" 2024-01-14 19:28:44.916 - error: shelly.0 (957) [MQTT] Unable to get mqttprefix of client with id "shelly1pmmini-543204abcca8" 2024-01-14 19:28:44.917 - error: shelly.0 (957) [MQTT] Unable to get mqttprefix of client with id "shelly1pmmini-543204addca8" 2024-01-14 19:28:44.918 - error: shelly.0 (957) [MQTT] Unable to get mqttprefix of client with id "shelly1pmmini-543204acee28" 2024-01-14 19:28:44.920 - error: shelly.0 (957) [MQTT] Error in function setMqttPrefixHttp (Gen 1) for (undefined / undefined / undefined): TypeError: Cannot read properties of undefined (reading 'replace') 2024-01-14 19:28:44.921 - error: shelly.0 (957) [MQTT] Unable to get mqttprefix of client with id "shelly1pmmini-543204acaf70" 2024-01-14 19:28:47.140 - error: shelly.0 (957) [MQTT] Unable to get mqttprefix of client with id "shelly1pmmini-543204abcca8" 2024-01-14 19:28:48.879 - error: shelly.0 (957) [MQTT] Unable to get mqttprefix of client with id "shelly1pmmini-543204ab95d8" 2024-01-14 19:28:48.881 - error: shelly.0 (957) [MQTT] Unable to get mqttprefix of client with id "shelly1pmmini-543204ad6264" 2024-01-14 19:28:48.882 - error: shelly.0 (957) [MQTT] Unable to get mqttprefix of client with id "shellyplusplugs-e465b860af58" 2024-01-14 19:28:48.883 - error: shelly.0 (957) [MQTT] Unable to get mqttprefix of client with id "shelly1pmmini-543204acee28" 2024-01-14 19:28:48.884 - error: shelly.0 (957) [MQTT] Unable to get mqttprefix of client with id "shelly1pmmini-543204acfe10" 2024-01-14 19:28:49.510 - info: shelly.0 (957) [MQTT] Device with client id "shelly1pmmini-543204abaf8c" connected! 2024-01-14 19:28:50.457 - error: shelly.0 (957) [MQTT] Unable to get mqttprefix of client with id "shelly1pmmini-543204adcc50" 2024-01-14 19:28:50.461 - error: shelly.0 (957) [MQTT] Unable to get mqttprefix of client with id "shelly1pmmini-543204aa80e8" 2024-01-14 19:28:50.461 - error: shelly.0 (957) [MQTT] Unable to get mqttprefix of client with id "shellyplusplugs-e465b860af58" 2024-01-14 19:28:52.993 - info: shelly.0 (957) [MQTT] Client Close: (shelly1pmmini / shelly1pmmini-543204acaf70 / shelly1pmmini#543204acaf70#1) (false) 2024-01-14 19:28:53.670 - error: shelly.0 (957) [MQTT] Unable to get mqttprefix of client with id "shellyplus2pm-a0a3b3684114" 2024-01-14 19:28:53.671 - error: shelly.0 (957) [MQTT] Unable to get mqttprefix of client with id "shellyplus2pm-a0a3b3684110" 2024-01-14 19:28:54.159 - info: shelly.0 (957) [MQTT] Device with client id "shellyplus2pm-e465b893c4d0" connected! 2024-01-14 19:28:55.518 - error: shelly.0 (957) [MQTT] Unable to get mqttprefix of client with id "shelly1pmmini-543204abaf8c" 2024-01-14 19:28:55.519 - error: shelly.0 (957) [MQTT] Unable to get mqttprefix of client with id "shelly1pmmini-543204acfe10" 2024-01-14 19:28:59.181 - info: shelly.0 (957) [MQTT] Device with client id "shellyplusplugs-e465b860af58" connected! 2024-01-14 19:28:59.507 - info: shelly.0 (957) [MQTT] Client Close: (shelly1pmmini / shelly1pmmini-543204abaf8c / shelly1pmmini#543204abaf8c#1) (false) 2024-01-14 19:28:59.827 - info: shelly.0 (957) [MQTT] Device with client id "shellyplus2pm-a0a3b3684114" connected! 2024-01-14 19:29:01.136 - info: shelly.0 (957) [MQTT] Device with client id "shelly1pmmini-543204abcca8" connected! 2024-01-14 19:29:01.166 - info: shelly.0 (957) [MQTT] Device with client id "shellyplus2pm-a0a3b3684110" connected! 2024-01-14 19:29:04.132 - info: shelly.0 (957) [MQTT] Device with client id "shelly1pmmini-543204ab95d8" connected! 2024-01-14 19:29:04.151 - info: shelly.0 (957) [MQTT] Client Close: (shellyplus2pm / shellyplus2pm-e465b893c4d0 / shellyplus2pm#e465b893c4d0#1) (false) 2024-01-14 19:29:06.153 - info: shelly.0 (957) [MQTT] Device with client id "shelly1pmmini-543204aa1ae0" connected! 2024-01-14 19:29:06.634 - info: shelly.0 (957) [MQTT] Device with client id "shelly1pmmini-543204aaa1f4" connected! 2024-01-14 19:29:07.035 - error: shelly.0 (957) [MQTT] Unable to get mqttprefix of client with id "shelly1pmmini-543204adcc50" 2024-01-14 19:29:07.964 - info: shelly.0 (957) [MQTT] Device with client id "shelly1pmmini-543204ad6264" connected! 2024-01-14 19:29:08.858 - info: shelly.0 (957) [MQTT] Device with client id "shelly1pmmini-543204aa8d5c" connected! 2024-01-14 19:29:09.179 - info: shelly.0 (957) [MQTT] Device with client id "shellyplus2pm-e465b8604d6c" connected! 2024-01-14 19:29:09.180 - info: shelly.0 (957) [MQTT] Client Close: (shellyplusplugs / shellyplusplugs-e465b860af58 / shellyplusplugs#e465b860af58#1) (false) 2024-01-14 19:29:09.400 - info: shelly.0 (957) [MQTT] Device with client id "shelly1pmmini-543204addca8" connected! 2024-01-14 19:29:09.817 - info: shelly.0 (957) [MQTT] Client Close: (shellyplus2pm / shellyplus2pm-a0a3b3684114 / shellyplus2pm#a0a3b3684114#1) (false) 2024-01-14 19:29:11.193 - info: shelly.0 (957) [MQTT] Device with client id "shelly1pmmini-543204acee28" connected! 2024-01-14 19:29:11.195 - info: shelly.0 (957) [MQTT] Client Close: (shellyplus2pm / shellyplus2pm-a0a3b3684110 / shellyplus2pm#a0a3b3684110#1) (false) 2024-01-14 19:29:11.195 - info: shelly.0 (957) [MQTT] Client Close: (shelly1pmmini / shelly1pmmini-543204abcca8 / shelly1pmmini#543204abcca8#1) (false) 2024-01-14 19:29:13.339 - error: shelly.0 (957) [MQTT] Unable to get mqttprefix of client with id "shelly1pmmini-543204aa80e8" 2024-01-14 19:29:14.124 - info: shelly.0 (957) [MQTT] Client Close: (shelly1pmmini / shelly1pmmini-543204ab95d8 / shelly1pmmini#543204ab95d8#1) (false) 2024-01-14 19:29:16.143 - info: shelly.0 (957) [MQTT] Client Close: (shelly1pmmini / shelly1pmmini-543204aa1ae0 / shelly1pmmini#543204aa1ae0#1) (false) 2024-01-14 19:29:16.242 - info: shelly.0 (957) [MQTT] Device with client id "shelly1pmmini-543204acfe10" connected! 2024-01-14 19:29:16.632 - info: shelly.0 (957) [MQTT] Client Close: (shelly1pmmini / shelly1pmmini-543204aaa1f4 / shelly1pmmini#543204aaa1f4#1) (false) 2024-01-14 19:29:17.954 - info: shelly.0 (957) [MQTT] Client Close: (shelly1pmmini / shelly1pmmini-543204ad6264 / shelly1pmmini#543204ad6264#1) (false) 2024-01-14 19:29:19.038 - info: shelly.0 (957) [MQTT] Client Close: (shelly1pmmini / shelly1pmmini-543204aa8d5c / shelly1pmmini#543204aa8d5c#1) (false) 2024-01-14 19:29:19.172 - info: shelly.0 (957) [MQTT] Client Close: (shellyplus2pm / shellyplus2pm-e465b8604d6c / shellyplus2pm#e465b8604d6c#1) (false) 2024-01-14 19:29:19.392 - info: shelly.0 (957) [MQTT] Client Close: (shelly1pmmini / shelly1pmmini-543204addca8 / shelly1pmmini#543204addca8#1) (false) 2024-01-14 19:29:20.814 - error: shelly.0 (957) [MQTT] Unable to get mqttprefix of client with id "shelly1pmmini-543204acaf70" 2024-01-14 19:29:20.827 - info: shelly.0 (957) [MQTT] Client Close: (shelly1pmmini / shelly1pmmini-543204acee28 / shelly1pmmini#543204acee28#1) (false) 2024-01-14 19:29:24.037 - error: shelly.0 (957) [MQTT] Unable to get mqttprefix of client with id "shelly1pmmini-543204abaf8c" 2024-01-14 19:29:26.297 - error: shelly.0 (957) [MQTT] Unable to get mqttprefix of client with id "shellyplus2pm-e465b893c4d0" 2024-01-14 19:29:26.298 - info: shelly.0 (957) [MQTT] Client Close: (shelly1pmmini / shelly1pmmini-543204acfe10 / shel

Version of nodejs

18.19.0

Version of ioBroker js-controller

5.0.17

Version of adapter

6.6.1

[github-actions[bot]]

Thanks for reporting a new issue @dike1982!

1. Please make sure your topic is not covered in the documentation
2. Ensure that you use the latest beta version (not the current stable version): 6.7.0
3. Please attach all necessary log files (in debug mode!), screenshots and other information to reproduce this issue

4. Search for the issue topic in other/closed issues to avoid duplicates!

   Otherwise this issue will be closed.

[dike1982]

Hier noch weitere Logs: Der Adapter wirft ständig Ereignis im Log ununterbrochen, das lähmt die iobroker:

2024-01-14 19:49:44.321  - info: shelly.0 (1134) [MQTT] Device with client id "shelly1pmmini-543204acee28" connected!
2024-01-14 19:49:44.692  - info: shelly.0 (1134) [MQTT] Device with client id "shelly1pmmini-543204aa8d5c" connected!
2024-01-14 19:49:45.626  - info: shelly.0 (1134) [MQTT] Device with client id "shelly1pmmini-543204ab95d8" connected!
2024-01-14 19:49:45.626  - info: shelly.0 (1134) [MQTT] Device with client id "shelly1pmmini-543204ab95d8" connected!
2024-01-14 19:49:46.603  - info: shelly.0 (1134) [MQTT] Device with client id "shelly1pmmini-543204abcca8" connected!
2024-01-14 19:49:46.603  - info: shelly.0 (1134) [MQTT] Device with client id "shelly1pmmini-543204abcca8" connected!
2024-01-14 19:49:47.591  - info: shelly.0 (1134) [MQTT] Device with client id "shellyplus2pm-a0a3b3684110" connected!
2024-01-14 19:49:47.742  - info: shelly.0 (1134) [MQTT] Device with client id "shelly1pmmini-543204abaf8c" connected!
2024-01-14 19:49:47.591  - info: shelly.0 (1134) [MQTT] Device with client id "shellyplus2pm-a0a3b3684110" connected!
2024-01-14 19:49:47.742  - info: shelly.0 (1134) [MQTT] Device with client id "shelly1pmmini-543204abaf8c" connected!
2024-01-14 19:49:49.963  - info: shelly.0 (1134) [MQTT] Device with client id "shellyplus2pm-e465b8604d6c" connected!
2024-01-14 19:49:49.963  - info: shelly.0 (1134) [MQTT] Device with client id "shellyplus2pm-e465b8604d6c" connected!
2024-01-14 19:49:51.135  - info: shelly.0 (1134) [MQTT] Device with client id "shellyplus2pm-a0a3b3684114" connected!
2024-01-14 19:49:51.426  - info: shelly.0 (1134) [MQTT] Device with client id "shelly1pmmini-543204aaa1f4" connected!
2024-01-14 19:49:51.135  - info: shelly.0 (1134) [MQTT] Device with client id "shellyplus2pm-a0a3b3684114" connected!
2024-01-14 19:49:51.426  - info: shelly.0 (1134) [MQTT] Device with client id "shelly1pmmini-543204aaa1f4" connected!
2024-01-14 19:49:52.255  - info: shelly.0 (1134) [MQTT] Device with client id "shelly1pmmini-543204ad6264" connected!
2024-01-14 19:49:52.255  - info: shelly.0 (1134) [MQTT] Device with client id "shelly1pmmini-543204ad6264" connected!
2024-01-14 19:49:54.314  - info: shelly.0 (1134) [MQTT] Client Close:  (shelly1pmmini / shelly1pmmini-543204acee28 / shelly1pmmini#543204acee28#1) (false)
2024-01-14 19:49:54.683  - info: shelly.0 (1134) [MQTT] Client Close:  (shelly1pmmini / shelly1pmmini-543204aa8d5c / shelly1pmmini#543204aa8d5c#1) (false)
2024-01-14 19:49:54.314  - info: shelly.0 (1134) [MQTT] Client Close:  (shelly1pmmini / shelly1pmmini-543204acee28 / shelly1pmmini#543204acee28#1) (false)
2024-01-14 19:49:54.683  - info: shelly.0 (1134) [MQTT] Client Close:  (shelly1pmmini / shelly1pmmini-543204aa8d5c / shelly1pmmini#543204aa8d5c#1) (false)
2024-01-14 19:49:55.500  - info: shelly.0 (1134) [MQTT] Device with client id "shelly1pmmini-543204aa1ae0" connected!
2024-01-14 19:49:55.620  - info: shelly.0 (1134) [MQTT] Client Close:  (shelly1pmmini / shelly1pmmini-543204ab95d8 / shelly1pmmini#543204ab95d8#1) (false)
2024-01-14 19:49:55.500  - info: shelly.0 (1134) [MQTT] Device with client id "shelly1pmmini-543204aa1ae0" connected!
2024-01-14 19:49:55.620  - info: shelly.0 (1134) [MQTT] Client Close:  (shelly1pmmini / shelly1pmmini-543204ab95d8 / shelly1pmmini#543204ab95d8#1) (false)
2024-01-14 19:49:56.594  - info: shelly.0 (1134) [MQTT] Client Close:  (shelly1pmmini / shelly1pmmini-543204abcca8 / shelly1pmmini#543204abcca8#1) (false)
2024-01-14 19:49:56.594  - info: shelly.0 (1134) [MQTT] Client Close:  (shelly1pmmini / shelly1pmmini-543204abcca8 / shelly1pmmini#543204abcca8#1) (false)
2024-01-14 19:49:57.585  - info: shelly.0 (1134) [MQTT] Client Close:  (shellyplus2pm / shellyplus2pm-a0a3b3684110 / shellyplus2pm#a0a3b3684110#1) (false)
2024-01-14 19:49:57.733  - info: shelly.0 (1134) [MQTT] Client Close:  (shelly1pmmini / shelly1pmmini-543204abaf8c / shelly1pmmini#543204abaf8c#1) (false)
2024-01-14 19:49:57.585  - info: shelly.0 (1134) [MQTT] Client Close:  (shellyplus2pm / shellyplus2pm-a0a3b3684110 / shellyplus2pm#a0a3b3684110#1) (false)
2024-01-14 19:49:57.733  - info: shelly.0 (1134) [MQTT] Client Close:  (shelly1pmmini / shelly1pmmini-543204abaf8c / shelly1pmmini#543204abaf8c#1) (false)
2024-01-14 19:49:58.604  - info: host.raspberrypi4 "system.adapter.shelly.0" disabled
2024-01-14 19:49:58.612  - info: shelly.0 (1134) [MQTT] Device with client id "shelly1pmmini-543204addca8" connected!
2024-01-14 19:49:58.606  - info: host.raspberrypi4 stopInstance system.adapter.shelly.0 (force=false, process=true)
2024-01-14 19:49:58.604  - info: host.raspberrypi4 "system.adapter.shelly.0" disabled
2024-01-14 19:49:58.612  - info: shelly.0 (1134) [MQTT] Device with client id "shelly1pmmini-543204addca8" connected!
2024-01-14 19:49:58.606  - info: host.raspberrypi4 stopInstance system.adapter.shelly.0 (force=false, process=true)
2024-01-14 19:49:59.950  - info: shelly.0 (1134) [MQTT] Client Close:  (shellyplus2pm / shellyplus2pm-e465b8604d6c / shellyplus2pm#e465b8604d6c#1) (false)
2024-01-14 19:49:59.950  - info: shelly.0 (1134) [MQTT] Client Close:  (shellyplus2pm / shellyplus2pm-e465b8604d6c / shellyplus2pm#e465b8604d6c#1) (false)
2024-01-14 19:50:01.129  - info: shelly.0 (1134) [MQTT] Client Close:  (shellyplus2pm / shellyplus2pm-a0a3b3684114 / shellyplus2pm#a0a3b3684114#1) (false)
2024-01-14 19:50:01.417  - info: shelly.0 (1134) [MQTT] Client Close:  (shelly1pmmini / shelly1pmmini-543204aaa1f4 / shelly1pmmini#543204aaa1f4#1) (false)
2024-01-14 19:50:01.129  - info: shelly.0 (1134) [MQTT] Client Close:  (shellyplus2pm / shellyplus2pm-a0a3b3684114 / shellyplus2pm#a0a3b3684114#1) (false)
2024-01-14 19:50:01.417  - info: shelly.0 (1134) [MQTT] Client Close:  (shelly1pmmini / shelly1pmmini-543204aaa1f4 / shelly1pmmini#543204aaa1f4#1) (false)
2024-01-14 19:50:02.621  - info: shelly.0 (1134) [MQTT] Client Close:  (shelly1pmmini / shelly1pmmini-543204ad6264 / shelly1pmmini#543204ad6264#1) (false)
2024-01-14 19:50:02.621  - info: shelly.0 (1134) [MQTT] Client Close:  (shelly1pmmini / shelly1pmmini-543204ad6264 / shelly1pmmini#543204ad6264#1) (false)
2024-01-14 19:50:05.491  - info: shelly.0 (1134) [MQTT] Client Close:  (shelly1pmmini / shelly1pmmini-543204aa1ae0 / shelly1pmmini#543204aa1ae0#1) (false)
2024-01-14 19:50:05.609  - info: shelly.0 (1134) Got terminate signal TERMINATE_YOURSELF
2024-01-14 19:50:05.626  - info: shelly.0 (1134) terminating
2024-01-14 19:50:05.631  - info: shelly.0 (1134) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
2024-01-14 19:50:06.134  - info: shelly.0 (1134) terminating
2024-01-14 19:50:05.491  - info: shelly.0 (1134) [MQTT] Client Close:  (shelly1pmmini / shelly1pmmini-543204aa1ae0 / shelly1pmmini#543204aa1ae0#1) (false)
2024-01-14 19:50:05.609  - info: shelly.0 (1134) Got terminate signal TERMINATE_YOURSELF
2024-01-14 19:50:05.626  - info: shelly.0 (1134) terminating
2024-01-14 19:50:05.631  - info: shelly.0 (1134) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
2024-01-14 19:50:06.134  - info: shelly.0 (1134) terminating
2024-01-14 19:50:07.135  - info: shelly.0 (1134) terminating with timeout
2024-01-14 19:50:07.135  - info: shelly.0 (1134) terminating with timeout
2024-01-14 19:50:08.395  - warn: shelly.0 (1134) redis get shelly.0.shelly1pmmini#543204abcca8#1.online, error - Connection is closed.
2024-01-14 19:50:08.397  - warn: shelly.0 (1134) get state error: DB closed
2024-01-14 19:50:08.397  - warn: shelly.0 (1134) redis get shelly.0.shellyplus2pm#e465b8604d6c#1.online, error - DB closed
2024-01-14 19:50:08.398  - warn: shelly.0 (1134) redis get shelly.0.shellyplus2pm#a0a3b3684110#1.online, error - DB closed
2024-01-14 19:50:08.398  - warn: shelly.0 (1134) redis get shelly.0.shelly1pmmini#543204abaf8c#1.online, error - DB closed
2024-01-14 19:50:08.399  - warn: shelly.0 (1134) redis get shelly.0.shelly1pmmini#543204acfe10#1.hostname, error - DB closed
2024-01-14 19:50:08.403  - error: shelly.0 (1134) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
2024-01-14 19:50:08.404  - error: shelly.0 (1134) unhandled promise rejection: DB closed
2024-01-14 19:50:08.415  - error: shelly.0 (1134) Error: DB closed
    at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25)
    at Socket.<anonymous> (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20)
    at Object.onceWrapper (node:events:632:26)
    at Socket.emit (node:events:517:28)
    at Socket.emit (node:domain:489:12)
    at TCP.<anonymous> (node:net:350:12)
2024-01-14 19:50:08.415  - error: shelly.0 (1134) DB closed
2024-01-14 19:50:08.455  - error: shelly.0 (1134) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
2024-01-14 19:50:08.455  - error: shelly.0 (1134) unhandled promise rejection: DB closed
2024-01-14 19:50:08.456  - error: shelly.0 (1134) Error: DB closed
    at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25)
    at Socket.<anonymous> (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20)
    at Object.onceWrapper (node:events:632:26)
    at Socket.emit (node:events:517:28)
    at Socket.emit (node:domain:489:12)
    at TCP.<anonymous> (node:net:350:12)
2024-01-14 19:50:08.458  - error: shelly.0 (1134) DB closed
2024-01-14 19:50:08.497  - warn: shelly.0 (1134) redis get shelly.0.shellyplus2pm#e465b8604d6c#1.online, error - Connection is closed.
2024-01-14 19:50:08.395  - warn: shelly.0 (1134) redis get shelly.0.shelly1pmmini#543204abcca8#1.online, error - Connection is closed.
2024-01-14 19:50:08.397  - warn: shelly.0 (1134) get state error: DB closed
2024-01-14 19:50:08.397  - warn: shelly.0 (1134) redis get shelly.0.shellyplus2pm#e465b8604d6c#1.online, error - DB closed
2024-01-14 19:50:08.398  - warn: shelly.0 (1134) redis get shelly.0.shellyplus2pm#a0a3b3684110#1.online, error - DB closed
2024-01-14 19:50:08.398  - warn: shelly.0 (1134) redis get shelly.0.shelly1pmmini#543204abaf8c#1.online, error - DB closed
2024-01-14 19:50:08.399  - warn: shelly.0 (1134) redis get shelly.0.shelly1pmmini#543204acfe10#1.hostname, error - DB closed
2024-01-14 19:50:08.403  - error: shelly.0 (1134) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
2024-01-14 19:50:08.404  - error: shelly.0 (1134) unhandled promise rejection: DB closed
2024-01-14 19:50:08.415  - error: shelly.0 (1134) Error: DB closed
    at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25)
    at Socket.<anonymous> (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20)
    at Object.onceWrapper (node:events:632:26)
    at Socket.emit (node:events:517:28)
    at Socket.emit (node:domain:489:12)
    at TCP.<anonymous> (node:net:350:12)
2024-01-14 19:50:08.415  - error: shelly.0 (1134) DB closed
2024-01-14 19:50:08.455  - error: shelly.0 (1134) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
2024-01-14 19:50:08.455  - error: shelly.0 (1134) unhandled promise rejection: DB closed
2024-01-14 19:50:08.456  - error: shelly.0 (1134) Error: DB closed
    at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25)
    at Socket.<anonymous> (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20)
    at Object.onceWrapper (node:events:632:26)
    at Socket.emit (node:events:517:28)
    at Socket.emit (node:domain:489:12)
    at TCP.<anonymous> (node:net:350:12)
2024-01-14 19:50:08.458  - error: shelly.0 (1134) DB closed
2024-01-14 19:50:08.497  - warn: shelly.0 (1134) redis get shelly.0.shellyplus2pm#e465b8604d6c#1.online, error - Connection is closed.
2024-01-14 19:50:10.253  - info: host.raspberrypi4 stopInstance system.adapter.shelly.0 send kill signal
2024-01-14 19:50:10.311  - warn: shelly.0 (1134) get state error: Connection is closed.
2024-01-14 19:50:10.316  - warn: shelly.0 (1134) redis get shelly.0.shellyplus2pm#a0a3b3684114#1.online, error - Connection is closed.
2024-01-14 19:50:10.317  - warn: shelly.0 (1134) redis get shelly.0.shelly1pmmini#543204aaa1f4#1.online, error - Connection is closed.
2024-01-14 19:50:10.328  - error: shelly.0 (1134) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
2024-01-14 19:50:10.328  - error: shelly.0 (1134) unhandled promise rejection: DB closed
2024-01-14 19:50:10.732  - error: shelly.0 (1134) Error: DB closed
    at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24)
    at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:122:25)
    at StateRedisClient.setState (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:726:40)
    at Shelly._setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:7710:33)
    at runNextTicks (node:internal/process/task_queues:60:5)
    at processImmediate (node:internal/timers:447:9)
2024-01-14 19:50:10.733  - error: shelly.0 (1134) DB closed
2024-01-14 19:50:10.253  - info: host.raspberrypi4 stopInstance system.adapter.shelly.0 send kill signal
2024-01-14 19:50:10.311  - warn: shelly.0 (1134) get state error: Connection is closed.
2024-01-14 19:50:10.316  - warn: shelly.0 (1134) redis get shelly.0.shellyplus2pm#a0a3b3684114#1.online, error - Connection is closed.
2024-01-14 19:50:10.317  - warn: shelly.0 (1134) redis get shelly.0.shelly1pmmini#543204aaa1f4#1.online, error - Connection is closed.
2024-01-14 19:50:10.328  - error: shelly.0 (1134) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
2024-01-14 19:50:10.328  - error: shelly.0 (1134) unhandled promise rejection: DB closed
2024-01-14 19:50:10.732  - error: shelly.0 (1134) Error: DB closed
    at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24)
    at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:122:25)
    at StateRedisClient.setState (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:726:40)
    at Shelly._setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:7710:33)
    at runNextTicks (node:internal/process/task_queues:60:5)
    at processImmediate (node:internal/timers:447:9)
2024-01-14 19:50:10.733  - error: shelly.0 (1134) DB closed
2024-01-14 19:50:12.045  - info: host.raspberrypi4 stopInstance system.adapter.shelly.0 killing pid 1134
2024-01-14 19:50:12.119  - warn: shelly.0 (1134) redis get shelly.0.shelly1pmmini#543204aa8d5c#1.hostname, error - Connection is closed.
2024-01-14 19:50:12.128  - warn: shelly.0 (1134) redis get shelly.0.shelly1pmmini#543204ad6264#1.online, error - Connection is closed.
2024-01-14 19:50:12.045  - info: host.raspberrypi4 stopInstance system.adapter.shelly.0 killing pid 1134
2024-01-14 19:50:12.119  - warn: shelly.0 (1134) redis get shelly.0.shelly1pmmini#543204aa8d5c#1.hostname, error - Connection is closed.
2024-01-14 19:50:12.128  - warn: shelly.0 (1134) redis get shelly.0.shelly1pmmini#543204ad6264#1.online, error - Connection is closed.
2024-01-14 19:50:13.322  - warn: shelly.0 (1134) get state error: Connection is closed.
2024-01-14 19:50:13.323  - warn: shelly.0 (1134) get state error: Connection is closed.
2024-01-14 19:50:13.324  - warn: shelly.0 (1134) redis get shelly.0.shellyplus2pm#a0a3b3684110#1.online, error - Connection is closed.
2024-01-14 19:50:13.325  - warn: shelly.0 (1134) redis get shelly.0.shelly1pmmini#543204aa1ae0#1.online, error - Connection is closed.
2024-01-14 19:50:13.328  - error: shelly.0 (1134) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
2024-01-14 19:50:13.328  - error: shelly.0 (1134) unhandled promise rejection: DB closed
2024-01-14 19:50:13.331  - error: shelly.0 (1134) Error: DB closed
    at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24)
    at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:122:25)
    at StateRedisClient.setState (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:726:40)
    at Shelly._setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:7710:33)
    at runNextTicks (node:internal/process/task_queues:60:5)
    at processImmediate (node:internal/timers:447:9)
2024-01-14 19:50:13.331  - error: shelly.0 (1134) DB closed
2024-01-14 19:50:13.349  - error: shelly.0 (1134) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
2024-01-14 19:50:13.351  - error: shelly.0 (1134) unhandled promise rejection: DB closed
2024-01-14 19:50:13.353  - error: shelly.0 (1134) Error: DB closed
    at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24)
    at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:122:25)
    at StateRedisClient.setState (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:726:40)
    at Shelly._setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:7710:33)
    at runNextTicks (node:internal/process/task_queues:60:5)
    at processImmediate (node:internal/timers:447:9)
2024-01-14 19:50:13.354  - error: shelly.0 (1134) DB closed
2024-01-14 19:50:13.322  - warn: shelly.0 (1134) get state error: Connection is closed.
2024-01-14 19:50:13.323  - warn: shelly.0 (1134) get state error: Connection is closed.
2024-01-14 19:50:13.324  - warn: shelly.0 (1134) redis get shelly.0.shellyplus2pm#a0a3b3684110#1.online, error - Connection is closed.
2024-01-14 19:50:13.325  - warn: shelly.0 (1134) redis get shelly.0.shelly1pmmini#543204aa1ae0#1.online, error - Connection is closed.
2024-01-14 19:50:13.328  - error: shelly.0 (1134) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
2024-01-14 19:50:13.328  - error: shelly.0 (1134) unhandled promise rejection: DB closed
2024-01-14 19:50:13.331  - error: shelly.0 (1134) Error: DB closed
    at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24)
    at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:122:25)
    at StateRedisClient.setState (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:726:40)
    at Shelly._setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:7710:33)
    at runNextTicks (node:internal/process/task_queues:60:5)
    at processImmediate (node:internal/timers:447:9)
2024-01-14 19:50:13.331  - error: shelly.0 (1134) DB closed
2024-01-14 19:50:13.349  - error: shelly.0 (1134) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
2024-01-14 19:50:13.351  - error: shelly.0 (1134) unhandled promise rejection: DB closed
2024-01-14 19:50:13.353  - error: shelly.0 (1134) Error: DB closed
    at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24)
    at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:122:25)
    at StateRedisClient.setState (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:726:40)
    at Shelly._setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:7710:33)
    at runNextTicks (node:internal/process/task_queues:60:5)
    at processImmediate (node:internal/timers:447:9)
2024-01-14 19:50:13.354  - error: shelly.0 (1134) DB closed
2024-01-14 19:50:15.160  - error: shelly.0 (1134) Cannot find view "system" for search "state" : DB closed
2024-01-14 19:50:15.160  - error: shelly.0 (1134) Cannot find view "system" for search "state" : DB closed
2024-01-14 19:50:15.162  - warn: shelly.0 (1134) Cannot get view: DB closed
2024-01-14 19:50:15.162  - warn: shelly.0 (1134) Cannot get view: DB closed
2024-01-14 19:50:15.163  - warn: shelly.0 (1134) Cannot get view: DB closed
2024-01-14 19:50:15.163  - warn: shelly.0 (1134) Cannot get view: DB closed
2024-01-14 19:50:15.167  - warn: shelly.0 (1134) Cannot get view: DB closed
2024-01-14 19:50:15.168  - warn: shelly.0 (1134) Cannot get view: DB closed
2024-01-14 19:50:15.168  - warn: shelly.0 (1134) Cannot get view: DB closed
2024-01-14 19:50:15.168  - warn: shelly.0 (1134) Cannot get view: DB closed
2024-01-14 19:50:15.169  - warn: shelly.0 (1134) Cannot get view: DB closed
2024-01-14 19:50:15.170  - error: shelly.0 (1134) Cannot find view "system" for search "channel" : DB closed
2024-01-14 19:50:15.180  - warn: shelly.0 (1134) Could not perform strict object check of state shelly.0.info.connection: DB closed
2024-01-14 19:50:15.180  - warn: shelly.0 (1134) get state error: Connection is closed.
2024-01-14 19:50:15.181  - warn: shelly.0 (1134) Could not perform strict object check of state shelly.0.info.connection: DB closed
2024-01-14 19:50:15.182  - warn: shelly.0 (1134) get state error: Connection is closed.
2024-01-14 19:50:15.208  - error: shelly.0 (1134) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
2024-01-14 19:50:15.209  - error: shelly.0 (1134) unhandled promise rejection: DB closed
2024-01-14 19:50:15.212  - error: shelly.0 (1134) Error: DB closed
    at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24)
    at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:122:25)
    at StateRedisClient.setState (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:726:40)
    at Shelly._setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:7710:33)
    at runNextTicks (node:internal/process/task_queues:60:5)
    at processImmediate (node:internal/timers:447:9)
2024-01-14 19:50:15.212  - error: shelly.0 (1134) DB closed
2024-01-14 19:50:15.223  - error: shelly.0 (1134) Error: DB closed
2024-01-14 19:50:15.224  - warn: shelly.0 (1134) setTimeout called, but adapter is shutting down
2024-01-14 19:50:15.225  - error: shelly.0 (1134) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
2024-01-14 19:50:15.225  - error: shelly.0 (1134) unhandled promise rejection: DB closed
2024-01-14 19:50:15.226  - error: shelly.0 (1134) Error: DB closed
    at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25)
    at Socket.<anonymous> (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20)
    at Object.onceWrapper (node:events:632:26)
    at Socket.emit (node:events:517:28)
    at Socket.emit (node:domain:489:12)
    at TCP.<anonymous> (node:net:350:12)
2024-01-14 19:50:15.227  - error: shelly.0 (1134) DB closed
2024-01-14 19:50:15.234  - error: shelly.0 (1134) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
2024-01-14 19:50:15.234  - error: shelly.0 (1134) unhandled promise rejection: DB closed
2024-01-14 19:50:15.236  - error: shelly.0 (1134) Error: DB closed
    at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24)
    at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:122:25)
    at StateRedisClient.setState (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:726:40)
    at Shelly._setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:7710:33)
    at runNextTicks (node:internal/process/task_queues:60:5)
    at processImmediate (node:internal/timers:447:9)
2024-01-14 19:50:15.237  - error: shelly.0 (1134) DB closed
2024-01-14 19:50:15.247  - error: shelly.0 (1134) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
2024-01-14 19:50:15.247  - error: shelly.0 (1134) unhandled promise rejection: DB closed
2024-01-14 19:50:15.248  - error: shelly.0 (1134) Error: DB closed
    at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25)
    at Socket.<anonymous> (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20)
    at Object.onceWrapper (node:events:632:26)
    at Socket.emit (node:events:517:28)
    at Socket.emit (node:domain:489:12)
    at TCP.<anonymous> (node:net:350:12)
2024-01-14 19:50:15.249  - error: shelly.0 (1134) DB closed
2024-01-14 19:50:15.260  - error: shelly.0 (1134) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
2024-01-14 19:50:15.260  - error: shelly.0 (1134) unhandled promise rejection: DB closed
2024-01-14 19:50:15.261  - error: shelly.0 (1134) Error: DB closed
    at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25)
    at Socket.<anonymous> (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20)
    at Object.onceWrapper (node:events:632:26)
    at Socket.emit (node:events:517:28)
    at Socket.emit (node:domain:489:12)
    at TCP.<anonymous> (node:net:350:12)
2024-01-14 19:50:15.263  - error: shelly.0 (1134) DB closed
2024-01-14 19:50:15.271  - error: shelly.0 (1134) Cannot find view "system" for search "state" : Connection is closed.
2024-01-14 19:50:15.273  - error: shelly.0 (1134) Cannot find view "system" for search "state" : Connection is closed.
2024-01-14 19:50:15.275  - error: shelly.0 (1134) Cannot find view "system" for search "state" : Connection is closed.
2024-01-14 19:50:15.277  - error: shelly.0 (1134) Cannot find view "system" for search "state" : Connection is closed.
2024-01-14 19:50:15.278  - error: shelly.0 (1134) Cannot find view "system" for search "state" : Connection is closed.
2024-01-14 19:50:15.280  - error: shelly.0 (1134) Cannot find view "system" for search "channel" : Connection is closed.
2024-01-14 19:50:15.436  - error: shelly.0 (1134) Cannot find view "system" for search "state" : Connection is closed.
2024-01-14 19:50:15.475  - error: shelly.0 (1134) uncaught exception: Connection is closed.
2024-01-14 19:50:15.475  - error: shelly.0 (1134) Error: Connection is closed.
    at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24)
    at Redis.scan (/opt/iobroker/node_modules/ioredis/built/commander.js:122:25)
    at ScanStream._read (/opt/iobroker/node_modules/ioredis/built/ScanStream.js:36:41)
    at ScanStream.Readable.read (node:internal/streams/readable:539:12)
    at resume_ (node:internal/streams/readable:1040:12)
    at processTicksAndRejections (node:internal/process/task_queues:82:21)
    at runNextTicks (node:internal/process/task_queues:64:3)
    at processImmediate (node:internal/timers:447:9)
2024-01-14 19:50:15.477  - error: shelly.0 (1134) Connection is closed.
2024-01-14 19:50:15.491  - error: shelly.0 (1134) uncaught exception: Connection is closed.
2024-01-14 19:50:15.492  - error: shelly.0 (1134) Error: Connection is closed.
    at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24)
    at Redis.scan (/opt/iobroker/node_modules/ioredis/built/commander.js:122:25)
    at ScanStream._read (/opt/iobroker/node_modules/ioredis/built/ScanStream.js:36:41)
    at ScanStream.Readable.read (node:internal/streams/readable:539:12)
    at resume_ (node:internal/streams/readable:1040:12)
    at processTicksAndRejections (node:internal/process/task_queues:82:21)
    at runNextTicks (node:internal/process/task_queues:64:3)
    at processImmediate (node:internal/timers:447:9)
2024-01-14 19:50:15.493  - error: shelly.0 (1134) Connection is closed.
2024-01-14 19:50:15.497  - error: shelly.0 (1134) uncaught exception: Connection is closed.
2024-01-14 19:50:15.498  - error: shelly.0 (1134) Error: Connection is closed.
    at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24)
    at Redis.scan (/opt/iobroker/node_modules/ioredis/built/commander.js:122:25)
    at ScanStream._read (/opt/iobroker/node_modules/ioredis/built/ScanStream.js:36:41)
    at ScanStream.Readable.read (node:internal/streams/readable:539:12)
    at resume_ (node:internal/streams/readable:1040:12)
    at processTicksAndRejections (node:internal/process/task_queues:82:21)
    at runNextTicks (node:internal/process/task_queues:64:3)
    at processImmediate (node:internal/timers:447:9)
2024-01-14 19:50:15.498  - error: shelly.0 (1134) Connection is closed.
2024-01-14 19:50:15.500  - error: shelly.0 (1134) uncaught exception: Connection is closed.
2024-01-14 19:50:15.500  - error: shelly.0 (1134) Error: Connection is closed.
    at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24)
    at Redis.scan (/opt/iobroker/node_modules/ioredis/built/commander.js:122:25)
    at ScanStream._read (/opt/iobroker/node_modules/ioredis/built/ScanStream.js:36:41)
    at ScanStream.Readable.read (node:internal/streams/readable:539:12)
    at resume_ (node:internal/streams/readable:1040:12)
    at processTicksAndRejections (node:internal/process/task_queues:82:21)
    at runNextTicks (node:internal/process/task_queues:64:3)
    at processImmediate (node:internal/timers:447:9)
2024-01-14 19:50:15.501  - error: shelly.0 (1134) Connection is closed.
2024-01-14 19:50:15.503  - error: shelly.0 (1134) uncaught exception: Connection is closed.
2024-01-14 19:50:15.503  - error: shelly.0 (1134) Error: Connection is closed.
    at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24)
    at Redis.scan (/opt/iobroker/node_modules/ioredis/built/commander.js:122:25)
    at ScanStream._read (/opt/iobroker/node_modules/ioredis/built/ScanStream.js:36:41)
    at ScanStream.Readable.read (node:internal/streams/readable:539:12)
    at resume_ (node:internal/streams/readable:1040:12)
    at processTicksAndRejections (node:internal/process/task_queues:82:21)
    at runNextTicks (node:internal/process/task_queues:64:3)
    at processImmediate (node:internal/timers:447:9)
2024-01-14 19:50:15.504  - error: shelly.0 (1134) Connection is closed.
2024-01-14 19:50:15.506  - error: shelly.0 (1134) uncaught exception: Connection is closed.
2024-01-14 19:50:15.506  - error: shelly.0 (1134) Error: Connection is closed.
    at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24)
    at Redis.scan (/opt/iobroker/node_modules/ioredis/built/commander.js:122:25)
    at ScanStream._read (/opt/iobroker/node_modules/ioredis/built/ScanStream.js:36:41)
    at ScanStream.Readable.read (node:internal/streams/readable:539:12)
    at resume_ (node:internal/streams/readable:1040:12)
    at processTicksAndRejections (node:internal/process/task_queues:82:21)
    at runNextTicks (node:internal/process/task_queues:64:3)
    at processImmediate (node:internal/timers:447:9)
2024-01-14 19:50:15.506  - error: shelly.0 (1134) Connection is closed.
2024-01-14 19:50:15.160  - error: shelly.0 (1134) Cannot find view "system" for search "state" : DB closed
2024-01-14 19:50:15.160  - error: shelly.0 (1134) Cannot find view "system" for search "state" : DB closed
2024-01-14 19:50:15.162  - warn: shelly.0 (1134) Cannot get view: DB closed
2024-01-14 19:50:15.162  - warn: shelly.0 (1134) Cannot get view: DB closed
2024-01-14 19:50:15.163  - warn: shelly.0 (1134) Cannot get view: DB closed
2024-01-14 19:50:15.163  - warn: shelly.0 (1134) Cannot get view: DB closed
2024-01-14 19:50:15.167  - warn: shelly.0 (1134) Cannot get view: DB closed
2024-01-14 19:50:15.168  - warn: shelly.0 (1134) Cannot get view: DB closed
2024-01-14 19:50:15.168  - warn: shelly.0 (1134) Cannot get view: DB closed
2024-01-14 19:50:15.168  - warn: shelly.0 (1134) Cannot get view: DB closed
2024-01-14 19:50:15.169  - warn: shelly.0 (1134) Cannot get view: DB closed
2024-01-14 19:50:15.170  - error: shelly.0 (1134) Cannot find view "system" for search "channel" : DB closed
2024-01-14 19:50:15.180  - warn: shelly.0 (1134) Could not perform strict object check of state shelly.0.info.connection: DB closed
2024-01-14 19:50:15.180  - warn: shelly.0 (1134) get state error: Connection is closed.
2024-01-14 19:50:15.181  - warn: shelly.0 (1134) Could not perform strict object check of state shelly.0.info.connection: DB closed
2024-01-14 19:50:15.182  - warn: shelly.0 (1134) get state error: Connection is closed.
2024-01-14 19:50:15.208  - error: shelly.0 (1134) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
2024-01-14 19:50:15.209  - error: shelly.0 (1134) unhandled promise rejection: DB closed
2024-01-14 19:50:15.212  - error: shelly.0 (1134) Error: DB closed
    at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24)
    at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:122:25)
    at StateRedisClient.setState (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:726:40)
    at Shelly._setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:7710:33)
    at runNextTicks (node:internal/process/task_queues:60:5)
    at processImmediate (node:internal/timers:447:9)
2024-01-14 19:50:15.212  - error: shelly.0 (1134) DB closed
2024-01-14 19:50:15.223  - error: shelly.0 (1134) Error: DB closed
2024-01-14 19:50:15.224  - warn: shelly.0 (1134) setTimeout called, but adapter is shutting down
2024-01-14 19:50:15.225  - error: shelly.0 (1134) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
2024-01-14 19:50:15.225  - error: shelly.0 (1134) unhandled promise rejection: DB closed
2024-01-14 19:50:15.226  - error: shelly.0 (1134) Error: DB closed
    at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25)
    at Socket.<anonymous> (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20)
    at Object.onceWrapper (node:events:632:26)
    at Socket.emit (node:events:517:28)
    at Socket.emit (node:domain:489:12)
    at TCP.<anonymous> (node:net:350:12)
2024-01-14 19:50:15.227  - error: shelly.0 (1134) DB closed
2024-01-14 19:50:15.234  - error: shelly.0 (1134) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
2024-01-14 19:50:15.234  - error: shelly.0 (1134) unhandled promise rejection: DB closed
2024-01-14 19:50:15.236  - error: shelly.0 (1134) Error: DB closed
    at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24)
    at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:122:25)
    at StateRedisClient.setState (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:726:40)
    at Shelly._setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:7710:33)
    at runNextTicks (node:internal/process/task_queues:60:5)
    at processImmediate (node:internal/timers:447:9)
2024-01-14 19:50:15.237  - error: shelly.0 (1134) DB closed
2024-01-14 19:50:15.247  - error: shelly.0 (1134) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
2024-01-14 19:50:15.247  - error: shelly.0 (1134) unhandled promise rejection: DB closed
2024-01-14 19:50:15.248  - error: shelly.0 (1134) Error: DB closed
    at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25)
    at Socket.<anonymous> (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20)
    at Object.onceWrapper (node:events:632:26)
    at Socket.emit (node:events:517:28)
    at Socket.emit (node:domain:489:12)
    at TCP.<anonymous> (node:net:350:12)
2024-01-14 19:50:15.249  - error: shelly.0 (1134) DB closed
2024-01-14 19:50:15.260  - error: shelly.0 (1134) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
2024-01-14 19:50:15.260  - error: shelly.0 (1134) unhandled promise rejection: DB closed
2024-01-14 19:50:15.261  - error: shelly.0 (1134) Error: DB closed
    at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25)
    at Socket.<anonymous> (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20)
    at Object.onceWrapper (node:events:632:26)
    at Socket.emit (node:events:517:28)
    at Socket.emit (node:domain:489:12)
    at TCP.<anonymous> (node:net:350:12)
2024-01-14 19:50:15.263  - error: shelly.0 (1134) DB closed
2024-01-14 19:50:15.271  - error: shelly.0 (1134) Cannot find view "system" for search "state" : Connection is closed.
2024-01-14 19:50:15.273  - error: shelly.0 (1134) Cannot find view "system" for search "state" : Connection is closed.
2024-01-14 19:50:15.275  - error: shelly.0 (1134) Cannot find view "system" for search "state" : Connection is closed.
2024-01-14 19:50:15.277  - error: shelly.0 (1134) Cannot find view "system" for search "state" : Connection is closed.
2024-01-14 19:50:15.278  - error: shelly.0 (1134) Cannot find view "system" for search "state" : Connection is closed.
2024-01-14 19:50:15.280  - error: shelly.0 (1134) Cannot find view "system" for search "channel" : Connection is closed.
2024-01-14 19:50:15.436  - error: shelly.0 (1134) Cannot find view "system" for search "state" : Connection is closed.
2024-01-14 19:50:15.475  - error: shelly.0 (1134) uncaught exception: Connection is closed.
2024-01-14 19:50:15.475  - error: shelly.0 (1134) Error: Connection is closed.
    at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24)
    at Redis.scan (/opt/iobroker/node_modules/ioredis/built/commander.js:122:25)
    at ScanStream._read (/opt/iobroker/node_modules/ioredis/built/ScanStream.js:36:41)
    at ScanStream.Readable.read (node:internal/streams/readable:539:12)
    at resume_ (node:internal/streams/readable:1040:12)
    at processTicksAndRejections (node:internal/process/task_queues:82:21)
    at runNextTicks (node:internal/process/task_queues:64:3)
    at processImmediate (node:internal/timers:447:9)
2024-01-14 19:50:15.477  - error: shelly.0 (1134) Connection is closed.
2024-01-14 19:50:15.491  - error: shelly.0 (1134) uncaught exception: Connection is closed.
2024-01-14 19:50:15.492  - error: shelly.0 (1134) Error: Connection is closed.
    at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24)
    at Redis.scan (/opt/iobroker/node_modules/ioredis/built/commander.js:122:25)
    at ScanStream._read (/opt/iobroker/node_modules/ioredis/built/ScanStream.js:36:41)
    at ScanStream.Readable.read (node:internal/streams/readable:539:12)
    at resume_ (node:internal/streams/readable:1040:12)
    at processTicksAndRejections (node:internal/process/task_queues:82:21)
    at runNextTicks (node:internal/process/task_queues:64:3)
    at processImmediate (node:internal/timers:447:9)
2024-01-14 19:50:15.493  - error: shelly.0 (1134) Connection is closed.
2024-01-14 19:50:15.497  - error: shelly.0 (1134) uncaught exception: Connection is closed.
2024-01-14 19:50:15.498  - error: shelly.0 (1134) Error: Connection is closed.
    at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24)
    at Redis.scan (/opt/iobroker/node_modules/ioredis/built/commander.js:122:25)
    at ScanStream._read (/opt/iobroker/node_modules/ioredis/built/ScanStream.js:36:41)
    at ScanStream.Readable.read (node:internal/streams/readable:539:12)
    at resume_ (node:internal/streams/readable:1040:12)
    at processTicksAndRejections (node:internal/process/task_queues:82:21)
    at runNextTicks (node:internal/process/task_queues:64:3)
    at processImmediate (node:internal/timers:447:9)
2024-01-14 19:50:15.498  - error: shelly.0 (1134) Connection is closed.
2024-01-14 19:50:15.500  - error: shelly.0 (1134) uncaught exception: Connection is closed.
2024-01-14 19:50:15.500  - error: shelly.0 (1134) Error: Connection is closed.
    at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24)
    at Redis.scan (/opt/iobroker/node_modules/ioredis/built/commander.js:122:25)
    at ScanStream._read (/opt/iobroker/node_modules/ioredis/built/ScanStream.js:36:41)
    at ScanStream.Readable.read (node:internal/streams/readable:539:12)
    at resume_ (node:internal/streams/readable:1040:12)
    at processTicksAndRejections (node:internal/process/task_queues:82:21)
    at runNextTicks (node:internal/process/task_queues:64:3)
    at processImmediate (node:internal/timers:447:9)
2024-01-14 19:50:15.501  - error: shelly.0 (1134) Connection is closed.
2024-01-14 19:50:15.503  - error: shelly.0 (1134) uncaught exception: Connection is closed.
2024-01-14 19:50:15.503  - error: shelly.0 (1134) Error: Connection is closed.
    at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24)
    at Redis.scan (/opt/iobroker/node_modules/ioredis/built/commander.js:122:25)
    at ScanStream._read (/opt/iobroker/node_modules/ioredis/built/ScanStream.js:36:41)
    at ScanStream.Readable.read (node:internal/streams/readable:539:12)
    at resume_ (node:internal/streams/readable:1040:12)
    at processTicksAndRejections (node:internal/process/task_queues:82:21)
    at runNextTicks (node:internal/process/task_queues:64:3)
    at processImmediate (node:internal/timers:447:9)
2024-01-14 19:50:15.504  - error: shelly.0 (1134) Connection is closed.
2024-01-14 19:50:15.506  - error: shelly.0 (1134) uncaught exception: Connection is closed.
2024-01-14 19:50:15.506  - error: shelly.0 (1134) Error: Connection is closed.
    at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24)
    at Redis.scan (/opt/iobroker/node_modules/ioredis/built/commander.js:122:25)
    at ScanStream._read (/opt/iobroker/node_modules/ioredis/built/ScanStream.js:36:41)
    at ScanStream.Readable.read (node:internal/streams/readable:539:12)
    at resume_ (node:internal/streams/readable:1040:12)
    at processTicksAndRejections (node:internal/process/task_queues:82:21)
    at runNextTicks (node:internal/process/task_queues:64:3)
    at processImmediate (node:internal/timers:447:9)
2024-01-14 19:50:15.506  - error: shelly.0 (1134) Connection is closed.
2024-01-14 19:50:26.227  - error: host.raspberrypi4 Caught by controller[1]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
2024-01-14 19:50:26.228  - error: host.raspberrypi4 Caught by controller[1]: Error: DB closed
2024-01-14 19:50:26.229  - error: host.raspberrypi4 Caught by controller[1]:     at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25)
2024-01-14 19:50:26.229  - error: host.raspberrypi4 Caught by controller[1]:     at Socket.<anonymous> (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20)
2024-01-14 19:50:26.229  - error: host.raspberrypi4 Caught by controller[1]:     at Object.onceWrapper (node:events:632:26)
2024-01-14 19:50:26.229  - error: host.raspberrypi4 Caught by controller[1]:     at Socket.emit (node:events:517:28)
2024-01-14 19:50:26.229  - error: host.raspberrypi4 Caught by controller[1]:     at Socket.emit (node:domain:489:12)
2024-01-14 19:50:26.229  - error: host.raspberrypi4 Caught by controller[1]:     at TCP.<anonymous> (node:net:350:12)
2024-01-14 19:50:26.230  - error: host.raspberrypi4 Caught by controller[1]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
2024-01-14 19:50:26.230  - error: host.raspberrypi4 Caught by controller[1]: Error: DB closed
2024-01-14 19:50:26.230  - error: host.raspberrypi4 Caught by controller[1]:     at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25)
2024-01-14 19:50:26.230  - error: host.raspberrypi4 Caught by controller[1]:     at Socket.<anonymous> (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20)
2024-01-14 19:50:26.230  - error: host.raspberrypi4 Caught by controller[1]:     at Object.onceWrapper (node:events:632:26)
2024-01-14 19:50:26.230  - error: host.raspberrypi4 Caught by controller[1]:     at Socket.emit (node:events:517:28)
2024-01-14 19:50:26.230  - error: host.raspberrypi4 Caught by controller[1]:     at Socket.emit (node:domain:489:12)
2024-01-14 19:50:26.231  - error: host.raspberrypi4 Caught by controller[1]:     at TCP.<anonymous> (node:net:350:12)
2024-01-14 19:50:26.231  - error: host.raspberrypi4 Caught by controller[2]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
2024-01-14 19:50:26.231  - error: host.raspberrypi4 Caught by controller[2]: Error: DB closed
2024-01-14 19:50:26.231  - error: host.raspberrypi4 Caught by controller[2]:     at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24)
2024-01-14 19:50:26.231  - error: host.raspberrypi4 Caught by controller[2]:     at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:122:25)
2024-01-14 19:50:26.231  - error: host.raspberrypi4 Caught by controller[2]:     at StateRedisClient.setState (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:726:40)
2024-01-14 19:50:26.231  - error: host.raspberrypi4 Caught by controller[2]:     at Shelly._setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:7710:33)
2024-01-14 19:50:26.232  - error: host.raspberrypi4 Caught by controller[2]:     at runNextTicks (node:internal/process/task_queues:60:5)
2024-01-14 19:50:26.232  - error: host.raspberrypi4 Caught by controller[2]:     at processImmediate (node:internal/timers:447:9)
2024-01-14 19:50:26.232  - error: host.raspberrypi4 Caught by controller[3]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
2024-01-14 19:50:26.232  - error: host.raspberrypi4 Caught by controller[3]: Error: DB closed
2024-01-14 19:50:26.232  - error: host.raspberrypi4 Caught by controller[3]:     at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24)
2024-01-14 19:50:26.232  - error: host.raspberrypi4 Caught by controller[3]:     at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:122:25)
2024-01-14 19:50:26.232  - error: host.raspberrypi4 Caught by controller[3]:     at StateRedisClient.setState (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:726:40)
2024-01-14 19:50:26.232  - error: host.raspberrypi4 Caught by controller[3]:     at Shelly._setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:7710:33)
2024-01-14 19:50:26.233  - error: host.raspberrypi4 Caught by controller[3]:     at runNextTicks (node:internal/process/task_queues:60:5)
2024-01-14 19:50:26.233  - error: host.raspberrypi4 Caught by controller[3]:     at processImmediate (node:internal/timers:447:9)
2024-01-14 19:50:26.233  - error: host.raspberrypi4 Caught by controller[3]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
2024-01-14 19:50:26.233  - error: host.raspberrypi4 Caught by controller[3]: Error: DB closed
2024-01-14 19:50:26.233  - error: host.raspberrypi4 Caught by controller[3]:     at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24)
2024-01-14 19:50:26.233  - error: host.raspberrypi4 Caught by controller[3]:     at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:122:25)
2024-01-14 19:50:26.233  - error: host.raspberrypi4 Caught by controller[3]:     at StateRedisClient.setState (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:726:40)
2024-01-14 19:50:26.234  - error: host.raspberrypi4 Caught by controller[3]:     at Shelly._setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:7710:33)
2024-01-14 19:50:26.234  - error: host.raspberrypi4 Caught by controller[3]:     at runNextTicks (node:internal/process/task_queues:60:5)
2024-01-14 19:50:26.234  - error: host.raspberrypi4 Caught by controller[3]:     at processImmediate (node:internal/timers:447:9)
2024-01-14 19:50:26.235  - error: host.raspberrypi4 Caught by controller[4]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
2024-01-14 19:50:26.235  - error: host.raspberrypi4 Caught by controller[4]: Error: DB closed
2024-01-14 19:50:26.235  - error: host.raspberrypi4 Caught by controller[4]:     at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24)
2024-01-14 19:50:26.235  - error: host.raspberrypi4 Caught by controller[4]:     at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:122:25)
2024-01-14 19:50:26.235  - error: host.raspberrypi4 Caught by controller[4]:     at StateRedisClient.setState (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:726:40)
2024-01-14 19:50:26.235  - error: host.raspberrypi4 Caught by controller[4]:     at Shelly._setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:7710:33)
2024-01-14 19:50:26.235  - error: host.raspberrypi4 Caught by controller[4]:     at runNextTicks (node:internal/process/task_queues:60:5)
2024-01-14 19:50:26.235  - error: host.raspberrypi4 Caught by controller[4]:     at processImmediate (node:internal/timers:447:9)
2024-01-14 19:50:26.236  - error: host.raspberrypi4 Caught by controller[4]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
2024-01-14 19:50:26.236  - error: host.raspberrypi4 Caught by controller[4]: Error: DB closed
2024-01-14 19:50:26.236  - error: host.raspberrypi4 Caught by controller[4]:     at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25)
2024-01-14 19:50:26.236  - error: host.raspberrypi4 Caught by controller[4]:     at Socket.<anonymous> (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20)
2024-01-14 19:50:26.236  - error: host.raspberrypi4 Caught by controller[4]:     at Object.onceWrapper (node:events:632:26)
2024-01-14 19:50:26.236  - error: host.raspberrypi4 Caught by controller[4]:     at Socket.emit (node:events:517:28)
2024-01-14 19:50:26.236  - error: host.raspberrypi4 Caught by controller[4]:     at Socket.emit (node:domain:489:12)
2024-01-14 19:50:26.236  - error: host.raspberrypi4 Caught by controller[4]:     at TCP.<anonymous> (node:net:350:12)
2024-01-14 19:50:26.236  - error: host.raspberrypi4 Caught by controller[4]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
2024-01-14 19:50:26.236  - error: host.raspberrypi4 Caught by controller[4]: Error: DB closed
2024-01-14 19:50:26.236  - error: host.raspberrypi4 Caught by controller[4]:     at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24)
2024-01-14 19:50:26.237  - error: host.raspberrypi4 Caught by controller[4]:     at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:122:25)
2024-01-14 19:50:26.237  - error: host.raspberrypi4 Caught by controller[4]:     at StateRedisClient.setState (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:726:40)
2024-01-14 19:50:26.237  - error: host.raspberrypi4 Caught by controller[4]:     at Shelly._setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:7710:33)
2024-01-14 19:50:26.237  - error: host.raspberrypi4 Caught by controller[4]:     at runNextTicks (node:internal/process/task_queues:60:5)
2024-01-14 19:50:26.237  - error: host.raspberrypi4 Caught by controller[4]:     at processImmediate (node:internal/timers:447:9)
2024-01-14 19:50:26.237  - error: host.raspberrypi4 Caught by controller[4]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
2024-01-14 19:50:26.237  - error: host.raspberrypi4 Caught by controller[4]: Error: DB closed
2024-01-14 19:50:26.237  - error: host.raspberrypi4 Caught by controller[4]:     at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25)
2024-01-14 19:50:26.237  - error: host.raspberrypi4 Caught by controller[4]:     at Socket.<anonymous> (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20)
2024-01-14 19:50:26.237  - error: host.raspberrypi4 Caught by controller[4]:     at Object.onceWrapper (node:events:632:26)
2024-01-14 19:50:26.238  - error: host.raspberrypi4 Caught by controller[4]:     at Socket.emit (node:events:517:28)
2024-01-14 19:50:26.238  - error: host.raspberrypi4 Caught by controller[4]:     at Socket.emit (node:domain:489:12)
2024-01-14 19:50:26.238  - error: host.raspberrypi4 Caught by controller[4]:     at TCP.<anonymous> (node:net:350:12)
2024-01-14 19:50:26.238  - error: host.raspberrypi4 Caught by controller[4]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
2024-01-14 19:50:26.238  - error: host.raspberrypi4 Caught by controller[4]: Error: DB closed
2024-01-14 19:50:26.238  - error: host.raspberrypi4 Caught by controller[4]:     at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25)
2024-01-14 19:50:26.238  - error: host.raspberrypi4 Caught by controller[4]:     at Socket.<anonymous> (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20)
2024-01-14 19:50:26.238  - error: host.raspberrypi4 Caught by controller[4]:     at Object.onceWrapper (node:events:632:26)
2024-01-14 19:50:26.238  - error: host.raspberrypi4 Caught by controller[4]:     at Socket.emit (node:events:517:28)
2024-01-14 19:50:26.238  - error: host.raspberrypi4 Caught by controller[4]:     at Socket.emit (node:domain:489:12)
2024-01-14 19:50:26.239  - error: host.raspberrypi4 Caught by controller[4]:     at TCP.<anonymous> (node:net:350:12)
2024-01-14 19:50:26.239  - error: host.raspberrypi4 Caught by controller[4]: Error: Connection is closed.
2024-01-14 19:50:26.239  - error: host.raspberrypi4 Caught by controller[4]:     at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24)
2024-01-14 19:50:26.239  - error: host.raspberrypi4 Caught by controller[4]:     at Redis.scan (/opt/iobroker/node_modules/ioredis/built/commander.js:122:25)
2024-01-14 19:50:26.239  - error: host.raspberrypi4 Caught by controller[4]:     at ScanStream._read (/opt/iobroker/node_modules/ioredis/built/ScanStream.js:36:41)
2024-01-14 19:50:26.239  - error: host.raspberrypi4 Caught by controller[4]:     at ScanStream.Readable.read (node:internal/streams/readable:539:12)
2024-01-14 19:50:26.239  - error: host.raspberrypi4 Caught by controller[4]:     at resume_ (node:internal/streams/readable:1040:12)
2024-01-14 19:50:26.239  - error: host.raspberrypi4 Caught by controller[4]:     at processTicksAndRejections (node:internal/process/task_queues:82:21)
2024-01-14 19:50:26.239  - error: host.raspberrypi4 Caught by controller[4]:     at runNextTicks (node:internal/process/task_queues:64:3)
2024-01-14 19:50:26.239  - error: host.raspberrypi4 Caught by controller[4]:     at processImmediate (node:internal/timers:447:9)
2024-01-14 19:50:26.240  - error: host.raspberrypi4 Caught by controller[4]: Error: Connection is closed.
2024-01-14 19:50:26.240  - error: host.raspberrypi4 Caught by controller[4]:     at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24)
2024-01-14 19:50:26.240  - error: host.raspberrypi4 Caught by controller[4]:     at Redis.scan (/opt/iobroker/node_modules/ioredis/built/commander.js:122:25)
2024-01-14 19:50:26.240  - error: host.raspberrypi4 Caught by controller[4]:     at ScanStream._read (/opt/iobroker/node_modules/ioredis/built/ScanStream.js:36:41)
2024-01-14 19:50:26.240  - error: host.raspberrypi4 Caught by controller[4]:     at ScanStream.Readable.read (node:internal/streams/readable:539:12)
2024-01-14 19:50:26.240  - error: host.raspberrypi4 Caught by controller[4]:     at resume_ (node:internal/streams/readable:1040:12)
2024-01-14 19:50:26.240  - error: host.raspberrypi4 Caught by controller[4]:     at processTicksAndRejections (node:internal/process/task_queues:82:21)
2024-01-14 19:50:26.240  - error: host.raspberrypi4 Caught by controller[4]:     at runNextTicks (node:internal/process/task_queues:64:3)
2024-01-14 19:50:26.240  - error: host.raspberrypi4 Caught by controller[4]:     at processImmediate (node:internal/timers:447:9)
2024-01-14 19:50:26.240  - error: host.raspberrypi4 Caught by controller[4]: Error: Connection is closed.
2024-01-14 19:50:26.241  - error: host.raspberrypi4 Caught by controller[4]:     at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24)
2024-01-14 19:50:26.241  - error: host.raspberrypi4 Caught by controller[4]:     at Redis.scan (/opt/iobroker/node_modules/ioredis/built/commander.js:122:25)
2024-01-14 19:50:26.241  - error: host.raspberrypi4 Caught by controller[4]:     at ScanStream._read (/opt/iobroker/node_modules/ioredis/built/ScanStream.js:36:41)
2024-01-14 19:50:26.241  - error: host.raspberrypi4 Caught by controller[4]:     at ScanStream.Readable.read (node:internal/streams/readable:539:12)
2024-01-14 19:50:26.241  - error: host.raspberrypi4 Caught by controller[4]:     at resume_ (node:internal/streams/readable:1040:12)
2024-01-14 19:50:26.241  - error: host.raspberrypi4 Caught by controller[4]:     at processTicksAndRejections (node:internal/process/task_queues:82:21)
2024-01-14 19:50:26.241  - error: host.raspberrypi4 Caught by controller[4]:     at runNextTicks (node:internal/process/task_queues:64:3)
2024-01-14 19:50:26.241  - error: host.raspberrypi4 Caught by controller[4]:     at processImmediate (node:internal/timers:447:9)
2024-01-14 19:50:26.241  - error: host.raspberrypi4 Caught by controller[4]: Error: Connection is closed.
2024-01-14 19:50:26.241  - error: host.raspberrypi4 Caught by controller[4]:     at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24)
2024-01-14 19:50:26.241  - error: host.raspberrypi4 Caught by controller[4]:     at Redis.scan (/opt/iobroker/node_modules/ioredis/built/commander.js:122:25)
2024-01-14 19:50:26.242  - error: host.raspberrypi4 Caught by controller[4]:     at ScanStream._read (/opt/iobroker/node_modules/ioredis/built/ScanStream.js:36:41)
2024-01-14 19:50:26.242  - error: host.raspberrypi4 Caught by controller[4]:     at ScanStream.Readable.read (node:internal/streams/readable:539:12)
2024-01-14 19:50:26.242  - error: host.raspberrypi4 Caught by controller[4]:     at resume_ (node:internal/streams/readable:1040:12)
2024-01-14 19:50:26.242  - error: host.raspberrypi4 Caught by controller[4]:     at processTicksAndRejections (node:internal/process/task_queues:82:21)
2024-01-14 19:50:26.242  - error: host.raspberrypi4 Caught by controller[4]:     at runNextTicks (node:internal/process/task_queues:64:3)
2024-01-14 19:50:26.242  - error: host.raspberrypi4 Caught by controller[4]:     at processImmediate (node:internal/timers:447:9)
2024-01-14 19:50:26.242  - error: host.raspberrypi4 Caught by controller[4]: Error: Connection is closed.
2024-01-14 19:50:26.242  - error: host.raspberrypi4 Caught by controller[4]:     at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24)
2024-01-14 19:50:26.242  - error: host.raspberrypi4 Caught by controller[4]:     at Redis.scan (/opt/iobroker/node_modules/ioredis/built/commander.js:122:25)
2024-01-14 19:50:26.242  - error: host.raspberrypi4 Caught by controller[4]:     at ScanStream._read (/opt/iobroker/node_modules/ioredis/built/ScanStream.js:36:41)
2024-01-14 19:50:26.243  - error: host.raspberrypi4 Caught by controller[4]:     at ScanStream.Readable.read (node:internal/streams/readable:539:12)
2024-01-14 19:50:26.243  - error: host.raspberrypi4 Caught by controller[4]:     at resume_ (node:internal/streams/readable:1040:12)
2024-01-14 19:50:26.243  - error: host.raspberrypi4 Caught by controller[4]:     at processTicksAndRejections (node:internal/process/task_queues:82:21)
2024-01-14 19:50:26.243  - error: host.raspberrypi4 Caught by controller[4]:     at runNextTicks (node:internal/process/task_queues:64:3)
2024-01-14 19:50:26.243  - error: host.raspberrypi4 Caught by controller[4]:     at processImmediate (node:internal/timers:447:9)
2024-01-14 19:50:26.243  - error: host.raspberrypi4 Caught by controller[4]: Error: Connection is closed.
2024-01-14 19:50:26.243  - error: host.raspberrypi4 Caught by controller[4]:     at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24)
2024-01-14 19:50:26.243  - error: host.raspberrypi4 Caught by controller[4]:     at Redis.scan (/opt/iobroker/node_modules/ioredis/built/commander.js:122:25)
2024-01-14 19:50:26.243  - error: host.raspberrypi4 Caught by controller[4]:     at ScanStream._read (/opt/iobroker/node_modules/ioredis/built/ScanStream.js:36:41)
2024-01-14 19:50:26.243  - error: host.raspberrypi4 Caught by controller[4]:     at ScanStream.Readable.read (node:internal/streams/readable:539:12)
2024-01-14 19:50:26.243  - error: host.raspberrypi4 Caught by controller[4]:     at resume_ (node:internal/streams/readable:1040:12)
2024-01-14 19:50:26.244  - error: host.raspberrypi4 Caught by controller[4]:     at processTicksAndRejections (node:internal/process/task_queues:82:21)
2024-01-14 19:50:26.244  - error: host.raspberrypi4 Caught by controller[4]:     at runNextTicks (node:internal/process/task_queues:64:3)
2024-01-14 19:50:26.244  - error: host.raspberrypi4 Caught by controller[4]:     at processImmediate (node:internal/timers:447:9)
2024-01-14 19:50:26.244  - info: host.raspberrypi4 instance system.adapter.shelly.0 terminated with code 1 (JS_CONTROLLER_STOPPED)
2024-01-14 19:50:26.227  - error: host.raspberrypi4 Caught by controller[1]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
2024-01-14 19:50:26.228  - error: host.raspberrypi4 Caught by controller[1]: Error: DB closed
2024-01-14 19:50:26.229  - error: host.raspberrypi4 Caught by controller[1]:     at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25)
2024-01-14 19:50:26.229  - error: host.raspberrypi4 Caught by controller[1]:     at Socket.<anonymous> (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20)
2024-01-14 19:50:26.229  - error: host.raspberrypi4 Caught by controller[1]:     at Object.onceWrapper (node:events:632:26)
2024-01-14 19:50:26.229  - error: host.raspberrypi4 Caught by controller[1]:     at Socket.emit (node:events:517:28)
2024-01-14 19:50:26.229  - error: host.raspberrypi4 Caught by controller[1]:     at Socket.emit (node:domain:489:12)
2024-01-14 19:50:26.229  - error: host.raspberrypi4 Caught by controller[1]:     at TCP.<anonymous> (node:net:350:12)
2024-01-14 19:50:26.230  - error: host.raspberrypi4 Caught by controller[1]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
2024-01-14 19:50:26.230  - error: host.raspberrypi4 Caught by controller[1]: Error: DB closed
2024-01-14 19:50:26.230  - error: host.raspberrypi4 Caught by controller[1]:     at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25)
2024-01-14 19:50:26.230  - error: host.raspberrypi4 Caught by controller[1]:     at Socket.<anonymous> (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20)
2024-01-14 19:50:26.230  - error: host.raspberrypi4 Caught by controller[1]:     at Object.onceWrapper (node:events:632:26)
2024-01-14 19:50:26.230  - error: host.raspberrypi4 Caught by controller[1]:     at Socket.emit (node:events:517:28)
2024-01-14 19:50:26.230  - error: host.raspberrypi4 Caught by controller[1]:     at Socket.emit (node:domain:489:12)
2024-01-14 19:50:26.231  - error: host.raspberrypi4 Caught by controller[1]:     at TCP.<anonymous> (node:net:350:12)
2024-01-14 19:50:26.231  - error: host.raspberrypi4 Caught by controller[2]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
2024-01-14 19:50:26.231  - error: host.raspberrypi4 Caught by controller[2]: Error: DB closed
2024-01-14 19:50:26.231  - error: host.raspberrypi4 Caught by controller[2]:     at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24)
2024-01-14 19:50:26.231  - error: host.raspberrypi4 Caught by controller[2]:     at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:122:25)
2024-01-14 19:50:26.231  - error: host.raspberrypi4 Caught by controller[2]:     at StateRedisClient.setState (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:726:40)
2024-01-14 19:50:26.231  - error: host.raspberrypi4 Caught by controller[2]:     at Shelly._setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:7710:33)
2024-01-14 19:50:26.232  - error: host.raspberrypi4 Caught by controller[2]:     at runNextTicks (node:internal/process/task_queues:60:5)
2024-01-14 19:50:26.232  - error: host.raspberrypi4 Caught by controller[2]:     at processImmediate (node:internal/timers:447:9)
2024-01-14 19:50:26.232  - error: host.raspberrypi4 Caught by controller[3]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
2024-01-14 19:50:26.232  - error: host.raspberrypi4 Caught by controller[3]: Error: DB closed
2024-01-14 19:50:26.232  - error: host.raspberrypi4 Caught by controller[3]:     at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24)
2024-01-14 19:50:26.232  - error: host.raspberrypi4 Caught by controller[3]:     at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:122:25)
2024-01-14 19:50:26.232  - error: host.raspberrypi4 Caught by controller[3]:     at StateRedisClient.setState (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:726:40)
2024-01-14 19:50:26.232  - error: host.raspberrypi4 Caught by controller[3]:     at Shelly._setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:7710:33)
2024-01-14 19:50:26.233  - error: host.raspberrypi4 Caught by controller[3]:     at runNextTicks (node:internal/process/task_queues:60:5)
2024-01-14 19:50:26.233  - error: host.raspberrypi4 Caught by controller[3]:     at processImmediate (node:internal/timers:447:9)
2024-01-14 19:50:26.233  - error: host.raspberrypi4 Caught by controller[3]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
2024-01-14 19:50:26.233  - error: host.raspberrypi4 Caught by controller[3]: Error: DB closed
2024-01-14 19:50:26.233  - error: host.raspberrypi4 Caught by controller[3]:     at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24)
2024-01-14 19:50:26.233  - error: host.raspberrypi4 Caught by controller[3]:     at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:122:25)
2024-01-14 19:50:26.233  - error: host.raspberrypi4 Caught by controller[3]:     at StateRedisClient.setState (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:726:40)
2024-01-14 19:50:26.234  - error: host.raspberrypi4 Caught by controller[3]:     at Shelly._setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:7710:33)
2024-01-14 19:50:26.234  - error: host.raspberrypi4 Caught by controller[3]:     at runNextTicks (node:internal/process/task_queues:60:5)
2024-01-14 19:50:26.234  - error: host.raspberrypi4 Caught by controller[3]:     at processImmediate (node:internal/timers:447:9)
2024-01-14 19:50:26.235  - error: host.raspberrypi4 Caught by controller[4]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
2024-01-14 19:50:26.235  - error: host.raspberrypi4 Caught by controller[4]: Error: DB closed
2024-01-14 19:50:26.235  - error: host.raspberrypi4 Caught by controller[4]:     at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24)
2024-01-14 19:50:26.235  - error: host.raspberrypi4 Caught by controller[4]:     at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:122:25)
2024-01-14 19:50:26.235  - error: host.raspberrypi4 Caught by controller[4]:     at StateRedisClient.setState (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:726:40)
2024-01-14 19:50:26.235  - error: host.raspberrypi4 Caught by controller[4]:     at Shelly._setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:7710:33)
2024-01-14 19:50:26.235  - error: host.raspberrypi4 Caught by controller[4]:     at runNextTicks (node:internal/process/task_queues:60:5)
2024-01-14 19:50:26.235  - error: host.raspberrypi4 Caught by controller[4]:     at processImmediate (node:internal/timers:447:9)
2024-01-14 19:50:26.236  - error: host.raspberrypi4 Caught by controller[4]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
2024-01-14 19:50:26.236  - error: host.raspberrypi4 Caught by controller[4]: Error: DB closed
2024-01-14 19:50:26.236  - error: host.raspberrypi4 Caught by controller[4]:     at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25)
2024-01-14 19:50:26.236  - error: host.raspberrypi4 Caught by controller[4]:     at Socket.<anonymous> (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20)
2024-01-14 19:50:26.236  - error: host.raspberrypi4 Caught by controller[4]:     at Object.onceWrapper (node:events:632:26)
2024-01-14 19:50:26.236  - error: host.raspberrypi4 Caught by controller[4]:     at Socket.emit (node:events:517:28)
2024-01-14 19:50:26.236  - error: host.raspberrypi4 Caught by controller[4]:     at Socket.emit (node:domain:489:12)
2024-01-14 19:50:26.236  - error: host.raspberrypi4 Caught by controller[4]:     at TCP.<anonymous> (node:net:350:12)
2024-01-14 19:50:26.236  - error: host.raspberrypi4 Caught by controller[4]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
2024-01-14 19:50:26.236  - error: host.raspberrypi4 Caught by controller[4]: Error: DB closed
2024-01-14 19:50:26.236  - error: host.raspberrypi4 Caught by controller[4]:     at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24)
2024-01-14 19:50:26.237  - error: host.raspberrypi4 Caught by controller[4]:     at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:122:25)
2024-01-14 19:50:26.237  - error: host.raspberrypi4 Caught by controller[4]:     at StateRedisClient.setState (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:726:40)
2024-01-14 19:50:26.237  - error: host.raspberrypi4 Caught by controller[4]:     at Shelly._setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:7710:33)
2024-01-14 19:50:26.237  - error: host.raspberrypi4 Caught by controller[4]:     at runNextTicks (node:internal/process/task_queues:60:5)
2024-01-14 19:50:26.237  - error: host.raspberrypi4 Caught by controller[4]:     at processImmediate (node:internal/timers:447:9)
2024-01-14 19:50:26.237  - error: host.raspberrypi4 Caught by controller[4]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
2024-01-14 19:50:26.237  - error: host.raspberrypi4 Caught by controller[4]: Error: DB closed
2024-01-14 19:50:26.237  - error: host.raspberrypi4 Caught by controller[4]:     at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25)
2024-01-14 19:50:26.237  - error: host.raspberrypi4 Caught by controller[4]:     at Socket.<anonymous> (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20)
2024-01-14 19:50:26.237  - error: host.raspberrypi4 Caught by controller[4]:     at Object.onceWrapper (node:events:632:26)
2024-01-14 19:50:26.238  - error: host.raspberrypi4 Caught by controller[4]:     at Socket.emit (node:events:517:28)
2024-01-14 19:50:26.238  - error: host.raspberrypi4 Caught by controller[4]:     at Socket.emit (node:domain:489:12)
2024-01-14 19:50:26.238  - error: host.raspberrypi4 Caught by controller[4]:     at TCP.<anonymous> (node:net:350:12)
2024-01-14 19:50:26.238  - error: host.raspberrypi4 Caught by controller[4]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
2024-01-14 19:50:26.238  - error: host.raspberrypi4 Caught by controller[4]: Error: DB closed
2024-01-14 19:50:26.238  - error: host.raspberrypi4 Caught by controller[4]:     at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25)
2024-01-14 19:50:26.238  - error: host.raspberrypi4 Caught by controller[4]:     at Socket.<anonymous> (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20)
2024-01-14 19:50:26.238  - error: host.raspberrypi4 Caught by controller[4]:     at Object.onceWrapper (node:events:632:26)
2024-01-14 19:50:26.238  - error: host.raspberrypi4 Caught by controller[4]:     at Socket.emit (node:events:517:28)
2024-01-14 19:50:26.238  - error: host.raspberrypi4 Caught by controller[4]:     at Socket.emit (node:domain:489:12)
2024-01-14 19:50:26.239  - error: host.raspberrypi4 Caught by controller[4]:     at TCP.<anonymous> (node:net:350:12)
2024-01-14 19:50:26.239  - error: host.raspberrypi4 Caught by controller[4]: Error: Connection is closed.
2024-01-14 19:50:26.239  - error: host.raspberrypi4 Caught by controller[4]:     at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24)
2024-01-14 19:50:26.239  - error: host.raspberrypi4 Caught by controller[4]:     at Redis.scan (/opt/iobroker/node_modules/ioredis/built/commander.js:122:25)
2024-01-14 19:50:26.239  - error: host.raspberrypi4 Caught by controller[4]:     at ScanStream._read (/opt/iobroker/node_modules/ioredis/built/ScanStream.js:36:41)
2024-01-14 19:50:26.239  - error: host.raspberrypi4 Caught by controller[4]:     at ScanStream.Readable.read (node:internal/streams/readable:539:12)
2024-01-14 19:50:26.239  - error: host.raspberrypi4 Caught by controller[4]:     at resume_ (node:internal/streams/readable:1040:12)
2024-01-14 19:50:26.239  - error: host.raspberrypi4 Caught by controller[4]:     at processTicksAndRejections (node:internal/process/task_queues:82:21)
2024-01-14 19:50:26.239  - error: host.raspberrypi4 Caught by controller[4]:     at runNextTicks (node:internal/process/task_queues:64:3)
2024-01-14 19:50:26.239  - error: host.raspberrypi4 Caught by controller[4]:     at processImmediate (node:internal/timers:447:9)
2024-01-14 19:50:26.240  - error: host.raspberrypi4 Caught by controller[4]: Error: Connection is closed.
2024-01-14 19:50:26.240  - error: host.raspberrypi4 Caught by controller[4]:     at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24)
2024-01-14 19:50:26.240  - error: host.raspberrypi4 Caught by controller[4]:     at Redis.scan (/opt/iobroker/node_modules/ioredis/built/commander.js:122:25)
2024-01-14 19:50:26.240  - error: host.raspberrypi4 Caught by controller[4]:     at ScanStream._read (/opt/iobroker/node_modules/ioredis/built/ScanStream.js:36:41)
2024-01-14 19:50:26.240  - error: host.raspberrypi4 Caught by controller[4]:     at ScanStream.Readable.read (node:internal/streams/readable:539:12)
2024-01-14 19:50:26.240  - error: host.raspberrypi4 Caught by controller[4]:     at resume_ (node:internal/streams/readable:1040:12)
2024-01-14 19:50:26.240  - error: host.raspberrypi4 Caught by controller[4]:     at processTicksAndRejections (node:internal/process/task_queues:82:21)
2024-01-14 19:50:26.240  - error: host.raspberrypi4 Caught by controller[4]:     at runNextTicks (node:internal/process/task_queues:64:3)
2024-01-14 19:50:26.240  - error: host.raspberrypi4 Caught by controller[4]:     at processImmediate (node:internal/timers:447:9)
2024-01-14 19:50:26.240  - error: host.raspberrypi4 Caught by controller[4]: Error: Connection is closed.
2024-01-14 19:50:26.241  - error: host.raspberrypi4 Caught by controller[4]:     at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24)
2024-01-14 19:50:26.241  - error: host.raspberrypi4 Caught by controller[4]:     at Redis.scan (/opt/iobroker/node_modules/ioredis/built/commander.js:122:25)
2024-01-14 19:50:26.241  - error: host.raspberrypi4 Caught by controller[4]:     at ScanStream._read (/opt/iobroker/node_modules/ioredis/built/ScanStream.js:36:41)
2024-01-14 19:50:26.241  - error: host.raspberrypi4 Caught by controller[4]:     at ScanStream.Readable.read (node:internal/streams/readable:539:12)
2024-01-14 19:50:26.241  - error: host.raspberrypi4 Caught by controller[4]:     at resume_ (node:internal/streams/readable:1040:12)
2024-01-14 19:50:26.241  - error: host.raspberrypi4 Caught by controller[4]:     at processTicksAndRejections (node:internal/process/task_queues:82:21)
2024-01-14 19:50:26.241  - error: host.raspberrypi4 Caught by controller[4]:     at runNextTicks (node:internal/process/task_queues:64:3)
2024-01-14 19:50:26.241  - error: host.raspberrypi4 Caught by controller[4]:     at processImmediate (node:internal/timers:447:9)
2024-01-14 19:50:26.241  - error: host.raspberrypi4 Caught by controller[4]: Error: Connection is closed.
2024-01-14 19:50:26.241  - error: host.raspberrypi4 Caught by controller[4]:     at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24)
2024-01-14 19:50:26.241  - error: host.raspberrypi4 Caught by controller[4]:     at Redis.scan (/opt/iobroker/node_modules/ioredis/built/commander.js:122:25)
2024-01-14 19:50:26.242  - error: host.raspberrypi4 Caught by controller[4]:     at ScanStream._read (/opt/iobroker/node_modules/ioredis/built/ScanStream.js:36:41)
2024-01-14 19:50:26.242  - error: host.raspberrypi4 Caught by controller[4]:     at ScanStream.Readable.read (node:internal/streams/readable:539:12)
2024-01-14 19:50:26.242  - error: host.raspberrypi4 Caught by controller[4]:     at resume_ (node:internal/streams/readable:1040:12)
2024-01-14 19:50:26.242  - error: host.raspberrypi4 Caught by controller[4]:     at processTicksAndRejections (node:internal/process/task_queues:82:21)
2024-01-14 19:50:26.242  - error: host.raspberrypi4 Caught by controller[4]:     at runNextTicks (node:internal/process/task_queues:64:3)
2024-01-14 19:50:26.242  - error: host.raspberrypi4 Caught by controller[4]:     at processImmediate (node:internal/timers:447:9)
2024-01-14 19:50:26.242  - error: host.raspberrypi4 Caught by controller[4]: Error: Connection is closed.
2024-01-14 19:50:26.242  - error: host.raspberrypi4 Caught by controller[4]:     at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24)
2024-01-14 19:50:26.242  - error: host.raspberrypi4 Caught by controller[4]:     at Redis.scan (/opt/iobroker/node_modules/ioredis/built/commander.js:122:25)
2024-01-14 19:50:26.242  - error: host.raspberrypi4 Caught by controller[4]:     at ScanStream._read (/opt/iobroker/node_modules/ioredis/built/ScanStream.js:36:41)
2024-01-14 19:50:26.243  - error: host.raspberrypi4 Caught by controller[4]:     at ScanStream.Readable.read (node:internal/streams/readable:539:12)
2024-01-14 19:50:26.243  - error: host.raspberrypi4 Caught by controller[4]:     at resume_ (node:internal/streams/readable:1040:12)
2024-01-14 19:50:26.243  - error: host.raspberrypi4 Caught by controller[4]:     at processTicksAndRejections (node:internal/process/task_queues:82:21)
2024-01-14 19:50:26.243  - error: host.raspberrypi4 Caught by controller[4]:     at runNextTicks (node:internal/process/task_queues:64:3)
2024-01-14 19:50:26.243  - error: host.raspberrypi4 Caught by controller[4]:     at processImmediate (node:internal/timers:447:9)
2024-01-14 19:50:26.243  - error: host.raspberrypi4 Caught by controller[4]: Error: Connection is closed.
2024-01-14 19:50:26.243  - error: host.raspberrypi4 Caught by controller[4]:     at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24)
2024-01-14 19:50:26.243  - error: host.raspberrypi4 Caught by controller[4]:     at Redis.scan (/opt/iobroker/node_modules/ioredis/built/commander.js:122:25)
2024-01-14 19:50:26.243  - error: host.raspberrypi4 Caught by controller[4]:     at ScanStream._read (/opt/iobroker/node_modules/ioredis/built/ScanStream.js:36:41)
2024-01-14 19:50:26.243  - error: host.raspberrypi4 Caught by controller[4]:     at ScanStream.Readable.read (node:internal/streams/readable:539:12)
2024-01-14 19:50:26.243  - error: host.raspberrypi4 Caught by controller[4]:     at resume_ (node:internal/streams/readable:1040:12)
2024-01-14 19:50:26.244  - error: host.raspberrypi4 Caught by controller[4]:     at processTicksAndRejections (node:internal/process/task_queues:82:21)
2024-01-14 19:50:26.244  - error: host.raspberrypi4 Caught by controller[4]:     at runNextTicks (node:internal/process/task_queues:64:3)
2024-01-14 19:50:26.244  - error: host.raspberrypi4 Caught by controller[4]:     at processImmediate (node:internal/timers:447:9)
2024-01-14 19:50:26.244  - info: host.raspberrypi4 instance system.adapter.shelly.0 terminated with code 1 (JS_CONTROLLER_STOPPED)

[dike1982]

Ich hab festgetsllt, dass ich dir die Logs nicht im debug mode gepostet habe. Das Log hätte ich, aber wie kann ich das hier posten. Wenn ich es hier reinkopiere habe ich zuviel Zeichen!

[klein0r]

Naja erstmal wird in dem Log nicht viel anderes stehen. Deine Objekt- und State-DB macht Probleme.

[dike1982]

Ah ha und wie löse ich das nun?

[dike1982]

Auf Hinweis einen Forenmitglieds habe ich den Device-Watcher Adapter deaktiviert. Aktuell läuft alles ohne Fehler. An was kann das liegen, dass die beiden sich nicht verstehen?

[klein0r]

An was kann das liegen, dass die beiden sich nicht verstehen?

Kann ich mir nicht erklären. Immerhin laufen die in getrennten Prozessen (wenn der compact mode nicht aktiviert wurde) und haben sonst auch nix miteinander zu tun.

[andiweli]

Hab hier ähnliches Problem mit einem Shelly Pro 3EM. Lief bis vor kurzem eigentlich problemlos, seit ein paar Tagen mehrmals die Stunde diese beiden Einträge:

shelly.1	2024-03-08 23:32:11.936	error	[MQTT] Unable to get mqttprefix of client with id "shellypro3em-34987a453838"
shelly.1	2024-03-08 23:32:11.930	error	[MQTT] Error in function setMqttPrefixHttp (Gen 1) for (undefined / undefined / undefined): TypeError: Cannot read properties of undefined (reading 'replace')

[Tom54497]

Nach Update noch immer bei Shelly Plus HT:

[MQTT] Error in function setMqttPrefixHttp (Gen 1) for (undefined / undefined / undefined): TypeError: Cannot read properties of undefined (reading 'replace')

[thurbo]

Ich hab das Problem noch bei einem ShellyPlus 2pm [MQTT] Error in function setMqttPrefixHttp (Gen 1) for (undefined / undefined / undefined): TypeError: Cannot read properties of undefined (reading 'replace')

Außerdem Connected der alle 12 Minuten neu.

[klein0r]

Das komische ist, dass in euren Fällen fast immer ein Gen2-Gerät denkt, es wäre Gen1-Gerät. Ich kann das nicht reproduzieren.

[diamand2k22]

Ich konnte das Problem für mich lösen in dem ich im Shelly Adapter unter benutzerdefinierten Einstellungen das Aktualisierungsintervall auf 120 Sek. eingestellt habe. Ich habe die neuste stable Firmware v1.3 auf all meinen Shelly 1Plus.

[Dette70]

Ich konnte das Problem für mich lösen in dem ich im Shelly Adapter unter benutzerdefinierten Einstellungen das Aktualisierungsintervall auf 120 Sek. eingestellt habe. Ich habe die neuste stable Firmware v1.3 auf all meinen Shelly 1Plus.

Habe den Adapter heute auf 6.9. aktualisiert und das Intervall auch von 15 sek auf 120 sek geändert. Bin gespannt, ob das hilft. Zumindest die "bekannten" Fehler beim Starten des Adapters waren weiter vorhanden, hören aber nach kurzer Zeit auf. Ich beobachte das mal weiter.

[diamand2k22]

Ich konnte das Problem für mich lösen in dem ich im Shelly Adapter unter benutzerdefinierten Einstellungen das Aktualisierungsintervall auf 120 Sek. eingestellt habe. Ich habe die neuste stable Firmware v1.3 auf all meinen Shelly 1Plus.

Habe den Adapter heute auf 6.9. aktualisiert und das Intervall auch von 15 sek auf 120 sek geändert. Bin gespannt, ob das hilft. Zumindest die "bekannten" Fehler beim Starten des Adapters waren weiter vorhanden, hören aber nach kurzer Zeit auf. Ich beobachte das mal weiter.

Ja am Anfang kommen die Fehler zwar, aber dann läuft er stabil. Ich denke das ist ein Bug vom Shelly Adapter und nicht von den Shelly Devices.

[ReinWei56]

Ich habe dieses Problem auch immer mal wieder, aber in keiner Regelmäßigkeit `

277524	2024-05-03 00:29:02.719	error	[MQTT] Unable to get mqttprefix of client with id "shellyplusht-c049ef8916d4"
shelly.1	277524	2024-05-03 00:29:02.685	error	[MQTT] Error in function setMqttPrefixHttp (Gen 1) for (undefined / undefined / undefined): TypeError: Cannot read properties of undefined (reading 'replace')

Meine Adapterversion ist die 6.9.0, Nodejs 18.20.2, NPM 10.5.0 Die Firmware war 1.2.2, habe jetzt das Update auf 1.3.0 gemacht. Ich beobachte das weiter

Habe jetzt die Meldung auch von einem TRV bekommem

`

shelly.1	277524	2024-05-06 05:45:40.955	error	[MQTT] Unable to get mqttprefix of client with id "shellytrv-84FD271BE878"
shelly.1	277524	2024-05-06 05:45:40.944	error	[MQTT] Error in function setMqttPrefixHttp (Gen 1) for 192.168.178.60 (undefined / undefined / undefined): TypeError: Cannot read properties of undefined (reading 'replace')

`

[Tom54497]

Ich konnte das Problem für mich lösen in dem ich im Shelly Adapter unter benutzerdefinierten Einstellungen das Aktualisierungsintervall auf 120 Sek. eingestellt habe. Ich habe die neuste stable Firmware v1.3 auf all meinen Shelly 1Plus.

FW 1.3 und 120 sec haben bei mir keine Änderung bewirkt

[diamand2k22]

Evtl. Mal mit der Zeit höher gehen bzw. den devicewatcher Adapter deaktivieren beim starten des Shelly Adapters. Der spukt hier auch immer mal wieder rein.

[klein0r]

den devicewatcher Adapter deaktivieren beim starten des Shelly Adapters

Bitte mal den technischen Hintergrund erklären

[Tom54497]

Evtl. Mal mit der Zeit höher gehen bzw. den devicewatcher Adapter deaktivieren beim starten des Shelly Adapters. Der spukt hier auch immer mal wieder rein.

Device watcher Adapter ist nicht installiert!

[diamand2k22]

den devicewatcher Adapter deaktivieren beim starten des Shelly Adapters

Bitte mal den technischen Hintergrund erklären

bei mir ist mit dem devicewatcher schon öfter mal der CPU-Load durch die Decke gegangen und hat andere Prozesse dadurch lahmgelegt.

[Dette70]

Ich konnte das Problem für mich lösen in dem ich im Shelly Adapter unter benutzerdefinierten Einstellungen das Aktualisierungsintervall auf 120 Sek. eingestellt habe. Ich habe die neuste stable Firmware v1.3 auf all meinen Shelly 1Plus.

Habe den Adapter heute auf 6.9. aktualisiert und das Intervall auch von 15 sek auf 120 sek geändert. Bin gespannt, ob das hilft. Zumindest die "bekannten" Fehler beim Starten des Adapters waren weiter vorhanden, hören aber nach kurzer Zeit auf. Ich beobachte das mal weiter.

So, bei mir läuft jetzt seit einer Woche die o. g. Variante. Seit dem habe ich keine MQTT Fehler mehr. FW sind alle Shelly's auf 1.3.

[megamacy]

Korrigiere mich wenn ich falsch liege, aber hat du jetzt nicht nur alle 2min ein Sensor Update?

[Dette70]

Korrigiere mich wenn ich falsch liege, aber hat du jetzt nicht nur alle 2min ein Sensor Update?

Hier müssten wir mal den Entwickler fragen, welchen genaue Effekt das Hochsetzen hat, bin kein MQTT Experte. Nach meinem Verständnis bezieht sich das NUR auf das Abfragen der Shelly's durch den Iobroker, jedoch nicht auf das Senden der Shelly's an den Iobroker. Ich bekomme z.B. von meinem Shelly Pro 3EM Daten weiterhin in deutlich kürzeren Intervallen als 120 sek.

[Imperial929]

I also had this issue - but it was my "stupidity".

Background: I replaced a Gen1 Device with a Gen2 Device, giving it the same IP (because it's a 1:1 replacement) and therefore the "stupid" iobroker was still using the old prefix structure under objects. I manually deleted the whole tree of this old shelly device, rebooted my shelly, and a new tree (this time as gen2) was created, solving this issue for me...

[Dette70]

Bei mit läuft die aktuelle Adapter-Version 7.0 seit nun seit Wochen fehlerfrei mit den Pro Geräten. Habe immer nur bei Neustart des Adapters einige reconnects, danach nicht mehr.

[mirkoengert]

Mit der Adapter-Version 7.0 habe ich das gleiche Problem, keine Besserung damit. Die bisherigen Shelly Firmware-Updates brachten keine Besserung. Heute alle Shellys auf Firmware 1.4.0 upgedatet - gleicher Mist in grün.... nach kurzer Zeit sind zig Fehler im Protokoll.

Ich hatte schonmal Probleme, weil die Shellys sich an Accespoints angemeldet haben im WLAN, die über einen Switch betrieben wurden. Damals (alles nur Gen 1 keine Gen2 Geräte) hatte ich dann auf einen managed Switch gewechselt, dann war es gut. Hatte dann mal die Accespoints testweise vom Switch genommen und direkt an den Router angeschlossen. Neben den Fehlermeldungen wurde das ganze System dadurch auch noch ewig lahm. Also die Accespoints wieder über den maneged Switch...

Was ich jetzt versucht habe, dass ich meine 32 Shelly Gen2 auf zwei Instanzen im iobroker aufzuteilen. Das sah direkt wesentlich besser aus. Zwischenzeitlich hatte ich schon wider den ein oder andere Fehler, allerdings immer nur bei Geräten der ursprünglichen Instanz. Werde das mal weiter beobachten und ggf. die Geräte zwischen den Instanzen "verschieben". Klar ist, dass dann ggf. die Scripte auf falsche Datenpunkte verweisen, wenn man diese direkt im Script verwendet hat.

[mirkoengert]

Also bis jetzt (ca. 11 Stunden) hab ich genau 12 mal die Fehlermeldung. Sie kommt immer wieder von den gleichen Shellys. Is auch ganz egal, welche Instanz. Ich denk, ich werd mal einen oder zwei in den Werkszustand resetten und neu befruchten. Ich berichte.

[mirkoengert]

Update: Es ist für mich pffensichtlich, dass das Problem weder beim ioBroker, noch beim Shelly Adapter und auch nicht beim Shelly selbst liegt. Die Shellys, welche die Fehlermeldung auslösen, sind definitiv für die Zeit x (reicht von Sekunden bis hin zu Minuten) vom WLAN getrennt. Somit suche ich jetzt im WLAN nach Einstellungen. Habe ein Netgear Orbi WLAN Mesh System. Hier habe ich jetzt folgende Einstellungen vorgenommen:

1. 20/40 MHz-Koexistenz deaktiviert
2. AX deaktiviert
3. Sendeleistung WLAN auf 50 % reduziert (habe neben dem Orbi Router noch 2 Orbi Satelliten als Accesspoints am Start - pro Stockwerk. Sendeleisteung völlig ausreichend mit 50%)

Mit diesen Einstellungen konnte ich mehrfach den ioBroker bzw. den Shelly Adapter neustarten ohne Fehlermeldung. Auch bekam ich jetzt innerhalb von 5 Stunden keine einzige Fehlermeldung.

[FreunderNacht]

@mirkoengert Es kann sein, daß es was mit den WLAN Einstellungen / Empfang zu tun hat. Ich hab jetzt auch mal geschaut, ich habe einen der sehr schlechten Empfang hat und dieser ist es auch der sich immer meldet.

[crunchip77]

habe heute einen defekten shelly 2.5 durch einen plus2pm ersetzt und hatte ebenfalls kontinuierlich(alle2-3 Minuten) diese Probleme `

2024-08-03 17:06:25.926 - error: shelly.0 (6507) [MQTT] Wrong MQTT authentification of client "shellyplus2pm-cc7b5c8946e0" -- 2024-08-03 17:06:25.956 - info: device-watcher.0 (306) Das folgende Gerät ist wieder verfügbar: Shelly: Rollo Wohnzimmer (16:51) 2024-08-03 17:07:38.777 - error: shelly.0 (6507) [MQTT] Error in function setMqttPrefixHttp (Gen 1) for (undefined / undefined / undefined): TypeError: Cannot read properties of undefined (reading 'replace') 2024-08-03 17:07:38.777 - error: shelly.0 (6507) [MQTT] Unable to get mqttprefix of client with id "shellyplus2pm-cc7b5c8946e0"

`

nach langem hin und her probieren, hält er nun seinen online Status/Verbindung seit rund 2 Std

• Adapter Abfragezeit auf 60 sec gestellt
• die shelly IP im unifi Netzwerk fixiert

Adapterversion 7.0.0 Firmware 20240726-114505/1.4.0-gb2aeadb Shelly SNSW-102P16EU

[mirkoengert]

Ich hab schon an allen meiner Shelly 2.5 (8 Stk.) einen defekten Kondensator getauscht. Es ist immer das gleiche Fehlerbild - keine WLAN Verbindung mehr... Da hatt Shelly leider eine schlechte Charge dieser Kondensatoren erwischt.

Das MQTT Fehlerproblem ist mittlerweile auch gelöst. Ich habe alle ioBroker Scripte deaktiviert. Die Steuerung der Shellys bewerkstellige ich jetzt mit direkten HTTP Befehlen bzw. mit Szenen über die Shelly Cloud.

Ich konnte irgendwann mal nachvollziehen, dass die Fehlermeldungen auflaufen, wenn ich Shellys über Scripte gesteuert habe. Da muss es ein Problem geben, wenn Datenpunkte per MQTT gesetzt werden. Kann ja dann eigentlich nur ein Fehler im Shelly Adapter sein.

[ETGermany]

10 ShellyPlusPlug im Netz mit FW 1.2.0 und 1.2.3 gemischt. Immer wieder die gleichen 7 davon (FW auch gemischt) bringen diesen Fehler:

Von den 7 habe ich nun mal den kompletten Objektbaum gelöscht, werde mich mal überraschen lassen, was die nächsten Tage bringen. Seit ein paar Tagen sind noch 3 weitere ShellyPlusPlug mit FW 1.4.0 dazu gekommen. die waren bisher auch noch nicht betroffen.

Werde mich in einigen Tagen wieder zu Wort melden.

[jenbenn]

Ich habe das selbe Problem, die Fehlermeldungen sind genau dieselben, der Pi bleibt über Stunden auf einer cpu-Last von 90-120% wodurch nichts mehr läuft und auch keine Skritpte mehr ausgeführt werden. Die Shelly gehen in willkürlicher Reihenfolge immer wieder einer nach dem anderen offline (client close, unable to get mqtt prefix) und kommen dann wieder online. Das ganze dauert manchmal 2 Stunden , manchmal 8 Stunden, bis alle Shellys permanent online und im Objektbaum alle grün sind und auch grün bleiben. Ind er Zwischenzeit wird dann das Protokoll mit Millionen von "Client CLose", "unable to get mqtt prefix" und "Client connected" Nachrichten zugemüllt.

Das Problem tritt immer auf nach einem der folgenden Ereignisse:

• Neustart des Iobrokers/Raspberyy Pi
• Firmwareupdate eines oder mehrerer shellys
• Integration eines neuen Shellys in iobroker
• Update des Shelly adapters

Das Problem tritt seltsamerweise aber nicht auf , wenn endlich alle Shelly nach Stunden permanent grün (online) sind und man dann (nur) den Shelly-Adpater pausiert und neu startet.

Das Problem betrifft nur den Iobroker, alle shellys sind jederzeit kontinuierlich und problemlos über die Shelly app ansprechbar.

Ich habe alles probiert, den Objkettbaum gelöscht, testweise einen andern Switch im Netzwerk installiert, den Adapter neu gestartet, was man so macht. Nichts hilft. Ich bin jetzt mittlerweile soweit, dass ich probeweise mal auf home Assistent wechseln werde.

[jenbenn]

Villeicht hilft das:

ICh habe jetzt mal den Shelly adapter ausgeschaltet und meine shellys stattdessen über den generellen mqtt Adapter eingebunden (umgestellt auf Port 1882). Dabei kommt es auch zu einen Vielzahl von Protokollemeldungen, die aber Infos und keine Error messages sind. Viel wichtiger: Diese Meldungen belasten die CPU offensichtlich nicht, die Auslastung bleibt zwischen 15 und 25% und das System bleibt responsiv. Ob die Shelly sich vernünftig ansteuern lassen muss ich noch testen. Hier das Protokoll aus dem mqtt Adapter:

2048

Log herunterladen

Log-Größe: 71.2 MB

Quelle | Zeit | debug |   -- | -- | -- | -- mqtt.0 | 2024-08-19 12:02:15.105 | info | Client [shellyplus2pm-80646fdc2a00] Received puback for unknown message ID: 1 mqtt.0 | 2024-08-19 12:02:08.260 | info | Client [shellyplusplugs-e465b8432078] publishOnSubscribe mqtt.0 | 2024-08-19 12:02:08.255 | info | Client [shellyplusplugs-e465b8432078] publishOnSubscribe mqtt.0 | 2024-08-19 12:02:08.252 | info | Client [shellyplusplugs-e465b8432078] publishOnSubscribe mqtt.0 | 2024-08-19 12:02:08.243 | info | Client [shellyplusplugs-e465b8432078] publishOnSubscribe mqtt.0 | 2024-08-19 12:02:08.224 | info | Client [shellyplusplugs-e465b8432078] publishOnSubscribe mqtt.0 | 2024-08-19 12:02:08.059 | info | Client [shellyplusplugs-e465b8432078] subscribes on "mqtt.0.shellyplusplugs-e465b8432078.command.switch:0" mqtt.0 | 2024-08-19 12:02:08.055 | info | Client [shellyplusplugs-e465b8432078] subscribes on "mqtt.0.shellies.command" mqtt.0 | 2024-08-19 12:02:08.051 | info | Client [shellyplusplugs-e465b8432078] subscribes on "mqtt.0.shellyplusplugs-e465b8432078.command" mqtt.0 | 2024-08-19 12:02:08.042 | info | Client [shellyplusplugs-e465b8432078] subscribes on "mqtt.0.shellyplusplugs-e465b8432078.command.sys" mqtt.0 | 2024-08-19 12:02:08.023 | info | Client [shellyplusplugs-e465b8432078] subscribes on "mqtt.0.shellyplusplugs-e465b8432078.rpc" mqtt.0 | 2024-08-19 12:02:07.993 | info | Client [shellyplusplugs-e465b8432078] connected with secret 1724061727992_8328 mqtt.0 | 2024-08-19 12:02:05.904 | info | Client [shellyplusplugs-e465b8432078] connection closed: closed mqtt.0 | 2024-08-19 12:02:05.109 | info | Client [shellyplus2pm-80646fdc2a00] Received puback for unknown message ID: 1 mqtt.0 | 2024-08-19 12:02:00.117 | info | Client [shellyplus2pm-80646fdc2a00] Received puback for unknown message ID: 1 mqtt.0 | 2024-08-19 12:02:00.048 | info | Client [shellyplusplugs-e465b8432078] Received puback for unknown message ID: 1 mqtt.0 | 2024-08-19 12:01:41.153 | info | Client [shellyplusplugs-e465b8432078] publishOnSubscribe mqtt.0 | 2024-08-19 12:01:41.149 | info | Client [shellyplusplugs-e465b8432078] publishOnSubscribe mqtt.0 | 2024-08-19 12:01:41.146 | info | Client [shellyplusplugs-e465b8432078] publishOnSubscribe mqtt.0 | 2024-08-19 12:01:41.137 | info | Client [shellyplusplugs-e465b8432078] publishOnSubscribe mqtt.0 | 2024-08-19 12:01:41.115 | info | Client [shellyplusplugs-e465b8432078] publishOnSubscribe mqtt.0 | 2024-08-19 12:01:40.953 | info | Client [shellyplusplugs-e465b8432078] subscribes on "mqtt.0.shellyplusplugs-e465b8432078.command.switch:0" mqtt.0 | 2024-08-19 12:01:40.949 | info | Client [shellyplusplugs-e465b8432078] subscribes on "mqtt.0.shellies.command" mqtt.0 | 2024-08-19 12:01:40.945 | info | Client [shellyplusplugs-e465b8432078] subscribes on "mqtt.0.shellyplusplugs-e465b8432078.command" mqtt.0 | 2024-08-19 12:01:40.936 | info | Client [shellyplusplugs-e465b8432078] subscribes on "mqtt.0.shellyplusplugs-e465b8432078.command.sys" mqtt.0 | 2024-08-19 12:01:40.915 | info | Client [shellyplusplugs-e465b8432078] subscribes on "mqtt.0.shellyplusplugs-e465b8432078.rpc" mqtt.0 | 2024-08-19 12:01:40.885 | info | Client [shellyplusplugs-e465b8432078] connected with secret 1724061700884_805 mqtt.0 | 2024-08-19 12:01:38.694 | info | Client [shellyplusplugs-e465b8432078] connection closed: closed mqtt.0 | 2024-08-19 12:01:28.679 | info | Client [shellyplusplugs-e465b8432078] Received puback for unknown message ID: 1 mqtt.0 | 2024-08-19 12:01:18.678 | info | Client [shellyplusplugs-e465b8432078] Received puback for unknown message ID: 1 mqtt.0 | 2024-08-19 12:01:10.395 | info | Client [shellyplus2pm-80646fdc2a00] publishOnSubscribe mqtt.0 | 2024-08-19 12:01:10.390 | info | Client [shellyplus2pm-80646fdc2a00] publishOnSubscribe mqtt.0 | 2024-08-19 12:01:10.384 | info | Client [shellyplus2pm-80646fdc2a00] publishOnSubscribe mqtt.0 | 2024-08-19 12:01:10.368 | info | Client [shellyplus2pm-80646fdc2a00] publishOnSubscribe mqtt.0 | 2024-08-19 12:01:10.334 | info | Client [shellyplus2pm-80646fdc2a00] publishOnSubscribe host.iobroker | 2024-08-19 12:01:10.311 | info | instance system.adapter.daswetter.0 having pid 16128 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) mqtt.0 | 2024-08-19 12:01:10.194 | info | Client [shellyplus2pm-80646fdc2a00] subscribes on "mqtt.0.shellyplus2pm-80646fdc2a00.command.cover:0" mqtt.0 | 2024-08-19 12:01:10.190 | info | Client [shellyplus2pm-80646fdc2a00] subscribes on "mqtt.0.shellies.command" mqtt.0 | 2024-08-19 12:01:10.184 | info | Client [shellyplus2pm-80646fdc2a00] subscribes on "mqtt.0.shellyplus2pm-80646fdc2a00.command" mqtt.0 | 2024-08-19 12:01:10.167 | info | Client [shellyplus2pm-80646fdc2a00] subscribes on "mqtt.0.shellyplus2pm-80646fdc2a00.command.sys" mqtt.0 | 2024-08-19 12:01:10.132 | info | Client [shellyplus2pm-80646fdc2a00] subscribes on "mqtt.0.shellyplus2pm-80646fdc2a00.rpc" mqtt.0 | 2024-08-19 12:01:10.101 | info | Client [shellyplus2pm-80646fdc2a00] connected with secret 1724061670100_4119 daswetter.0 | 2024-08-19 12:01:09.748 | info | Terminated (ADAPTER_REQUESTED_TERMINATION): All data handled, adapter stopped until next scheduled moment mqtt.0 | 2024-08-19 12:01:08.678 | info | Client [shellyplusplugs-e465b8432078] Received puback for unknown message ID: 1 mqtt.0 | 2024-08-19 12:01:07.950 | info | Client [shellyplus2pm-80646fdc2a00] connection closed: closed daswetter.0 | 2024-08-19 12:01:02.153 | info | still wrong data structure from server received! repaired... mqtt.0 | 2024-08-19 12:01:00.096 | info | Client [shellyplus2pm-80646fdc2a00] Received puback for unknown message ID: 1 mqtt.0 | 2024-08-19 12:01:00.037 | info | Client [shellyplusplugs-e465b8432078] Received puback for unknown message ID: 1 daswetter.0 | 2024-08-19 12:00:38.908 | info | starting. Version 3.1.15 in /opt/iobroker/node_modules/iobroker.daswetter, node: v18.19.0, js-controller: 6.0.9 mqtt.0 | 2024-08-19 12:00:38.220 | info | Client [shellyplus2pm-80646fdc2a00] publishOnSubscribe mqtt.0 | 2024-08-19 12:00:38.207 | info | Client [shellyplus2pm-80646fdc2a00] publishOnSubscribe mqtt.0 | 2024-08-19 12:00:38.196 | info | Client [shellyplus2pm-80646fdc2a00] publishOnSubscribe mqtt.0 | 2024-08-19 12:00:38.191 | info | Client [shellyplus2pm-80646fdc2a00] publishOnSubscribe mqtt.0 | 2024-08-19 12:00:38.159 | info | Client [shellyplus2pm-80646fdc2a00] publishOnSubscribe mqtt.0 | 2024-08-19 12:00:38.018 | info | Client [shellyplus2pm-80646fdc2a00] subscribes on "mqtt.0.shellyplus2pm-80646fdc2a00.command.cover:0" mqtt.0 | 2024-08-19 12:00:38.007 | info | Client [shellyplus2pm-80646fdc2a00] subscribes on "mqtt.0.shellies.command" mqtt.0 | 2024-08-19 12:00:37.996 | info | Client [shellyplus2pm-80646fdc2a00] subscribes on "mqtt.0.shellyplus2pm-80646fdc2a00.command" mqtt.0 | 2024-08-19 12:00:37.990 | info | Client [shellyplus2pm-80646fdc2a00] subscribes on "mqtt.0.shellyplus2pm-80646fdc2a00.command.sys" mqtt.0 | 2024-08-19 12:00:37.958 | info | Client [shellyplus2pm-80646fdc2a00] subscribes on "mqtt.0.shellyplus2pm-80646fdc2a00.rpc" mqtt.0 | 2024-08-19 12:00:37.925 | info | Client [shellyplus2pm-80646fdc2a00] connected with secret 1724061637924_4829 mqtt.0 | 2024-08-19 12:00:35.875 | info | Client [shellyplus2pm-80646fdc2a00] connection closed: closed host.iobroker | 2024-08-19 12:00:35.043 | info | instance system.adapter.daswetter.0 in version "3.1.15" started with pid 16128 mqtt.0 | 2024-08-19 12:00:28.945 | info | Client [shellyplusplugs-e465b8432078] publishOnSubscribe mqtt.0 | 2024-08-19 12:00:28.940 | info | Client [shellyplusplugs-e465b8432078] publishOnSubscribe mqtt.0 | 2024-08-19 12:00:28.937 | info | Client [shellyplusplugs-e465b8432078] publishOnSubscribe mqtt.0 | 2024-08-19 12:00:28.928 | info | Client [shellyplusplugs-e465b8432078] publishOnSubscribe mqtt.0 | 2024-08-19 12:00:28.907 | info | Client [shellyplusplugs-e465b8432078] publishOnSubscribe mqtt.0 | 2024-08-19 12:00:28.744 | info | Client [shellyplusplugs-e465b8432078] subscribes on "mqtt.0.shellyplusplugs-e465b8432078.command.switch:0" mqtt.0 | 2024-08-19 12:00:28.740 | info | Client [shellyplusplugs-e465b8432078] subscribes on "mqtt.0.shellies.command" mqtt.0 | 2024-08-19 12:00:28.736 | info | Client [shellyplusplugs-e465b8432078] subscribes on "mqtt.0.shellyplusplugs-e465b8432078.command" mqtt.0 | 2024-08-19 12:00:28.727 | info | Client [shellyplusplugs-e465b8432078] subscribes on "mqtt.0.shellyplusplugs-e465b8432078.command.sys" mqtt.0 | 2024-08-19 12:00:28.706 | info | Client [shellyplusplugs-e465b8432078] subscribes on "mqtt.0.shellyplusplugs-e465b8432078.rpc" mqtt.0 | 2024-08-19 12:00:28.674 | info | Client [shellyplusplugs-e465b8432078] connected with secret 1724061628673_849 mqtt.0 | 2024-08-19 12:00:26.536 | info | Client [shellyplusplugs-e465b8432078] connection closed: closed mqtt.0 | 2024-08-19 12:00:25.853 | info | Client [shellyplus2pm-80646fdc2a00] Received puback for unknown message ID: 1 fusionsolar.0 | 2024-08-19 12:00:25.643 | error | API returned failCode #407 (access frequency is too high) - giving up now :-( mqtt.0 | 2024-08-19 12:00:16.519 | info | Client [shellyplusplugs-e465b8432078] Received puback for unknown message ID: 1 fusionsolar.0 | 2024-08-19 12:00:15.907 | error | Cannot read properties of null (reading '0') mqtt.0 | 2024-08-19 12:00:15.846 | info | Client [shellyplus2pm-80646fdc2a00] Received puback for unknown message ID: 1 host.iobroker | 2024-08-19 12:00:15.096 | info | instance system.adapter.ical.0 having pid 16080 terminated with code 0 (NO_ERROR) ical.0 | 2024-08-19 12:00:14.514 | info | Terminated (NO_ERROR): Without reason host.iobroker | 2024-08-19 12:00:13.109 | info | instance system.adapter.dwd.0 having pid 16100 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) dwd.0 | 2024-08-19 12:00:12.570 | info | Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason dwd.0 | 2024-08-19 12:00:10.774 | info | starting. Version 2.8.5 in /opt/iobroker/node_modules/iobroker.dwd, node: v18.19.0, js-controller: 6.0.9 smartgarden.0 | 2024-08-19 12:00:09.875 | info | starting. Version 2.0.1 in /opt/iobroker/node_modules/iobroker.smartgarden, node: v18.19.0, js-controller: 6.0.9 mqtt.0 | 2024-08-19 12:00:06.523 | info | Client [shellyplusplugs-e465b8432078] Received puback for unknown message ID: 1 ical.0 | 2024-08-19 12:00:06.119 | info | starting. Version 1.15.0 in /opt/iobroker/node_modules/iobroker.ical, node: v18.19.0, js-controller: 6.0.9 mqtt.0 | 2024-08-19 12:00:05.846 | info | Client [shellyplus2pm-80646fdc2a00] Received puback for unknown message ID: 1

>

[crunchip77]

@jenbenn lösch mal deine privaten ical Daten aus dem Log

[jenbenn]

Villeicht hilft das:

ICh habe jetzt mal den Shelly adapter ausgeschaltet und meine shellys stattdessen über den generellen mqtt Adapter eingebunden (umgestellt auf Port 1882). Dabei kommt es auch zu einen Vielzahl von Protokollemeldungen, die aber Infos und keine Error messages sind. Viel wichtiger: Diese Meldungen belasten die CPU offensichtlich nicht, die Auslastung bleibt zwischen 15 und 25% und das System bleibt responsiv. Ob die Shelly sich vernünftig ansteuern lassen muss ich noch testen. Hier das Protokoll aus dem mqtt Adapter:

2048 Log herunterladen Log-Größe: 71.2 MB

Quelle | Zeit | debug |   -- | -- | -- | -- mqtt.0 | 2024-08-19 12:02:15.105 | info | Client [shellyplus2pm-80646fdc2a00] Received puback for unknown message ID: 1 mqtt.0 | 2024-08-19 12:02:08.260 | info | Client [shellyplusplugs-e465b8432078] publishOnSubscribe mqtt.0 | 2024-08-19 12:02:08.255 | info | Client [shellyplusplugs-e465b8432078] publishOnSubscribe mqtt.0 | 2024-08-19 12:02:08.252 | info | Client [shellyplusplugs-e465b8432078] publishOnSubscribe mqtt.0 | 2024-08-19 12:02:08.243 | info | Client [shellyplusplugs-e465b8432078] publishOnSubscribe mqtt.0 | 2024-08-19 12:02:08.224 | info | Client [shellyplusplugs-e465b8432078] publishOnSubscribe mqtt.0 | 2024-08-19 12:02:08.059 | info | Client [shellyplusplugs-e465b8432078] subscribes on "mqtt.0.shellyplusplugs-e465b8432078.command.switch:0" mqtt.0 | 2024-08-19 12:02:08.055 | info | Client [shellyplusplugs-e465b8432078] subscribes on "mqtt.0.shellies.command" mqtt.0 | 2024-08-19 12:02:08.051 | info | Client [shellyplusplugs-e465b8432078] subscribes on "mqtt.0.shellyplusplugs-e465b8432078.command" mqtt.0 | 2024-08-19 12:02:08.042 | info | Client [shellyplusplugs-e465b8432078] subscribes on "mqtt.0.shellyplusplugs-e465b8432078.command.sys" mqtt.0 | 2024-08-19 12:02:08.023 | info | Client [shellyplusplugs-e465b8432078] subscribes on "mqtt.0.shellyplusplugs-e465b8432078.rpc" mqtt.0 | 2024-08-19 12:02:07.993 | info | Client [shellyplusplugs-e465b8432078] connected with secret 1724061727992_8328 mqtt.0 | 2024-08-19 12:02:05.904 | info | Client [shellyplusplugs-e465b8432078] connection closed: closed mqtt.0 | 2024-08-19 12:02:05.109 | info | Client [shellyplus2pm-80646fdc2a00] Received puback for unknown message ID: 1 mqtt.0 | 2024-08-19 12:02:00.117 | info | Client [shellyplus2pm-80646fdc2a00] Received puback for unknown message ID: 1 mqtt.0 | 2024-08-19 12:02:00.048 | info | Client [shellyplusplugs-e465b8432078] Received puback for unknown message ID: 1 mqtt.0 | 2024-08-19 12:01:41.153 | info | Client [shellyplusplugs-e465b8432078] publishOnSubscribe mqtt.0 | 2024-08-19 12:01:41.149 | info | Client [shellyplusplugs-e465b8432078] publishOnSubscribe mqtt.0 | 2024-08-19 12:01:41.146 | info | Client [shellyplusplugs-e465b8432078] publishOnSubscribe mqtt.0 | 2024-08-19 12:01:41.137 | info | Client [shellyplusplugs-e465b8432078] publishOnSubscribe mqtt.0 | 2024-08-19 12:01:41.115 | info | Client [shellyplusplugs-e465b8432078] publishOnSubscribe mqtt.0 | 2024-08-19 12:01:40.953 | info | Client [shellyplusplugs-e465b8432078] subscribes on "mqtt.0.shellyplusplugs-e465b8432078.command.switch:0" mqtt.0 | 2024-08-19 12:01:40.949 | info | Client [shellyplusplugs-e465b8432078] subscribes on "mqtt.0.shellies.command" mqtt.0 | 2024-08-19 12:01:40.945 | info | Client [shellyplusplugs-e465b8432078] subscribes on "mqtt.0.shellyplusplugs-e465b8432078.command" mqtt.0 | 2024-08-19 12:01:40.936 | info | Client [shellyplusplugs-e465b8432078] subscribes on "mqtt.0.shellyplusplugs-e465b8432078.command.sys" mqtt.0 | 2024-08-19 12:01:40.915 | info | Client [shellyplusplugs-e465b8432078] subscribes on "mqtt.0.shellyplusplugs-e465b8432078.rpc" mqtt.0 | 2024-08-19 12:01:40.885 | info | Client [shellyplusplugs-e465b8432078] connected with secret 1724061700884_805 mqtt.0 | 2024-08-19 12:01:38.694 | info | Client [shellyplusplugs-e465b8432078] connection closed: closed mqtt.0 | 2024-08-19 12:01:28.679 | info | Client [shellyplusplugs-e465b8432078] Received puback for unknown message ID: 1 mqtt.0 | 2024-08-19 12:01:18.678 | info | Client [shellyplusplugs-e465b8432078] Received puback for unknown message ID: 1 mqtt.0 | 2024-08-19 12:01:10.395 | info | Client [shellyplus2pm-80646fdc2a00] publishOnSubscribe mqtt.0 | 2024-08-19 12:01:10.390 | info | Client [shellyplus2pm-80646fdc2a00] publishOnSubscribe mqtt.0 | 2024-08-19 12:01:10.384 | info | Client [shellyplus2pm-80646fdc2a00] publishOnSubscribe mqtt.0 | 2024-08-19 12:01:10.368 | info | Client [shellyplus2pm-80646fdc2a00] publishOnSubscribe mqtt.0 | 2024-08-19 12:01:10.334 | info | Client [shellyplus2pm-80646fdc2a00] publishOnSubscribe host.iobroker | 2024-08-19 12:01:10.311 | info | instance system.adapter.daswetter.0 having pid 16128 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) mqtt.0 | 2024-08-19 12:01:10.194 | info | Client [shellyplus2pm-80646fdc2a00] subscribes on "mqtt.0.shellyplus2pm-80646fdc2a00.command.cover:0" mqtt.0 | 2024-08-19 12:01:10.190 | info | Client [shellyplus2pm-80646fdc2a00] subscribes on "mqtt.0.shellies.command" mqtt.0 | 2024-08-19 12:01:10.184 | info | Client [shellyplus2pm-80646fdc2a00] subscribes on "mqtt.0.shellyplus2pm-80646fdc2a00.command" mqtt.0 | 2024-08-19 12:01:10.167 | info | Client [shellyplus2pm-80646fdc2a00] subscribes on "mqtt.0.shellyplus2pm-80646fdc2a00.command.sys" mqtt.0 | 2024-08-19 12:01:10.132 | info | Client [shellyplus2pm-80646fdc2a00] subscribes on "mqtt.0.shellyplus2pm-80646fdc2a00.rpc" mqtt.0 | 2024-08-19 12:01:10.101 | info | Client [shellyplus2pm-80646fdc2a00] connected with secret 1724061670100_4119 daswetter.0 | 2024-08-19 12:01:09.748 | info | Terminated (ADAPTER_REQUESTED_TERMINATION): All data handled, adapter stopped until next scheduled moment mqtt.0 | 2024-08-19 12:01:08.678 | info | Client [shellyplusplugs-e465b8432078] Received puback for unknown message ID: 1 mqtt.0 | 2024-08-19 12:01:07.950 | info | Client [shellyplus2pm-80646fdc2a00] connection closed: closed daswetter.0 | 2024-08-19 12:01:02.153 | info | still wrong data structure from server received! repaired... mqtt.0 | 2024-08-19 12:01:00.096 | info | Client [shellyplus2pm-80646fdc2a00] Received puback for unknown message ID: 1 mqtt.0 | 2024-08-19 12:01:00.037 | info | Client [shellyplusplugs-e465b8432078] Received puback for unknown message ID: 1 daswetter.0 | 2024-08-19 12:00:38.908 | info | starting. Version 3.1.15 in /opt/iobroker/node_modules/iobroker.daswetter, node: v18.19.0, js-controller: 6.0.9 mqtt.0 | 2024-08-19 12:00:38.220 | info | Client [shellyplus2pm-80646fdc2a00] publishOnSubscribe mqtt.0 | 2024-08-19 12:00:38.207 | info | Client [shellyplus2pm-80646fdc2a00] publishOnSubscribe mqtt.0 | 2024-08-19 12:00:38.196 | info | Client [shellyplus2pm-80646fdc2a00] publishOnSubscribe mqtt.0 | 2024-08-19 12:00:38.191 | info | Client [shellyplus2pm-80646fdc2a00] publishOnSubscribe mqtt.0 | 2024-08-19 12:00:38.159 | info | Client [shellyplus2pm-80646fdc2a00] publishOnSubscribe mqtt.0 | 2024-08-19 12:00:38.018 | info | Client [shellyplus2pm-80646fdc2a00] subscribes on "mqtt.0.shellyplus2pm-80646fdc2a00.command.cover:0" mqtt.0 | 2024-08-19 12:00:38.007 | info | Client [shellyplus2pm-80646fdc2a00] subscribes on "mqtt.0.shellies.command" mqtt.0 | 2024-08-19 12:00:37.996 | info | Client [shellyplus2pm-80646fdc2a00] subscribes on "mqtt.0.shellyplus2pm-80646fdc2a00.command" mqtt.0 | 2024-08-19 12:00:37.990 | info | Client [shellyplus2pm-80646fdc2a00] subscribes on "mqtt.0.shellyplus2pm-80646fdc2a00.command.sys" mqtt.0 | 2024-08-19 12:00:37.958 | info | Client [shellyplus2pm-80646fdc2a00] subscribes on "mqtt.0.shellyplus2pm-80646fdc2a00.rpc" mqtt.0 | 2024-08-19 12:00:37.925 | info | Client [shellyplus2pm-80646fdc2a00] connected with secret 1724061637924_4829 mqtt.0 | 2024-08-19 12:00:35.875 | info | Client [shellyplus2pm-80646fdc2a00] connection closed: closed host.iobroker | 2024-08-19 12:00:35.043 | info | instance system.adapter.daswetter.0 in version "3.1.15" started with pid 16128 mqtt.0 | 2024-08-19 12:00:28.945 | info | Client [shellyplusplugs-e465b8432078] publishOnSubscribe mqtt.0 | 2024-08-19 12:00:28.940 | info | Client [shellyplusplugs-e465b8432078] publishOnSubscribe mqtt.0 | 2024-08-19 12:00:28.937 | info | Client [shellyplusplugs-e465b8432078] publishOnSubscribe mqtt.0 | 2024-08-19 12:00:28.928 | info | Client [shellyplusplugs-e465b8432078] publishOnSubscribe mqtt.0 | 2024-08-19 12:00:28.907 | info | Client [shellyplusplugs-e465b8432078] publishOnSubscribe mqtt.0 | 2024-08-19 12:00:28.744 | info | Client [shellyplusplugs-e465b8432078] subscribes on "mqtt.0.shellyplusplugs-e465b8432078.command.switch:0" mqtt.0 | 2024-08-19 12:00:28.740 | info | Client [shellyplusplugs-e465b8432078] subscribes on "mqtt.0.shellies.command" mqtt.0 | 2024-08-19 12:00:28.736 | info | Client [shellyplusplugs-e465b8432078] subscribes on "mqtt.0.shellyplusplugs-e465b8432078.command" mqtt.0 | 2024-08-19 12:00:28.727 | info | Client [shellyplusplugs-e465b8432078] subscribes on "mqtt.0.shellyplusplugs-e465b8432078.command.sys" mqtt.0 | 2024-08-19 12:00:28.706 | info | Client [shellyplusplugs-e465b8432078] subscribes on "mqtt.0.shellyplusplugs-e465b8432078.rpc" mqtt.0 | 2024-08-19 12:00:28.674 | info | Client [shellyplusplugs-e465b8432078] connected with secret 1724061628673_849 mqtt.0 | 2024-08-19 12:00:26.536 | info | Client [shellyplusplugs-e465b8432078] connection closed: closed mqtt.0 | 2024-08-19 12:00:25.853 | info | Client [shellyplus2pm-80646fdc2a00] Received puback for unknown message ID: 1 fusionsolar.0 | 2024-08-19 12:00:25.643 | error | API returned failCode #407 (access frequency is too high) - giving up now :-( mqtt.0 | 2024-08-19 12:00:16.519 | info | Client [shellyplusplugs-e465b8432078] Received puback for unknown message ID: 1 fusionsolar.0 | 2024-08-19 12:00:15.907 | error | Cannot read properties of null (reading '0') mqtt.0 | 2024-08-19 12:00:15.846 | info | Client [shellyplus2pm-80646fdc2a00] Received puback for unknown message ID: 1 host.iobroker | 2024-08-19 12:00:15.096 | info | instance system.adapter.ical.0 having pid 16080 terminated with code 0 (NO_ERROR) ical.0 | 2024-08-19 12:00:14.514 | info | Terminated (NO_ERROR): Without reason host.iobroker | 2024-08-19 12:00:13.109 | info | instance system.adapter.dwd.0 having pid 16100 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) dwd.0 | 2024-08-19 12:00:12.570 | info | Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason dwd.0 | 2024-08-19 12:00:10.774 | info | starting. Version 2.8.5 in /opt/iobroker/node_modules/iobroker.dwd, node: v18.19.0, js-controller: 6.0.9 smartgarden.0 | 2024-08-19 12:00:09.875 | info | starting. Version 2.0.1 in /opt/iobroker/node_modules/iobroker.smartgarden, node: v18.19.0, js-controller: Received puback for unknown message ID: 1 ical.0 | 2024-08-19 12:00:06.119 | info | starting. Version 1.15.0 in /opt/iobroker/node_modules/iobroker.ical, node: v18.19.0, js-controller: 6.0.9 mqtt.0 | 2024-08-19 12:00:05.846 | info | Client [shellyplus2pm-80646fdc2a00] Received puback for unknown message ID: 1

Ok macht am Ende leider doch keinen Unterschied. Nach ca. 15 min geht die CPU Auslastung auch im mqtt Adapter auf 120% hoch und alles blockiert...

[ETGermany]

@jenbenn, so wie es bei dir aussieht, würde ich behaupten, dass in deinem Netzwerk etwas nicht stimmt. Bei meinen Shellies kommt das nur sporadisch vor, auch mal 2,3 oder 4 Tage gar nicht. Seit meinem Eintrag vor 2 Tagen ist noch alles okay.

Übrigens von Raspberry bin ich schon lange weg und auf günstige, leistungsstärkere Mini-PC umgestiegen, als OS nur Ubuntu-Server drauf, läuft alles sehr gemütlich ab:

[jenbenn]

@jenbenn, so wie es bei dir aussieht, würde ich behaupten, dass in deinem Netzwerk etwas nicht stimmt. Bei meinen Shellies kommt das nur sporadisch vor, auch mal 2,3 oder 4 Tage gar nicht. Seit meinem Eintrag vor 2 Tagen ist noch alles okay.

Übrigens von Raspberry bin ich schon lange weg und auf günstige, leistungsstärkere Mini-PC umgestiegen, als OS nur Ubuntu-Server drauf, läuft alles sehr gemütlich ab:

Danke für die Antwort. Hättest DU einen Tipp was der Fehler im Netzwerk sein könnte? Ich habe eine Fritzbox 7590 die an einem 16 port Switch hängt (probiert habe ich alternativ einen unmanaged Netgear Switch und managed TPLink Switch , macht aber keinen Unterschied). An dem Switch hängen per LAN-Kabel drei Fritz Repeater, die als Access points konfiguriert sind und mit der Fritzbox im Mesh arbeiten. Die Shelly vebinden sich mit meinem Wlan über die Access points , ich habe in der Fritzbox feste Ip Adressen zugewiesen. An Einstellungen in der Fritzbox habe ich schon ziemlich viel probiert, das hat aber alles nichts geändert...

[ETGermany]

Hättest DU einen Tipp was der Fehler im Netzwerk sein könnte? Ich habe eine Fritzbox 7590

Ja, einen Tipp hätte ich, Es gibt bei einigen dieser FB 7590 Probleme mit dem 2,4 GHz - Netz, welches ja für die Shellies notwendig ist:

https://www.computerbild.de/artikel/cb-News-DSL-WLAN-Defekt-FritzBox-Probleme-38508675.html

Möglich, dass sich dieses Problem gerade bei deiner FB manifestiert. AVM tauscht solche Geräte aus:

https://www.golem.de/news/wlan-router-ausfall-des-2-4-ghz-wlan-bei-fritzbox-7590-2405-185377.html

Wenn die Shellies allerdings mit den Repeatern verbunden sind, hat die FB keine Schuld. Solltest dir mal die Logs der FB und Repeater anschauen, ob sich die Shellies hier viel ab- und anmelden:

[jenbenn]

Hättest DU einen Tipp was der Fehler im Netzwerk sein könnte? Ich habe eine Fritzbox 7590

Ja, einen Tipp hätte ich, Es gibt bei einigen dieser FB 7590 Probleme mit dem 2,4 GHz - Netz, welches ja für die Shellies notwendig ist:

https://www.computerbild.de/artikel/cb-News-DSL-WLAN-Defekt-FritzBox-Probleme-38508675.html

Möglich, dass sich dieses Problem gerade bei deiner FB manifestiert. AVM tauscht solche Geräte aus:

https://www.golem.de/news/wlan-router-ausfall-des-2-4-ghz-wlan-bei-fritzbox-7590-2405-185377.html

Wenn die Shellies allerdings mit den Repeatern verbunden sind, hat die FB keine Schuld. Solltest dir mal die Logs der FB und Repeater anschauen, ob sich die Shellies hier viel ab- und anmelden:

Danke, die WLAN Verbindung scheint stabil. Der Fritzbox log zeigt keine EInträge der Shellys bezgl An- und Abmeldung. Auch sind ja alle Shellys permanenten übe die App und Shelly Cloud steuer-und ansprechbar. Nur eben nicht über den den iobroker, der die mqtt Verbindung nicht hält bzw. laufend beendet.

[Dette70]

Nur nochmal als keiner Hinweis/Reminder. Vor Monaten gab es hier einen Hinweis, die Abfragezeit im Adapter auf 120 sek zu erhöhen (das betrifft nur die Abfrage des iobrokers, nicht die Meldung der Shelly's). Das hat zumindest bei mir damals geholfen. Danach kamen die Fehler nur einmalig beim Start des Adapters, danach waren sie weg. Vieleicht geht damit auch die Last runter...

[jenbenn]

Nur nochmal als keiner Hinweis/Reminder. Vor Monaten gab es hier einen Hinweis, die Abfragezeit im Adapter auf 120 sek zu erhöhen (das betrifft nur die Abfrage des iobrokers, nicht die Meldung der Shelly's). Das hat zumindest bei mir damals geholfen. Danach kamen die Fehler nur einmalig beim Start des Adapters, danach waren sie weg. Vieleicht geht damit auch die Last runter...

Danke. Habe ich alles versucht. Habe die Abfragezeit probeweise mal auf 5, 60, 120 und 600 Sekunden gesetzt. Das hat alles keinen Unterschied gemacht.

[jenbenn]

Kann jemand etwas hierzu sagen: [https://www.smarthome-forum.eu/blog/entry/61-shelly-und-iobroker-mqtt-problem/] Angeblich gibt es Probleme weil der Shelly Adpater MQTT5 nur teilweise unterstützt, was gerade bei größeren Installationen Probleme bereiten soll. Das wäre insofern logisch, als dass meine Probleme auch erst aufgetreten sind nachdem ich mehr und mehr shelly geräte installiert habe ( den genauen Punkt, ab wann es Probleme gab,mkann ich nicht mehr nachvollziehen)

[ETGermany]

Kann jemand etwas hierzu sagen: [https://www.smarthome-forum.eu/blog/entry/61-shelly-und-iobroker-mqtt-problem/]

Hier geht's um den MQTT-Adapter, ohne wirkliche Problembeschreibung, nur dass die Daten wohl nicht ankommen. Dürfte mit deinem Problem nichts zu tun haben, bei dir geht ja auch Shelly-Adapter (MQTT) nicht. Ich sage immer noch, dein Raspberry-System ist überlastet, wenn Router und Repeater in Ordnung sind und du schon alles Vorgeschlagene ausprobiert hast. Bei uns sind ein System mit 70 Shellies, davon 20 via Shelly-MQTT das andere System mit 45 Shellies, davon 22 via Shelly-MQTT. Beim ersten keine Probleme mit der von mir vor 4 Tagen mitgeteilten Fehlermeldung, beim 2. System seit 4 Tagen keine Fehlermeldung mehr. Und dann kommen bei beiden System noch eine Menge anderer Geräte dazu. Mein Vorschlag wie schon mal geschrieben, einen Mini-PC aufbauen. Wir haben N51, hier ein bedeutend stärkerer N95 für 145 EUR:

[](url)

[crunchip77]

Oder einfach mal den WLAN Kanal ändern, kann sein das dieser überlastet ist.

[jenbenn]

Oder einfach mal den WLAN Kanal ändern, kann sein das dieser überlastet ist.

Habe ich versucht (Kanal 6 manuell festgelegt) , bringt aber leider auch nichts. DIe Statistik der Fritz Box zeigt dass alle 2,4 MhZ Kanäle zu keinem Zeitpunkt des Tages zu mehr als 30% belastet sind, auch nicht durch Nachbarnetzwerke.

[jenbenn]

Kann jemand etwas hierzu sagen: [https://www.smarthome-forum.eu/blog/entry/61-shelly-und-iobroker-mqtt-problem/]

Hier geht's um den MQTT-Adapter, ohne wirkliche Problembeschreibung, nur dass die Daten wohl nicht ankommen. Dürfte mit deinem Problem nichts zu tun haben, bei dir geht ja auch Shelly-Adapter (MQTT) nicht. Ich sage immer noch, dein Raspberry-System ist überlastet, wenn Router und Repeater in Ordnung sind und du schon alles Vorgeschlagene ausprobiert hast. Bei uns sind ein System mit 70 Shellies, davon 20 via Shelly-MQTT das andere System mit 45 Shellies, davon 22 via Shelly-MQTT. Beim ersten keine Probleme mit der von mir vor 4 Tagen mitgeteilten Fehlermeldung, beim 2. System seit 4 Tagen keine Fehlermeldung mehr. Und dann kommen bei beiden System noch eine Menge anderer Geräte dazu. Mein Vorschlag wie schon mal geschrieben, einen Mini-PC aufbauen. Wir haben N51, hier ein bedeutend stärkerer N95 für 145 EUR:

Danke, wie hast Du diesem PC den IObroker aufgesetzt? Hast DU den Windows Installer benutzt? Wenn ja, kann man unter dem vorinstallierten Windows 10/11 konfigurieren, dass der PC als Server arbeitet und per LAn auf ihn zugreifen? Oder hast Du Windows runtergeschmissen und ein Linux installiert? Danke!

[Dette70]

Danke, wie hast Du diesem PC den IObroker aufgesetzt? Hast DU den Windows Installer benutzt? Wenn ja, kann man unter dem vorinstallierten Windows 10/11 konfigurieren, dass der PC als Server arbeitet und per LAn auf ihn zugreifen? Oder hast Du Windows runtergeschmissen und ein Linux installiert? Danke!

Wenn ich Dir was empfehlen darf, nimm so einen Mini PC (z.B. Intel NUC, mit mindestens 16 GB RAM) und installiere Dir Proxmox oder eine andere virtuelle Umgebung. Dort dann iobroker auf einem ubuntu oder debian linux. Dann hast Du gleich noch genug Kapazität für weitere virtuelle Server und vor allen Dingen hast Du die perfekte Sicherung, wenn mal was kaputt geht.

[ETGermany]

Danke, wie hast Du diesem PC den IObroker aufgesetzt?

Also, machs richtig, nichts virtuelles, alles Schwachstellen. Link zum günstigen PC hatte ich schon geschickt, da reichen die 8 GB Memory bei weitem aus. Ubuntu-Server installieren, gesamte Festplatte nutzen lassen - Download:

https://ubuntu.com/download/server

Wenn das fertig ist, ioBroker installieren: sudo -s apt update apt upgrade apt-get install curl curl -sLf https://deb.nodesource.com/setup_20.x | bash - apt-get install -y nodejs curl -sLf https://iobroker.net/install.sh | bash -

Internet ist voll mit Anleitungen, auch für InfluxDB und Grafana.

[mcm1957]

Sorry Leute

Aber hier ist KEIN Diskussionsforum. Setup eines PC, Diskussionen ob virtuell oder nativ haben nichts mit dem Problem hier zu tun. Wechselt damit ins Forum.

Ich behalte mir vor OffTopic Inhalt hier auszublenden.