Skip to content
New issue

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

Sign up for GitHub

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

Already on GitHub? Sign in to your account

Jump to bottom

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

Open
3 tasks done
dike1982 opened this issue Jan 14, 2024 · 144 comments
Open
3 tasks done

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

dike1982 opened this issue Jan 14, 2024 · 144 comments
Assignees
@klein0r

Comments

@dike1982
Copy link

dike1982 commented Jan 14, 2024 •
edited by mcm1957
Loading

I'm sure that

  • This issue is still present in the current beta version of this adapter
  • There is no other (open) issue with the same topic (use the search!)
  • 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 GitHub Actions
Copy link

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
Copy link
Author

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
Copy link
Author

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
Copy link
Contributor

klein0r commented Jan 15, 2024

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

@dike1982
Copy link
Author

Ah ha und wie löse ich das nun?

@dike1982
Copy link
Author

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
Copy link
Contributor

klein0r commented Jan 16, 2024

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
Copy link

andiweli commented Mar 8, 2024 •
edited
Loading

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
Copy link

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
Copy link

thurbo commented Apr 6, 2024

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
Copy link
Contributor

klein0r commented Apr 29, 2024

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.

This was referenced Apr 29, 2024
Closed
Closed
Closed
@diamand2k22
Copy link

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
Copy link

Dette70 commented May 2, 2024

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
Copy link

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
Copy link

ReinWei56 commented May 3, 2024 •
edited
Loading

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

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
Copy link

Tom54497 commented May 3, 2024 •
edited by klein0r
Loading

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
Copy link

diamand2k22 commented May 3, 2024 •
edited by klein0r
Loading

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
Copy link
Contributor

klein0r commented May 3, 2024

den devicewatcher Adapter deaktivieren beim starten des Shelly Adapters

Bitte mal den technischen Hintergrund erklären

@Tom54497
Copy link

Tom54497 commented May 3, 2024 •
edited by klein0r
Loading

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
Copy link

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
Copy link

Dette70 commented May 10, 2024

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
Copy link

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

@Dette70
Copy link

Dette70 commented May 10, 2024 •
edited
Loading

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
Copy link
Contributor

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
Copy link

Dette70 commented Jul 23, 2024

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
Copy link

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.

@diamand2k22

This comment has been minimized.

Sign in to view
@uwe72

This comment has been minimized.

Sign in to view
@schutzgeist-mf

This comment has been minimized.

Sign in to view
@sansonifabio

This comment has been minimized.

Sign in to view
@uwe72

This comment has been minimized.

Sign in to view
@schutzgeist-mf

This comment has been minimized.

Sign in to view
@diamand2k22

This comment has been minimized.

Sign in to view
@uwe72

This comment has been minimized.

Sign in to view
@klein0r
Copy link
Contributor

klein0r commented Jan 26, 2025

Leute ihr generiert mir hier einen Haufen Notifications, nur um zu sagen dass ihr nicht wisst wo das Problem im Code zu finden ist. So weit war ich auch schon. Ich brauche handfeste Gründe - gerne einen PR. Weitere Kommentare, dass "jemand das Problem auch hat" oder "auch nicht weiß, woran es liegt" bringt hier ja niemanden weiter.

@schutzgeist-mf
Copy link

schutzgeist-mf commented Jan 26, 2025 •
edited
Loading

Leute ihr generiert mir hier einen Haufen Notifications, nur um zu sagen dass ihr nicht wisst wo das Problem im Code zu finden ist. So weit war ich auch schon. Ich brauche handfeste Gründe - gerne einen PR. Weitere Kommentare, dass "jemand das Problem auch hat" oder "auch nicht weiß, woran es liegt" bringt hier ja niemanden weiter.

Versteh ich jetzt nicht, sind solche threats nicht dazu da, zu versuchen nochmal genauer die aktuellen Situationen zu vergleichen und hier ggfs. Gemeinsamkeiten zu finden die uns (oder dir) der Lösung irgendwie helfen könnte.
Und ja auch klar , wollte ich mitteilen dass das Problem trotz neuerer Adapter und Iobroker / Js Versionen noch existiert.

Wie können wir dir noch helfen ? Gerne können wir eine Remote Session auf meiner Umgebung machen und debuggen. iobroker ist bei mir vitualisiert , wir können dadurch immer wieder auf verschiedene snapshots zurück springen
Oder ein direktes wireguard vpn mit zurgiff auf meinen Debian Server :-) ?

@klein0r
Copy link
Contributor

klein0r commented Jan 26, 2025

@schutzgeist-mf Das heißt, wenn Du mit dem dev-server eine neue Instanz des Shelly-Adapter startest und dann genau ein Gerät der Plus- oder Pro-Serie hinzufügst, kannst Du das Problem reproduzieren? Das wäre tatsächlich interessant. Teile gerne mal ein komplettes Debug-Log, die Firmware-Version des Shellies, Details zu Deiner Netzwerkumgebung usw.

@schutzgeist-mf
Copy link

@klein0r das bringe ich dir asap

Nur zur Bestätigung. Du möchtest das ich eine weitere Shelly Instanz erstelle und hier ein Gerät der (ich nenne sie mal) Gen 2 reinnehmen. Nach aktuell verhalten bekomme ich dann immer sofort den Fehler und nen Adapter Absturz.

Gerne bereite den alles anschließen vor und melde mich asap

@klein0r
Copy link
Contributor

klein0r commented Jan 26, 2025

@schutzgeist-mf Nein - am besten eine Installation mit dem dev-server. Also Shelly Repo klonen, dev-server setup, ... und dann mit VSCode z.B. das Projekt öffnen um live darin zu arbeiten. Also nicht in einem Produktivsystem. Wie soll man da debuggen?

z.B. https://www.youtube.com/watch?v=A9UETXyAmL4
Mittlerweile mache ich das in Proxmox: https://www.youtube.com/watch?v=Glx4kd3eX70

@schutzgeist-mf
Copy link

schutzgeist-mf commented Jan 29, 2025 •
edited
Loading

Ich habe für mich wohl endlich das Problem gefunden, vielleicht hilft das dem einen oder anderen:

Mein Iobroker Server steht in der DMZ, ich habe bis dahin immer gedacht das die Shelly mit dem MQTT Protokoll die Verbindung zum IOBroker initieren. Bei genauerer prüfen sehe ich aber das auch der IoBroker Server (also der Adapter) neue Verbindungen zu den Shellys aufbaut und das auf Port 80.

Nachdem ich die Firewall geöffnet habe das Verbindungen mit diesen Ports auch in die andere Richtung eröffnet werden darf, gibt es auch keine MQTTprefiy of client error meldung, und der Adapter bleibt stabil.

192.168.30.58 ist der Shelly
192.168.255.13 ist der Server

DMZ | tcp | 192.168.255.13:38624 -> 192.168.30.58:80 | FIN_WAIT_2:FIN_WAIT_2 | 4 / 2 | 180 B / 84 B

DMZ | tcp | 192.168.255.13:49586 -> 192.168.30.58:80 | FIN_WAIT_2:FIN_WAIT_2 | 4 / 2 | 180 B / 84 B

@sansonifabio
Copy link

sansonifabio commented Jan 30, 2025 •
edited
Loading

@klein0r guten morgen eine vieleicht dumme Frage.

Kann der Fehler daher kommen das man diese Shellys auch als Blutooth Gateweway nutzen kann und deshalb die Fehler auflaufen?

Herzliche Grüße
Fabio

Image

Image

@klein0r
Copy link
Contributor

klein0r commented Jan 30, 2025

Nachdem ich die Firewall geöffnet habe das Verbindungen mit diesen Ports auch in die andere Richtung eröffnet werden darf

Genau, der MQTT Prefix wird nämlich per HTTP geholt (das würde ich gern in Zukunft alles rauswerfen). Und wenn das abgelehnt wird, gibt es eine Fehlermeldung. Aber das wird wohl nicht jeder hier so eingeschränkt haben?!

@olli-r
Copy link

olli-r commented Jan 30, 2025

Bei mir hängt es nicht an verschiedenen Subnetzen, ich habe mal tcpdump laufen lassen:

tcpdump.txt

Ich hatte den Adapter neu gestartet und ab dann aufgezeichnet. Man sieht gut, dass ca. alle 61 Sekunden eine Abfrage vom Server zum Shelly erfolgt. Dann irgendwann ist die Abfrage nach bereits 50 Sekunden und der Shelly gibt ein 401 zurück. Der Adapter versucht's nochmal und dann klappt die Authentifizierung.

-> Warum ist die Abfrage im Fehlerfall immer 10 Sekunden früher als bei denen, wo die Authentifizierung funktioniert?
-> Wieso schlägt diese fehl?

Ich kann mal mit Wireshark da ran, werde ich aber erst die Tage zu kommen. Wäre interessant zu wissen, ob der Adapter eventuell falsche Credentials übermittelt oder ob's am Shelly liegt.

@klein0r
Copy link
Contributor

klein0r commented Jan 30, 2025

Wäre interessant zu wissen, ob der Adapter eventuell falsche Credentials übermittelt oder ob's am Shelly liegt.

Es gibt eine Situation, wo die Verbindung vom Shelly abgelehnt wird, wenn genau in dem Moment die Uhrzeit via NTP aktualisiert wird. Aber ob es da einen Zusammenhang gibt? Diese MQTT-Prefix-Geschichte passiert ja eigentlich nur 1x, wenn sich ein Shelly verbindet.

@FreunderNacht
Copy link

Wäre interessant zu wissen, ob der Adapter eventuell falsche Credentials übermittelt oder ob's am Shelly liegt.

Es gibt eine Situation, wo die Verbindung vom Shelly abgelehnt wird, wenn genau in dem Moment die Uhrzeit via NTP aktualisiert wird. Aber ob es da einen Zusammenhang gibt? Diese MQTT-Prefix-Geschichte passiert ja eigentlich nur 1x, wenn sich ein Shelly verbindet.

Hi Mathias,
kann es sein, das die MQTT-Prefix-Geschichte auch passiert, wenn sich der Shelly, aufgrund des AP-Romings, zu einem anderen AP Verbindet?

Ich hatte bei mir noch nie viele Fehler, aber bei einem PM-mini (Waschmaschine) sehr oft aber auch nur wenn die Waschmaschine an war und Strom verbraucht hat.

Seit dem ich das AP-Roming im PM-mini auf -90 und das Intervall auf 600 Sekunden gestellt habe, hab ich eigentlich Ruhe.

Könnte es sein, das wenn der Shelly viel zu tun hat (wie bei mir, wenn die Waschmaschine läuft) und denn z.B. noch ein AP-Roming dazu kommt in dem Moment etwas überlastet ist und die Anfrage beim ersten mal verwirft?

Ich weiß, ist reine Spekulation.

@klein0r
Copy link
Contributor

klein0r commented Jan 30, 2025

@FreunderNacht Könnte schon sein. Jedenfalls wäre ein Wechsel des AP ggf. mit einer neuen Verbindung gegen den MQTT-Broker verbunden. Damit würde dann der MQTT-Prefix ebenfalls wieder geholt und das ganze "Onboarding" durchlaufen.

Die Frage bleibt aber dennoch, warum das dann nicht funktioniert (bzw. was genau den Fehler auslöst).

@olli-r
Copy link

olli-r commented Jan 30, 2025

Es gibt eine Situation, wo die Verbindung vom Shelly abgelehnt wird, wenn genau in dem Moment die Uhrzeit via NTP aktualisiert wird. Aber ob es da einen Zusammenhang gibt? Diese MQTT-Prefix-Geschichte passiert ja eigentlich nur 1x, wenn sich ein Shelly verbindet.

Naja, aber dann würde HTTP 401 Unauthorized keinen Sinn machen...

@FreunderNacht
Copy link

@klein0r
Bei dem PM-mini könnte ich mir das vielleicht noch erklären, das zu viel abzuarbeiten hat und die Anfrage nicht rechtzeitig verarbeitet wird (passiert ja nur, zumindest in nennenswerter Häufigkeit, wenn die Waschmaschine läuft und er ständige Daten abschicken musss) aber ob das bei den anderen auch so ist weiß mich nicht.

Ehrlich gesagt bin ich selbst nicht so überzeugt von der Theorie.
Ich wollte sie nur mal erwähnt haben, weil bei mir fast nur Meldungen nach Adapter-Start (auch nicht von allen Gen2 Geräten) und bei dem PM-mini wenn die Waschmaschine läuft und er arbeiten muss gekommen sind.

@olli-r
Könnte es sein, das die Anfrage/Autorisierung nicht richtig verarbeitet werden konnte und damit als falsch eingestuft wurde?

Sind alles leider nur Theorien 😫😫😫

@diamand2k22
Copy link

Wie kommt dann der Zusammenhang mit der CPU Last zu Stande? Wenn ich einen Restart des Shelly Adapters aus dem System heraus mache , dann dauert es gefühlt Stunden, bis der Mqtt Prefix Fehler verschwindet. Sobald ich alle Adapter beende und nur den Shelly Adapter starte, kommt dieser Fehler beim Start erst gar nicht 🤔🤯

@splizz1st
Copy link

Wie kommt dann der Zusammenhang mit der CPU Last zu Stande? Wenn ich einen Restart des Shelly Adapters aus dem System heraus mache , dann dauert es gefühlt Stunden, bis der Mqtt Prefix Fehler verschwindet. Sobald ich alle Adapter beende und nur den Shelly Adapter starte, kommt dieser Fehler beim Start erst gar nicht 🤔🤯

Exakt das gleiche Verhalten bei mir. Ein Iobroker Neustart ist auch ein großes Problem. Teils komme ich nur über die Konsole auf den Iobroker und muss da den Shelly Adapter stoppen.

Ich habe die Shelly’s in einem subnetz als den Iobroker. Es gibt aber keine Firewall-Regeln die eine Verbindung behindert.

@FreunderNacht
Copy link

FreunderNacht commented Jan 30, 2025 •
edited
Loading

Bei mir ist alles (noch) im gleichen Netz, sowohl der IOBroker als auch die Shellys.
Ich habe sehr wenig Probleme (nur einige wenige kurz nach Adapter Start).

Kann hier noch jemand bestätigen oder widerlegen das es vielleicht daran liege könnte oder zumindest die größere Probleme macht, wenn IOBroker und Shelly in unterschiedlichen netzen sind?

@ETGermany
Copy link

Also für mich steht fest, dass das Problem bei schlechter WLAN-Verbindung auftreten kann, nicht zwangsweise muss. Ein Shelly hatte sich gestern (warum auch immer) in einen entfernten Repeater eingewählt RSSI: -90 dBm (No Signal), konnte allerdings noch auf den Shelly per Web-IF zugreifen, wenn auch mühselig.
Wi-Fi Roaming -80 dBm hatte den Shelly wohl nicht auf einen anderen Repeater umschalten lassen, bzw. warum hat der überhaupt gewechselt, das konnte ich nicht verifizieren. Hatte dann auf -60 dBm umgestellt, dann wurde auch wieder schnell auf einen anderen Repeater umgeschaltet mit RSSI: -44 dBm.
Laut FB-Ereignisse hatte sich der Shelly von 14:51 Uhr bis 20:00 Uhr 20 mal ab- und angemeldet, davon aber nur 5 Mal die Fehlermeldung im ioBroker gebracht; dies innerhalb von nur 15 Minuten gegen Ende der 6 Stunden.
Die Frage ist dann immer noch, weshalb die Fehlermeldung mit (Gen 1) kommt.
Ansonsten keine Problem mit meinen vielen Shellies - wie bereits früher schon geschrieben.

Image

@Rudi-Ment
Copy link

Hi.
Ich habe mir jetzt sehr viele Threats und vermeintliche Lösungen zu diesem Thema durchgelesen.
Einiges habe ich ausprobiert und die Meldungen gingen einfach nicht weg. Wurden auch nicht weniger.

Ich habe jetzt FÜR MICH folgende Lösung, die jetzt bereits ein paar Tage ohne Probleme läuft:

Ich habe eine Fritzbox 7590, einen Repeater 2400 über LAN und einen Repeater 1700 über WLAN angebunden.
Für beide Repeater habe ich das MESH deaktiviert. Beide Repeater strahlen jetzt eine andere SSID aus. Somit habe ich quasi drei unterscheidliche WLAN-SSIDs im Haus, aber die Adressvergabe ist immer noch über die Fritzbox im selben Adressraum.

Die Shellys habe ich neu zugeordnet und ihnen der SSID zugeteilt, die am nächsten dran ist.
Also Rolläden Esszimmer am Repeater im Esszimmer usw.

Aktuell keine Probleme mehr.

@FreunderNacht
Copy link

@Rudi-Ment
Auch keine Meldungen beim Neustart des Adapters?

@Rudi-Ment
Copy link

Wenn der Adapter einmal komplett gestartet ist, sind die Meldungen weg.
Anfangs kommen mal ein paar Meldungen.
So ein oder zwei Minuten vielleicht.

@FreunderNacht
Copy link

@Rudi-Ment
Genauso bei mir auch, ich habe allerdings nur das AP Roaming geändert (Rssi auf - 90 / Zeit auf 600 Sekunden).
Seit dem ist es eigentlich so wie du beschrieben hast, nach Adapter-Start kommen noch ein paar Meldungen und dann kommt eigentlich nichts mehr.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@klein0r klein0r

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests