Weiter zum Inhalt
  • Home
  • Aktuell
  • Tags
  • 0 Ungelesen 0
  • Kategorien
  • Unreplied
  • Beliebt
  • GitHub
  • Docu
  • Hilfe
Skins
  • Hell
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dunkel
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Standard: (Kein Skin)
  • Kein Skin
Einklappen
ioBroker Logo

Community Forum

donate donate
  1. ioBroker Community Home
  2. Deutsch
  3. ioBroker Allgemein
  4. Synology NAS hängt sich auf

NEWS

  • Monatsrückblick Januar/Februar 2026 ist online!
    BluefoxB
    Bluefox
    18
    1
    784

  • Jahresrückblick 2025 – unser neuer Blogbeitrag ist online! ✨
    BluefoxB
    Bluefox
    18
    1
    6.2k

  • Neuer Blogbeitrag: Monatsrückblick - Dezember 2025 🎄
    BluefoxB
    Bluefox
    13
    1
    1.5k

Synology NAS hängt sich auf

Geplant Angeheftet Gesperrt Verschoben ioBroker Allgemein
21 Beiträge 6 Kommentatoren 2.1k Aufrufe 5 Beobachtet
  • Älteste zuerst
  • Neuste zuerst
  • Meiste Stimmen
Antworten
  • In einem neuen Thema antworten
Anmelden zum Antworten
Dieses Thema wurde gelöscht. Nur Nutzer mit entsprechenden Rechten können es sehen.
  • V vo5tr0

    @arteck
    Ich hab meine Antwort jetzt bearbeitet. Es liegt definitiv nicht an den Scripten. Habe alle abgeschaltet, aber gerade eben hatte ich wieder das selbe Problem. Die Auslastung ging hoch auf 100%, ich habe sofort den Container abgeschaltet. Das ging auch noch. Kurz gewartet, wieder eingeschaltet und weg war mein NAS. Jetzt ist es wieder nicht mehr erreichbar und muss vom Strom getrennt werden

    Bildschirmfoto 2022-05-10 um 23.42.04.png

    andreA Offline
    andreA Offline
    andre
    Developer
    schrieb am zuletzt editiert von andre
    #5

    @vo5tr0 Kannst du einen Prozess innerhalb des Containers identifizieren der die CPU Last verursacht?

    30477494-fffc-420b-95c6-718fd76646f6-image.png

    [EDIT] Leider gibt das die Oberfläche der DS nicht her, aber unter Docker kann man grundsätzlich auch die Ressourcen (RAM, CPU) limitieren. Das könnte ggf. erstmal helfen, dass deine DS nicht immer abkackt... Dann hätte man ggf. ne bessere Chance zu analysieren was in dem Container los ist...

    MfG,
    André

    Bitte keine Support-Fragen per PN! Nutzt die öffentliche Kanäle damit auch andere von den Antworten profitieren können!

    1 Antwort Letzte Antwort
    0
    • Jey CeeJ Online
      Jey CeeJ Online
      Jey Cee
      Developer
      schrieb am zuletzt editiert von
      #6

      Das die NAS sich aufhängt hat schon mal nichts mit ioBroker zu tun. Die DS sollte den Container Hardware Resourcen mässig Limitieren und da scheint nicht zu passieren. Hier könnte Andre sein Tipp helfen.

      Das die CPU Last des Containers plötzlich auf 100% springt könnte an der Boost Funktion der CPU liegen. Der Taktet normal mit 1.5Ghz und Boostet bis 2.3Ghz. Der Plötzliche Sprung entsteht vielleicht durch das runter Takten der CPU. Wahrscheinlich gibt es da noch einen zweiten Faktor der im selben Augenblick present ist.
      Möglich das die CPU auch nicht mehr schnell genug hoch Taktet, evtl. wegen zu hoher Temperarur.

      Wenn es möglich ist Überwach mal die CPU Frequenz und die CPU Temperatur.

      Persönlicher Support
      Spenden -> paypal.me/J3YC33

      V 1 Antwort Letzte Antwort
      0
      • apollon77A apollon77

        Welches dsm? 6 oder 7?

        Irgendwas hilfreiches im Iobroker log? Fangen wir doch mal mit spolchen Grundfragen an ;-))

        V Offline
        V Offline
        vo5tr0
        schrieb am zuletzt editiert von
        #7

        @apollon77

        DSM 7 :)

        Gegen 23:04 habe ich die hohe Auslastung bemerkt und den Container abgeschaltet. Dann um 23:05 Uhr wieder gestartet. Die Auslastung ging sofort hoch auf 100%, laut Docker log kam der erneute Shutdown Befehl noch an und der Container wurde auch gegen 23:07 Uhr erfolgreich gestoppt. Zu dem Zeitpunkt war mein NAS aber schon nicht mehr erreichbar.

        Ich packe hier einfach Mal die letzen Zeilen aus dem IO Broker Log rein, aber etwas auffälliges konnte ich nicht sehen

        2022-05-10 21:03:05.739  - info: web.0 (288) ==> Connected system.user.admin from ::ffff:192.168.178.140
        2022-05-10 21:03:05.741  - info: web.0 (288) ==> Connected system.user.admin from ::ffff:192.168.178.140
        2022-05-10 21:05:48.309  - info: web.0 (288) <== Disconnect system.user.admin from ::ffff:192.168.178.140 flot
        2022-05-10 21:05:48.310  - info: web.0 (288) <== Disconnect system.user.admin from ::ffff:192.168.178.140 flot
        2022-05-10 21:09:03.658  - info: web.0 (288) ==> Connected system.user.admin from ::ffff:192.168.178.140
        2022-05-10 21:09:03.658  - info: web.0 (288) ==> Connected system.user.admin from ::ffff:192.168.178.140
        2022-05-10 21:11:46.345  - info: web.0 (288) <== Disconnect system.user.admin from ::ffff:192.168.178.140 flot
        2022-05-10 21:11:46.347  - info: web.0 (288) <== Disconnect system.user.admin from ::ffff:192.168.178.140 flot
        2022-05-10 21:15:01.192  - info: web.0 (288) ==> Connected system.user.admin from ::ffff:192.168.178.140
        2022-05-10 21:15:01.193  - info: web.0 (288) ==> Connected system.user.admin from ::ffff:192.168.178.140
        2022-05-10 21:50:02.503  - info: web.0 (288) <== Disconnect system.user.admin from ::ffff:192.168.178.140 flot
        2022-05-10 21:50:02.510  - info: web.0 (288) <== Disconnect system.user.admin from ::ffff:192.168.178.140 flot
        2022-05-10 21:50:03.731  - info: web.0 (288) ==> Connected system.user.admin from ::ffff:192.168.178.140
        2022-05-10 21:50:04.769  - info: web.0 (288) ==> Connected system.user.admin from ::ffff:192.168.178.140
        2022-05-10 21:50:09.188  - info: web.0 (288) <== Disconnect system.user.admin from ::ffff:192.168.178.140 flot
        2022-05-10 21:50:09.196  - info: web.0 (288) ==> Connected system.user.admin from ::ffff:192.168.178.140
        2022-05-10 21:50:09.197  - info: web.0 (288) ==> Connected system.user.admin from ::ffff:192.168.178.140
        2022-05-10 21:50:09.198  - info: web.0 (288) <== Disconnect system.user.admin from ::ffff:192.168.178.140 flot
        2022-05-10 21:50:10.772  - info: web.0 (288) ==> Connected system.user.admin from ::ffff:192.168.178.140
        2022-05-10 21:50:10.773  - info: web.0 (288) ==> Connected system.user.admin from ::ffff:192.168.178.140
        2022-05-10 21:50:12.015  - info: web.0 (288) <== Disconnect system.user.admin from ::ffff:192.168.178.140 flot
        2022-05-10 21:50:12.019  - info: web.0 (288) <== Disconnect system.user.admin from ::ffff:192.168.178.140 flot
        2022-05-10 21:50:13.784  - info: web.0 (288) ==> Connected system.user.admin from ::ffff:192.168.178.140
        2022-05-10 21:50:13.785  - info: web.0 (288) ==> Connected system.user.admin from ::ffff:192.168.178.140
        2022-05-10 21:50:15.448  - info: web.0 (288) <== Disconnect system.user.admin from ::ffff:192.168.178.140 flot
        2022-05-10 21:50:15.450  - info: web.0 (288) <== Disconnect system.user.admin from ::ffff:192.168.178.140 flot
        2022-05-10 21:50:16.868  - info: web.0 (288) ==> Connected system.user.admin from ::ffff:192.168.178.140
        2022-05-10 21:50:16.872  - info: web.0 (288) ==> Connected system.user.admin from ::ffff:192.168.178.140
        2022-05-10 21:50:26.644  - info: web.0 (288) <== Disconnect system.user.admin from ::ffff:192.168.178.140 flot
        2022-05-10 21:50:26.647  - info: web.0 (288) <== Disconnect system.user.admin from ::ffff:192.168.178.140 flot
        2022-05-10 21:50:28.368  - info: web.0 (288) ==> Connected system.user.admin from ::ffff:192.168.178.140
        2022-05-10 21:50:28.377  - info: web.0 (288) ==> Connected system.user.admin from ::ffff:192.168.178.140
        2022-05-10 21:52:39.194  - info: web.0 (288) <== Disconnect system.user.admin from ::ffff:192.168.178.140 
        2022-05-10 21:52:39.195  - info: web.0 (288) <== Disconnect system.user.admin from ::ffff:192.168.178.140 
        2022-05-10 21:53:04.085  - info: web.0 (288) <== Disconnect system.user.admin from ::ffff:192.168.178.140 flot
        2022-05-10 21:53:04.087  - info: web.0 (288) <== Disconnect system.user.admin from ::ffff:192.168.178.140 flot
        2022-05-10 21:53:05.616  - info: web.0 (288) ==> Connected system.user.admin from ::ffff:192.168.178.140
        2022-05-10 21:53:06.204  - info: web.0 (288) ==> Connected system.user.admin from ::ffff:192.168.178.140
        2022-05-10 22:04:32.893  - info: web.0 (288) <== Disconnect system.user.admin from ::ffff:192.168.178.140 flot
        2022-05-10 22:04:32.906  - info: web.0 (288) <== Disconnect system.user.admin from ::ffff:192.168.178.140 flot
        2022-05-10 22:04:34.158  - info: web.0 (288) ==> Connected system.user.admin from ::ffff:192.168.178.140
        2022-05-10 22:04:35.461  - info: web.0 (288) ==> Connected system.user.admin from ::ffff:192.168.178.140
        2022-05-10 22:09:39.343  - info: web.0 (288) <== Disconnect system.user.admin from ::ffff:192.168.178.140 flot
        2022-05-10 22:09:39.383  - info: web.0 (288) <== Disconnect system.user.admin from ::ffff:192.168.178.140 flot
        2022-05-10 22:55:52.184  - info: web.0 (288) ==> Connected system.user.admin from ::ffff:192.168.180.89
        2022-05-10 22:55:53.090  - info: web.0 (288) ==> Connected system.user.admin from ::ffff:192.168.180.89
        2022-05-10 23:02:56.657  - info: web.0 (288) <== Disconnect system.user.admin from ::ffff:192.168.180.89 flot
        2022-05-10 23:02:57.923  - info: web.0 (288) ==> Connected system.user.admin from ::ffff:192.168.180.89
        2022-05-10 23:03:49.937  - info: web.0 (288) <== Disconnect system.user.admin from ::ffff:192.168.180.89 flot
        2022-05-10 23:03:52.694  - info: web.0 (288) ==> Connected system.user.admin from ::ffff:192.168.180.89
        2022-05-10 23:05:39.173  - info: host.buanet-iobroker1 iobroker.js-controller version 4.0.15 js-controller starting
        2022-05-10 23:05:39.179  - info: host.buanet-iobroker1 Copyright (c) 2014-2022 bluefox, 2014 hobbyquaker
        2022-05-10 23:05:39.180  - info: host.buanet-iobroker1 hostname: buanet-iobroker1, node: v14.19.1
        2022-05-10 23:05:39.180  - info: host.buanet-iobroker1 ip addresses: 192.168.178.3 172.19.0.1 fe80::42:96ff:fea4:97df 172.17.0.1 fe80::42:22ff:fe70:b7e2 fe80::8cac:dbff:feee:8378 fe80::acd6:77ff:fe61:b496 fe80::b0e0:ff:fe97:da1d fe80::4420:c7ff:fed8:83
        2022-05-10 23:05:41.665  - info: host.buanet-iobroker1 connected to Objects and States
        2022-05-10 23:05:41.704  - info: host.buanet-iobroker1 added notifications configuration of host
        2022-05-10 23:05:42.305  - info: host.buanet-iobroker1 27 instances found
        2022-05-10 23:05:42.372  - info: host.buanet-iobroker1 starting 18 instances
        2022-05-10 23:05:42.757  - info: host.buanet-iobroker1 instance system.adapter.admin.0 started with pid 126
        2022-05-10 23:05:45.009  - info: admin.0 (126) starting. Version 5.3.1 in /opt/iobroker/node_modules/iobroker.admin, node: v14.19.1, js-controller: 4.0.15
        2022-05-10 23:05:45.063  - info: admin.0 (126) requesting all states
        2022-05-10 23:05:45.064  - info: admin.0 (126) requesting all objects
        2022-05-10 23:05:46.202  - info: admin.0 (126) received all objects
        2022-05-10 23:05:46.710  - info: host.buanet-iobroker1 instance system.adapter.javascript.0 started with pid 141
        2022-05-10 23:05:47.619  - info: admin.0 (126) Request actual repository...
        2022-05-10 23:05:47.641  - info: admin.0 (126) http server listening on port 8081
        2022-05-10 23:05:47.642  - info: admin.0 (126) Use link "http://localhost:8081" to configure.
        2022-05-10 23:05:48.020  - info: host.buanet-iobroker1 Updating repository "stable" under "http://download.iobroker.net/sources-dist.json"
        2022-05-10 23:05:50.531  - info: host.buanet-iobroker1 instance system.adapter.history.0 started with pid 152
        2022-05-10 23:05:50.596  - info: admin.0 (126) Repository received successfully.
        2022-05-10 23:05:51.267  - info: javascript.0 (141) starting. Version 5.2.21 in /opt/iobroker/node_modules/iobroker.javascript, node: v14.19.1, js-controller: 4.0.15
        2022-05-10 23:05:51.516  - info: javascript.0 (141) requesting all states
        2022-05-10 23:05:51.518  - info: javascript.0 (141) requesting all objects
        2022-05-10 23:05:52.827  - info: javascript.0 (141) received all objects
        2022-05-10 23:05:52.956  - info: javascript.0 (141) received all states
        2022-05-10 23:05:53.312  - error: admin.0 (126) error
        2022-05-10 23:05:53.484  - info: history.0 (152) starting. Version 1.10.5 in /opt/iobroker/node_modules/iobroker.history, node: v14.19.1, js-controller: 4.0.15
        2022-05-10 23:05:53.601  - info: history.0 (152) enabled logging of sonoff.0.Smartmeter.Power_Total_in (Count=1), Alias=false
        2022-05-10 23:05:53.603  - info: history.0 (152) enabled logging of sonoff.0.Smartmeter.Power_Power_curr (Count=2), Alias=false
        2022-05-10 23:05:53.604  - info: history.0 (152) enabled logging of sonoff.0.Smartmeter.Power_Total_out (Count=3), Alias=false
        2022-05-10 23:05:53.604  - info: history.0 (152) enabled logging of fritzdect.0.DECT_087610067164.state (Count=4), Alias=false
        2022-05-10 23:05:53.605  - info: history.0 (152) enabled logging of fritzdect.0.DECT_087610067164.power (Count=5), Alias=false
        2022-05-10 23:05:53.606  - info: history.0 (152) enabled logging of fritzdect.0.DECT_087610067164.celsius (Count=6), Alias=false
        2022-05-10 23:05:53.606  - info: history.0 (152) enabled logging of shelly.1.shellyplus1pm#7c87ce64d6d0#1.Relay0.Power (Count=7), Alias=false
        2022-05-10 23:05:54.438  - info: host.buanet-iobroker1 instance system.adapter.telegram.0 started with pid 183
        2022-05-10 23:05:58.459  - info: host.buanet-iobroker1 instance system.adapter.sonoff.0 started with pid 194
        2022-05-10 23:05:58.631  - info: telegram.0 (183) starting. Version 1.12.2 in /opt/iobroker/node_modules/iobroker.telegram, node: v14.19.1, js-controller: 4.0.15
        2022-05-10 23:06:00.421  - info: sonoff.0 (194) starting. Version 2.4.7 in /opt/iobroker/node_modules/iobroker.sonoff, node: v14.19.1, js-controller: 4.0.15
        2022-05-10 23:06:00.483  - info: sonoff.0 (194) Starting MQTT authenticated  server on port 1883
        2022-05-10 23:06:02.431  - info: host.buanet-iobroker1 instance system.adapter.alexa2.0 started with pid 213
        2022-05-10 23:06:04.790  - info: alexa2.0 (213) starting. Version 3.11.2 in /opt/iobroker/node_modules/iobroker.alexa2, node: v14.19.1, js-controller: 4.0.15
        2022-05-10 23:06:04.953  - info: alexa2.0 (213) Proxy IP not set, use first network interface (192.168.178.3) instead
        2022-05-10 23:06:06.449  - info: host.buanet-iobroker1 instance system.adapter.alexa2.1 started with pid 228
        2022-05-10 23:06:08.789  - info: alexa2.1 (228) starting. Version 3.11.2 in /opt/iobroker/node_modules/iobroker.alexa2, node: v14.19.1, js-controller: 4.0.15
        2022-05-10 23:06:09.066  - info: alexa2.1 (228) Proxy IP not set, use first network interface (192.168.178.3) instead
        2022-05-10 23:06:09.100  - info: alexa2.0 (213) Update cookie in adapter configuration ... restarting ...
        2022-05-10 23:06:09.153  - info: host.buanet-iobroker1 stopInstance system.adapter.alexa2.0 (force=false, process=true)
        2022-05-10 23:06:09.177  - info: alexa2.0 (213) Got terminate signal TERMINATE_YOURSELF
        2022-05-10 23:06:09.178  - info: alexa2.0 (213) terminating
        2022-05-10 23:06:09.180  - info: alexa2.0 (213) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
        2022-05-10 23:06:09.202  - info: host.buanet-iobroker1 stopInstance system.adapter.alexa2.0 send kill signal
        2022-05-10 23:06:09.746  - info: host.buanet-iobroker1 instance system.adapter.alexa2.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
        2022-05-10 23:06:10.401  - info: host.buanet-iobroker1 instance system.adapter.meross.0 started with pid 256
        2022-05-10 23:06:12.298  - info: host.buanet-iobroker1 instance system.adapter.alexa2.0 started with pid 267
        2022-05-10 23:06:12.769  - info: alexa2.1 (228) Update cookie in adapter configuration ... restarting ...
        2022-05-10 23:06:12.845  - info: host.buanet-iobroker1 stopInstance system.adapter.alexa2.1 (force=false, process=true)
        2022-05-10 23:06:12.868  - info: alexa2.1 (228) Got terminate signal TERMINATE_YOURSELF
        2022-05-10 23:06:12.880  - info: alexa2.1 (228) terminating
        2022-05-10 23:06:12.885  - info: alexa2.1 (228) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
        2022-05-10 23:06:12.909  - info: host.buanet-iobroker1 stopInstance system.adapter.alexa2.1 send kill signal
        2022-05-10 23:06:12.917  - info: meross.0 (256) starting. Version 1.10.1 in /opt/iobroker/node_modules/iobroker.meross, node: v14.19.1, js-controller: 4.0.15
        2022-05-10 23:06:13.468  - error: meross.0 (256) Meross Connection Error: Error: 0: 
        2022-05-10 23:06:13.470  - info: host.buanet-iobroker1 instance system.adapter.alexa2.1 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
        2022-05-10 23:06:14.337  - info: alexa2.0 (267) starting. Version 3.11.2 in /opt/iobroker/node_modules/iobroker.alexa2, node: v14.19.1, js-controller: 4.0.15
        2022-05-10 23:06:14.463  - info: host.buanet-iobroker1 instance system.adapter.shelly.0 started with pid 287
        2022-05-10 23:06:14.508  - info: alexa2.0 (267) Proxy IP not set, use first network interface (192.168.178.3) instead
        2022-05-10 23:06:15.972  - info: host.buanet-iobroker1 instance system.adapter.alexa2.1 started with pid 294
        2022-05-10 23:06:17.312  - info: alexa2.0 (267) Alexa-Push-Connection (macDms = true) established. Disable Polling
        2022-05-10 23:06:17.732  - info: shelly.0 (287) starting. Version 5.3.2 in /opt/iobroker/node_modules/iobroker.shelly, node: v14.19.1, js-controller: 4.0.15
        2022-05-10 23:06:18.103  - info: shelly.0 (287) Starting in CoAP mode.
        2022-05-10 23:06:18.298  - info: alexa2.1 (294) starting. Version 3.11.2 in /opt/iobroker/node_modules/iobroker.alexa2, node: v14.19.1, js-controller: 4.0.15
        2022-05-10 23:06:18.561  - info: alexa2.1 (294) Proxy IP not set, use first network interface (192.168.178.3) instead
        2022-05-10 23:06:18.564  - info: host.buanet-iobroker1 instance system.adapter.hue.0 started with pid 317
        2022-05-10 23:06:19.289  - info: shelly.0 (287) [CoAP] Listening for packets in the network
        2022-05-10 23:06:20.988  - info: alexa2.1 (294) Alexa-Push-Connection (macDms = true) established. Disable Polling
        2022-05-10 23:06:21.206  - info: alexa2.1 (294) Unknown Device, but enabling commands, Try it and report back if commands work.
        2022-05-10 23:06:21.208  - info: alexa2.1 (294) Report to developer as GitHub issue with details for device. Please grab full next line pot. from logfile on disk if cutted
        2022-05-10 23:06:21.208  - info: alexa2.1 (294)     Device-type:A3QS1XP2U6UJX9 (AMAZON_MUSIC,SIRIUSXM,MICROPHONE,PERSISTENT_CONNECTION,I_HEART_RADIO,TUNE_IN,CHANGE_NAME,DREAM_TRAINING,TOUCH_INITIATED,ADAPTIVE_LISTENING,AUDIBLE,SLEEP,MUSIC_SKILL,GOLDFISH,TIMERS_AND_ALARMS,VOLUME_SETTING,APPLE_MUSIC,AUDIO_PLAYER,TIDAL,SUPPORTS_CONNECTED_HOME_CLOUD_ONLY,KINDLE_BOOKS,DEEZER,DEREGISTER_DEVICE,HANDS_FREE)
        2022-05-10 23:06:21.466  - info: shelly.0 (287) [CoAP] Device 192.168.180.98 (shellyplug-s / shellyplug-s-16A2C3 / SHPLG2-1#16A2C3#1) connected! Polltime set to 15 sec.
        2022-05-10 23:06:21.979  - info: hue.0 (317) starting. Version 3.6.5 in /opt/iobroker/node_modules/iobroker.hue, node: v14.19.1, js-controller: 4.0.15
        2022-05-10 23:06:22.532  - info: host.buanet-iobroker1 instance system.adapter.shelly.1 started with pid 332
        2022-05-10 23:06:23.681  - info: hue.0 (317) skip switch: Daylight.configured
        2022-05-10 23:06:23.682  - info: hue.0 (317) skip switch: Daylight.sunriseoffset
        2022-05-10 23:06:23.683  - info: hue.0 (317) skip switch: Daylight.sunsetoffset
        2022-05-10 23:06:23.707  - info: hue.0 (317) skip switch: Hue temperature sensor 1.alert
        2022-05-10 23:06:23.707  - info: hue.0 (317) skip switch: Hue temperature sensor 1.ledindication
        2022-05-10 23:06:23.708  - info: hue.0 (317) skip switch: Hue temperature sensor 1.usertest
        2022-05-10 23:06:23.716  - info: hue.0 (317) skip switch: Bad Sensor.alert
        2022-05-10 23:06:23.717  - info: hue.0 (317) skip switch: Bad Sensor.ledindication
        2022-05-10 23:06:23.717  - info: hue.0 (317) skip switch: Bad Sensor.usertest
        2022-05-10 23:06:23.719  - info: hue.0 (317) skip switch: Bad Sensor.sensitivity
        2022-05-10 23:06:23.720  - info: hue.0 (317) skip switch: Bad Sensor.sensitivitymax
        2022-05-10 23:06:23.746  - info: hue.0 (317) skip switch: Hue ambient light sensor 1.alert
        2022-05-10 23:06:23.747  - info: hue.0 (317) skip switch: Hue ambient light sensor 1.tholddark
        2022-05-10 23:06:23.747  - info: hue.0 (317) skip switch: Hue ambient light sensor 1.tholdoffset
        2022-05-10 23:06:23.748  - info: hue.0 (317) skip switch: Hue ambient light sensor 1.ledindication
        2022-05-10 23:06:23.749  - info: hue.0 (317) skip switch: Hue ambient light sensor 1.usertest
        2022-05-10 23:06:23.761  - info: hue.0 (317) skip switch: MotionSensor 13.Companion.status
        2022-05-10 23:06:23.767  - info: hue.0 (317) skip switch: Hue temperature sensor 3.alert
        2022-05-10 23:06:23.768  - info: hue.0 (317) skip switch: Hue temperature sensor 3.ledindication
        2022-05-10 23:06:23.769  - info: hue.0 (317) skip switch: Hue temperature sensor 3.usertest
        2022-05-10 23:06:23.777  - info: hue.0 (317) skip switch: Eingangsbereich Sensor.alert
        2022-05-10 23:06:23.777  - info: hue.0 (317) skip switch: Eingangsbereich Sensor.ledindication
        2022-05-10 23:06:23.778  - info: hue.0 (317) skip switch: Eingangsbereich Sensor.usertest
        2022-05-10 23:06:23.778  - info: hue.0 (317) skip switch: Eingangsbereich Sensor.sensitivity
        2022-05-10 23:06:23.779  - info: hue.0 (317) skip switch: Eingangsbereich Sensor.sensitivitymax
        2022-05-10 23:06:23.793  - info: hue.0 (317) skip switch: Hue ambient light sensor 3.alert
        2022-05-10 23:06:23.794  - info: hue.0 (317) skip switch: Hue ambient light sensor 3.tholddark
        2022-05-10 23:06:23.796  - info: hue.0 (317) skip switch: Hue ambient light sensor 3.tholdoffset
        2022-05-10 23:06:23.796  - info: hue.0 (317) skip switch: Hue ambient light sensor 3.ledindication
        2022-05-10 23:06:23.798  - info: hue.0 (317) skip switch: Hue ambient light sensor 3.usertest
        2022-05-10 23:06:23.809  - info: hue.0 (317) skip switch: MotionSensor 39.Companion.status
        2022-05-10 23:06:23.813  - info: hue.0 (317) skip switch: Hue temperature sensor 4.alert
        2022-05-10 23:06:23.814  - info: hue.0 (317) skip switch: Hue temperature sensor 4.ledindication
        2022-05-10 23:06:23.814  - info: hue.0 (317) skip switch: Hue temperature sensor 4.usertest
        2022-05-10 23:06:23.823  - info: hue.0 (317) skip switch: Küche Sensor.alert
        2022-05-10 23:06:23.823  - info: hue.0 (317) skip switch: Küche Sensor.ledindication
        2022-05-10 23:06:23.824  - info: hue.0 (317) skip switch: Küche Sensor.usertest
        2022-05-10 23:06:23.824  - info: hue.0 (317) skip switch: Küche Sensor.sensitivity
        2022-05-10 23:06:23.826  - info: hue.0 (317) skip switch: Küche Sensor.sensitivitymax
        2022-05-10 23:06:23.838  - info: hue.0 (317) skip switch: Hue ambient light sensor 4.alert
        2022-05-10 23:06:23.838  - info: hue.0 (317) skip switch: Hue ambient light sensor 4.tholddark
        2022-05-10 23:06:23.840  - info: hue.0 (317) skip switch: Hue ambient light sensor 4.tholdoffset
        2022-05-10 23:06:23.841  - info: hue.0 (317) skip switch: Hue ambient light sensor 4.ledindication
        2022-05-10 23:06:23.843  - info: hue.0 (317) skip switch: Hue ambient light sensor 4.usertest
        2022-05-10 23:06:23.856  - info: hue.0 (317) skip switch: MotionSensor 46.Companion.status
        2022-05-10 23:06:23.862  - info: hue.0 (317) skip switch: Dimmer Switch 55 SceneCycle.status
        2022-05-10 23:06:23.876  - info: hue.0 (317) skip switch: Dimmer Switch 57 SceneCycle.status
        2022-05-10 23:06:23.918  - info: hue.0 (317) skip switch: Garten Sensor.alert
        2022-05-10 23:06:23.919  - info: hue.0 (317) skip switch: Garten Sensor.sensitivity
        2022-05-10 23:06:23.919  - info: hue.0 (317) skip switch: Garten Sensor.sensitivitymax
        2022-05-10 23:06:23.920  - info: hue.0 (317) skip switch: Garten Sensor.ledindication
        2022-05-10 23:06:23.920  - info: hue.0 (317) skip switch: Garten Sensor.usertest
        2022-05-10 23:06:23.931  - info: hue.0 (317) skip switch: Hue outdoor ambient light sensor.alert
        2022-05-10 23:06:23.932  - info: hue.0 (317) skip switch: Hue outdoor ambient light sensor.tholddark
        2022-05-10 23:06:23.933  - info: hue.0 (317) skip switch: Hue outdoor ambient light sensor.tholdoffset
        2022-05-10 23:06:23.933  - info: hue.0 (317) skip switch: Hue outdoor ambient light sensor.ledindication
        2022-05-10 23:06:23.934  - info: hue.0 (317) skip switch: Hue outdoor ambient light sensor.usertest
        2022-05-10 23:06:23.942  - info: hue.0 (317) skip switch: Hue outdoor temperature sensor 1.alert
        2022-05-10 23:06:23.943  - info: hue.0 (317) skip switch: Hue outdoor temperature sensor 1.ledindication
        2022-05-10 23:06:23.944  - info: hue.0 (317) skip switch: Hue outdoor temperature sensor 1.usertest
        2022-05-10 23:06:23.955  - info: hue.0 (317) skip switch: cycling.status
        2022-05-10 23:06:23.967  - info: hue.0 (317) skip switch: cycleState.status
        2022-05-10 23:06:23.976  - info: hue.0 (317) skip switch: Start and stop.status
        2022-05-10 23:06:23.983  - warn: hue.0 (317) channel "Start_and_stop" already exists, using "Start_and_stop_CLIPGenericStatus" for sensor 130
        2022-05-10 23:06:23.984  - info: hue.0 (317) skip switch: Start and stop CLIPGenericStatus.status
        2022-05-10 23:06:23.990  - info: hue.0 (317) skip switch: dimDirection.status
        2022-05-10 23:06:24.002  - info: hue.0 (317) skip switch: isDimming.status
        2022-05-10 23:06:24.006  - info: hue.0 (317) skip switch: slotState.status
        2022-05-10 23:06:24.010  - warn: hue.0 (317) channel "cycling" already exists, using "cycling_CLIPGenericStatus" for sensor 139
        2022-05-10 23:06:24.014  - info: hue.0 (317) skip switch: cycling CLIPGenericStatus.status
        2022-05-10 23:06:24.022  - info: hue.0 (317) skip switch: Garten Sensor Haustüre.alert
        2022-05-10 23:06:24.023  - info: hue.0 (317) skip switch: Garten Sensor Haustüre.sensitivity
        2022-05-10 23:06:24.023  - info: hue.0 (317) skip switch: Garten Sensor Haustüre.sensitivitymax
        2022-05-10 23:06:24.028  - info: hue.0 (317) skip switch: Garten Sensor Haustüre.ledindication
        2022-05-10 23:06:24.030  - info: hue.0 (317) skip switch: Garten Sensor Haustüre.usertest
        2022-05-10 23:06:24.039  - warn: hue.0 (317) channel "Hue_outdoor_ambient_light_sensor" already exists, using "Hue_outdoor_ambient_light_sensor_ZLLLightLevel" for sensor 141
        2022-05-10 23:06:24.040  - info: hue.0 (317) skip switch: Hue outdoor ambient light sensor ZLLLightLevel.alert
        2022-05-10 23:06:24.040  - info: hue.0 (317) skip switch: Hue outdoor ambient light sensor ZLLLightLevel.tholddark
        2022-05-10 23:06:24.041  - info: hue.0 (317) skip switch: Hue outdoor ambient light sensor ZLLLightLevel.tholdoffset
        2022-05-10 23:06:24.041  - info: hue.0 (317) skip switch: Hue outdoor ambient light sensor ZLLLightLevel.ledindication
        2022-05-10 23:06:24.042  - info: hue.0 (317) skip switch: Hue outdoor ambient light sensor ZLLLightLevel.usertest
        2022-05-10 23:06:24.055  - info: hue.0 (317) skip switch: Hue outdoor temperature sensor 2.alert
        2022-05-10 23:06:24.056  - info: hue.0 (317) skip switch: Hue outdoor temperature sensor 2.ledindication
        2022-05-10 23:06:24.057  - info: hue.0 (317) skip switch: Hue outdoor temperature sensor 2.usertest
        2022-05-10 23:06:24.069  - info: hue.0 (317) skip switch: roomstate.status
        2022-05-10 23:06:24.099  - info: hue.0 (317) skip switch: presenceState.status
        2022-05-10 23:06:24.117  - info: hue.0 (317) skip switch: timeBasedSlotState.status
        2022-05-10 23:06:24.125  - info: hue.0 (317) skip switch: timeBasedCycling.status
        2022-05-10 23:06:24.137  - info: hue.0 (317) skip switch: needToTurnOn.status
        2022-05-10 23:06:24.148  - warn: hue.0 (317) channel "Küche_oben" already exists, using "Küche_oben_ZLLPresence" for sensor 195
        2022-05-10 23:06:24.148  - info: hue.0 (317) skip switch: Küche oben ZLLPresence.alert
        2022-05-10 23:06:24.152  - info: hue.0 (317) skip switch: Küche oben ZLLPresence.sensitivity
        2022-05-10 23:06:24.152  - info: hue.0 (317) skip switch: Küche oben ZLLPresence.sensitivitymax
        2022-05-10 23:06:24.155  - info: hue.0 (317) skip switch: Küche oben ZLLPresence.ledindication
        2022-05-10 23:06:24.163  - info: hue.0 (317) skip switch: Küche oben ZLLPresence.usertest
        2022-05-10 23:06:24.177  - info: hue.0 (317) skip switch: Hue ambient light sensor 5.alert
        2022-05-10 23:06:24.183  - info: hue.0 (317) skip switch: Hue ambient light sensor 5.tholddark
        2022-05-10 23:06:24.184  - info: hue.0 (317) skip switch: Hue ambient light sensor 5.tholdoffset
        2022-05-10 23:06:24.186  - info: hue.0 (317) skip switch: Hue ambient light sensor 5.ledindication
        2022-05-10 23:06:24.188  - info: hue.0 (317) skip switch: Hue ambient light sensor 5.usertest
        2022-05-10 23:06:24.210  - info: hue.0 (317) skip switch: Hue temperature sensor 5.alert
        2022-05-10 23:06:24.212  - info: hue.0 (317) skip switch: Hue temperature sensor 5.ledindication
        2022-05-10 23:06:24.212  - info: hue.0 (317) skip switch: Hue temperature sensor 5.usertest
        2022-05-10 23:06:24.226  - warn: hue.0 (317) channel "presenceState" already exists, using "presenceState_CLIPGenericStatus" for sensor 208
        2022-05-10 23:06:24.229  - info: hue.0 (317) skip switch: presenceState CLIPGenericStatus.status
        2022-05-10 23:06:24.237  - info: hue.0 (317) skip switch: textState.status
        2022-05-10 23:06:24.238  - info: hue.0 (317) created/updated 46 sensor channels
        2022-05-10 23:06:25.002  - info: shelly.0 (287) [CoAP] Device 192.168.178.157 (shellyswitch25 / shellyswitch25-98CDAC38AE0F / SHSW-25#98CDAC38AE0F#1) connected! Polltime set to 15 sec.
        2022-05-10 23:06:25.887  - info: hue.0 (317) created/updated 25 light channels
        2022-05-10 23:06:25.904  - warn: hue.0 (317) channel "Decke" already exists, using "Decke_LightGroup" for group 2
        2022-05-10 23:06:25.928  - warn: hue.0 (317) channel "Küche" already exists, using "Küche_Room" for group 7
        2022-05-10 23:06:25.975  - warn: hue.0 (317) channel "Küche_oben" already exists, using "Küche_oben_Room" for group 14
        2022-05-10 23:06:25.981  - warn: hue.0 (317) channel "Garten" already exists, using "Garten_Room" for group 17
        2022-05-10 23:06:25.991  - warn: hue.0 (317) channel "Custom_group_for_$lights" already exists, using "Custom_group_for_$lights_LightGroup" for group 21
        2022-05-10 23:06:25.993  - info: hue.0 (317) created/updated 17 groups channels
        2022-05-10 23:06:26.037  - info: hue.0 (317) created/updated 184 scenes
        2022-05-10 23:06:26.038  - info: hue.0 (317) creating/updating bridge device
        2022-05-10 23:06:26.083  - info: shelly.1 (332) starting. Version 5.3.2 in /opt/iobroker/node_modules/iobroker.shelly, node: v14.19.1, js-controller: 4.0.15
        2022-05-10 23:06:26.307  - info: shelly.1 (332) Starting in MQTT mode. Listening on 0.0.0.0:1884
        2022-05-10 23:06:26.593  - info: host.buanet-iobroker1 instance system.adapter.discovery.0 started with pid 359
        2022-05-10 23:06:29.326  - info: shelly.0 (287) [CoAP] Device 192.168.180.102 (shellyplug-s / shellyplug-s-16CE7A / SHPLG2-1#16CE7A#1) connected! Polltime set to 15 sec.
        2022-05-10 23:06:29.783  - info: discovery.0 (359) starting. Version 2.7.5 in /opt/iobroker/node_modules/iobroker.discovery, node: v14.19.1, js-controller: 4.0.15
        2022-05-10 23:06:30.540  - info: host.buanet-iobroker1 instance system.adapter.backitup.0 started with pid 375
        2022-05-10 23:06:32.862  - info: shelly.0 (287) [CoAP] Device 192.168.178.183 (shellyswitch25 / shellyswitch25-E8DB84803175 / SHSW-25#E8DB84803175#1) connected! Polltime set to 15 sec.
        2022-05-10 23:06:33.034  - info: backitup.0 (375) starting. Version 2.3.3 in /opt/iobroker/node_modules/iobroker.backitup, node: v14.19.1, js-controller: 4.0.15
        2022-05-10 23:06:33.138  - info: backitup.0 (375) [iobroker] backup was activated at 02:40 every 1 day(s)
        2022-05-10 23:06:34.502  - info: host.buanet-iobroker1 instance system.adapter.web.0 started with pid 390
        2022-05-10 23:06:37.422  - info: web.0 (390) starting. Version 4.2.0 in /opt/iobroker/node_modules/iobroker.web, node: v14.19.1, js-controller: 4.0.15
        2022-05-10 23:06:37.949  - info: web.0 (390) socket.io server listening on port 8082
        2022-05-10 23:06:37.957  - info: alexa2.0 (267) Subscribing to states...
        2022-05-10 23:06:37.964  - info: web.0 (390) http server listening on port 8082
        2022-05-10 23:06:38.497  - info: host.buanet-iobroker1 instance system.adapter.fritzdect.0 started with pid 405
        2022-05-10 23:06:40.608  - info: fritzdect.0 (405) starting. Version 2.2.3 in /opt/iobroker/node_modules/iobroker.fritzdect, node: v14.19.1, js-controller: 4.0.15
        2022-05-10 23:06:40.637  - info: fritzdect.0 (405) fritzdect entered ready
        2022-05-10 23:06:40.669  - info: fritzdect.0 (405) fritzdect uses USER: fbsmarthome
        2022-05-10 23:06:41.484  - info: fritzdect.0 (405) checking user permissions
        2022-05-10 23:06:41.648  - info: fritzdect.0 (405) the rights are : {"Name":"HomeAuto","Access":"2"}
        2022-05-10 23:06:41.649  - info: fritzdect.0 (405) start creating devices/groups
        2022-05-10 23:06:41.756  - info: web.0 (390) ==> Connected system.user.admin from ::ffff:192.168.180.89
        2022-05-10 23:06:41.926  - info: fritzdect.0 (405) CREATE Devices 4
        2022-05-10 23:06:41.980  - info: fritzdect.0 (405) setting up switch 
        2022-05-10 23:06:41.986  - info: fritzdect.0 (405) setting up temperatur 
        2022-05-10 23:06:41.988  - info: fritzdect.0 (405) setting up switch 
        2022-05-10 23:06:42.044  - info: fritzdect.0 (405) setting up temperatur 
        2022-05-10 23:06:42.058  - info: fritzdect.0 (405) setting up thermostat 
        2022-05-10 23:06:42.068  - info: fritzdect.0 (405) setting up powermeter 
        2022-05-10 23:06:42.073  - info: fritzdect.0 (405) setting up temperatur 
        2022-05-10 23:06:42.076  - info: fritzdect.0 (405) setting up powermeter 
        2022-05-10 23:06:42.120  - info: fritzdect.0 (405) setting up simpleonoff
        2022-05-10 23:06:42.121  - info: fritzdect.0 (405) setting up temperatur 
        2022-05-10 23:06:42.129  - info: fritzdect.0 (405) setting up simpleonoff
        2022-05-10 23:06:42.255  - info: fritzdect.0 (405) setting up thermostat nextchange
        2022-05-10 23:06:42.333  - info: fritzdect.0 (405) State value to set for "fritzdect.0.DECT_109710995216.windowopenactivetime" has to be type "number" but received type "string" 
        2022-05-10 23:06:42.372  - info: fritzdect.0 (405) State value to set for "fritzdect.0.DECT_109710995216.boostactivetime" has to be type "number" but received type "string" 
        2022-05-10 23:06:42.454  - info: fritzdect.0 (405) CREATE groups 1
        2022-05-10 23:06:45.518  - info: fritzdect.0 (405) setting up groupinfo 
        2022-05-10 23:06:46.981  - info: fritzdect.0 (405) setting up thermostat 
        2022-05-10 23:06:49.733  - info: host.buanet-iobroker1 instance system.adapter.lg-thinq.0 started with pid 1260
        2022-05-10 23:06:49.738  - info: sonoff.0 (194) Client [Smartmeter] connected with secret 1652216809655_8075
        2022-05-10 23:06:53.875  - info: host.buanet-iobroker1 instance system.adapter.mercedesme.0 started with pid 1484
        2022-05-10 23:06:54.367  - info: host.buanet-iobroker1 instance system.adapter.sourceanalytix.0 started with pid 1516
        2022-05-10 23:06:54.573  - info: fritzdect.0 (405) setting up thermostat nextchange
        2022-05-10 23:06:54.933  - info: fritzdect.0 (405) State value to set for "fritzdect.0.DECT_grpEFC2DD-3CA0C0661.windowopenactivetime" has to be type "number" but received type "string" 
        2022-05-10 23:06:54.972  - info: fritzdect.0 (405) State value to set for "fritzdect.0.DECT_grpEFC2DD-3CA0C0661.boostactivetime" has to be type "number" but received type "string" 
        2022-05-10 23:06:55.099  - info: fritzdect.0 (405) finished creating devices/groups (if any)
        2022-05-10 23:06:55.100  - info: fritzdect.0 (405) start creating templates 
        2022-05-10 23:06:55.555  - info: fritzdect.0 (405) finished creating templates (if any) 
        2022-05-10 23:06:55.558  - info: fritzdect.0 (405) start initial updating devices/groups
        2022-05-10 23:07:00.450  - info: fritzdect.0 (405) finished initial updating devices/groups
        2022-05-10 23:07:00.450  - info: fritzdect.0 (405) going over to cyclic polling, messages to poll activity only in debug-mode 
        2022-05-10 23:07:08.772  - info: web.0 (390) ==> Connected system.user.admin from ::ffff:192.168.180.89
        2022-05-10 23:07:10.386  - info: web.0 (390) ==> Connected system.user.admin from ::ffff:192.168.180.89
        2022-05-10 23:07:14.589  - warn: lg-thinq.0 (1260) slow connection to objects DB. Still waiting ...
        2022-05-10 23:07:17.221  - info: shelly.1 (332) [MQTT] Device 192.168.178.109 (shellyplus1pm / shellyplus1pm-7c87ce64d6d0 / shellyplus1pm#7c87ce64d6d0#1) connected! Polltime set to 5 sec.
        2022-05-10 23:07:17.652  - warn: sourceanalytix.0 (1516) slow connection to objects DB. Still waiting ...
        2022-05-10 23:07:17.705  - info: shelly.1 (332) [MQTT] Device 192.168.180.97 (shellyplus1pm / shellyplus1pm-3c610579db50 / shellyplus1pm#3c610579db50#1) connected! Polltime set to 5 sec.
        2022-05-10 23:07:24.725  - warn: mercedesme.0 (1484) slow connection to objects DB. Still waiting ...
        
        
        apollon77A 1 Antwort Letzte Antwort
        0
        • V vo5tr0

          @apollon77

          DSM 7 :)

          Gegen 23:04 habe ich die hohe Auslastung bemerkt und den Container abgeschaltet. Dann um 23:05 Uhr wieder gestartet. Die Auslastung ging sofort hoch auf 100%, laut Docker log kam der erneute Shutdown Befehl noch an und der Container wurde auch gegen 23:07 Uhr erfolgreich gestoppt. Zu dem Zeitpunkt war mein NAS aber schon nicht mehr erreichbar.

          Ich packe hier einfach Mal die letzen Zeilen aus dem IO Broker Log rein, aber etwas auffälliges konnte ich nicht sehen

          2022-05-10 21:03:05.739  - info: web.0 (288) ==> Connected system.user.admin from ::ffff:192.168.178.140
          2022-05-10 21:03:05.741  - info: web.0 (288) ==> Connected system.user.admin from ::ffff:192.168.178.140
          2022-05-10 21:05:48.309  - info: web.0 (288) <== Disconnect system.user.admin from ::ffff:192.168.178.140 flot
          2022-05-10 21:05:48.310  - info: web.0 (288) <== Disconnect system.user.admin from ::ffff:192.168.178.140 flot
          2022-05-10 21:09:03.658  - info: web.0 (288) ==> Connected system.user.admin from ::ffff:192.168.178.140
          2022-05-10 21:09:03.658  - info: web.0 (288) ==> Connected system.user.admin from ::ffff:192.168.178.140
          2022-05-10 21:11:46.345  - info: web.0 (288) <== Disconnect system.user.admin from ::ffff:192.168.178.140 flot
          2022-05-10 21:11:46.347  - info: web.0 (288) <== Disconnect system.user.admin from ::ffff:192.168.178.140 flot
          2022-05-10 21:15:01.192  - info: web.0 (288) ==> Connected system.user.admin from ::ffff:192.168.178.140
          2022-05-10 21:15:01.193  - info: web.0 (288) ==> Connected system.user.admin from ::ffff:192.168.178.140
          2022-05-10 21:50:02.503  - info: web.0 (288) <== Disconnect system.user.admin from ::ffff:192.168.178.140 flot
          2022-05-10 21:50:02.510  - info: web.0 (288) <== Disconnect system.user.admin from ::ffff:192.168.178.140 flot
          2022-05-10 21:50:03.731  - info: web.0 (288) ==> Connected system.user.admin from ::ffff:192.168.178.140
          2022-05-10 21:50:04.769  - info: web.0 (288) ==> Connected system.user.admin from ::ffff:192.168.178.140
          2022-05-10 21:50:09.188  - info: web.0 (288) <== Disconnect system.user.admin from ::ffff:192.168.178.140 flot
          2022-05-10 21:50:09.196  - info: web.0 (288) ==> Connected system.user.admin from ::ffff:192.168.178.140
          2022-05-10 21:50:09.197  - info: web.0 (288) ==> Connected system.user.admin from ::ffff:192.168.178.140
          2022-05-10 21:50:09.198  - info: web.0 (288) <== Disconnect system.user.admin from ::ffff:192.168.178.140 flot
          2022-05-10 21:50:10.772  - info: web.0 (288) ==> Connected system.user.admin from ::ffff:192.168.178.140
          2022-05-10 21:50:10.773  - info: web.0 (288) ==> Connected system.user.admin from ::ffff:192.168.178.140
          2022-05-10 21:50:12.015  - info: web.0 (288) <== Disconnect system.user.admin from ::ffff:192.168.178.140 flot
          2022-05-10 21:50:12.019  - info: web.0 (288) <== Disconnect system.user.admin from ::ffff:192.168.178.140 flot
          2022-05-10 21:50:13.784  - info: web.0 (288) ==> Connected system.user.admin from ::ffff:192.168.178.140
          2022-05-10 21:50:13.785  - info: web.0 (288) ==> Connected system.user.admin from ::ffff:192.168.178.140
          2022-05-10 21:50:15.448  - info: web.0 (288) <== Disconnect system.user.admin from ::ffff:192.168.178.140 flot
          2022-05-10 21:50:15.450  - info: web.0 (288) <== Disconnect system.user.admin from ::ffff:192.168.178.140 flot
          2022-05-10 21:50:16.868  - info: web.0 (288) ==> Connected system.user.admin from ::ffff:192.168.178.140
          2022-05-10 21:50:16.872  - info: web.0 (288) ==> Connected system.user.admin from ::ffff:192.168.178.140
          2022-05-10 21:50:26.644  - info: web.0 (288) <== Disconnect system.user.admin from ::ffff:192.168.178.140 flot
          2022-05-10 21:50:26.647  - info: web.0 (288) <== Disconnect system.user.admin from ::ffff:192.168.178.140 flot
          2022-05-10 21:50:28.368  - info: web.0 (288) ==> Connected system.user.admin from ::ffff:192.168.178.140
          2022-05-10 21:50:28.377  - info: web.0 (288) ==> Connected system.user.admin from ::ffff:192.168.178.140
          2022-05-10 21:52:39.194  - info: web.0 (288) <== Disconnect system.user.admin from ::ffff:192.168.178.140 
          2022-05-10 21:52:39.195  - info: web.0 (288) <== Disconnect system.user.admin from ::ffff:192.168.178.140 
          2022-05-10 21:53:04.085  - info: web.0 (288) <== Disconnect system.user.admin from ::ffff:192.168.178.140 flot
          2022-05-10 21:53:04.087  - info: web.0 (288) <== Disconnect system.user.admin from ::ffff:192.168.178.140 flot
          2022-05-10 21:53:05.616  - info: web.0 (288) ==> Connected system.user.admin from ::ffff:192.168.178.140
          2022-05-10 21:53:06.204  - info: web.0 (288) ==> Connected system.user.admin from ::ffff:192.168.178.140
          2022-05-10 22:04:32.893  - info: web.0 (288) <== Disconnect system.user.admin from ::ffff:192.168.178.140 flot
          2022-05-10 22:04:32.906  - info: web.0 (288) <== Disconnect system.user.admin from ::ffff:192.168.178.140 flot
          2022-05-10 22:04:34.158  - info: web.0 (288) ==> Connected system.user.admin from ::ffff:192.168.178.140
          2022-05-10 22:04:35.461  - info: web.0 (288) ==> Connected system.user.admin from ::ffff:192.168.178.140
          2022-05-10 22:09:39.343  - info: web.0 (288) <== Disconnect system.user.admin from ::ffff:192.168.178.140 flot
          2022-05-10 22:09:39.383  - info: web.0 (288) <== Disconnect system.user.admin from ::ffff:192.168.178.140 flot
          2022-05-10 22:55:52.184  - info: web.0 (288) ==> Connected system.user.admin from ::ffff:192.168.180.89
          2022-05-10 22:55:53.090  - info: web.0 (288) ==> Connected system.user.admin from ::ffff:192.168.180.89
          2022-05-10 23:02:56.657  - info: web.0 (288) <== Disconnect system.user.admin from ::ffff:192.168.180.89 flot
          2022-05-10 23:02:57.923  - info: web.0 (288) ==> Connected system.user.admin from ::ffff:192.168.180.89
          2022-05-10 23:03:49.937  - info: web.0 (288) <== Disconnect system.user.admin from ::ffff:192.168.180.89 flot
          2022-05-10 23:03:52.694  - info: web.0 (288) ==> Connected system.user.admin from ::ffff:192.168.180.89
          2022-05-10 23:05:39.173  - info: host.buanet-iobroker1 iobroker.js-controller version 4.0.15 js-controller starting
          2022-05-10 23:05:39.179  - info: host.buanet-iobroker1 Copyright (c) 2014-2022 bluefox, 2014 hobbyquaker
          2022-05-10 23:05:39.180  - info: host.buanet-iobroker1 hostname: buanet-iobroker1, node: v14.19.1
          2022-05-10 23:05:39.180  - info: host.buanet-iobroker1 ip addresses: 192.168.178.3 172.19.0.1 fe80::42:96ff:fea4:97df 172.17.0.1 fe80::42:22ff:fe70:b7e2 fe80::8cac:dbff:feee:8378 fe80::acd6:77ff:fe61:b496 fe80::b0e0:ff:fe97:da1d fe80::4420:c7ff:fed8:83
          2022-05-10 23:05:41.665  - info: host.buanet-iobroker1 connected to Objects and States
          2022-05-10 23:05:41.704  - info: host.buanet-iobroker1 added notifications configuration of host
          2022-05-10 23:05:42.305  - info: host.buanet-iobroker1 27 instances found
          2022-05-10 23:05:42.372  - info: host.buanet-iobroker1 starting 18 instances
          2022-05-10 23:05:42.757  - info: host.buanet-iobroker1 instance system.adapter.admin.0 started with pid 126
          2022-05-10 23:05:45.009  - info: admin.0 (126) starting. Version 5.3.1 in /opt/iobroker/node_modules/iobroker.admin, node: v14.19.1, js-controller: 4.0.15
          2022-05-10 23:05:45.063  - info: admin.0 (126) requesting all states
          2022-05-10 23:05:45.064  - info: admin.0 (126) requesting all objects
          2022-05-10 23:05:46.202  - info: admin.0 (126) received all objects
          2022-05-10 23:05:46.710  - info: host.buanet-iobroker1 instance system.adapter.javascript.0 started with pid 141
          2022-05-10 23:05:47.619  - info: admin.0 (126) Request actual repository...
          2022-05-10 23:05:47.641  - info: admin.0 (126) http server listening on port 8081
          2022-05-10 23:05:47.642  - info: admin.0 (126) Use link "http://localhost:8081" to configure.
          2022-05-10 23:05:48.020  - info: host.buanet-iobroker1 Updating repository "stable" under "http://download.iobroker.net/sources-dist.json"
          2022-05-10 23:05:50.531  - info: host.buanet-iobroker1 instance system.adapter.history.0 started with pid 152
          2022-05-10 23:05:50.596  - info: admin.0 (126) Repository received successfully.
          2022-05-10 23:05:51.267  - info: javascript.0 (141) starting. Version 5.2.21 in /opt/iobroker/node_modules/iobroker.javascript, node: v14.19.1, js-controller: 4.0.15
          2022-05-10 23:05:51.516  - info: javascript.0 (141) requesting all states
          2022-05-10 23:05:51.518  - info: javascript.0 (141) requesting all objects
          2022-05-10 23:05:52.827  - info: javascript.0 (141) received all objects
          2022-05-10 23:05:52.956  - info: javascript.0 (141) received all states
          2022-05-10 23:05:53.312  - error: admin.0 (126) error
          2022-05-10 23:05:53.484  - info: history.0 (152) starting. Version 1.10.5 in /opt/iobroker/node_modules/iobroker.history, node: v14.19.1, js-controller: 4.0.15
          2022-05-10 23:05:53.601  - info: history.0 (152) enabled logging of sonoff.0.Smartmeter.Power_Total_in (Count=1), Alias=false
          2022-05-10 23:05:53.603  - info: history.0 (152) enabled logging of sonoff.0.Smartmeter.Power_Power_curr (Count=2), Alias=false
          2022-05-10 23:05:53.604  - info: history.0 (152) enabled logging of sonoff.0.Smartmeter.Power_Total_out (Count=3), Alias=false
          2022-05-10 23:05:53.604  - info: history.0 (152) enabled logging of fritzdect.0.DECT_087610067164.state (Count=4), Alias=false
          2022-05-10 23:05:53.605  - info: history.0 (152) enabled logging of fritzdect.0.DECT_087610067164.power (Count=5), Alias=false
          2022-05-10 23:05:53.606  - info: history.0 (152) enabled logging of fritzdect.0.DECT_087610067164.celsius (Count=6), Alias=false
          2022-05-10 23:05:53.606  - info: history.0 (152) enabled logging of shelly.1.shellyplus1pm#7c87ce64d6d0#1.Relay0.Power (Count=7), Alias=false
          2022-05-10 23:05:54.438  - info: host.buanet-iobroker1 instance system.adapter.telegram.0 started with pid 183
          2022-05-10 23:05:58.459  - info: host.buanet-iobroker1 instance system.adapter.sonoff.0 started with pid 194
          2022-05-10 23:05:58.631  - info: telegram.0 (183) starting. Version 1.12.2 in /opt/iobroker/node_modules/iobroker.telegram, node: v14.19.1, js-controller: 4.0.15
          2022-05-10 23:06:00.421  - info: sonoff.0 (194) starting. Version 2.4.7 in /opt/iobroker/node_modules/iobroker.sonoff, node: v14.19.1, js-controller: 4.0.15
          2022-05-10 23:06:00.483  - info: sonoff.0 (194) Starting MQTT authenticated  server on port 1883
          2022-05-10 23:06:02.431  - info: host.buanet-iobroker1 instance system.adapter.alexa2.0 started with pid 213
          2022-05-10 23:06:04.790  - info: alexa2.0 (213) starting. Version 3.11.2 in /opt/iobroker/node_modules/iobroker.alexa2, node: v14.19.1, js-controller: 4.0.15
          2022-05-10 23:06:04.953  - info: alexa2.0 (213) Proxy IP not set, use first network interface (192.168.178.3) instead
          2022-05-10 23:06:06.449  - info: host.buanet-iobroker1 instance system.adapter.alexa2.1 started with pid 228
          2022-05-10 23:06:08.789  - info: alexa2.1 (228) starting. Version 3.11.2 in /opt/iobroker/node_modules/iobroker.alexa2, node: v14.19.1, js-controller: 4.0.15
          2022-05-10 23:06:09.066  - info: alexa2.1 (228) Proxy IP not set, use first network interface (192.168.178.3) instead
          2022-05-10 23:06:09.100  - info: alexa2.0 (213) Update cookie in adapter configuration ... restarting ...
          2022-05-10 23:06:09.153  - info: host.buanet-iobroker1 stopInstance system.adapter.alexa2.0 (force=false, process=true)
          2022-05-10 23:06:09.177  - info: alexa2.0 (213) Got terminate signal TERMINATE_YOURSELF
          2022-05-10 23:06:09.178  - info: alexa2.0 (213) terminating
          2022-05-10 23:06:09.180  - info: alexa2.0 (213) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
          2022-05-10 23:06:09.202  - info: host.buanet-iobroker1 stopInstance system.adapter.alexa2.0 send kill signal
          2022-05-10 23:06:09.746  - info: host.buanet-iobroker1 instance system.adapter.alexa2.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
          2022-05-10 23:06:10.401  - info: host.buanet-iobroker1 instance system.adapter.meross.0 started with pid 256
          2022-05-10 23:06:12.298  - info: host.buanet-iobroker1 instance system.adapter.alexa2.0 started with pid 267
          2022-05-10 23:06:12.769  - info: alexa2.1 (228) Update cookie in adapter configuration ... restarting ...
          2022-05-10 23:06:12.845  - info: host.buanet-iobroker1 stopInstance system.adapter.alexa2.1 (force=false, process=true)
          2022-05-10 23:06:12.868  - info: alexa2.1 (228) Got terminate signal TERMINATE_YOURSELF
          2022-05-10 23:06:12.880  - info: alexa2.1 (228) terminating
          2022-05-10 23:06:12.885  - info: alexa2.1 (228) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
          2022-05-10 23:06:12.909  - info: host.buanet-iobroker1 stopInstance system.adapter.alexa2.1 send kill signal
          2022-05-10 23:06:12.917  - info: meross.0 (256) starting. Version 1.10.1 in /opt/iobroker/node_modules/iobroker.meross, node: v14.19.1, js-controller: 4.0.15
          2022-05-10 23:06:13.468  - error: meross.0 (256) Meross Connection Error: Error: 0: 
          2022-05-10 23:06:13.470  - info: host.buanet-iobroker1 instance system.adapter.alexa2.1 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
          2022-05-10 23:06:14.337  - info: alexa2.0 (267) starting. Version 3.11.2 in /opt/iobroker/node_modules/iobroker.alexa2, node: v14.19.1, js-controller: 4.0.15
          2022-05-10 23:06:14.463  - info: host.buanet-iobroker1 instance system.adapter.shelly.0 started with pid 287
          2022-05-10 23:06:14.508  - info: alexa2.0 (267) Proxy IP not set, use first network interface (192.168.178.3) instead
          2022-05-10 23:06:15.972  - info: host.buanet-iobroker1 instance system.adapter.alexa2.1 started with pid 294
          2022-05-10 23:06:17.312  - info: alexa2.0 (267) Alexa-Push-Connection (macDms = true) established. Disable Polling
          2022-05-10 23:06:17.732  - info: shelly.0 (287) starting. Version 5.3.2 in /opt/iobroker/node_modules/iobroker.shelly, node: v14.19.1, js-controller: 4.0.15
          2022-05-10 23:06:18.103  - info: shelly.0 (287) Starting in CoAP mode.
          2022-05-10 23:06:18.298  - info: alexa2.1 (294) starting. Version 3.11.2 in /opt/iobroker/node_modules/iobroker.alexa2, node: v14.19.1, js-controller: 4.0.15
          2022-05-10 23:06:18.561  - info: alexa2.1 (294) Proxy IP not set, use first network interface (192.168.178.3) instead
          2022-05-10 23:06:18.564  - info: host.buanet-iobroker1 instance system.adapter.hue.0 started with pid 317
          2022-05-10 23:06:19.289  - info: shelly.0 (287) [CoAP] Listening for packets in the network
          2022-05-10 23:06:20.988  - info: alexa2.1 (294) Alexa-Push-Connection (macDms = true) established. Disable Polling
          2022-05-10 23:06:21.206  - info: alexa2.1 (294) Unknown Device, but enabling commands, Try it and report back if commands work.
          2022-05-10 23:06:21.208  - info: alexa2.1 (294) Report to developer as GitHub issue with details for device. Please grab full next line pot. from logfile on disk if cutted
          2022-05-10 23:06:21.208  - info: alexa2.1 (294)     Device-type:A3QS1XP2U6UJX9 (AMAZON_MUSIC,SIRIUSXM,MICROPHONE,PERSISTENT_CONNECTION,I_HEART_RADIO,TUNE_IN,CHANGE_NAME,DREAM_TRAINING,TOUCH_INITIATED,ADAPTIVE_LISTENING,AUDIBLE,SLEEP,MUSIC_SKILL,GOLDFISH,TIMERS_AND_ALARMS,VOLUME_SETTING,APPLE_MUSIC,AUDIO_PLAYER,TIDAL,SUPPORTS_CONNECTED_HOME_CLOUD_ONLY,KINDLE_BOOKS,DEEZER,DEREGISTER_DEVICE,HANDS_FREE)
          2022-05-10 23:06:21.466  - info: shelly.0 (287) [CoAP] Device 192.168.180.98 (shellyplug-s / shellyplug-s-16A2C3 / SHPLG2-1#16A2C3#1) connected! Polltime set to 15 sec.
          2022-05-10 23:06:21.979  - info: hue.0 (317) starting. Version 3.6.5 in /opt/iobroker/node_modules/iobroker.hue, node: v14.19.1, js-controller: 4.0.15
          2022-05-10 23:06:22.532  - info: host.buanet-iobroker1 instance system.adapter.shelly.1 started with pid 332
          2022-05-10 23:06:23.681  - info: hue.0 (317) skip switch: Daylight.configured
          2022-05-10 23:06:23.682  - info: hue.0 (317) skip switch: Daylight.sunriseoffset
          2022-05-10 23:06:23.683  - info: hue.0 (317) skip switch: Daylight.sunsetoffset
          2022-05-10 23:06:23.707  - info: hue.0 (317) skip switch: Hue temperature sensor 1.alert
          2022-05-10 23:06:23.707  - info: hue.0 (317) skip switch: Hue temperature sensor 1.ledindication
          2022-05-10 23:06:23.708  - info: hue.0 (317) skip switch: Hue temperature sensor 1.usertest
          2022-05-10 23:06:23.716  - info: hue.0 (317) skip switch: Bad Sensor.alert
          2022-05-10 23:06:23.717  - info: hue.0 (317) skip switch: Bad Sensor.ledindication
          2022-05-10 23:06:23.717  - info: hue.0 (317) skip switch: Bad Sensor.usertest
          2022-05-10 23:06:23.719  - info: hue.0 (317) skip switch: Bad Sensor.sensitivity
          2022-05-10 23:06:23.720  - info: hue.0 (317) skip switch: Bad Sensor.sensitivitymax
          2022-05-10 23:06:23.746  - info: hue.0 (317) skip switch: Hue ambient light sensor 1.alert
          2022-05-10 23:06:23.747  - info: hue.0 (317) skip switch: Hue ambient light sensor 1.tholddark
          2022-05-10 23:06:23.747  - info: hue.0 (317) skip switch: Hue ambient light sensor 1.tholdoffset
          2022-05-10 23:06:23.748  - info: hue.0 (317) skip switch: Hue ambient light sensor 1.ledindication
          2022-05-10 23:06:23.749  - info: hue.0 (317) skip switch: Hue ambient light sensor 1.usertest
          2022-05-10 23:06:23.761  - info: hue.0 (317) skip switch: MotionSensor 13.Companion.status
          2022-05-10 23:06:23.767  - info: hue.0 (317) skip switch: Hue temperature sensor 3.alert
          2022-05-10 23:06:23.768  - info: hue.0 (317) skip switch: Hue temperature sensor 3.ledindication
          2022-05-10 23:06:23.769  - info: hue.0 (317) skip switch: Hue temperature sensor 3.usertest
          2022-05-10 23:06:23.777  - info: hue.0 (317) skip switch: Eingangsbereich Sensor.alert
          2022-05-10 23:06:23.777  - info: hue.0 (317) skip switch: Eingangsbereich Sensor.ledindication
          2022-05-10 23:06:23.778  - info: hue.0 (317) skip switch: Eingangsbereich Sensor.usertest
          2022-05-10 23:06:23.778  - info: hue.0 (317) skip switch: Eingangsbereich Sensor.sensitivity
          2022-05-10 23:06:23.779  - info: hue.0 (317) skip switch: Eingangsbereich Sensor.sensitivitymax
          2022-05-10 23:06:23.793  - info: hue.0 (317) skip switch: Hue ambient light sensor 3.alert
          2022-05-10 23:06:23.794  - info: hue.0 (317) skip switch: Hue ambient light sensor 3.tholddark
          2022-05-10 23:06:23.796  - info: hue.0 (317) skip switch: Hue ambient light sensor 3.tholdoffset
          2022-05-10 23:06:23.796  - info: hue.0 (317) skip switch: Hue ambient light sensor 3.ledindication
          2022-05-10 23:06:23.798  - info: hue.0 (317) skip switch: Hue ambient light sensor 3.usertest
          2022-05-10 23:06:23.809  - info: hue.0 (317) skip switch: MotionSensor 39.Companion.status
          2022-05-10 23:06:23.813  - info: hue.0 (317) skip switch: Hue temperature sensor 4.alert
          2022-05-10 23:06:23.814  - info: hue.0 (317) skip switch: Hue temperature sensor 4.ledindication
          2022-05-10 23:06:23.814  - info: hue.0 (317) skip switch: Hue temperature sensor 4.usertest
          2022-05-10 23:06:23.823  - info: hue.0 (317) skip switch: Küche Sensor.alert
          2022-05-10 23:06:23.823  - info: hue.0 (317) skip switch: Küche Sensor.ledindication
          2022-05-10 23:06:23.824  - info: hue.0 (317) skip switch: Küche Sensor.usertest
          2022-05-10 23:06:23.824  - info: hue.0 (317) skip switch: Küche Sensor.sensitivity
          2022-05-10 23:06:23.826  - info: hue.0 (317) skip switch: Küche Sensor.sensitivitymax
          2022-05-10 23:06:23.838  - info: hue.0 (317) skip switch: Hue ambient light sensor 4.alert
          2022-05-10 23:06:23.838  - info: hue.0 (317) skip switch: Hue ambient light sensor 4.tholddark
          2022-05-10 23:06:23.840  - info: hue.0 (317) skip switch: Hue ambient light sensor 4.tholdoffset
          2022-05-10 23:06:23.841  - info: hue.0 (317) skip switch: Hue ambient light sensor 4.ledindication
          2022-05-10 23:06:23.843  - info: hue.0 (317) skip switch: Hue ambient light sensor 4.usertest
          2022-05-10 23:06:23.856  - info: hue.0 (317) skip switch: MotionSensor 46.Companion.status
          2022-05-10 23:06:23.862  - info: hue.0 (317) skip switch: Dimmer Switch 55 SceneCycle.status
          2022-05-10 23:06:23.876  - info: hue.0 (317) skip switch: Dimmer Switch 57 SceneCycle.status
          2022-05-10 23:06:23.918  - info: hue.0 (317) skip switch: Garten Sensor.alert
          2022-05-10 23:06:23.919  - info: hue.0 (317) skip switch: Garten Sensor.sensitivity
          2022-05-10 23:06:23.919  - info: hue.0 (317) skip switch: Garten Sensor.sensitivitymax
          2022-05-10 23:06:23.920  - info: hue.0 (317) skip switch: Garten Sensor.ledindication
          2022-05-10 23:06:23.920  - info: hue.0 (317) skip switch: Garten Sensor.usertest
          2022-05-10 23:06:23.931  - info: hue.0 (317) skip switch: Hue outdoor ambient light sensor.alert
          2022-05-10 23:06:23.932  - info: hue.0 (317) skip switch: Hue outdoor ambient light sensor.tholddark
          2022-05-10 23:06:23.933  - info: hue.0 (317) skip switch: Hue outdoor ambient light sensor.tholdoffset
          2022-05-10 23:06:23.933  - info: hue.0 (317) skip switch: Hue outdoor ambient light sensor.ledindication
          2022-05-10 23:06:23.934  - info: hue.0 (317) skip switch: Hue outdoor ambient light sensor.usertest
          2022-05-10 23:06:23.942  - info: hue.0 (317) skip switch: Hue outdoor temperature sensor 1.alert
          2022-05-10 23:06:23.943  - info: hue.0 (317) skip switch: Hue outdoor temperature sensor 1.ledindication
          2022-05-10 23:06:23.944  - info: hue.0 (317) skip switch: Hue outdoor temperature sensor 1.usertest
          2022-05-10 23:06:23.955  - info: hue.0 (317) skip switch: cycling.status
          2022-05-10 23:06:23.967  - info: hue.0 (317) skip switch: cycleState.status
          2022-05-10 23:06:23.976  - info: hue.0 (317) skip switch: Start and stop.status
          2022-05-10 23:06:23.983  - warn: hue.0 (317) channel "Start_and_stop" already exists, using "Start_and_stop_CLIPGenericStatus" for sensor 130
          2022-05-10 23:06:23.984  - info: hue.0 (317) skip switch: Start and stop CLIPGenericStatus.status
          2022-05-10 23:06:23.990  - info: hue.0 (317) skip switch: dimDirection.status
          2022-05-10 23:06:24.002  - info: hue.0 (317) skip switch: isDimming.status
          2022-05-10 23:06:24.006  - info: hue.0 (317) skip switch: slotState.status
          2022-05-10 23:06:24.010  - warn: hue.0 (317) channel "cycling" already exists, using "cycling_CLIPGenericStatus" for sensor 139
          2022-05-10 23:06:24.014  - info: hue.0 (317) skip switch: cycling CLIPGenericStatus.status
          2022-05-10 23:06:24.022  - info: hue.0 (317) skip switch: Garten Sensor Haustüre.alert
          2022-05-10 23:06:24.023  - info: hue.0 (317) skip switch: Garten Sensor Haustüre.sensitivity
          2022-05-10 23:06:24.023  - info: hue.0 (317) skip switch: Garten Sensor Haustüre.sensitivitymax
          2022-05-10 23:06:24.028  - info: hue.0 (317) skip switch: Garten Sensor Haustüre.ledindication
          2022-05-10 23:06:24.030  - info: hue.0 (317) skip switch: Garten Sensor Haustüre.usertest
          2022-05-10 23:06:24.039  - warn: hue.0 (317) channel "Hue_outdoor_ambient_light_sensor" already exists, using "Hue_outdoor_ambient_light_sensor_ZLLLightLevel" for sensor 141
          2022-05-10 23:06:24.040  - info: hue.0 (317) skip switch: Hue outdoor ambient light sensor ZLLLightLevel.alert
          2022-05-10 23:06:24.040  - info: hue.0 (317) skip switch: Hue outdoor ambient light sensor ZLLLightLevel.tholddark
          2022-05-10 23:06:24.041  - info: hue.0 (317) skip switch: Hue outdoor ambient light sensor ZLLLightLevel.tholdoffset
          2022-05-10 23:06:24.041  - info: hue.0 (317) skip switch: Hue outdoor ambient light sensor ZLLLightLevel.ledindication
          2022-05-10 23:06:24.042  - info: hue.0 (317) skip switch: Hue outdoor ambient light sensor ZLLLightLevel.usertest
          2022-05-10 23:06:24.055  - info: hue.0 (317) skip switch: Hue outdoor temperature sensor 2.alert
          2022-05-10 23:06:24.056  - info: hue.0 (317) skip switch: Hue outdoor temperature sensor 2.ledindication
          2022-05-10 23:06:24.057  - info: hue.0 (317) skip switch: Hue outdoor temperature sensor 2.usertest
          2022-05-10 23:06:24.069  - info: hue.0 (317) skip switch: roomstate.status
          2022-05-10 23:06:24.099  - info: hue.0 (317) skip switch: presenceState.status
          2022-05-10 23:06:24.117  - info: hue.0 (317) skip switch: timeBasedSlotState.status
          2022-05-10 23:06:24.125  - info: hue.0 (317) skip switch: timeBasedCycling.status
          2022-05-10 23:06:24.137  - info: hue.0 (317) skip switch: needToTurnOn.status
          2022-05-10 23:06:24.148  - warn: hue.0 (317) channel "Küche_oben" already exists, using "Küche_oben_ZLLPresence" for sensor 195
          2022-05-10 23:06:24.148  - info: hue.0 (317) skip switch: Küche oben ZLLPresence.alert
          2022-05-10 23:06:24.152  - info: hue.0 (317) skip switch: Küche oben ZLLPresence.sensitivity
          2022-05-10 23:06:24.152  - info: hue.0 (317) skip switch: Küche oben ZLLPresence.sensitivitymax
          2022-05-10 23:06:24.155  - info: hue.0 (317) skip switch: Küche oben ZLLPresence.ledindication
          2022-05-10 23:06:24.163  - info: hue.0 (317) skip switch: Küche oben ZLLPresence.usertest
          2022-05-10 23:06:24.177  - info: hue.0 (317) skip switch: Hue ambient light sensor 5.alert
          2022-05-10 23:06:24.183  - info: hue.0 (317) skip switch: Hue ambient light sensor 5.tholddark
          2022-05-10 23:06:24.184  - info: hue.0 (317) skip switch: Hue ambient light sensor 5.tholdoffset
          2022-05-10 23:06:24.186  - info: hue.0 (317) skip switch: Hue ambient light sensor 5.ledindication
          2022-05-10 23:06:24.188  - info: hue.0 (317) skip switch: Hue ambient light sensor 5.usertest
          2022-05-10 23:06:24.210  - info: hue.0 (317) skip switch: Hue temperature sensor 5.alert
          2022-05-10 23:06:24.212  - info: hue.0 (317) skip switch: Hue temperature sensor 5.ledindication
          2022-05-10 23:06:24.212  - info: hue.0 (317) skip switch: Hue temperature sensor 5.usertest
          2022-05-10 23:06:24.226  - warn: hue.0 (317) channel "presenceState" already exists, using "presenceState_CLIPGenericStatus" for sensor 208
          2022-05-10 23:06:24.229  - info: hue.0 (317) skip switch: presenceState CLIPGenericStatus.status
          2022-05-10 23:06:24.237  - info: hue.0 (317) skip switch: textState.status
          2022-05-10 23:06:24.238  - info: hue.0 (317) created/updated 46 sensor channels
          2022-05-10 23:06:25.002  - info: shelly.0 (287) [CoAP] Device 192.168.178.157 (shellyswitch25 / shellyswitch25-98CDAC38AE0F / SHSW-25#98CDAC38AE0F#1) connected! Polltime set to 15 sec.
          2022-05-10 23:06:25.887  - info: hue.0 (317) created/updated 25 light channels
          2022-05-10 23:06:25.904  - warn: hue.0 (317) channel "Decke" already exists, using "Decke_LightGroup" for group 2
          2022-05-10 23:06:25.928  - warn: hue.0 (317) channel "Küche" already exists, using "Küche_Room" for group 7
          2022-05-10 23:06:25.975  - warn: hue.0 (317) channel "Küche_oben" already exists, using "Küche_oben_Room" for group 14
          2022-05-10 23:06:25.981  - warn: hue.0 (317) channel "Garten" already exists, using "Garten_Room" for group 17
          2022-05-10 23:06:25.991  - warn: hue.0 (317) channel "Custom_group_for_$lights" already exists, using "Custom_group_for_$lights_LightGroup" for group 21
          2022-05-10 23:06:25.993  - info: hue.0 (317) created/updated 17 groups channels
          2022-05-10 23:06:26.037  - info: hue.0 (317) created/updated 184 scenes
          2022-05-10 23:06:26.038  - info: hue.0 (317) creating/updating bridge device
          2022-05-10 23:06:26.083  - info: shelly.1 (332) starting. Version 5.3.2 in /opt/iobroker/node_modules/iobroker.shelly, node: v14.19.1, js-controller: 4.0.15
          2022-05-10 23:06:26.307  - info: shelly.1 (332) Starting in MQTT mode. Listening on 0.0.0.0:1884
          2022-05-10 23:06:26.593  - info: host.buanet-iobroker1 instance system.adapter.discovery.0 started with pid 359
          2022-05-10 23:06:29.326  - info: shelly.0 (287) [CoAP] Device 192.168.180.102 (shellyplug-s / shellyplug-s-16CE7A / SHPLG2-1#16CE7A#1) connected! Polltime set to 15 sec.
          2022-05-10 23:06:29.783  - info: discovery.0 (359) starting. Version 2.7.5 in /opt/iobroker/node_modules/iobroker.discovery, node: v14.19.1, js-controller: 4.0.15
          2022-05-10 23:06:30.540  - info: host.buanet-iobroker1 instance system.adapter.backitup.0 started with pid 375
          2022-05-10 23:06:32.862  - info: shelly.0 (287) [CoAP] Device 192.168.178.183 (shellyswitch25 / shellyswitch25-E8DB84803175 / SHSW-25#E8DB84803175#1) connected! Polltime set to 15 sec.
          2022-05-10 23:06:33.034  - info: backitup.0 (375) starting. Version 2.3.3 in /opt/iobroker/node_modules/iobroker.backitup, node: v14.19.1, js-controller: 4.0.15
          2022-05-10 23:06:33.138  - info: backitup.0 (375) [iobroker] backup was activated at 02:40 every 1 day(s)
          2022-05-10 23:06:34.502  - info: host.buanet-iobroker1 instance system.adapter.web.0 started with pid 390
          2022-05-10 23:06:37.422  - info: web.0 (390) starting. Version 4.2.0 in /opt/iobroker/node_modules/iobroker.web, node: v14.19.1, js-controller: 4.0.15
          2022-05-10 23:06:37.949  - info: web.0 (390) socket.io server listening on port 8082
          2022-05-10 23:06:37.957  - info: alexa2.0 (267) Subscribing to states...
          2022-05-10 23:06:37.964  - info: web.0 (390) http server listening on port 8082
          2022-05-10 23:06:38.497  - info: host.buanet-iobroker1 instance system.adapter.fritzdect.0 started with pid 405
          2022-05-10 23:06:40.608  - info: fritzdect.0 (405) starting. Version 2.2.3 in /opt/iobroker/node_modules/iobroker.fritzdect, node: v14.19.1, js-controller: 4.0.15
          2022-05-10 23:06:40.637  - info: fritzdect.0 (405) fritzdect entered ready
          2022-05-10 23:06:40.669  - info: fritzdect.0 (405) fritzdect uses USER: fbsmarthome
          2022-05-10 23:06:41.484  - info: fritzdect.0 (405) checking user permissions
          2022-05-10 23:06:41.648  - info: fritzdect.0 (405) the rights are : {"Name":"HomeAuto","Access":"2"}
          2022-05-10 23:06:41.649  - info: fritzdect.0 (405) start creating devices/groups
          2022-05-10 23:06:41.756  - info: web.0 (390) ==> Connected system.user.admin from ::ffff:192.168.180.89
          2022-05-10 23:06:41.926  - info: fritzdect.0 (405) CREATE Devices 4
          2022-05-10 23:06:41.980  - info: fritzdect.0 (405) setting up switch 
          2022-05-10 23:06:41.986  - info: fritzdect.0 (405) setting up temperatur 
          2022-05-10 23:06:41.988  - info: fritzdect.0 (405) setting up switch 
          2022-05-10 23:06:42.044  - info: fritzdect.0 (405) setting up temperatur 
          2022-05-10 23:06:42.058  - info: fritzdect.0 (405) setting up thermostat 
          2022-05-10 23:06:42.068  - info: fritzdect.0 (405) setting up powermeter 
          2022-05-10 23:06:42.073  - info: fritzdect.0 (405) setting up temperatur 
          2022-05-10 23:06:42.076  - info: fritzdect.0 (405) setting up powermeter 
          2022-05-10 23:06:42.120  - info: fritzdect.0 (405) setting up simpleonoff
          2022-05-10 23:06:42.121  - info: fritzdect.0 (405) setting up temperatur 
          2022-05-10 23:06:42.129  - info: fritzdect.0 (405) setting up simpleonoff
          2022-05-10 23:06:42.255  - info: fritzdect.0 (405) setting up thermostat nextchange
          2022-05-10 23:06:42.333  - info: fritzdect.0 (405) State value to set for "fritzdect.0.DECT_109710995216.windowopenactivetime" has to be type "number" but received type "string" 
          2022-05-10 23:06:42.372  - info: fritzdect.0 (405) State value to set for "fritzdect.0.DECT_109710995216.boostactivetime" has to be type "number" but received type "string" 
          2022-05-10 23:06:42.454  - info: fritzdect.0 (405) CREATE groups 1
          2022-05-10 23:06:45.518  - info: fritzdect.0 (405) setting up groupinfo 
          2022-05-10 23:06:46.981  - info: fritzdect.0 (405) setting up thermostat 
          2022-05-10 23:06:49.733  - info: host.buanet-iobroker1 instance system.adapter.lg-thinq.0 started with pid 1260
          2022-05-10 23:06:49.738  - info: sonoff.0 (194) Client [Smartmeter] connected with secret 1652216809655_8075
          2022-05-10 23:06:53.875  - info: host.buanet-iobroker1 instance system.adapter.mercedesme.0 started with pid 1484
          2022-05-10 23:06:54.367  - info: host.buanet-iobroker1 instance system.adapter.sourceanalytix.0 started with pid 1516
          2022-05-10 23:06:54.573  - info: fritzdect.0 (405) setting up thermostat nextchange
          2022-05-10 23:06:54.933  - info: fritzdect.0 (405) State value to set for "fritzdect.0.DECT_grpEFC2DD-3CA0C0661.windowopenactivetime" has to be type "number" but received type "string" 
          2022-05-10 23:06:54.972  - info: fritzdect.0 (405) State value to set for "fritzdect.0.DECT_grpEFC2DD-3CA0C0661.boostactivetime" has to be type "number" but received type "string" 
          2022-05-10 23:06:55.099  - info: fritzdect.0 (405) finished creating devices/groups (if any)
          2022-05-10 23:06:55.100  - info: fritzdect.0 (405) start creating templates 
          2022-05-10 23:06:55.555  - info: fritzdect.0 (405) finished creating templates (if any) 
          2022-05-10 23:06:55.558  - info: fritzdect.0 (405) start initial updating devices/groups
          2022-05-10 23:07:00.450  - info: fritzdect.0 (405) finished initial updating devices/groups
          2022-05-10 23:07:00.450  - info: fritzdect.0 (405) going over to cyclic polling, messages to poll activity only in debug-mode 
          2022-05-10 23:07:08.772  - info: web.0 (390) ==> Connected system.user.admin from ::ffff:192.168.180.89
          2022-05-10 23:07:10.386  - info: web.0 (390) ==> Connected system.user.admin from ::ffff:192.168.180.89
          2022-05-10 23:07:14.589  - warn: lg-thinq.0 (1260) slow connection to objects DB. Still waiting ...
          2022-05-10 23:07:17.221  - info: shelly.1 (332) [MQTT] Device 192.168.178.109 (shellyplus1pm / shellyplus1pm-7c87ce64d6d0 / shellyplus1pm#7c87ce64d6d0#1) connected! Polltime set to 5 sec.
          2022-05-10 23:07:17.652  - warn: sourceanalytix.0 (1516) slow connection to objects DB. Still waiting ...
          2022-05-10 23:07:17.705  - info: shelly.1 (332) [MQTT] Device 192.168.180.97 (shellyplus1pm / shellyplus1pm-3c610579db50 / shellyplus1pm#3c610579db50#1) connected! Polltime set to 5 sec.
          2022-05-10 23:07:24.725  - warn: mercedesme.0 (1484) slow connection to objects DB. Still waiting ...
          
          
          apollon77A Offline
          apollon77A Offline
          apollon77
          schrieb am zuletzt editiert von
          #8

          @vo5tr0 STrange ... Log stoppt 23:03:52.694 ... WIe sieht es denn RAMM mäßig aus? Vllt ist da ja was und er Swappt sich zu Tode?

          Beitrag hat geholfen? Votet rechts unten im Beitrag :-) https://paypal.me/Apollon77 / https://github.com/sponsors/Apollon77

          • Debug-Log für Instanz einschalten? Admin -> Instanzen -> Expertenmodus -> Instanz aufklappen - Loglevel ändern
          • Logfiles auf Platte /opt/iobroker/log/… nutzen, Admin schneidet Zeilen ab
          1 Antwort Letzte Antwort
          0
          • Jey CeeJ Jey Cee

            Das die NAS sich aufhängt hat schon mal nichts mit ioBroker zu tun. Die DS sollte den Container Hardware Resourcen mässig Limitieren und da scheint nicht zu passieren. Hier könnte Andre sein Tipp helfen.

            Das die CPU Last des Containers plötzlich auf 100% springt könnte an der Boost Funktion der CPU liegen. Der Taktet normal mit 1.5Ghz und Boostet bis 2.3Ghz. Der Plötzliche Sprung entsteht vielleicht durch das runter Takten der CPU. Wahrscheinlich gibt es da noch einen zweiten Faktor der im selben Augenblick present ist.
            Möglich das die CPU auch nicht mehr schnell genug hoch Taktet, evtl. wegen zu hoher Temperarur.

            Wenn es möglich ist Überwach mal die CPU Frequenz und die CPU Temperatur.

            V Offline
            V Offline
            vo5tr0
            schrieb am zuletzt editiert von
            #9

            @jey-cee & @andre

            Danke für die Tipps, das werde ich mir Mal anschauen. Leider habe ich in dem Moment nur ein paar Sekunden Zeit um noch irgendwas zu tun, bis es wieder weg ist...

            Könnte es eventuell am Arbeitsspeicher hängen? Das war hardwaretechnisch die einzige Änderung, die ich am NAS vorgenommen habe. Ein 4GB Modul von Crucial nachgesteckt.

            apollon77A 1 Antwort Letzte Antwort
            0
            • V vo5tr0

              @jey-cee & @andre

              Danke für die Tipps, das werde ich mir Mal anschauen. Leider habe ich in dem Moment nur ein paar Sekunden Zeit um noch irgendwas zu tun, bis es wieder weg ist...

              Könnte es eventuell am Arbeitsspeicher hängen? Das war hardwaretechnisch die einzige Änderung, die ich am NAS vorgenommen habe. Ein 4GB Modul von Crucial nachgesteckt.

              apollon77A Offline
              apollon77A Offline
              apollon77
              schrieb am zuletzt editiert von
              #10

              @vo5tr0 sagte in Synology NAS hängt sich auf:

              Ein 4GB Modul von Crucial nachgesteckt.

              Auch das wäre ne valide Option meiner (an der Stelle) Laien-Meinung nach :-)

              Beitrag hat geholfen? Votet rechts unten im Beitrag :-) https://paypal.me/Apollon77 / https://github.com/sponsors/Apollon77

              • Debug-Log für Instanz einschalten? Admin -> Instanzen -> Expertenmodus -> Instanz aufklappen - Loglevel ändern
              • Logfiles auf Platte /opt/iobroker/log/… nutzen, Admin schneidet Zeilen ab
              1 Antwort Letzte Antwort
              0
              • V vo5tr0

                @arteck
                Ich hab meine Antwort jetzt bearbeitet. Es liegt definitiv nicht an den Scripten. Habe alle abgeschaltet, aber gerade eben hatte ich wieder das selbe Problem. Die Auslastung ging hoch auf 100%, ich habe sofort den Container abgeschaltet. Das ging auch noch. Kurz gewartet, wieder eingeschaltet und weg war mein NAS. Jetzt ist es wieder nicht mehr erreichbar und muss vom Strom getrennt werden

                Bildschirmfoto 2022-05-10 um 23.42.04.png

                GlasfaserG Online
                GlasfaserG Online
                Glasfaser
                schrieb am zuletzt editiert von
                #11

                @vo5tr0 sagte in Synology NAS hängt sich auf:

                Es liegt definitiv nicht an den Scripten. Habe alle abgeschaltet,

                Auch danach den Container neu gestartet , bzw. mit

                ps auxww|grep io
                

                überprüft , ob Zombies noch laufen .

                Zeige doch mal was du so hast :

                iobroker update -i
                iobroker list instances
                iobroker list adapters
                
                sudo ln -s /usr/bin/node /usr/bin/nodejs
                uname -m && which nodejs node npm && nodejs -v && node -v && npm -v && whoami && pwd && sudo apt update &> /dev/null && sudo apt update && apt policy nodejs
                

                Synology 918+ 16GB - ioBroker in Docker v9 , VISO auf Trekstor Primebook C13 13,3" , Hikvision Domkameras mit Surveillance Station .. CCU RaspberryMatic in Synology VM .. Zigbee CC2538+CC2592 .. Sonoff .. KNX .. Modbus ..

                V 1 Antwort Letzte Antwort
                0
                • GlasfaserG Glasfaser

                  @vo5tr0 sagte in Synology NAS hängt sich auf:

                  Es liegt definitiv nicht an den Scripten. Habe alle abgeschaltet,

                  Auch danach den Container neu gestartet , bzw. mit

                  ps auxww|grep io
                  

                  überprüft , ob Zombies noch laufen .

                  Zeige doch mal was du so hast :

                  iobroker update -i
                  iobroker list instances
                  iobroker list adapters
                  
                  sudo ln -s /usr/bin/node /usr/bin/nodejs
                  uname -m && which nodejs node npm && nodejs -v && node -v && npm -v && whoami && pwd && sudo apt update &> /dev/null && sudo apt update && apt policy nodejs
                  
                  V Offline
                  V Offline
                  vo5tr0
                  schrieb am zuletzt editiert von
                  #12

                  @glasfaser

                  Nein, den Container habe ich danach nicht neugestartet, wusste nicht, dass das nötig ist :)

                  root@buanet-iobroker1:/opt/iobroker# iobroker update -i                                                                   
                  Used repository: stable                                                                                                   
                  Adapter    "admin"        : 5.3.8    , installed 5.3.8                                                                    
                  Adapter    "alexa2"       : 3.11.2   , installed 3.11.2                                                                   
                  Adapter    "backitup"     : 2.4.6    , installed 2.4.6                                                                    
                  Adapter    "discovery"    : 3.0.3    , installed 3.0.3                                                                    
                  Adapter    "dysonairpurifier": 2.5.1 , installed 2.5.1                                                                    
                  Adapter    "flot"         : 1.10.7   , installed 1.10.7                                                                   
                  Adapter    "fritzdect"    : 2.2.3    , installed 2.2.3                                                                    
                  Adapter    "history"      : 1.11.1   , installed 1.11.1                                                                   
                  Adapter    "hue"          : 3.6.5    , installed 3.6.5                                                                    
                  Adapter    "iot"          : 1.11.4   , installed 1.11.4                                                                   
                  Adapter    "javascript"   : 5.2.21   , installed 5.2.21                                                                   
                  Controller "js-controller": 4.0.23   , installed 4.0.15 [Updatable]                                                       
                  Adapter    "lg-thinq"     : 0.0.7    , installed 0.0.7                                                                    
                  Adapter    "mercedesme"   : 0.0.56   , installed 0.0.56                                                                   
                  Adapter    "meross"       : 1.10.5   , installed 1.10.5                                                                   
                  Adapter    "mihome"       : 1.4.0    , installed 1.4.0                                                                    
                  Adapter    "ocpp"         : 0.4.0    , installed 0.4.0                                                                    
                  Adapter    "ping"         : 1.5.3    , installed 1.5.3                                                                    
                  Adapter    "radar2"       : 2.0.3    , installed 2.0.3                                                                    
                  Adapter    "shelly"       : 5.3.2    , installed 5.3.2                                                                    
                  Adapter    "simple-api"   : 2.6.4    , installed 2.6.5                                                                    
                  Adapter    "socketio"     : 4.2.0    , installed 4.2.0                                                                    
                  Adapter    "sonoff"       : 2.5.1    , installed 2.5.1                                                                    
                  Adapter    "telegram"     : 1.12.2   , installed 1.12.2                                                                   
                  Adapter    "text2command" : 2.2.1    , installed 2.2.1                                                                    
                  Adapter    "web"          : 4.2.3    , installed 4.2.3                                                                    
                  Adapter    "ws"           : 1.2.0    , installed 1.3.0  
                  
                  root@buanet-iobroker1:/opt/iobroker# iobroker list instances                                                              
                  + system.adapter.admin.0                  : admin                 : buanet-iobroker1                         -  enabled, p
                  ort: 8081, bind: 0.0.0.0, run as: admin                                                                                   
                  + system.adapter.alexa2.0                 : alexa2                : buanet-iobroker1                         -  enabled   
                  + system.adapter.alexa2.1                 : alexa2                : buanet-iobroker1                         -  enabled   
                  + system.adapter.backitup.0               : backitup              : buanet-iobroker1                         -  enabled   
                  + system.adapter.discovery.0              : discovery             : buanet-iobroker1                         -  enabled   
                    system.adapter.dysonairpurifier.0       : dysonairpurifier      : buanet-iobroker1                         - disabled   
                    system.adapter.dysonairpurifier.1       : dysonairpurifier      : buanet-iobroker1                         - disabled   
                    system.adapter.flot.0                   : flot                  : buanet-iobroker1                         -  enabled   
                  + system.adapter.fritzdect.0              : fritzdect             : buanet-iobroker1                         -  enabled   
                  + system.adapter.history.0                : history               : buanet-iobroker1                         -  enabled   
                    system.adapter.hue.0                    : hue                   : buanet-iobroker1                         - disabled, p
                  ort: 443                                                                                                                  
                    system.adapter.iot.0                    : iot                   : buanet-iobroker1                         - disabled   
                  + system.adapter.javascript.0             : javascript            : buanet-iobroker1                         -  enabled   
                  + system.adapter.lg-thinq.0               : lg-thinq              : buanet-iobroker1                         -  enabled   
                  + system.adapter.mercedesme.0             : mercedesme            : buanet-iobroker1                         -  enabled   
                  + system.adapter.meross.0                 : meross                : buanet-iobroker1                         -  enabled   
                    system.adapter.ocpp.0                   : ocpp                  : buanet-iobroker1                         - disabled, p
                  ort: 9220                                                                                                                 
                    system.adapter.ping.0                   : ping                  : buanet-iobroker1                         - disabled   
                    system.adapter.radar2.0                 : radar2                : buanet-iobroker1                         - disabled   
                  + system.adapter.shelly.0                 : shelly                : buanet-iobroker1                         -  enabled, p
                  ort: 1885, bind: 0.0.0.0                                                                                                  
                  + system.adapter.shelly.1                 : shelly                : buanet-iobroker1                         -  enabled, p
                  ort: 1884, bind: 0.0.0.0                                                                                                  
                  + system.adapter.sonoff.0                 : sonoff                : buanet-iobroker1                         -  enabled, p
                  ort: 1883, bind: 0.0.0.0                                                                                                  
                  + system.adapter.sourceanalytix.0         : sourceanalytix        : buanet-iobroker1                         -  enabled   
                    system.adapter.switchbot-hub.0          : switchbot-hub         : buanet-iobroker1                         - disabled   
                  + system.adapter.telegram.0               : telegram              : buanet-iobroker1                         -  enabled, p
                  ort: 8443, bind: 0.0.0.0                                                                                                  
                    system.adapter.text2command.0           : text2command          : buanet-iobroker1                         - disabled   
                  + system.adapter.web.0                    : web                   : buanet-iobroker1                         -  enabled, p
                  ort: 8082, bind: 0.0.0.0, run as: admin                                                                                   
                                                                                                                                            
                  + instance is alive                  
                  
                  root@buanet-iobroker1:/opt/iobroker# iobroker list adapters                                                               
                  system.adapter.admin                   : admin          - v5.3.8                                                          
                  system.adapter.alexa2                  : alexa2         - v3.11.2                                                         
                  system.adapter.backitup                : backitup       - v2.4.6                                                          
                  system.adapter.discovery               : discovery      - v3.0.3                                                          
                  system.adapter.dysonairpurifier        : dysonairpurifier - v2.5.1                                                        
                  system.adapter.flot                    : flot           - v1.10.7                                                         
                  system.adapter.fritzdect               : fritzdect      - v2.2.3                                                          
                  system.adapter.history                 : history        - v1.11.1                                                         
                  system.adapter.hue                     : hue            - v3.6.5                                                          
                  system.adapter.iot                     : iot            - v1.11.4                                                         
                  system.adapter.javascript              : javascript     - v5.2.21                                                         
                  system.adapter.lg-thinq                : lg-thinq       - v0.0.7                                                          
                  system.adapter.mercedesme              : mercedesme     - v0.0.56                                                         
                  system.adapter.meross                  : meross         - v1.10.5                                                         
                  system.adapter.mihome                  : mihome         - v1.4.0                                                          
                  system.adapter.ocpp                    : ocpp           - v0.4.0                                                          
                  system.adapter.ping                    : ping           - v1.5.3                                                          
                  system.adapter.radar2                  : radar2         - v2.0.3                                                          
                  system.adapter.shelly                  : shelly         - v5.3.2                                                          
                  system.adapter.sonoff                  : sonoff         - v2.5.1                                                          
                  system.adapter.sourceanalytix          : sourceanalytix - v0.4.14                                                         
                  system.adapter.switchbot-hub           : switchbot-hub  - v0.1.2                                                          
                  system.adapter.telegram                : telegram       - v1.12.2                                                         
                  system.adapter.text2command            : text2command   - v2.2.1                                                          
                  system.adapter.web                     : web            - v4.2.3                                                          
                  
                  
                  root@buanet-iobroker1:/opt/iobroker# sudo ln -s /usr/bin/node /usr/bin/nodejs                                             
                  sudo: unable to resolve host buanet-iobroker1: Name or service not known                                                  
                  ln: failed to create symbolic link '/usr/bin/nodejs': File exists  
                  
                  root@buanet-iobroker1:/opt/iobroker# uname -m && which nodejs node npm && nodejs -v && node -v && npm -v && whoami && pwd 
                  && sudo apt update &> /dev/null && sudo apt update && apt policy nodejs                                                   
                  x86_64                                                                                                                    
                  /usr/bin/nodejs                                                                                                           
                  /usr/bin/node                                                                                                             
                  /usr/bin/npm                                                                                                              
                  v14.19.1                                                                                                                  
                  v14.19.1                                                                                                                  
                  sudo: unable to resolve host buanet-iobroker1: Name or service not known                                                  
                  6.14.16                                                                                                                   
                  root                                                                                                                      
                  /opt/iobroker                                                                                                             
                  sudo: unable to resolve host buanet-iobroker1: Name or service not known                                                  
                  Hit:1 http://deb.debian.org/debian bullseye InRelease                                                                     
                  Hit:2 http://deb.debian.org/debian bullseye-updates InRelease                                                             
                  Hit:3 http://security.debian.org/debian-security bullseye-security InRelease                                              
                  Hit:4 https://deb.nodesource.com/node_14.x bullseye InRelease                                                             
                  Reading package lists... Done                                                                                             
                  Building dependency tree... Done                                                                                          
                  Reading state information... Done                                                                                         
                  5 packages can be upgraded. Run 'apt list --upgradable' to see them.                                                      
                  nodejs:                                                                                                                   
                    Installed: 14.19.1-deb-1nodesource1                                                                                     
                    Candidate: 14.19.2-deb-1nodesource1                                                                                     
                    Version table:                                                                                                          
                       14.19.2-deb-1nodesource1 500                                                                                         
                          500 https://deb.nodesource.com/node_14.x bullseye/main amd64 Packages                                             
                   *** 14.19.1-deb-1nodesource1 100                                                                                         
                          100 /var/lib/dpkg/status                                                                                          
                       12.22.5~dfsg-2~11u1 500                                                                                              
                          500 http://deb.debian.org/debian bullseye/main amd64 Packages                                                     
                          500 http://security.debian.org/debian-security bullseye-security/main amd64 Packages 
                  
                  
                  apollon77A 1 Antwort Letzte Antwort
                  0
                  • V vo5tr0

                    @glasfaser

                    Nein, den Container habe ich danach nicht neugestartet, wusste nicht, dass das nötig ist :)

                    root@buanet-iobroker1:/opt/iobroker# iobroker update -i                                                                   
                    Used repository: stable                                                                                                   
                    Adapter    "admin"        : 5.3.8    , installed 5.3.8                                                                    
                    Adapter    "alexa2"       : 3.11.2   , installed 3.11.2                                                                   
                    Adapter    "backitup"     : 2.4.6    , installed 2.4.6                                                                    
                    Adapter    "discovery"    : 3.0.3    , installed 3.0.3                                                                    
                    Adapter    "dysonairpurifier": 2.5.1 , installed 2.5.1                                                                    
                    Adapter    "flot"         : 1.10.7   , installed 1.10.7                                                                   
                    Adapter    "fritzdect"    : 2.2.3    , installed 2.2.3                                                                    
                    Adapter    "history"      : 1.11.1   , installed 1.11.1                                                                   
                    Adapter    "hue"          : 3.6.5    , installed 3.6.5                                                                    
                    Adapter    "iot"          : 1.11.4   , installed 1.11.4                                                                   
                    Adapter    "javascript"   : 5.2.21   , installed 5.2.21                                                                   
                    Controller "js-controller": 4.0.23   , installed 4.0.15 [Updatable]                                                       
                    Adapter    "lg-thinq"     : 0.0.7    , installed 0.0.7                                                                    
                    Adapter    "mercedesme"   : 0.0.56   , installed 0.0.56                                                                   
                    Adapter    "meross"       : 1.10.5   , installed 1.10.5                                                                   
                    Adapter    "mihome"       : 1.4.0    , installed 1.4.0                                                                    
                    Adapter    "ocpp"         : 0.4.0    , installed 0.4.0                                                                    
                    Adapter    "ping"         : 1.5.3    , installed 1.5.3                                                                    
                    Adapter    "radar2"       : 2.0.3    , installed 2.0.3                                                                    
                    Adapter    "shelly"       : 5.3.2    , installed 5.3.2                                                                    
                    Adapter    "simple-api"   : 2.6.4    , installed 2.6.5                                                                    
                    Adapter    "socketio"     : 4.2.0    , installed 4.2.0                                                                    
                    Adapter    "sonoff"       : 2.5.1    , installed 2.5.1                                                                    
                    Adapter    "telegram"     : 1.12.2   , installed 1.12.2                                                                   
                    Adapter    "text2command" : 2.2.1    , installed 2.2.1                                                                    
                    Adapter    "web"          : 4.2.3    , installed 4.2.3                                                                    
                    Adapter    "ws"           : 1.2.0    , installed 1.3.0  
                    
                    root@buanet-iobroker1:/opt/iobroker# iobroker list instances                                                              
                    + system.adapter.admin.0                  : admin                 : buanet-iobroker1                         -  enabled, p
                    ort: 8081, bind: 0.0.0.0, run as: admin                                                                                   
                    + system.adapter.alexa2.0                 : alexa2                : buanet-iobroker1                         -  enabled   
                    + system.adapter.alexa2.1                 : alexa2                : buanet-iobroker1                         -  enabled   
                    + system.adapter.backitup.0               : backitup              : buanet-iobroker1                         -  enabled   
                    + system.adapter.discovery.0              : discovery             : buanet-iobroker1                         -  enabled   
                      system.adapter.dysonairpurifier.0       : dysonairpurifier      : buanet-iobroker1                         - disabled   
                      system.adapter.dysonairpurifier.1       : dysonairpurifier      : buanet-iobroker1                         - disabled   
                      system.adapter.flot.0                   : flot                  : buanet-iobroker1                         -  enabled   
                    + system.adapter.fritzdect.0              : fritzdect             : buanet-iobroker1                         -  enabled   
                    + system.adapter.history.0                : history               : buanet-iobroker1                         -  enabled   
                      system.adapter.hue.0                    : hue                   : buanet-iobroker1                         - disabled, p
                    ort: 443                                                                                                                  
                      system.adapter.iot.0                    : iot                   : buanet-iobroker1                         - disabled   
                    + system.adapter.javascript.0             : javascript            : buanet-iobroker1                         -  enabled   
                    + system.adapter.lg-thinq.0               : lg-thinq              : buanet-iobroker1                         -  enabled   
                    + system.adapter.mercedesme.0             : mercedesme            : buanet-iobroker1                         -  enabled   
                    + system.adapter.meross.0                 : meross                : buanet-iobroker1                         -  enabled   
                      system.adapter.ocpp.0                   : ocpp                  : buanet-iobroker1                         - disabled, p
                    ort: 9220                                                                                                                 
                      system.adapter.ping.0                   : ping                  : buanet-iobroker1                         - disabled   
                      system.adapter.radar2.0                 : radar2                : buanet-iobroker1                         - disabled   
                    + system.adapter.shelly.0                 : shelly                : buanet-iobroker1                         -  enabled, p
                    ort: 1885, bind: 0.0.0.0                                                                                                  
                    + system.adapter.shelly.1                 : shelly                : buanet-iobroker1                         -  enabled, p
                    ort: 1884, bind: 0.0.0.0                                                                                                  
                    + system.adapter.sonoff.0                 : sonoff                : buanet-iobroker1                         -  enabled, p
                    ort: 1883, bind: 0.0.0.0                                                                                                  
                    + system.adapter.sourceanalytix.0         : sourceanalytix        : buanet-iobroker1                         -  enabled   
                      system.adapter.switchbot-hub.0          : switchbot-hub         : buanet-iobroker1                         - disabled   
                    + system.adapter.telegram.0               : telegram              : buanet-iobroker1                         -  enabled, p
                    ort: 8443, bind: 0.0.0.0                                                                                                  
                      system.adapter.text2command.0           : text2command          : buanet-iobroker1                         - disabled   
                    + system.adapter.web.0                    : web                   : buanet-iobroker1                         -  enabled, p
                    ort: 8082, bind: 0.0.0.0, run as: admin                                                                                   
                                                                                                                                              
                    + instance is alive                  
                    
                    root@buanet-iobroker1:/opt/iobroker# iobroker list adapters                                                               
                    system.adapter.admin                   : admin          - v5.3.8                                                          
                    system.adapter.alexa2                  : alexa2         - v3.11.2                                                         
                    system.adapter.backitup                : backitup       - v2.4.6                                                          
                    system.adapter.discovery               : discovery      - v3.0.3                                                          
                    system.adapter.dysonairpurifier        : dysonairpurifier - v2.5.1                                                        
                    system.adapter.flot                    : flot           - v1.10.7                                                         
                    system.adapter.fritzdect               : fritzdect      - v2.2.3                                                          
                    system.adapter.history                 : history        - v1.11.1                                                         
                    system.adapter.hue                     : hue            - v3.6.5                                                          
                    system.adapter.iot                     : iot            - v1.11.4                                                         
                    system.adapter.javascript              : javascript     - v5.2.21                                                         
                    system.adapter.lg-thinq                : lg-thinq       - v0.0.7                                                          
                    system.adapter.mercedesme              : mercedesme     - v0.0.56                                                         
                    system.adapter.meross                  : meross         - v1.10.5                                                         
                    system.adapter.mihome                  : mihome         - v1.4.0                                                          
                    system.adapter.ocpp                    : ocpp           - v0.4.0                                                          
                    system.adapter.ping                    : ping           - v1.5.3                                                          
                    system.adapter.radar2                  : radar2         - v2.0.3                                                          
                    system.adapter.shelly                  : shelly         - v5.3.2                                                          
                    system.adapter.sonoff                  : sonoff         - v2.5.1                                                          
                    system.adapter.sourceanalytix          : sourceanalytix - v0.4.14                                                         
                    system.adapter.switchbot-hub           : switchbot-hub  - v0.1.2                                                          
                    system.adapter.telegram                : telegram       - v1.12.2                                                         
                    system.adapter.text2command            : text2command   - v2.2.1                                                          
                    system.adapter.web                     : web            - v4.2.3                                                          
                    
                    
                    root@buanet-iobroker1:/opt/iobroker# sudo ln -s /usr/bin/node /usr/bin/nodejs                                             
                    sudo: unable to resolve host buanet-iobroker1: Name or service not known                                                  
                    ln: failed to create symbolic link '/usr/bin/nodejs': File exists  
                    
                    root@buanet-iobroker1:/opt/iobroker# uname -m && which nodejs node npm && nodejs -v && node -v && npm -v && whoami && pwd 
                    && sudo apt update &> /dev/null && sudo apt update && apt policy nodejs                                                   
                    x86_64                                                                                                                    
                    /usr/bin/nodejs                                                                                                           
                    /usr/bin/node                                                                                                             
                    /usr/bin/npm                                                                                                              
                    v14.19.1                                                                                                                  
                    v14.19.1                                                                                                                  
                    sudo: unable to resolve host buanet-iobroker1: Name or service not known                                                  
                    6.14.16                                                                                                                   
                    root                                                                                                                      
                    /opt/iobroker                                                                                                             
                    sudo: unable to resolve host buanet-iobroker1: Name or service not known                                                  
                    Hit:1 http://deb.debian.org/debian bullseye InRelease                                                                     
                    Hit:2 http://deb.debian.org/debian bullseye-updates InRelease                                                             
                    Hit:3 http://security.debian.org/debian-security bullseye-security InRelease                                              
                    Hit:4 https://deb.nodesource.com/node_14.x bullseye InRelease                                                             
                    Reading package lists... Done                                                                                             
                    Building dependency tree... Done                                                                                          
                    Reading state information... Done                                                                                         
                    5 packages can be upgraded. Run 'apt list --upgradable' to see them.                                                      
                    nodejs:                                                                                                                   
                      Installed: 14.19.1-deb-1nodesource1                                                                                     
                      Candidate: 14.19.2-deb-1nodesource1                                                                                     
                      Version table:                                                                                                          
                         14.19.2-deb-1nodesource1 500                                                                                         
                            500 https://deb.nodesource.com/node_14.x bullseye/main amd64 Packages                                             
                     *** 14.19.1-deb-1nodesource1 100                                                                                         
                            100 /var/lib/dpkg/status                                                                                          
                         12.22.5~dfsg-2~11u1 500                                                                                              
                            500 http://deb.debian.org/debian bullseye/main amd64 Packages                                                     
                            500 http://security.debian.org/debian-security bullseye-security/main amd64 Packages 
                    
                    
                    apollon77A Offline
                    apollon77A Offline
                    apollon77
                    schrieb am zuletzt editiert von
                    #13

                    @vo5tr0 In jedem Fall mal sicherheitshalber controller updated. sicher ist sicher

                    Beitrag hat geholfen? Votet rechts unten im Beitrag :-) https://paypal.me/Apollon77 / https://github.com/sponsors/Apollon77

                    • Debug-Log für Instanz einschalten? Admin -> Instanzen -> Expertenmodus -> Instanz aufklappen - Loglevel ändern
                    • Logfiles auf Platte /opt/iobroker/log/… nutzen, Admin schneidet Zeilen ab
                    GlasfaserG 1 Antwort Letzte Antwort
                    0
                    • V Offline
                      V Offline
                      vo5tr0
                      schrieb am zuletzt editiert von
                      #14

                      Ich habe entweder den History Adapter oder Flot in Verdacht. Was auch immer das da treibt, aber gerade wollte ich über Flot das Diagramm zum Stromverbrauch abrufen und plötzlich war die Auslastung wieder bei 100%. Dieses Mal hat es sich zum Glück aber nach ein paar Minuten wieder gefangen.

                      5f9d8f41-f8a3-4534-87af-55030b4b1196-image.png

                      apollon77A GlasfaserG 2 Antworten Letzte Antwort
                      0
                      • V vo5tr0

                        Ich habe entweder den History Adapter oder Flot in Verdacht. Was auch immer das da treibt, aber gerade wollte ich über Flot das Diagramm zum Stromverbrauch abrufen und plötzlich war die Auslastung wieder bei 100%. Dieses Mal hat es sich zum Glück aber nach ein paar Minuten wieder gefangen.

                        5f9d8f41-f8a3-4534-87af-55030b4b1196-image.png

                        apollon77A Offline
                        apollon77A Offline
                        apollon77
                        schrieb am zuletzt editiert von
                        #15

                        @vo5tr0 Was macht denn "dieses Diagramm"?

                        HIntergrund: History startet für jede Datenanfrage einen weiteren Prozess damit der Adapterprozess nicht blockiert wird. Dann werden die Daten aus den JSON Files gelesen - je nach Dauer kann das einigen sein und die werden dann verarbeitet.

                        Beitrag hat geholfen? Votet rechts unten im Beitrag :-) https://paypal.me/Apollon77 / https://github.com/sponsors/Apollon77

                        • Debug-Log für Instanz einschalten? Admin -> Instanzen -> Expertenmodus -> Instanz aufklappen - Loglevel ändern
                        • Logfiles auf Platte /opt/iobroker/log/… nutzen, Admin schneidet Zeilen ab
                        V 1 Antwort Letzte Antwort
                        0
                        • V vo5tr0

                          Ich habe entweder den History Adapter oder Flot in Verdacht. Was auch immer das da treibt, aber gerade wollte ich über Flot das Diagramm zum Stromverbrauch abrufen und plötzlich war die Auslastung wieder bei 100%. Dieses Mal hat es sich zum Glück aber nach ein paar Minuten wieder gefangen.

                          5f9d8f41-f8a3-4534-87af-55030b4b1196-image.png

                          GlasfaserG Online
                          GlasfaserG Online
                          Glasfaser
                          schrieb am zuletzt editiert von Glasfaser
                          #16

                          @vo5tr0 sagte in Synology NAS hängt sich auf:

                          und plötzlich war die Auslastung wieder bei 100%

                          bitte nicht so auf die visuelle Anzeige schauen .. das ist nur eine grobe Anzeige .

                          Ich habe auch eine Synology DS918+ , mit 16 Gb und habe manchmal den selben Effekt " Lichtspiel " im ioBroker Container , jenachdem .... was mit ioBroker gerade gemacht wird !

                          Wenn ich das bei mir immer beobachen würde bei jedem Spriptstart / Adapterstart usw. , wäre das unsinnig .......

                          Ausschlaggebend ist das Prozess Log , aber das sieht bei dir gerade harmlos aus ...

                          Du kannst auch hier die Filteranzeige setzen ....

                          52aaf3f3-530f-4817-bd14-9087f4004cf0-grafik.png

                          EDIT:

                          IO Broker läuft bei mir auf meiner Synology DS918+ im Docker Container.

                          und was hast du sonst noch nebenbei auf deiner Synology laufen !?

                          Synology 918+ 16GB - ioBroker in Docker v9 , VISO auf Trekstor Primebook C13 13,3" , Hikvision Domkameras mit Surveillance Station .. CCU RaspberryMatic in Synology VM .. Zigbee CC2538+CC2592 .. Sonoff .. KNX .. Modbus ..

                          1 Antwort Letzte Antwort
                          0
                          • apollon77A apollon77

                            @vo5tr0 Was macht denn "dieses Diagramm"?

                            HIntergrund: History startet für jede Datenanfrage einen weiteren Prozess damit der Adapterprozess nicht blockiert wird. Dann werden die Daten aus den JSON Files gelesen - je nach Dauer kann das einigen sein und die werden dann verarbeitet.

                            V Offline
                            V Offline
                            vo5tr0
                            schrieb am zuletzt editiert von
                            #17

                            @apollon77

                            Das Diagramm zeigt mir 3 Werte an: Den aktuellen Stromverbrauch + Zählerstand über den Sonoff Adapter + Was gerade von der Balkonanlage eingespeist wird über den Shelly Adapter
                            Bildschirmfoto 2022-05-13 um 08.32.14.png

                            @Glasfaser
                            klar, dass es mal kurz auf 100% springt ist normal. Aber in dem Fall bleibt es halt da für eine längere Zeit. Im Docker Fenster und gleichzeitig auch die Auslastung vom NAS selbst.

                            Neben iobroker habe ich noch Plex (kein Docker container), Portainer und Paperless laufen.

                            Das Teil hängt sich auch nicht irgendwann in der Nacht auf oder so, sondern immer dann wenn ich kurz vorher das Diagramm aufgerufen habe. Merken tue ich es auch daran, dass das Diagramm nicht mehr lädt oder wenn der Tab im Hintergrund noch offen war, alles voll mit kreuz und quer laufenden Linien ist. Dann habe ich noch kurz Zeit mich auf der DS Oberfläche umzuschauen. Ich weiß nicht, ob es sicher am Diagramm liegt oder nicht, aber irgendwas das ich in dem Moment mache, muss das Problem auslösen.

                            apollon77A 1 Antwort Letzte Antwort
                            0
                            • V vo5tr0

                              @apollon77

                              Das Diagramm zeigt mir 3 Werte an: Den aktuellen Stromverbrauch + Zählerstand über den Sonoff Adapter + Was gerade von der Balkonanlage eingespeist wird über den Shelly Adapter
                              Bildschirmfoto 2022-05-13 um 08.32.14.png

                              @Glasfaser
                              klar, dass es mal kurz auf 100% springt ist normal. Aber in dem Fall bleibt es halt da für eine längere Zeit. Im Docker Fenster und gleichzeitig auch die Auslastung vom NAS selbst.

                              Neben iobroker habe ich noch Plex (kein Docker container), Portainer und Paperless laufen.

                              Das Teil hängt sich auch nicht irgendwann in der Nacht auf oder so, sondern immer dann wenn ich kurz vorher das Diagramm aufgerufen habe. Merken tue ich es auch daran, dass das Diagramm nicht mehr lädt oder wenn der Tab im Hintergrund noch offen war, alles voll mit kreuz und quer laufenden Linien ist. Dann habe ich noch kurz Zeit mich auf der DS Oberfläche umzuschauen. Ich weiß nicht, ob es sicher am Diagramm liegt oder nicht, aber irgendwas das ich in dem Moment mache, muss das Problem auslösen.

                              apollon77A Offline
                              apollon77A Offline
                              apollon77
                              schrieb am zuletzt editiert von apollon77
                              #18

                              @vo5tr0 Aber dann sollten da maximal 3 (!) Prozesse kurz laufen (auch weils nur 1 Tag ist) und nicht so viele ... es sei denn du hast das Chart auf gefühlten 10 Tabs offen :-)

                              Vllt mal Adapzter debug log aktivieren und schauen was so zu sehen ist

                              Beitrag hat geholfen? Votet rechts unten im Beitrag :-) https://paypal.me/Apollon77 / https://github.com/sponsors/Apollon77

                              • Debug-Log für Instanz einschalten? Admin -> Instanzen -> Expertenmodus -> Instanz aufklappen - Loglevel ändern
                              • Logfiles auf Platte /opt/iobroker/log/… nutzen, Admin schneidet Zeilen ab
                              V 1 Antwort Letzte Antwort
                              0
                              • apollon77A apollon77

                                @vo5tr0 In jedem Fall mal sicherheitshalber controller updated. sicher ist sicher

                                GlasfaserG Online
                                GlasfaserG Online
                                Glasfaser
                                schrieb am zuletzt editiert von
                                #19

                                @vo5tr0

                                @apollon77 sagte in Synology NAS hängt sich auf:

                                @vo5tr0 In jedem Fall mal sicherheitshalber controller updated. sicher ist sicher

                                Hast du das gemacht !?

                                Synology 918+ 16GB - ioBroker in Docker v9 , VISO auf Trekstor Primebook C13 13,3" , Hikvision Domkameras mit Surveillance Station .. CCU RaspberryMatic in Synology VM .. Zigbee CC2538+CC2592 .. Sonoff .. KNX .. Modbus ..

                                1 Antwort Letzte Antwort
                                0
                                • apollon77A apollon77

                                  @vo5tr0 Aber dann sollten da maximal 3 (!) Prozesse kurz laufen (auch weils nur 1 Tag ist) und nicht so viele ... es sei denn du hast das Chart auf gefühlten 10 Tabs offen :-)

                                  Vllt mal Adapzter debug log aktivieren und schauen was so zu sehen ist

                                  V Offline
                                  V Offline
                                  vo5tr0
                                  schrieb am zuletzt editiert von
                                  #20

                                  @apollon77

                                  Das denke ich mir auch :)
                                  Nein, das Chart ist maximal auf zwei Tabs offen (Einmal der Editor, einmal Vollbild)

                                  Dann schaue ich Mal, was das debug Log spricht.

                                  @Glasfaser
                                  Ja, ist aktuell

                                  V 1 Antwort Letzte Antwort
                                  0
                                  • V vo5tr0

                                    @apollon77

                                    Das denke ich mir auch :)
                                    Nein, das Chart ist maximal auf zwei Tabs offen (Einmal der Editor, einmal Vollbild)

                                    Dann schaue ich Mal, was das debug Log spricht.

                                    @Glasfaser
                                    Ja, ist aktuell

                                    V Offline
                                    V Offline
                                    vo5tr0
                                    schrieb am zuletzt editiert von
                                    #21

                                    Ich denke es ist noch zu früh das zu sagen, aber bisher sieht es super aus :)

                                    Dinge, die ich gemacht habe:

                                    • Docker Container CPU Priorität auf Low gestellt
                                    • Update aller io Broker Komponenten
                                    • Flot Diagramm Live Update deaktiviert
                                    • Daten nicht mehr direkt vom Adapter genommen, sondern per Script in eigene Datenpunkte geschrieben und von da aus geloggt

                                    Seit dem habe ich den History Prozess kaum bis gar nicht mehr in der Liste gesehen und die Auslastung war auch durchgehend sehr niedrig. Also mindestens eine der Aktionen hat geholfen :)

                                    1 Antwort Letzte Antwort
                                    1

                                    Hey! Du scheinst an dieser Unterhaltung interessiert zu sein, hast aber noch kein Konto.

                                    Hast du es satt, bei jedem Besuch durch die gleichen Beiträge zu scrollen? Wenn du dich für ein Konto anmeldest, kommst du immer genau dorthin zurück, wo du zuvor warst, und kannst dich über neue Antworten benachrichtigen lassen (entweder per E-Mail oder Push-Benachrichtigung). Du kannst auch Lesezeichen speichern und Beiträge positiv bewerten, um anderen Community-Mitgliedern deine Wertschätzung zu zeigen.

                                    Mit deinem Input könnte dieser Beitrag noch besser werden 💗

                                    Registrieren Anmelden
                                    Antworten
                                    • In einem neuen Thema antworten
                                    Anmelden zum Antworten
                                    • Älteste zuerst
                                    • Neuste zuerst
                                    • Meiste Stimmen


                                    Support us

                                    ioBroker
                                    Community Adapters
                                    Donate
                                    FAQ Cloud / IOT
                                    HowTo: Node.js-Update
                                    HowTo: Backup/Restore
                                    Downloads
                                    BLOG

                                    503

                                    Online

                                    32.8k

                                    Benutzer

                                    82.7k

                                    Themen

                                    1.3m

                                    Beiträge
                                    Community
                                    Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen | Einwilligungseinstellungen
                                    ioBroker Community 2014-2025
                                    logo
                                    • Anmelden

                                    • Du hast noch kein Konto? Registrieren

                                    • Anmelden oder registrieren, um zu suchen
                                    • Erster Beitrag
                                      Letzter Beitrag
                                    0
                                    • Home
                                    • Aktuell
                                    • Tags
                                    • Ungelesen 0
                                    • Kategorien
                                    • Unreplied
                                    • Beliebt
                                    • GitHub
                                    • Docu
                                    • Hilfe