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. admin interface leer

NEWS

  • Neuer ioBroker-Blog online: Monatsrückblick März/April 2026
    BluefoxB
    Bluefox
    8
    1
    1.8k

  • Verwendung von KI bitte immer deutlich kennzeichnen
    HomoranH
    Homoran
    11
    1
    751

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

admin interface leer

Geplant Angeheftet Gesperrt Verschoben ioBroker Allgemein
27 Beiträge 3 Kommentatoren 2.3k Aufrufe 3 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.
  • stephan1827S stephan1827

    @glasfaser Habe den port von admin auch auf 8081 gesetzt aber dann geht weder die Visu noch das admmin interface. Ich bin nicht mehr sicher warum ich den Port geändert habe aber das ist schon ewig so.

    2022-07-23 17:09:49.538  - info: admin.0 (420) Got terminate signal TERMINATE_YOURSELF
    2022-07-23 17:09:49.540  - info: admin.0 (420) terminating http server on port 8081
    2022-07-23 17:09:49.540  - info: admin.0 (420) terminating
    2022-07-23 17:09:49.541  - info: admin.0 (420) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
    2022-07-23 17:09:49.578  - info: host.iobroker stopInstance system.adapter.admin.0 send kill signal
    2022-07-23 17:09:50.141  - info: host.iobroker instance system.adapter.admin.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
    2022-07-23 17:09:52.669  - info: host.iobroker instance system.adapter.admin.0 started with pid 2639
    2022-07-23 17:09:54.032  - info: admin.0 (2639) starting. Version 5.3.8 in /opt/iobroker/node_modules/iobroker.admin, node: v16.16.0, js-controller: 4.0.23
    2022-07-23 17:09:54.069  - info: admin.0 (2639) requesting all states
    2022-07-23 17:09:54.070  - info: admin.0 (2639) requesting all objects
    2022-07-23 17:09:55.077  - info: admin.0 (2639) received all objects
    2022-07-23 17:09:55.248  - info: admin.0 (2639) http server listening on port 8083
    2022-07-23 17:09:55.248  - info: admin.0 (2639) Use link "http://localhost:8083" to configure.
    2022-07-23 17:10:11.142  - info: host.iobroker received SIGTERM
    2022-07-23 17:10:11.143  - info: host.iobroker stopInstance system.adapter.admin.0 (force=false, process=true)
    2022-07-23 17:10:11.143  - info: host.iobroker stopInstance system.adapter.javascript.0 (force=false, process=true)
    2022-07-23 17:10:11.144  - info: host.iobroker stopInstance system.adapter.pushover.0 (force=false, process=true)
    2022-07-23 17:10:11.144  - info: host.iobroker stopInstance system.adapter.node-red.0 (force=false, process=true)
    2022-07-23 17:10:11.145  - info: host.iobroker stopInstance system.adapter.history.0 (force=false, process=true)
    2022-07-23 17:10:11.145  - info: host.iobroker stopInstance system.adapter.alexa2.0 (force=false, process=true)
    2022-07-23 17:10:11.145  - info: host.iobroker stopInstance system.adapter.hm-rega.0 (force=false, process=true)
    2022-07-23 17:10:11.145  - info: host.iobroker stopInstance system.adapter.hm-rpc.0 (force=false, process=true)
    2022-07-23 17:10:11.145  - info: host.iobroker stopInstance system.adapter.hm-rpc.1 (force=false, process=true)
    2022-07-23 17:10:11.145  - info: host.iobroker stopInstance system.adapter.hm-rpc.2 (force=false, process=true)
    2022-07-23 17:10:11.146  - info: host.iobroker stopInstance system.adapter.hue.0 (force=false, process=true)
    2022-07-23 17:10:11.146  - info: host.iobroker stopInstance system.adapter.modbus.0 (force=false, process=true)
    2022-07-23 17:10:11.146  - info: host.iobroker stopInstance system.adapter.fritzbox.0 (force=false, process=true)
    2022-07-23 17:10:11.146  - info: host.iobroker stopInstance system.adapter.ping.0 (force=false, process=true)
    2022-07-23 17:10:11.146  - info: host.iobroker stopInstance system.adapter.backitup.0 (force=false, process=true)
    2022-07-23 17:10:11.146  - info: host.iobroker stopInstance system.adapter.ebus.0 (force=false, process=true)
    2022-07-23 17:10:11.146  - info: host.iobroker stopInstance system.adapter.info.0 (force=false, process=true)
    2022-07-23 17:10:11.147  - info: host.iobroker stopInstance system.adapter.iot.0 (force=false, process=true)
    2022-07-23 17:10:11.147  - info: host.iobroker stopInstance system.adapter.vis-fancyswitch.0 (force=false, process=false)
    2022-07-23 17:10:11.147  - info: host.iobroker stopInstance system.adapter.vis-hqwidgets.0 (force=false, process=false)
    2022-07-23 17:10:11.147  - info: host.iobroker stopInstance system.adapter.vis-jqui-mfd.0 (force=false, process=false)
    2022-07-23 17:10:11.147  - info: host.iobroker stopInstance system.adapter.vis.0 (force=false, process=false)
    2022-07-23 17:10:11.147  - info: host.iobroker stopInstance system.adapter.web.0 (force=false, process=false)
    2022-07-23 17:10:11.147  - info: host.iobroker stopInstance system.adapter.vis-materialdesign.0 (force=false, process=false)
    2022-07-23 17:10:11.147  - info: host.iobroker stopInstance system.adapter.vis-google-fonts.0 (force=false, process=false)
    2022-07-23 17:10:11.147  - info: host.iobroker stopInstance system.adapter.vis-weather.0 (force=false, process=false)
    2022-07-23 17:10:11.147  - info: host.iobroker stopInstance system.adapter.daswetter.0 (force=false, process=false)
    2022-07-23 17:10:11.148  - info: host.iobroker stopInstance canceled schedule system.adapter.daswetter.0
    2022-07-23 17:10:11.148  - info: host.iobroker stopInstance system.adapter.systeminfo.0 (force=false, process=true)
    2022-07-23 17:10:11.148  - info: host.iobroker stopInstance system.adapter.bring.0 (force=false, process=true)
    2022-07-23 17:10:11.149  - info: host.iobroker stopInstance system.adapter.plenticore.0 (force=false, process=true)
    2022-07-23 17:10:11.149  - info: host.iobroker stopInstance system.adapter.vis-history.0 (force=false, process=false)
    2022-07-23 17:10:11.149  - info: host.iobroker stopInstance system.adapter.jarvis.0 (force=false, process=true)
    2022-07-23 17:10:11.149  - info: host.iobroker stopInstance system.adapter.yahka.0 (force=false, process=true)
    2022-07-23 17:10:11.154  - info: node-red.0 (477) kill node-red task
    2022-07-23 17:10:11.164  - info: admin.0 (2639) Got terminate signal TERMINATE_YOURSELF
    2022-07-23 17:10:11.165  - info: admin.0 (2639) terminating http server on port 8083
    2022-07-23 17:10:11.165  - info: admin.0 (2639) terminating
    2022-07-23 17:10:11.166  - info: admin.0 (2639) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
    2022-07-23 17:10:11.169  - info: javascript.0 (435) Got terminate signal TERMINATE_YOURSELF
    2022-07-23 17:10:11.169  - info: pushover.0 (462) Got terminate signal TERMINATE_YOURSELF
    2022-07-23 17:10:11.172  - info: hm-rpc.2 (603) Got terminate signal TERMINATE_YOURSELF
    2022-07-23 17:10:11.170  - info: alexa2.0 (518) Got terminate signal TERMINATE_YOURSELF
    2022-07-23 17:10:11.174  - info: ping.0 (675) Got terminate signal TERMINATE_YOURSELF
    2022-07-23 17:10:11.174  - info: modbus.0 (633) Got terminate signal TERMINATE_YOURSELF
    2022-07-23 17:10:11.175  - info: hm-rpc.1 (575) Got terminate signal TERMINATE_YOURSELF
    2022-07-23 17:10:11.172  - info: alexa2.0 (518) terminating
    2022-07-23 17:10:11.173  - info: alexa2.0 (518) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
    2022-07-23 17:10:11.178  - info: hue.0 (618) Got terminate signal TERMINATE_YOURSELF
    2022-07-23 17:10:11.172  - info: hm-rpc.0 (560) Got terminate signal TERMINATE_YOURSELF
    2022-07-23 17:10:11.179  - info: info.0 (723) Got terminate signal TERMINATE_YOURSELF
    2022-07-23 17:10:11.178  - info: backitup.0 (693) Got terminate signal TERMINATE_YOURSELF
    2022-07-23 17:10:11.180  - info: ebus.0 (708) Got terminate signal TERMINATE_YOURSELF
    2022-07-23 17:10:11.171  - info: hm-rega.0 (545) Got terminate signal TERMINATE_YOURSELF
    2022-07-23 17:10:11.181  - info: info.0 (723) cleaned everything up...
    2022-07-23 17:10:11.181  - info: info.0 (723) terminating
    2022-07-23 17:10:11.182  - info: info.0 (723) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
    2022-07-23 17:10:11.175  - info: fritzbox.0 (648) Got terminate signal TERMINATE_YOURSELF
    2022-07-23 17:10:11.186  - info: bring.0 (1786) Got terminate signal TERMINATE_YOURSELF
    2022-07-23 17:10:11.173  - info: hm-rpc.2 (603) binrpc -> 192.168.86.50:8701/ init ["xmlrpc_bin://192.168.86.35:8701",""]
    2022-07-23 17:10:11.185  - info: iot.0 (1129) Got terminate signal TERMINATE_YOURSELF
    2022-07-23 17:10:11.187  - info: bring.0 (1786) [END] Stopping Bring! adapter...
    2022-07-23 17:10:11.188  - info: bring.0 (1786) terminating
    2022-07-23 17:10:11.188  - info: bring.0 (1786) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
    2022-07-23 17:10:11.185  - info: systeminfo.0 (1679) Got terminate signal TERMINATE_YOURSELF
    2022-07-23 17:10:11.187  - info: systeminfo.0 (1679) terminating
    2022-07-23 17:10:11.188  - info: systeminfo.0 (1679) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
    2022-07-23 17:10:11.176  - info: hm-rpc.1 (575) xmlrpc -> 192.168.86.50:2010/ init ["http://192.168.86.35:2010",""]
    2022-07-23 17:10:11.179  - info: backitup.0 (693) cleaned everything up...
    2022-07-23 17:10:11.181  - info: backitup.0 (693) terminating
    2022-07-23 17:10:11.185  - info: backitup.0 (693) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
    2022-07-23 17:10:11.191  - info: plenticore.0 (1863) Got terminate signal TERMINATE_YOURSELF
    2022-07-23 17:10:11.173  - info: hm-rpc.0 (560) xmlrpc -> 192.168.86.50:2001/ init ["http://192.168.86.35:2001",""]
    2022-07-23 17:10:11.181  - info: ebus.0 (708) cleaned everything up...
    2022-07-23 17:10:11.184  - info: ebus.0 (708) terminating
    2022-07-23 17:10:11.192  - info: ebus.0 (708) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
    2022-07-23 17:10:11.196  - info: node-red.0 (477) node-red exited with 0
    2022-07-23 17:10:11.183  - info: modbus.0 (633) terminating
    2022-07-23 17:10:11.192  - info: modbus.0 (633) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
    2022-07-23 17:10:11.194  - info: plenticore.0 (1863) [END] Stopping plenticore adapter...
    2022-07-23 17:10:11.195  - info: plenticore.0 (1863) terminating
    2022-07-23 17:10:11.196  - info: plenticore.0 (1863) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
    2022-07-23 17:10:11.196  - info: iot.0 (1129) terminating
    2022-07-23 17:10:11.197  - info: iot.0 (1129) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
    2022-07-23 17:10:11.194  - info: fritzbox.0 (648) terminating
    2022-07-23 17:10:11.200  - info: fritzbox.0 (648) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
    2022-07-23 17:10:11.201  - info: yahka.0 (2098) Got terminate signal TERMINATE_YOURSELF
    2022-07-23 17:10:11.200  - info: jarvis.0 (2023) Got terminate signal TERMINATE_YOURSELF
    2022-07-23 17:10:11.193  - info: hm-rpc.2 (603) Disconnected
    2022-07-23 17:10:11.204  - info: yahka.0 (2098) cleaning up ...
    2022-07-23 17:10:11.204  - info: yahka.0 (2098) cleaned up ...
    2022-07-23 17:10:11.206  - info: yahka.0 (2098) terminating
    2022-07-23 17:10:11.207  - info: yahka.0 (2098) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
    2022-07-23 17:10:11.211  - info: hm-rpc.1 (575) Disconnected
    2022-07-23 17:10:11.207  - info: jarvis.0 (2023) Adapter stopped und unloaded.
    2022-07-23 17:10:11.207  - info: jarvis.0 (2023) terminating
    2022-07-23 17:10:11.209  - info: jarvis.0 (2023) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
    2022-07-23 17:10:11.213  - info: hm-rpc.1 (575) terminating
    2022-07-23 17:10:11.214  - info: hm-rpc.1 (575) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
    2022-07-23 17:10:11.219  - info: host.iobroker stopInstance system.adapter.admin.0 send kill signal
    2022-07-23 17:10:11.220  - info: hm-rpc.0 (560) Disconnected
    2022-07-23 17:10:11.207  - info: hm-rpc.2 (603) terminating
    2022-07-23 17:10:11.208  - info: hm-rpc.2 (603) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
    2022-07-23 17:10:11.225  - info: host.iobroker stopInstance system.adapter.javascript.0 send kill signal
    2022-07-23 17:10:11.171  - info: javascript.0 (435) Stop script script.js.common.AlarmModus
    2022-07-23 17:10:11.190  - info: javascript.0 (435) Stop script script.js.common.Alexa
    2022-07-23 17:10:11.195  - info: javascript.0 (435) Stop script script.js.common.Solar
    2022-07-23 17:10:11.199  - info: javascript.0 (435) Stop script script.js.common.Homematic_Meldungen
    2022-07-23 17:10:11.220  - info: javascript.0 (435) Stop script script.js.common.Jarvis
    2022-07-23 17:10:11.226  - info: javascript.0 (435) Stop script script.js.common.Zigbee
    2022-07-23 17:10:11.226  - info: javascript.0 (435) Stop script script.js.common.Alarm
    2022-07-23 17:10:11.225  - info: host.iobroker stopInstance system.adapter.pushover.0 send kill signal
    2022-07-23 17:10:11.225  - info: host.iobroker stopInstance system.adapter.alexa2.0 send kill signal
    2022-07-23 17:10:11.225  - info: host.iobroker stopInstance system.adapter.hm-rega.0 send kill signal
    2022-07-23 17:10:11.225  - info: host.iobroker stopInstance system.adapter.hm-rpc.0 send kill signal
    2022-07-23 17:10:11.226  - info: host.iobroker stopInstance system.adapter.hm-rpc.1 send kill signal
    2022-07-23 17:10:11.226  - info: host.iobroker stopInstance system.adapter.hm-rpc.2 send kill signal
    2022-07-23 17:10:11.226  - info: host.iobroker stopInstance system.adapter.hue.0 send kill signal
    2022-07-23 17:10:11.226  - info: host.iobroker stopInstance system.adapter.modbus.0 send kill signal
    2022-07-23 17:10:11.226  - info: host.iobroker stopInstance system.adapter.fritzbox.0 send kill signal
    2022-07-23 17:10:11.226  - info: host.iobroker stopInstance system.adapter.ping.0 send kill signal
    2022-07-23 17:10:11.226  - info: host.iobroker stopInstance system.adapter.backitup.0 send kill signal
    2022-07-23 17:10:11.226  - info: host.iobroker stopInstance system.adapter.ebus.0 send kill signal
    2022-07-23 17:10:11.226  - info: host.iobroker stopInstance system.adapter.info.0 send kill signal
    2022-07-23 17:10:11.226  - info: host.iobroker stopInstance system.adapter.iot.0 send kill signal
    2022-07-23 17:10:11.227  - info: host.iobroker stopInstance system.adapter.systeminfo.0 send kill signal
    2022-07-23 17:10:11.227  - info: host.iobroker stopInstance system.adapter.bring.0 send kill signal
    2022-07-23 17:10:11.227  - info: host.iobroker stopInstance system.adapter.plenticore.0 send kill signal
    2022-07-23 17:10:11.227  - info: host.iobroker stopInstance system.adapter.jarvis.0 send kill signal
    2022-07-23 17:10:11.227  - info: host.iobroker stopInstance system.adapter.yahka.0 send kill signal
    2022-07-23 17:10:11.230  - info: hue.0 (618) cleaned everything up...
    2022-07-23 17:10:11.231  - info: hue.0 (618) terminating
    2022-07-23 17:10:11.232  - info: hue.0 (618) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
    2022-07-23 17:10:11.221  - info: hm-rpc.0 (560) terminating
    2022-07-23 17:10:11.230  - info: hm-rpc.0 (560) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
    2022-07-23 17:10:11.236  - info: javascript.0 (435) terminating
    2022-07-23 17:10:11.238  - info: javascript.0 (435) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
    2022-07-23 17:10:11.245  - info: hm-rega.0 (545) terminating
    2022-07-23 17:10:11.246  - info: hm-rega.0 (545) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
    2022-07-23 17:10:11.250  - info: plenticore.0 (1863) Logged out from API
    2022-07-23 17:10:11.251  - info: iot.0 (1129) Connection changed: disconnect
    2022-07-23 17:10:11.251  - info: iot.0 (1129) Connection lost
    2022-07-23 17:10:11.671  - info: pushover.0 (462) terminating
    2022-07-23 17:10:11.672  - info: pushover.0 (462) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
    2022-07-23 17:10:11.676  - info: ping.0 (675) terminating
    2022-07-23 17:10:11.677  - info: ping.0 (675) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
    2022-07-23 17:10:11.802  - info: host.iobroker instance system.adapter.admin.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
    2022-07-23 17:10:12.056  - info: host.iobroker instance system.adapter.alexa2.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
    2022-07-23 17:10:12.159  - info: host.iobroker instance system.adapter.backitup.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
    2022-07-23 17:10:12.159  - info: host.iobroker instance system.adapter.info.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
    2022-07-23 17:10:12.322  - info: history.0 (503) Terminated (NO_ERROR): Without reason
    2022-07-23 17:10:12.391  - info: host.iobroker stopInstance system.adapter.javascript.0 killing pid 435
    2022-07-23 17:10:12.392  - info: host.iobroker stopInstance system.adapter.pushover.0 killing pid 462
    2022-07-23 17:10:12.392  - info: host.iobroker stopInstance system.adapter.hm-rega.0 killing pid 545
    2022-07-23 17:10:12.392  - info: host.iobroker stopInstance system.adapter.hm-rpc.0 killing pid 560
    2022-07-23 17:10:12.392  - info: host.iobroker stopInstance system.adapter.hm-rpc.1 killing pid 575
    2022-07-23 17:10:12.393  - info: host.iobroker stopInstance system.adapter.hm-rpc.2 killing pid 603
    2022-07-23 17:10:12.393  - info: host.iobroker stopInstance system.adapter.hue.0 killing pid 618
    2022-07-23 17:10:12.393  - info: host.iobroker stopInstance system.adapter.ping.0 killing pid 675
    2022-07-23 17:10:12.393  - info: host.iobroker stopInstance system.adapter.jarvis.0 killing pid 2023
    2022-07-23 17:10:12.393  - info: host.iobroker stopInstance system.adapter.yahka.0 killing pid 2098
    2022-07-23 17:10:12.452  - info: host.iobroker instance system.adapter.modbus.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
    2022-07-23 17:10:12.586  - info: host.iobroker instance system.adapter.ebus.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
    2022-07-23 17:10:12.587  - info: host.iobroker instance system.adapter.systeminfo.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
    2022-07-23 17:10:12.616  - info: host.iobroker instance system.adapter.bring.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
    2022-07-23 17:10:12.673  - info: pushover.0 (462) terminating with timeout
    2022-07-23 17:10:12.678  - info: ping.0 (675) terminating with timeout
    2022-07-23 17:10:12.638  - info: host.iobroker instance system.adapter.iot.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
    2022-07-23 17:10:12.748  - info: host.iobroker instance system.adapter.plenticore.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
    2022-07-23 17:10:12.778  - info: host.iobroker instance system.adapter.fritzbox.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
    2022-07-23 17:10:13.059  - info: host.iobroker instance system.adapter.yahka.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
    2022-07-23 17:10:13.082  - info: host.iobroker instance system.adapter.hm-rega.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
    2022-07-23 17:10:13.165  - info: host.iobroker instance system.adapter.hm-rpc.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
    2022-07-23 17:10:13.165  - info: host.iobroker instance system.adapter.hm-rpc.1 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
    2022-07-23 17:10:13.186  - info: host.iobroker instance system.adapter.hm-rpc.2 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
    2022-07-23 17:10:13.232  - info: host.iobroker instance system.adapter.hue.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
    2022-07-23 17:10:13.233  - info: host.iobroker instance system.adapter.jarvis.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
    2022-07-23 17:10:13.260  - info: host.iobroker instance system.adapter.javascript.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
    2022-07-23 17:10:13.380  - info: host.iobroker instance system.adapter.pushover.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
    2022-07-23 17:10:13.402  - info: host.iobroker instance system.adapter.ping.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
    2022-07-23 17:10:13.462  - info: host.iobroker instance system.adapter.history.0 terminated with code 0 (NO_ERROR)
    2022-07-23 17:10:16.145  - info: host.iobroker stopInstance timeout 5000 system.adapter.node-red.0 killing pid  477
    2022-07-23 17:10:16.649  - info: node-red.0 (477) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
    2022-07-23 17:10:17.231  - info: host.iobroker instance system.adapter.node-red.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP)
    2022-07-23 17:10:17.231  - info: host.iobroker All instances are stopped.
    2022-07-23 17:10:17.386  - info: host.iobroker terminated
    2022-07-23 17:10:42.082  - info: host.iobroker iobroker.js-controller version 4.0.23 js-controller starting
    2022-07-23 17:10:42.085  - info: host.iobroker Copyright (c) 2014-2022 bluefox, 2014 hobbyquaker
    2022-07-23 17:10:42.086  - info: host.iobroker hostname: iobroker, node: v16.16.0
    2022-07-23 17:10:42.086  - info: host.iobroker ip addresses: 192.168.86.35 fe80::211:32ff:fee9:7b3f 172.17.0.1 fe80::42:1dff:fe89:d167 fe80::1821:8aff:fe81:9b4a
    2022-07-23 17:10:43.209  - info: host.iobroker connected to Objects and States
    2022-07-23 17:10:43.247  - info: host.iobroker added notifications configuration of host
    2022-07-23 17:10:43.733  - info: host.iobroker 40 instances found
    2022-07-23 17:10:43.767  - info: host.iobroker starting 30 instances
    2022-07-23 17:10:43.867  - info: host.iobroker instance system.adapter.admin.0 started with pid 419
    2022-07-23 17:10:45.168  - info: admin.0 (419) starting. Version 5.3.8 in /opt/iobroker/node_modules/iobroker.admin, node: v16.16.0, js-controller: 4.0.23
    2022-07-23 17:10:45.193  - info: admin.0 (419) requesting all states
    2022-07-23 17:10:45.194  - info: admin.0 (419) requesting all objects
    2022-07-23 17:10:46.268  - info: admin.0 (419) received all objects
    2022-07-23 17:10:46.474  - info: admin.0 (419) http server listening on port 8083
    2022-07-23 17:10:46.475  - info: admin.0 (419) Use link "http://localhost:8083" to configure.
    2022-07-23 17:10:47.948  - info: host.iobroker instance system.adapter.javascript.0 started with pid 434
    2022-07-23 17:10:49.737  - info: javascript.0 (434) starting. Version 5.7.0 in /opt/iobroker/node_modules/iobroker.javascript, node: v16.16.0, js-controller: 4.0.23
    2022-07-23 17:10:50.576  - info: javascript.0 (434) requesting all states
    2022-07-23 17:10:50.577  - info: javascript.0 (434) requesting all objects
    2022-07-23 17:10:51.864  - info: host.iobroker instance system.adapter.pushover.0 started with pid 463
    2022-07-23 17:10:51.950  - info: javascript.0 (434) received all objects
    2022-07-23 17:10:51.964  - info: javascript.0 (434) received all states
    2022-07-23 17:10:52.007  - error: javascript.0 (434) The Mirror directory is not allowed to be a central ioBroker directory!
    2022-07-23 17:10:52.007  - error: javascript.0 (434) Directory /opt/iobroker/backups/scripte is not allowed to mirror files!
    2022-07-23 17:10:52.017  - info: javascript.0 (434) Start javascript script.js.common.AlarmModus
    2022-07-23 17:10:53.131  - info: pushover.0 (463) starting. Version 2.1.0 in /opt/iobroker/node_modules/iobroker.pushover, node: v16.16.0, js-controller: 4.0.23
    2022-07-23 17:10:52.048  - info: javascript.0 (434) script.js.common.AlarmModus: registered 1 subscription and 0 schedules
    2022-07-23 17:10:52.048  - info: javascript.0 (434) Start javascript script.js.common.Alexa
    2022-07-23 17:10:52.054  - info: javascript.0 (434) script.js.common.Alexa: registered 13 subscriptions and 0 schedules
    2022-07-23 17:10:52.054  - info: javascript.0 (434) Start javascript script.js.common.Solar
    2022-07-23 17:10:52.115  - info: javascript.0 (434) script.js.common.Solar: registered 12 subscriptions and 10 schedules
    2022-07-23 17:10:52.116  - info: javascript.0 (434) Start javascript script.js.common.Homematic_Meldungen
    2022-07-23 17:10:53.529  - info: javascript.0 (434) script.js.common.Homematic_Meldungen: Homematic-Servicemeldungen: Phillip Heizung  ist nicht erreichbar<br>Keller Aufgang Heizung  ist nicht erreichbar<br>Weihnachtsbeleuchtung  ist nicht erreichbar<br>Phillip Heizung  hat eine schlechte Batterie<br>Keller Aufgang Heizung  hat eine schlechte Batterie<br>
    2022-07-23 17:10:53.530  - info: javascript.0 (434) script.js.common.Homematic_Meldungen: Anzahl Homematic-Servicemeldungen: 5
    2022-07-23 17:10:53.531  - info: javascript.0 (434) script.js.common.Homematic_Meldungen: registered 204 subscriptions and 1 schedule
    2022-07-23 17:10:53.651  - info: javascript.0 (434) Start javascript script.js.common.Jarvis
    2022-07-23 17:10:53.664  - info: javascript.0 (434) script.js.common.Jarvis: registered 30 subscriptions and 1 schedule
    2022-07-23 17:10:53.664  - info: javascript.0 (434) Start javascript script.js.common.Zigbee
    2022-07-23 17:10:53.668  - info: javascript.0 (434) script.js.common.Zigbee: registered 9 subscriptions and 0 schedules
    2022-07-23 17:10:53.673  - info: javascript.0 (434) Start javascript script.js.common.Alarm
    2022-07-23 17:10:53.677  - info: javascript.0 (434) script.js.common.Alarm: registered 17 subscriptions and 0 schedules
    2022-07-23 17:10:53.687  - info: javascript.0 (434) script.js.common.Jarvis: Phillip Heizung  ist nicht erreichbar<br>Keller Aufgang Heizung  ist nicht erreichbar<br>Weihnachtsbeleuchtung  ist nicht erreichbar<br>Phillip Heizung  hat eine schlechte Batterie<br>Keller Aufgang Heizung  hat eine schlechte Batterie<br>
    2022-07-23 17:10:55.855  - info: host.iobroker instance system.adapter.node-red.0 started with pid 478
    2022-07-23 17:10:56.997  - info: node-red.0 (478) starting. Version 3.3.1 in /opt/iobroker/node_modules/iobroker.node-red, node: v16.16.0, js-controller: 4.0.23
    2022-07-23 17:10:57.015  - info: node-red.0 (478) Requested NPM packages: ["node-red-contrib-bool-gate","node-red-contrib-azure-iot-hub"]
    2022-07-23 17:10:57.935  - info: node-red.0 (478) Starting node-red: --max-old-space-size=128 /opt/iobroker/node_modules/node-red/red.js -v --settings /opt/iobroker/iobroker-data/node-red/settings.js
    2022-07-23 17:10:59.866  - info: host.iobroker instance system.adapter.history.0 started with pid 504
    2022-07-23 17:11:01.188  - warn: node-red.0 (478) 23 Jul 17:11:01 - [warn] Projekte deaktiviert: editorTheme.projects.enabled=false
    2022-07-23 17:11:01.201  - warn: node-red.0 (478) (node:493) [DEP0128] DeprecationWarning: Invalid 'main' field in '/opt/iobroker/iobroker-data/node-red/node_modules/azure-iothub/node_modules/azure-iot-amqp-base/package.json' of 'main.js'. Please either fix that or report it to the module author
    (Use `node --trace-deprecation ...` to show where the warning was created)
    2022-07-23 17:11:01.202  - warn: node-red.0 (478) (node:493) [DEP0128] DeprecationWarning: Invalid 'main' field in '/opt/iobroker/iobroker-data/node-red/node_modules/azure-iot-amqp-base/package.json' of 'main.js'. Please either fix that or report it to the module author
    (node:493) [DEP0128] DeprecationWarning: Invalid 'main' field in '/opt/iobroker/iobroker-data/node-red/node_modules/azure-iot-device-amqp-ws/node_modules/azure-iot-amqp-base/package.json' of 'main.js'. Please either fix that or report it to the module author
    (node:493) [DEP0128] DeprecationWarning: Invalid 'main' field in '/opt/iobroker/iobroker-data/node-red/node_modules/azure-iot-device-amqp-ws/node_modules/azure-iot-amqp-base/package.json' of 'main.js'. Please either fix that or report it to the module author
    2022-07-23 17:11:01.207  - info: history.0 (504) starting. Version 1.11.1 in /opt/iobroker/node_modules/iobroker.history, node: v16.16.0, js-controller: 4.0.23
    2022-07-23 17:11:01.349  - info: history.0 (504) enabled logging of hm-rega.0.18981 (Count=1), Alias=false
    2022-07-23 17:11:01.350  - info: history.0 (504) enabled logging of hm-rega.0.1981 (Count=2), Alias=false
    2022-07-23 17:11:01.350  - info: history.0 (504) enabled logging of hm-rega.0.2688 (Count=3), Alias=false
    2022-07-23 17:11:01.351  - info: history.0 (504) enabled logging of hm-rega.0.3039 (Count=4), Alias=false
    2022-07-23 17:11:01.351  - info: history.0 (504) enabled logging of hm-rega.0.9284 (Count=5), Alias=false
    2022-07-23 17:11:01.351  - info: history.0 (504) enabled logging of hm-rega.0.950 (Count=6), Alias=false
    2022-07-23 17:11:01.352  - info: history.0 (504) enabled logging of hm-rega.0.alarms (Count=7), Alias=false
    2022-07-23 17:11:01.352  - info: history.0 (504) enabled logging of hm-rega.0.maintenance (Count=8), Alias=false
    2022-07-23 17:11:01.353  - info: history.0 (504) enabled logging of hm-rpc.0.NEQ0871169.4.ACTUAL_TEMPERATURE (Count=9), Alias=false
    2022-07-23 17:11:01.353  - info: history.0 (504) enabled logging of hm-rpc.0.NEQ0871169.4.SET_TEMPERATURE (Count=10), Alias=false
    2022-07-23 17:11:01.353  - info: history.0 (504) enabled logging of hm-rpc.0.NEQ0871169.4.VALVE_STATE (Count=11), Alias=false
    2022-07-23 17:11:01.354  - info: history.0 (504) enabled logging of hm-rpc.0.NEQ0871170.4.ACTUAL_TEMPERATURE (Count=12), Alias=false
    2022-07-23 17:11:01.354  - info: history.0 (504) enabled logging of hm-rpc.0.NEQ0871170.4.SET_TEMPERATURE (Count=13), Alias=false
    2022-07-23 17:11:01.354  - info: history.0 (504) enabled logging of hm-rpc.0.NEQ0871170.4.VALVE_STATE (Count=14), Alias=false
    2022-07-23 17:11:01.355  - info: history.0 (504) enabled logging of hm-rpc.0.NEQ0871175.4.ACTUAL_TEMPERATURE (Count=15), Alias=false
    2022-07-23 17:11:01.355  - info: history.0 (504) enabled logging of hm-rpc.0.NEQ0871175.4.SET_TEMPERATURE (Count=16), Alias=false
    2022-07-23 17:11:01.355  - info: history.0 (504) enabled logging of hm-rpc.0.NEQ0871175.4.VALVE_STATE (Count=17), Alias=false
    2022-07-23 17:11:01.356  - info: history.0 (504) enabled logging of hm-rpc.0.NEQ0871224.4.ACTUAL_TEMPERATURE (Count=18), Alias=false
    2022-07-23 17:11:01.356  - info: history.0 (504) enabled logging of hm-rpc.0.NEQ0871224.4.SET_TEMPERATURE (Count=19), Alias=false
    2022-07-23 17:11:01.356  - info: history.0 (504) enabled logging of hm-rpc.0.NEQ0871224.4.VALVE_STATE (Count=20), Alias=false
    2022-07-23 17:11:01.356  - info: history.0 (504) enabled logging of hm-rpc.0.NEQ1773663.4.ACTUAL_TEMPERATURE (Count=21), Alias=false
    2022-07-23 17:11:01.356  - info: history.0 (504) enabled logging of hm-rpc.0.NEQ1773663.4.SET_TEMPERATURE (Count=22), Alias=false
    2022-07-23 17:11:01.357  - info: history.0 (504) enabled logging of hm-rpc.0.NEQ1773663.4.VALVE_STATE (Count=23), Alias=false
    2022-07-23 17:11:01.357  - info: history.0 (504) enabled logging of hm-rpc.0.OEQ0160601.1.HUMIDITY (Count=24), Alias=false
    2022-07-23 17:11:01.357  - info: history.0 (504) enabled logging of hm-rpc.0.OEQ0160601.1.TEMPERATURE (Count=25), Alias=false
    2022-07-23 17:11:01.357  - info: history.0 (504) enabled logging of hm-rpc.0.OEQ0239290.4.ACTUAL_TEMPERATURE (Count=26), Alias=false
    2022-07-23 17:11:01.357  - info: history.0 (504) enabled logging of hm-rpc.0.OEQ0239290.4.SET_TEMPERATURE (Count=27), Alias=false
    2022-07-23 17:11:01.357  - info: history.0 (504) enabled logging of hm-rpc.0.OEQ0239290.4.VALVE_STATE (Count=28), Alias=false
    2022-07-23 17:11:01.358  - info: history.0 (504) enabled logging of hm-rpc.0.OEQ0661458.4.ACTUAL_TEMPERATURE (Count=29), Alias=false
    2022-07-23 17:11:01.358  - info: history.0 (504) enabled logging of hm-rpc.0.OEQ0661458.4.SET_TEMPERATURE (Count=30), Alias=false
    2022-07-23 17:11:01.358  - info: history.0 (504) enabled logging of hm-rpc.0.OEQ0661458.4.VALVE_STATE (Count=31), Alias=false
    2022-07-23 17:11:01.358  - info: history.0 (504) enabled logging of hm-rpc.0.OEQ0668242.4.ACTUAL_TEMPERATURE (Count=32), Alias=false
    2022-07-23 17:11:01.358  - info: history.0 (504) enabled logging of hm-rpc.0.OEQ0668242.4.SET_TEMPERATURE (Count=33), Alias=false
    2022-07-23 17:11:01.358  - info: history.0 (504) enabled logging of hm-rpc.0.OEQ0668242.4.VALVE_STATE (Count=34), Alias=false
    2022-07-23 17:11:01.359  - info: history.0 (504) enabled logging of hm-rpc.0.OEQ0669002.4.ACTUAL_TEMPERATURE (Count=35), Alias=false
    2022-07-23 17:11:01.359  - info: history.0 (504) enabled logging of hm-rpc.0.OEQ0669002.4.SET_TEMPERATURE (Count=36), Alias=false
    2022-07-23 17:11:01.359  - info: history.0 (504) enabled logging of hm-rpc.0.OEQ0669002.4.VALVE_STATE (Count=37), Alias=false
    2022-07-23 17:11:01.359  - info: history.0 (504) enabled logging of hm-rega.0.22568 (Count=38), Alias=false
    2022-07-23 17:11:01.359  - info: history.0 (504) enabled logging of hm-rega.0.22569 (Count=39), Alias=false
    2022-07-23 17:11:01.360  - info: history.0 (504) enabled logging of hm-rpc.1.00201A49A02B30.1.SET_POINT_TEMPERATURE (Count=40), Alias=false
    2022-07-23 17:11:01.360  - info: history.0 (504) enabled logging of hm-rpc.1.00201A49A02B30.1.LEVEL (Count=41), Alias=false
    2022-07-23 17:11:01.360  - info: history.0 (504) enabled logging of hm-rpc.1.00201A49A02B30.1.VALVE_STATE (Count=42), Alias=false
    2022-07-23 17:11:01.360  - info: history.0 (504) enabled logging of hm-rpc.1.00201A49A02B30.1.ACTUAL_TEMPERATURE (Count=43), Alias=false
    2022-07-23 17:11:01.361  - info: history.0 (504) enabled logging of daswetter.0.NextHours.Location_1.Day_1.current.temp_value (Count=44), Alias=false
    2022-07-23 17:11:01.361  - info: history.0 (504) enabled logging of javascript.0.Solar.Piko_DC_power (Count=45), Alias=false
    2022-07-23 17:11:01.361  - info: history.0 (504) enabled logging of javascript.0.Solar.Piko_AC_power (Count=46), Alias=false
    2022-07-23 17:11:01.361  - info: history.0 (504) enabled logging of javascript.0.Solar.Plenticore_AC_power (Count=47), Alias=false
    2022-07-23 17:11:01.361  - info: history.0 (504) enabled logging of javascript.0.Solar.Power_From_Grid (Count=48), Alias=false
    2022-07-23 17:11:01.361  - info: history.0 (504) enabled logging of javascript.0.Solar.Power_To_Grid (Count=49), Alias=false
    2022-07-23 17:11:01.362  - info: history.0 (504) enabled logging of javascript.0.Solar.Power_Used (Count=50), Alias=false
    2022-07-23 17:11:01.362  - info: history.0 (504) enabled logging of javascript.0.Solar.Daily_Used (Count=51), Alias=false
    2022-07-23 17:11:01.362  - info: history.0 (504) enabled logging of javascript.0.Solar.Weekly_Used (Count=52), Alias=false
    2022-07-23 17:11:01.362  - info: history.0 (504) enabled logging of javascript.0.Solar.Monthly_Used (Count=53), Alias=false
    2022-07-23 17:11:01.362  - info: history.0 (504) enabled logging of javascript.0.Solar.Yearly_Used (Count=54), Alias=false
    2022-07-23 17:11:01.362  - info: history.0 (504) enabled logging of javascript.0.Solar.Power_PV (Count=55), Alias=false
    2022-07-23 17:11:01.363  - info: history.0 (504) enabled logging of javascript.0.Solar.Daily_PV (Count=56), Alias=false
    2022-07-23 17:11:01.363  - info: history.0 (504) enabled logging of javascript.0.Solar.Weekly_PV (Count=57), Alias=false
    2022-07-23 17:11:01.363  - info: history.0 (504) enabled logging of javascript.0.Solar.Yearly_PV (Count=58), Alias=false
    2022-07-23 17:11:01.363  - info: history.0 (504) enabled logging of javascript.0.Solar.Daily_To_Grid (Count=59), Alias=false
    2022-07-23 17:11:01.363  - info: history.0 (504) enabled logging of javascript.0.Solar.Weekly_To_Grid (Count=60), Alias=false
    2022-07-23 17:11:01.363  - info: history.0 (504) enabled logging of javascript.0.Solar.Monthly_To_Grid (Count=61), Alias=false
    2022-07-23 17:11:01.363  - info: history.0 (504) enabled logging of javascript.0.Solar.Yearly_To_Grid (Count=62), Alias=false
    2022-07-23 17:11:01.364  - info: history.0 (504) enabled logging of javascript.0.Solar.Daily_From_Grid (Count=63), Alias=false
    2022-07-23 17:11:01.364  - info: history.0 (504) enabled logging of javascript.0.Solar.Weekly_From_Grid (Count=64), Alias=false
    2022-07-23 17:11:01.364  - info: history.0 (504) enabled logging of javascript.0.Solar.Monthly_From_Grid (Count=65), Alias=false
    2022-07-23 17:11:01.364  - info: history.0 (504) enabled logging of javascript.0.Solar.Yearly_From_Grid (Count=66), Alias=false
    2022-07-23 17:11:01.364  - info: history.0 (504) enabled logging of javascript.0.Solar.Daily_Autark (Count=67), Alias=false
    2022-07-23 17:11:01.364  - info: history.0 (504) enabled logging of javascript.0.Solar.Weekly_Autark (Count=68), Alias=false
    2022-07-23 17:11:01.364  - info: history.0 (504) enabled logging of javascript.0.Solar.Monthly_Autark (Count=69), Alias=false
    2022-07-23 17:11:01.365  - info: history.0 (504) enabled logging of javascript.0.Solar.Yearly_Autark (Count=70), Alias=false
    2022-07-23 17:11:01.365  - info: history.0 (504) enabled logging of javascript.0.Solar.Monthly_PV (Count=71), Alias=false
    2022-07-23 17:11:01.365  - info: history.0 (504) enabled logging of javascript.0.Solar.Daily_Autark_Total (Count=72), Alias=false
    2022-07-23 17:11:01.365  - info: history.0 (504) enabled logging of javascript.0.Solar.Weekly_Autark_Total (Count=73), Alias=false
    2022-07-23 17:11:01.365  - info: history.0 (504) enabled logging of javascript.0.Solar.Monthly_Autark_Total (Count=74), Alias=false
    2022-07-23 17:11:01.365  - info: history.0 (504) enabled logging of javascript.0.Solar.Yearly_Autark_Total (Count=75), Alias=false
    2022-07-23 17:11:01.365  - info: history.0 (504) enabled logging of javascript.0.Solar.Daily_Used_Total (Count=76), Alias=false
    2022-07-23 17:11:01.366  - info: history.0 (504) enabled logging of javascript.0.Solar.Weekly_Used_Total (Count=77), Alias=false
    2022-07-23 17:11:01.366  - info: history.0 (504) enabled logging of javascript.0.Solar.Monthly_Used_Total (Count=78), Alias=false
    2022-07-23 17:11:01.366  - info: history.0 (504) enabled logging of javascript.0.Solar.Yearly_Used_Total (Count=79), Alias=false
    2022-07-23 17:11:01.366  - info: history.0 (504) enabled logging of javascript.0.Solar.Daily_PV_Total (Count=80), Alias=false
    2022-07-23 17:11:01.366  - info: history.0 (504) enabled logging of javascript.0.Solar.Weekly_PV_Total (Count=81), Alias=false
    2022-07-23 17:11:01.366  - info: history.0 (504) enabled logging of javascript.0.Solar.Monthly_PV_Total (Count=82), Alias=false
    2022-07-23 17:11:01.366  - info: history.0 (504) enabled logging of javascript.0.Solar.Yearly_PV_Total (Count=83), Alias=false
    2022-07-23 17:11:01.367  - info: history.0 (504) enabled logging of javascript.0.Solar.Daily_To_Grid_Total (Count=84), Alias=false
    2022-07-23 17:11:01.367  - info: history.0 (504) enabled logging of javascript.0.Solar.Weekly_To_Grid_Total (Count=85), Alias=false
    2022-07-23 17:11:01.367  - info: history.0 (504) enabled logging of javascript.0.Solar.Monthly_To_Grid_Total (Count=86), Alias=false
    2022-07-23 17:11:01.367  - info: history.0 (504) enabled logging of javascript.0.Solar.Yearly_To_Grid_Total (Count=87), Alias=false
    2022-07-23 17:11:01.367  - info: history.0 (504) enabled logging of javascript.0.Solar.Daily_From_Grid_Total (Count=88), Alias=false
    2022-07-23 17:11:01.367  - info: history.0 (504) enabled logging of javascript.0.Solar.Weekly_From_Grid_Total (Count=89), Alias=false
    2022-07-23 17:11:01.367  - info: history.0 (504) enabled logging of javascript.0.Solar.Monthly_From_Grid_Total (Count=90), Alias=false
    2022-07-23 17:11:01.368  - info: history.0 (504) enabled logging of javascript.0.Solar.Yearly_From_Grid_Total (Count=91), Alias=false
    2022-07-23 17:11:01.368  - info: history.0 (504) enabled logging of javascript.0.Solar.Piko_Percent (Count=92), Alias=false
    2022-07-23 17:11:01.368  - info: history.0 (504) enabled logging of javascript.0.Solar.Plenticore_Percent (Count=93), Alias=false
    2022-07-23 17:11:01.368  - info: history.0 (504) enabled logging of javascript.0.Solar.Daily_Euro (Count=94), Alias=false
    2022-07-23 17:11:01.368  - info: history.0 (504) enabled logging of javascript.0.Solar.Weekly_Euro (Count=95), Alias=false
    2022-07-23 17:11:01.368  - info: history.0 (504) enabled logging of javascript.0.Solar.Monthly_Euro (Count=96), Alias=false
    2022-07-23 17:11:01.368  - info: history.0 (504) enabled logging of javascript.0.Solar.Yearly_Euro (Count=97), Alias=false
    2022-07-23 17:11:01.369  - info: history.0 (504) enabled logging of javascript.0.Solar.Daily_Euro_Total (Count=98), Alias=false
    2022-07-23 17:11:01.369  - info: history.0 (504) enabled logging of javascript.0.Solar.Weekly_Euro_Total (Count=99), Alias=false
    2022-07-23 17:11:01.369  - info: history.0 (504) enabled logging of javascript.0.Solar.Monthly_Euro_Total (Count=100), Alias=false
    2022-07-23 17:11:01.369  - info: history.0 (504) enabled logging of javascript.0.Solar.Yearly_Euro_Total (Count=101), Alias=false
    2022-07-23 17:11:01.369  - info: history.0 (504) enabled logging of javascript.0.Solar.Power_From_Battery (Count=102), Alias=false
    2022-07-23 17:11:01.369  - info: history.0 (504) enabled logging of javascript.0.Solar.Power_To_Battery (Count=103), Alias=false
    2022-07-23 17:11:01.369  - info: history.0 (504) enabled logging of javascript.0.Solar.Daily_To_Battery (Count=104), Alias=false
    2022-07-23 17:11:01.370  - info: history.0 (504) enabled logging of javascript.0.Solar.Weekly_To_Battery (Count=105), Alias=false
    2022-07-23 17:11:01.370  - info: history.0 (504) enabled logging of javascript.0.Solar.Monthly_To_Battery (Count=106), Alias=false
    2022-07-23 17:11:01.370  - info: history.0 (504) enabled logging of javascript.0.Solar.Yearly_To_Battery (Count=107), Alias=false
    2022-07-23 17:11:01.370  - info: history.0 (504) enabled logging of javascript.0.Solar.Daily_To_Battery_Total (Count=108), Alias=false
    2022-07-23 17:11:01.370  - info: history.0 (504) enabled logging of javascript.0.Solar.Weekly_To_Battery_Total (Count=109), Alias=false
    2022-07-23 17:11:01.370  - info: history.0 (504) enabled logging of javascript.0.Solar.Monthly_To_Battery_Total (Count=110), Alias=false
    2022-07-23 17:11:01.370  - info: history.0 (504) enabled logging of javascript.0.Solar.Yearly_To_Battery_Total (Count=111), Alias=false
    2022-07-23 17:11:01.371  - info: history.0 (504) enabled logging of javascript.0.Solar.Daily_From_Battery (Count=112), Alias=false
    2022-07-23 17:11:01.371  - info: history.0 (504) enabled logging of javascript.0.Solar.Weekly_From_Battery (Count=113), Alias=false
    2022-07-23 17:11:01.371  - info: history.0 (504) enabled logging of javascript.0.Solar.Monthly_From_Battery (Count=114), Alias=false
    2022-07-23 17:11:01.371  - info: history.0 (504) enabled logging of javascript.0.Solar.Yearly_From_Battery (Count=115), Alias=false
    2022-07-23 17:11:01.371  - info: history.0 (504) enabled logging of javascript.0.Solar.Daily_From_Battery_Total (Count=116), Alias=false
    2022-07-23 17:11:01.371  - info: history.0 (504) enabled logging of javascript.0.Solar.Weekly_From_Battery_Total (Count=117), Alias=false
    2022-07-23 17:11:01.371  - info: history.0 (504) enabled logging of javascript.0.Solar.Monthly_From_Battery_Total (Count=118), Alias=false
    2022-07-23 17:11:01.372  - info: history.0 (504) enabled logging of javascript.0.Solar.Yearly_From_Battery_Total (Count=119), Alias=false
    2022-07-23 17:11:01.372  - info: history.0 (504) enabled logging of javascript.0.Solar.Daily_From_Overpower (Count=120), Alias=false
    2022-07-23 17:11:01.372  - info: history.0 (504) enabled logging of javascript.0.Solar.Weekly_From_Overpower (Count=121), Alias=false
    2022-07-23 17:11:01.372  - info: history.0 (504) enabled logging of javascript.0.Solar.Monthly_From_Overpower (Count=122), Alias=false
    2022-07-23 17:11:01.372  - info: history.0 (504) enabled logging of javascript.0.Solar.Yearly_From_Overpower (Count=123), Alias=false
    2022-07-23 17:11:01.372  - info: history.0 (504) enabled logging of javascript.0.Solar.Daily_From_Overpower_Total (Count=124), Alias=false
    2022-07-23 17:11:01.373  - info: history.0 (504) enabled logging of javascript.0.Solar.Weekly_From_Overpower_Total (Count=125), Alias=false
    2022-07-23 17:11:01.373  - info: history.0 (504) enabled logging of javascript.0.Solar.Monthly_From_Overpower_Total (Count=126), Alias=false
    2022-07-23 17:11:01.373  - info: history.0 (504) enabled logging of javascript.0.Solar.Yearly_From_Overpower_Total (Count=127), Alias=false
    2022-07-23 17:11:01.373  - info: history.0 (504) enabled logging of javascript.0.Solar.Power_Overpower (Count=128), Alias=false
    2022-07-23 17:11:01.373  - info: history.0 (504) enabled logging of plenticore.0.devices.local.battery.SoC (Count=129), Alias=false
    2022-07-23 17:11:01.373  - info: history.0 (504) enabled logging of plenticore.0.devices.local.battery.Charge_P (Count=130), Alias=false
    2022-07-23 17:11:01.373  - info: history.0 (504) enabled logging of jarvis.0.addNotification (Count=131), Alias=false
    2022-07-23 17:11:01.374  - info: history.0 (504) enabled logging of hm-rpc.1.00201D89A26CC9.1.SET_POINT_TEMPERATURE (Count=132), Alias=false
    2022-07-23 17:11:01.374  - info: history.0 (504) enabled logging of hm-rpc.1.00201D89A26CC9.1.LEVEL (Count=133), Alias=false
    2022-07-23 17:11:01.374  - info: history.0 (504) enabled logging of hm-rpc.1.00201D89A26CC9.1.ACTUAL_TEMPERATURE (Count=134), Alias=false
    2022-07-23 17:11:01.374  - info: history.0 (504) enabled logging of ebus.0.broadcast.messages.betrd.fields.kesseltemp.value (Count=135), Alias=false
    2022-07-23 17:11:01.374  - info: history.0 (504) enabled logging of ebus.0.broadcast.messages.betrd.fields.boilertemp.value (Count=136), Alias=false
    2022-07-23 17:11:01.374  - info: history.0 (504) enabled logging of ebus.0.broadcast.messages.betrd.fields.aussentemp.value (Count=137), Alias=false
    2022-07-23 17:11:01.375  - info: history.0 (504) enabled logging of ebus.0.broadcast.messages.sollw.fields.kesselsolltemp.value (Count=138), Alias=false
    2022-07-23 17:11:01.375  - info: history.0 (504) enabled logging of ebus.0.broadcast.messages.sollw.fields.aussentemp.value (Count=139), Alias=false
    2022-07-23 17:11:01.375  - info: history.0 (504) enabled logging of ebus.0.broadcast.messages.sollw.fields.brauchwassersolltemp.value (Count=140), Alias=false
    2022-07-23 17:11:01.375  - info: history.0 (504) enabled logging of ping.0.iobroker.Repeater1200.alive (Count=141), Alias=false
    2022-07-23 17:11:01.375  - info: history.0 (504) enabled logging of ping.0.iobroker.Repeater1200.time (Count=142), Alias=false
    2022-07-23 17:11:01.375  - info: history.0 (504) enabled logging of ping.0.iobroker.Repeater1750.alive (Count=143), Alias=false
    2022-07-23 17:11:01.376  - info: history.0 (504) enabled logging of ping.0.iobroker.Repeater1750.time (Count=144), Alias=false
    2022-07-23 17:11:01.376  - info: history.0 (504) enabled logging of ping.0.iobroker.Repeater3000.alive (Count=145), Alias=false
    2022-07-23 17:11:01.376  - info: history.0 (504) enabled logging of ping.0.iobroker.Repeater3000.time (Count=146), Alias=false
    2022-07-23 17:11:03.858  - info: host.iobroker instance system.adapter.alexa2.0 started with pid 519
    2022-07-23 17:11:05.114  - info: alexa2.0 (519) starting. Version 3.12.0 in /opt/iobroker/node_modules/iobroker.alexa2, node: v16.16.0, js-controller: 4.0.23
    2022-07-23 17:11:07.862  - info: host.iobroker instance system.adapter.hm-rega.0 started with pid 546
    2022-07-23 17:11:08.321  - info: alexa2.0 (519) Alexa-Push-Connection (macDms = true) established. Disable Polling
    2022-07-23 17:11:08.818  - info: alexa2.0 (519) Unknown Device, but enabling commands, Try it and report back if commands work.
    2022-07-23 17:11:08.818  - info: alexa2.0 (519) Report to developer as GitHub issue with details for device. Please grab full next line pot. from logfile on disk if cutted
    2022-07-23 17:11:08.819  - info: alexa2.0 (519)     Device-type:A3EVMLQTU6WL1W (ARTHUR_TARGET,SUPPORTS_LOCALE_SWITCH,FLASH_BRIEFING,MULTI_WAKEWORDS_SUPPORTED,CUSTOM_ALARM_TONE,SOUND_SETTINGS,VOLUME_SETTING,MICROPHONE,CHANGE_NAME,SHARKNADO,SUPPORTS_CONNECTED_HOME_CLOUD_ONLY,PERSISTENT_CONNECTION,EARCONS,BT_PAIRING_FLOW_V2,ASCENDING_ALARM_VOLUME,ADAPTIVE_LISTENING,SUPPORTS_SOFTWARE_VERSION,PAIR_BT_SINK,DIALOG_INTERFACE_VERSION,TIMERS_AND_ALARMS,SUPPORTS_LOCALE,SPEECH_RECOGNIZER_USS,ACTIVE_AFTER_FRO,REMINDERS)
    2022-07-23 17:11:09.337  - info: hm-rega.0 (546) starting. Version 3.0.40 in /opt/iobroker/node_modules/iobroker.hm-rega, node: v16.16.0, js-controller: 4.0.23
    2022-07-23 17:11:09.476  - info: hm-rega.0 (546) subscribe hm-rpc.0.BidCoS-RF.50.PRESS_SHORT
    2022-07-23 17:11:09.541  - info: hm-rega.0 (546) ReGaHSS 192.168.86.50 up
    2022-07-23 17:11:10.216  - warn: hm-rega.0 (546) time difference local-ccu 55s
    2022-07-23 17:11:11.868  - info: host.iobroker instance system.adapter.hm-rpc.0 started with pid 561
    2022-07-23 17:11:13.109  - info: hm-rega.0 (546) request state values
    2022-07-23 17:11:13.714  - info: hm-rpc.0 (561) starting. Version 1.15.12 (non-npm: ioBroker/ioBroker.hm-rpc) in /opt/iobroker/node_modules/iobroker.hm-rpc, node: v16.16.0, js-controller: 4.0.23
    2022-07-23 17:11:13.887  - info: hm-rpc.0 (561) xmlrpc server is trying to listen on 192.168.86.35:2001
    2022-07-23 17:11:13.888  - info: hm-rpc.0 (561) xmlrpc client is trying to connect to 192.168.86.50:2001/ with ["http://192.168.86.35:2001","iobroker:hm-rpc.0:51f4679f58faa9997c53c2e24bcfe14e"]
    2022-07-23 17:11:13.939  - info: hm-rpc.0 (561) xmlrpc <- system.listMethods ["iobroker:hm-rpc.0:51f4679f58faa9997c53c2e24bcfe14e"]
    2022-07-23 17:11:13.958  - info: hm-rpc.0 (561) xmlrpc <- listDevices ["iobroker:hm-rpc.0:51f4679f58faa9997c53c2e24bcfe14e"]
    2022-07-23 17:11:14.036  - info: hm-rpc.0 (561) xmlrpc -> 179 devices
    2022-07-23 17:11:14.096  - info: hm-rpc.0 (561) Connected
    2022-07-23 17:11:14.646  - info: javascript.0 (434) script.js.common.Homematic_Meldungen: STICKY_UNREACH Meldung: hm-rpc.0.NEQ1773663.0.STICKY_UNREACH wurde auf <true> gesetzt. Das Homematic Gerät ist wieder uneingeschränkt erreichbar.
    2022-07-23 17:11:14.647  - info: javascript.0 (434) script.js.common.Homematic_Meldungen: Homematic-Servicemeldungen: Phillip Heizung  ist nicht erreichbar<br>Keller Aufgang Heizung  ist nicht erreichbar<br>Weihnachtsbeleuchtung  ist nicht erreichbar<br>Phillip Heizung  hat eine schlechte Batterie<br>Keller Aufgang Heizung  hat eine schlechte Batterie<br>
    2022-07-23 17:11:14.647  - info: javascript.0 (434) script.js.common.Homematic_Meldungen: Anzahl Homematic-Servicemeldungen: 5
    2022-07-23 17:11:14.648  - info: javascript.0 (434) script.js.common.Homematic_Meldungen: STICKY_UNREACH Meldung: hm-rpc.0.OEQ0669002.0.STICKY_UNREACH wurde auf <true> gesetzt. Das Homematic Gerät ist wieder uneingeschränkt erreichbar.
    2022-07-23 17:11:14.649  - info: javascript.0 (434) script.js.common.Homematic_Meldungen: Homematic-Servicemeldungen: Phillip Heizung  ist nicht erreichbar<br>Keller Aufgang Heizung  ist nicht erreichbar<br>Weihnachtsbeleuchtung  ist nicht erreichbar<br>Phillip Heizung  hat eine schlechte Batterie<br>Keller Aufgang Heizung  hat eine schlechte Batterie<br>
    2022-07-23 17:11:14.649  - info: javascript.0 (434) script.js.common.Homematic_Meldungen: Anzahl Homematic-Servicemeldungen: 5
    2022-07-23 17:11:14.937  - info: javascript.0 (434) script.js.common.Homematic_Meldungen: Homematic-Servicemeldungen: Phillip Heizung  ist nicht erreichbar<br>Keller Aufgang Heizung  ist nicht erreichbar<br>Weihnachtsbeleuchtung  ist nicht erreichbar<br>Phillip Heizung  hat eine schlechte Batterie<br>Keller Aufgang Heizung  hat eine schlechte Batterie<br>
    2022-07-23 17:11:14.937  - info: javascript.0 (434) script.js.common.Homematic_Meldungen: Anzahl Homematic-Servicemeldungen: 5
    2022-07-23 17:11:14.938  - info: javascript.0 (434) script.js.common.Jarvis: Phillip Heizung  ist nicht erreichbar<br>Keller Aufgang Heizung  ist nicht erreichbar<br>Weihnachtsbeleuchtung  ist nicht erreichbar<br>Phillip Heizung  hat eine schlechte Batterie<br>Keller Aufgang Heizung  hat eine schlechte Batterie<br>
    2022-07-23 17:11:14.938  - info: javascript.0 (434) script.js.common.Homematic_Meldungen: Homematic-Servicemeldungen: Phillip Heizung  ist nicht erreichbar<br>Keller Aufgang Heizung  ist nicht erreichbar<br>Weihnachtsbeleuchtung  ist nicht erreichbar<br>Phillip Heizung  hat eine schlechte Batterie<br>Keller Aufgang Heizung  hat eine schlechte Batterie<br>
    2022-07-23 17:11:14.939  - info: javascript.0 (434) script.js.common.Homematic_Meldungen: Anzahl Homematic-Servicemeldungen: 5
    2022-07-23 17:11:14.939  - info: javascript.0 (434) script.js.common.Jarvis: Phillip Heizung  ist nicht erreichbar<br>Keller Aufgang Heizung  ist nicht erreichbar<br>Weihnachtsbeleuchtung  ist nicht erreichbar<br>Phillip Heizung  hat eine schlechte Batterie<br>Keller Aufgang Heizung  hat eine schlechte Batterie<br>
    2022-07-23 17:11:15.230  - info: javascript.0 (434) script.js.common.Jarvis: Phillip Heizung  ist nicht erreichbar<br>Keller Aufgang Heizung  ist nicht erreichbar<br>Weihnachtsbeleuchtung  ist nicht erreichbar<br>Phillip Heizung  hat eine schlechte Batterie<br>Keller Aufgang Heizung  hat eine schlechte Batterie<br>
    2022-07-23 17:11:15.327  - info: javascript.0 (434) script.js.common.Jarvis: Phillip Heizung  ist nicht erreichbar<br>Keller Aufgang Heizung  ist nicht erreichbar<br>Weihnachtsbeleuchtung  ist nicht erreichbar<br>Phillip Heizung  hat eine schlechte Batterie<br>Keller Aufgang Heizung  hat eine schlechte Batterie<br>
    2022-07-23 17:11:15.328  - info: javascript.0 (434) script.js.common.Homematic_Meldungen: STICKY_UNREACH Meldung: hm-rpc.0.NEQ0871224.0.STICKY_UNREACH wurde auf <true> gesetzt. Das Homematic Gerät ist wieder uneingeschränkt erreichbar.
    2022-07-23 17:11:15.329  - info: javascript.0 (434) script.js.common.Homematic_Meldungen: Homematic-Servicemeldungen: Phillip Heizung  ist nicht erreichbar<br>Keller Aufgang Heizung  ist nicht erreichbar<br>Weihnachtsbeleuchtung  ist nicht erreichbar<br>Phillip Heizung  hat eine schlechte Batterie<br>Keller Aufgang Heizung  hat eine schlechte Batterie<br>
    2022-07-23 17:11:15.329  - info: javascript.0 (434) script.js.common.Homematic_Meldungen: Anzahl Homematic-Servicemeldungen: 5
    2022-07-23 17:11:15.878  - info: host.iobroker instance system.adapter.hm-rpc.1 started with pid 576
    2022-07-23 17:11:15.957  - info: javascript.0 (434) script.js.common.Homematic_Meldungen: STICKY_UNREACH Meldung: hm-rpc.0.NEQ0401353.0.STICKY_UNREACH wurde auf <true> gesetzt. Das Homematic Gerät ist wieder uneingeschränkt erreichbar.
    2022-07-23 17:11:15.958  - info: javascript.0 (434) script.js.common.Homematic_Meldungen: Homematic-Servicemeldungen: Phillip Heizung  ist nicht erreichbar<br>Keller Aufgang Heizung  ist nicht erreichbar<br>Weihnachtsbeleuchtung  ist nicht erreichbar<br>Phillip Heizung  hat eine schlechte Batterie<br>Keller Aufgang Heizung  hat eine schlechte Batterie<br>
    2022-07-23 17:11:15.958  - info: javascript.0 (434) script.js.common.Homematic_Meldungen: Anzahl Homematic-Servicemeldungen: 5
    2022-07-23 17:11:15.959  - info: javascript.0 (434) script.js.common.Homematic_Meldungen: Homematic-Servicemeldungen: Phillip Heizung  ist nicht erreichbar<br>Keller Aufgang Heizung  ist nicht erreichbar<br>Weihnachtsbeleuchtung  ist nicht erreichbar<br>Phillip Heizung  hat eine schlechte Batterie<br>Keller Aufgang Heizung  hat eine schlechte Batterie<br>
    2022-07-23 17:11:15.960  - info: javascript.0 (434) script.js.common.Homematic_Meldungen: Anzahl Homematic-Servicemeldungen: 5
    2022-07-23 17:11:15.960  - info: javascript.0 (434) script.js.common.Jarvis: Phillip Heizung  ist nicht erreichbar<br>Keller Aufgang Heizung  ist nicht erreichbar<br>Weihnachtsbeleuchtung  ist nicht erreichbar<br>Phillip Heizung  hat eine schlechte Batterie<br>Keller Aufgang Heizung  hat eine schlechte Batterie<br>
    2022-07-23 17:11:16.329  - info: javascript.0 (434) script.js.common.Homematic_Meldungen: Homematic-Servicemeldungen: Phillip Heizung  ist nicht erreichbar<br>Keller Aufgang Heizung  ist nicht erreichbar<br>Weihnachtsbeleuchtung  ist nicht erreichbar<br>Phillip Heizung  hat eine schlechte Batterie<br>Keller Aufgang Heizung  hat eine schlechte Batterie<br>
    2022-07-23 17:11:16.329  - info: javascript.0 (434) script.js.common.Homematic_Meldungen: Anzahl Homematic-Servicemeldungen: 5
    2022-07-23 17:11:16.330  - info: javascript.0 (434) script.js.common.Jarvis: Phillip Heizung  ist nicht erreichbar<br>Keller Aufgang Heizung  ist nicht erreichbar<br>Weihnachtsbeleuchtung  ist nicht erreichbar<br>Phillip Heizung  hat eine schlechte Batterie<br>Keller Aufgang Heizung  hat eine schlechte Batterie<br>
    2022-07-23 17:11:16.330  - info: javascript.0 (434) script.js.common.Jarvis: Phillip Heizung  ist nicht erreichbar<br>Keller Aufgang Heizung  ist nicht erreichbar<br>Weihnachtsbeleuchtung  ist nicht erreichbar<br>Phillip Heizung  hat eine schlechte Batterie<br>Keller Aufgang Heizung  hat eine schlechte Batterie<br>
    2022-07-23 17:11:16.429  - info: hm-rega.0 (546) Updated all datapoints
    2022-07-23 17:11:16.524  - info: javascript.0 (434) script.js.common.Jarvis: Phillip Heizung  ist nicht erreichbar<br>Keller Aufgang Heizung  ist nicht erreichbar<br>Weihnachtsbeleuchtung  ist nicht erreichbar<br>Phillip Heizung  hat eine schlechte Batterie<br>Keller Aufgang Heizung  hat eine schlechte Batterie<br>
    2022-07-23 17:11:16.698  - info: hm-rega.0 (546) added/updated 1 objects
    2022-07-23 17:11:16.729  - info: hm-rega.0 (546) got 42 variables
    2022-07-23 17:11:17.509  - info: hm-rega.0 (546) added/updated 42 variables
    2022-07-23 17:11:17.510  - info: hm-rega.0 (546) deleted 0 variables
    2022-07-23 17:11:17.538  - info: hm-rega.0 (546) got 48 programs
    2022-07-23 17:11:17.550  - info: hm-rpc.1 (576) starting. Version 1.15.12 (non-npm: ioBroker/ioBroker.hm-rpc) in /opt/iobroker/node_modules/iobroker.hm-rpc, node: v16.16.0, js-controller: 4.0.23
    2022-07-23 17:11:17.692  - info: hm-rpc.1 (576) xmlrpc server is trying to listen on 192.168.86.35:2010
    2022-07-23 17:11:17.693  - info: hm-rpc.1 (576) xmlrpc client is trying to connect to 192.168.86.50:2010/ with ["http://192.168.86.35:2010","iobroker:hm-rpc.1:ef79136c1d2ef92154b3f6604ef29adf"]
    2022-07-23 17:11:17.727  - info: hm-rpc.1 (576) Connected
    2022-07-23 17:11:17.738  - info: hm-rpc.1 (576) xmlrpc <- listDevices ["iobroker:hm-rpc.1:ef79136c1d2ef92154b3f6604ef29adf"]
    2022-07-23 17:11:17.812  - info: hm-rpc.1 (576) xmlrpc -> 0 devices
    2022-07-23 17:11:18.291  - info: hm-rpc.1 (576) xmlrpc <- newDevices 212
    2022-07-23 17:11:18.366  - info: hm-rpc.1 (576) new HMIP devices/channels after filter: 0
    2022-07-23 17:11:18.422  - info: hm-rega.0 (546) added/updated 48 programs
    2022-07-23 17:11:18.423  - info: hm-rega.0 (546) deleted 0 programs
    2022-07-23 17:11:19.856  - info: host.iobroker instance system.adapter.hm-rpc.2 started with pid 591
    2022-07-23 17:11:21.206  - info: hm-rpc.2 (591) starting. Version 1.15.12 (non-npm: ioBroker/ioBroker.hm-rpc) in /opt/iobroker/node_modules/iobroker.hm-rpc, node: v16.16.0, js-controller: 4.0.23
    2022-07-23 17:11:21.351  - info: hm-rpc.2 (591) binrpc server is trying to listen on 192.168.86.35:8701
    2022-07-23 17:11:21.351  - info: hm-rpc.2 (591) binrpc client is trying to connect to 192.168.86.50:8701/ with ["xmlrpc_bin://192.168.86.35:8701","iobroker:hm-rpc.2:2a319a3ec7ec9ea22f86865c577e678a"]
    2022-07-23 17:11:21.426  - info: hm-rpc.2 (591) binrpc -> listDevices 36
    2022-07-23 17:11:21.477  - info: hm-rpc.2 (591) new CUxD devices/channels after filter: 0
    2022-07-23 17:11:21.479  - info: hm-rpc.2 (591) Connected
    2022-07-23 17:11:23.126  - info: alexa2.0 (519) Subscribing to states...
    
    2022-07-23 17:11:23.990  - info: host.iobroker instance system.adapter.hue.0 started with pid 619
    2022-07-23 17:11:25.440  - info: hue.0 (619) starting. Version 3.7.0 in /opt/iobroker/node_modules/iobroker.hue, node: v16.16.0, js-controller: 4.0.23
    2022-07-23 17:11:25.634  - info: hue.0 (619) skip switch: Daylight.configured
    2022-07-23 17:11:25.635  - info: hue.0 (619) skip switch: Daylight.sunriseoffset
    2022-07-23 17:11:25.635  - info: hue.0 (619) skip switch: Daylight.sunsetoffset
    2022-07-23 17:11:25.638  - info: hue.0 (619) skip switch: Küche wall switch module 1.devicemode
    2022-07-23 17:11:25.638  - info: hue.0 (619) skip switch: Küche wall switch module 1.devicemodevalues
    2022-07-23 17:11:25.640  - info: hue.0 (619) skip switch: Hue wall switch module 1.devicemode
    2022-07-23 17:11:25.640  - info: hue.0 (619) skip switch: Hue wall switch module 1.devicemodevalues
    2022-07-23 17:11:25.641  - info: hue.0 (619) created/updated 4 sensor channels
    2022-07-23 17:11:25.769  - info: hue.0 (619) created/updated 11 light channels
    2022-07-23 17:11:25.773  - info: hue.0 (619) created/updated 6 groups channels
    2022-07-23 17:11:25.776  - info: hue.0 (619) created/updated 25 scenes
    2022-07-23 17:11:25.776  - info: hue.0 (619) creating/updating bridge device
    2022-07-23 17:11:27.861  - info: host.iobroker instance system.adapter.modbus.0 started with pid 634
    2022-07-23 17:11:29.078  - info: modbus.0 (634) starting. Version 5.0.4 in /opt/iobroker/node_modules/iobroker.modbus, node: v16.16.0, js-controller: 4.0.23
    2022-07-23 17:11:29.343  - info: modbus.0 (634) Connected to slave 192.168.86.153
    2022-07-23 17:11:31.880  - info: host.iobroker instance system.adapter.fritzbox.0 started with pid 649
    2022-07-23 17:11:33.369  - info: fritzbox.0 (649) starting. Version 0.5.0 (non-npm: ruhr70/ioBroker.fritzbox) in /opt/iobroker/node_modules/iobroker.fritzbox, node: v16.16.0, js-controller: 4.0.23
    2022-07-23 17:11:33.394  - info: fritzbox.0 (649) try to connect: 192.168.86.1
    2022-07-23 17:11:33.395  - info: fritzbox.0 (649) Trying to connect to TR-064: 192.168.86.1:49000
    2022-07-23 17:11:33.419  - info: fritzbox.0 (649) adapter connected to fritzbox: 192.168.86.1
    2022-07-23 17:11:34.488  - info: fritzbox.0 (649) Successfully connected to TR-064
    2022-07-23 17:11:34.599  - warn: fritzbox.0 (649) TR-064: Error reading files from dir /tam: Error: ENOENT: no such file or directory, scandir 'tam'
    2022-07-23 17:11:35.861  - info: host.iobroker instance system.adapter.ping.0 started with pid 677
    2022-07-23 17:11:37.074  - info: ping.0 (677) starting. Version 1.5.3 in /opt/iobroker/node_modules/iobroker.ping, node: v16.16.0, js-controller: 4.0.23
    2022-07-23 17:11:37.183  - warn: ping.0 (677) Object ping.0.iobroker.Repeater3000. is invalid: obj.type has to exist
    2022-07-23 17:11:37.183  - warn: ping.0 (677) This object will not be created in future versions. Please report this to the developer.
    2022-07-23 17:11:37.184  - error: ping.0 (677) Cannot update channel : ping.0.iobroker.Repeater3000 Error: Error: The id "ping.0.iobroker.Repeater3000." is invalid. Ids are not allowed to end in "."
    2022-07-23 17:11:39.863  - info: host.iobroker instance system.adapter.backitup.0 started with pid 695
    2022-07-23 17:11:41.163  - info: backitup.0 (695) starting. Version 2.4.9 in /opt/iobroker/node_modules/iobroker.backitup, node: v16.16.0, js-controller: 4.0.23
    2022-07-23 17:11:41.222  - info: backitup.0 (695) [iobroker] backup was activated at 02:00 every 3 day(s)
    2022-07-23 17:11:41.260  - info: backitup.0 (695) [ccu] backup was activated at 01:30 every 7 day(s)
    2022-07-23 17:11:43.860  - info: host.iobroker instance system.adapter.ebus.0 started with pid 710
    2022-07-23 17:11:45.187  - info: ebus.0 (710) starting. Version 3.0.2 (non-npm: rg-engineering/ioBroker.ebus) in /opt/iobroker/node_modules/iobroker.ebus, node: v16.16.0, js-controller: 4.0.23
    2022-07-23 17:11:47.860  - info: host.iobroker instance system.adapter.info.0 started with pid 725
    2022-07-23 17:11:49.855  - info: info.0 (725) starting. Version 1.9.19 in /opt/iobroker/node_modules/iobroker.info, node: v16.16.0, js-controller: 4.0.23
    2022-07-23 17:11:49.916  - info: info.0 (725) Reading/updating systemdata.
    2022-07-23 17:11:50.375  - info: info.0 (725) State value to set for "info.0.sysinfo.cpu.info.speed" has to be type "string" but received type "number" 
    2022-07-23 17:11:50.399  - info: info.0 (725) State value to set for "info.0.sysinfo.cpu.info.cache-l3" has to be type "number" but received type "string" 
    2022-07-23 17:11:50.444  - info: info.0 (725) Reading CPU data every 3 seconds.
    2022-07-23 17:11:50.510  - info: info.0 (725) cpu Temp res = {"main":46,"cores":[47,47,48,49],"max":49,"socket":[],"chipset":null}
    2022-07-23 17:11:50.528  - info: info.0 (725) Reading CPU temp data every 3 seconds.
    2022-07-23 17:11:50.546  - info: info.0 (725) Reading CPU current speed every 3 seconds.
    2022-07-23 17:11:50.579  - info: info.0 (725) Reading memory data every 3 seconds.
    2022-07-23 17:11:50.668  - info: info.0 (725) Reading battery data every 8 seconds.
    2022-07-23 17:11:51.085  - info: info.0 (725) Reading user data every 8 seconds.
    2022-07-23 17:11:51.159  - info: info.0 (725) Reading process data every 8 seconds.
    2022-07-23 17:11:51.660  - info: info.0 (725) State value to set for "info.0.sysinfo.disks.diskLayout.dev4.size" has to be type "string" but received type "number" 
    2022-07-23 17:11:51.663  - info: info.0 (725) State value to set for "info.0.sysinfo.disks.diskLayout.dev0.size" has to be type "string" but received type "number" 
    2022-07-23 17:11:51.664  - info: info.0 (725) State value to set for "info.0.sysinfo.disks.diskLayout.dev1.size" has to be type "string" but received type "number" 
    2022-07-23 17:11:51.666  - info: info.0 (725) State value to set for "info.0.sysinfo.disks.diskLayout.dev2.size" has to be type "string" but received type "number" 
    2022-07-23 17:11:51.666  - info: info.0 (725) State value to set for "info.0.sysinfo.disks.diskLayout.dev3.size" has to be type "string" but received type "number" 
    2022-07-23 17:11:51.691  - info: info.0 (725) Reading disk data every 8 seconds.
    2022-07-23 17:11:51.862  - info: host.iobroker instance system.adapter.iot.0 started with pid 1109
    2022-07-23 17:11:52.318  - info: info.0 (725) Reading network data every 3 seconds.
    2022-07-23 17:11:53.362  - info: iot.0 (1109) starting. Version 1.11.4 in /opt/iobroker/node_modules/iobroker.iot, node: v16.16.0, js-controller: 4.0.23
    2022-07-23 17:11:53.400  - info: iot.0 (1109) Connecting with a18wym7vjdl22g.iot.eu-west-1.amazonaws.com
    2022-07-23 17:11:53.698  - info: iot.0 (1109) Connection changed: connect
    2022-07-23 17:11:57.012  - info: vis.0 (1230) starting. Version 1.4.15 in /opt/iobroker/node_modules/iobroker.vis, node: v16.16.0, js-controller: 4.0.23
    2022-07-23 17:11:57.181  - info: vis.0 (1230) vis license is OK.
    2022-07-23 17:11:57.982  - info: vis.0 (1230) Terminated (NO_ERROR): Without reason
    2022-07-23 17:11:58.572  - info: host.iobroker instance system.adapter.vis.0 terminated while should be started once
    2022-07-23 17:11:59.856  - info: host.iobroker instance system.adapter.web.0 started with pid 1377
    2022-07-23 17:12:01.178  - info: web.0 (1377) starting. Version 4.3.0 in /opt/iobroker/node_modules/iobroker.web, node: v16.16.0, js-controller: 4.0.23
    2022-07-23 17:12:01.332  - info: web.0 (1377) socket.io server listening on port 8081
    2022-07-23 17:12:01.335  - info: web.0 (1377) http server listening on port 8081
    2022-07-23 17:12:04.949  - info: vis-google-fonts.0 (1444) starting. Version 1.0.3 in /opt/iobroker/node_modules/iobroker.vis-google-fonts, node: v16.16.0, js-controller: 4.0.23
    2022-07-23 17:12:05.540  - info: vis-google-fonts.0 (1444) Terminated (NO_ERROR): Without reason
    2022-07-23 17:12:06.133  - info: host.iobroker instance system.adapter.vis-google-fonts.0 terminated while should be started once
    2022-07-23 17:12:07.867  - info: host.iobroker instance scheduled system.adapter.daswetter.0 */15 * * * *
    2022-07-23 17:12:07.889  - info: host.iobroker instance system.adapter.daswetter.0 started with pid 1573
    2022-07-23 17:12:09.198  - info: daswetter.0 (1573) starting. Version 3.1.2 in /opt/iobroker/node_modules/iobroker.daswetter, node: v16.16.0, js-controller: 4.0.23
    2022-07-23 17:12:11.797  - info: host.iobroker instance system.adapter.systeminfo.0 started with pid 1679
    2022-07-23 17:12:13.193  - info: systeminfo.0 (1679) starting. Version 0.3.0 (non-npm: frankjoke/ioBroker.systeminfo) in /opt/iobroker/node_modules/iobroker.systeminfo, node: v16.16.0, js-controller: 4.0.23
    2022-07-23 17:12:14.173  - info: systeminfo.0 (1679) Startup Systeminfo Adapter systeminfo.0: {  startup: '',  items: [    {      name: 'Piko.[Type/Value]',      type: 'web',      source: 'http://192.168.86.157/measurements.xml',      regexp: "Device.Measurements.Measurement[?(@.Type=='AC_Power' || @.Type=='DC_Voltage' || @.Type=='DC_Current')]",      conv: 'xml',      role: 'number',      write: '',      sched: '*/10 * * * * *'    }  ],  lang: 'de',  latitude: 51.9793,  longitude: 7.7942}
    2022-07-23 17:12:14.309  - info: systeminfo.0 (1679) Adapter systeminfo.0 started and found 1/3 items/states to process.
    2022-07-23 17:12:15.864  - info: host.iobroker instance system.adapter.bring.0 started with pid 1787
    2022-07-23 17:12:17.300  - info: bring.0 (1787) starting. Version 1.8.1 in /opt/iobroker/node_modules/iobroker.bring, node: v16.16.0, js-controller: 4.0.23
    2022-07-23 17:12:17.791  - info: bring.0 (1787) [LOGIN] Successfully logged in as stephan
    2022-07-23 17:12:19.040  - info: daswetter.0 (1573) still wrong data structure from server received! repaired...
    2022-07-23 17:12:19.872  - info: host.iobroker instance system.adapter.plenticore.0 started with pid 1863
    2022-07-23 17:12:21.457  - info: plenticore.0 (1863) starting. Version 2.2.0 in /opt/iobroker/node_modules/iobroker.plenticore, node: v16.16.0, js-controller: 4.0.23
    2022-07-23 17:12:21.478  - info: plenticore.0 (1863) [START] Starting adapter plenticore v2.2.0r237
    2022-07-23 17:12:21.529  - info: plenticore.0 (1863) Configured Wp of panel(s) is 0
    2022-07-23 17:12:21.530  - info: plenticore.0 (1863) [INFO] Configured polling interval: 20000
    2022-07-23 17:12:21.801  - info: web.0 (1377) ==> Connected system.user.admin from ::ffff:192.168.86.118
    2022-07-23 17:12:21.894  - info: plenticore.0 (1863) Not enabling forecast data.
    2022-07-23 17:12:21.895  - info: plenticore.0 (1863) Not enabling MinSoC forecast data.
    2022-07-23 17:12:22.606  - info: daswetter.0 (1573) Terminated (ADAPTER_REQUESTED_TERMINATION): All data handled, adapter stopped until next scheduled moment
    2022-07-23 17:12:23.115  - info: daswetter.0 (1573) cleaned everything up...
    2022-07-23 17:12:23.191  - info: host.iobroker instance system.adapter.daswetter.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
    2022-07-23 17:12:23.916  - info: host.iobroker instance system.adapter.jarvis.0 started with pid 2066
    2022-07-23 17:12:25.208  - info: jarvis.0 (2066) starting. Version 3.0.12-beta.3 (non-npm: Zefau/ioBroker.jarvis#bacd7221d9990610ee6c684e0ec6fddd397cde79) in /opt/iobroker/node_modules/iobroker.jarvis, node: v16.16.0, js-controller: 4.0.23
    2022-07-23 17:12:25.258  - info: jarvis.0 (2066) Found Backups for layout.
    2022-07-23 17:12:25.260  - info: jarvis.0 (2066) Found Backups for styles.
    2022-07-23 17:12:25.260  - info: jarvis.0 (2066) Found Backups for settings.
    2022-07-23 17:12:25.261  - info: jarvis.0 (2066) Found Backups for widgets.
    2022-07-23 17:12:25.284  - info: jarvis.0 (2066) Found Backups for devices.
    2022-07-23 17:12:27.798  - info: host.iobroker instance system.adapter.yahka.0 started with pid 2140
    2022-07-23 17:12:29.202  - info: yahka.0 (2140) starting. Version 0.13.1 in /opt/iobroker/node_modules/iobroker.yahka, node: v16.16.0, js-controller: 4.0.23
    2022-07-23 17:12:29.224  - info: yahka.0 (2140) adapter ready, checking config
    2022-07-23 17:12:29.232  - info: yahka.0 (2140) adding Wohnzimmer Heizung with UUID: 2521183a-dec7-421a-a763-c10f4be10961
    2022-07-23 17:12:29.237  - info: yahka.0 (2140) publishing bridge iobroker on 0.0.0.0 using ciao
    
    GlasfaserG Offline
    GlasfaserG Offline
    Glasfaser
    schrieb am zuletzt editiert von
    #17

    @stephan1827 sagte in admin interface leer:

    2022-07-23 17:10:45.168 - info: admin.0 (419) starting. Version 5.3.8 in /opt/iobroker/node_modules/iobroker.admin, node: v16.16.0, js-controller: 4.0.23

    Der Admin läuft doch ... und jetzt

    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 ..

    stephan1827S 1 Antwort Letzte Antwort
    0
    • Thomas BraunT Thomas Braun

      @stephan1827 sagte in admin interface leer:

      2022-07-23 17:10:52.007  - error: javascript.0 (434) The Mirror directory is not allowed to be a central ioBroker directory!         
      2022-07-23 17:10:52.007  - error: javascript.0 (434) Directory /opt/iobroker/backups/scripte is not allowed to mirror files!
      

      Ändern, mit dem jetzigen Setup läufst du Gefahr da Schleifen anzulegen.

      stephan1827S Offline
      stephan1827S Offline
      stephan1827
      schrieb am zuletzt editiert von
      #18

      @thomas-braun sagte in admin interface leer:

      rectory is not allowed to be a central ioBroker directory! 2022-07-23 17:10:52.007 - error: javascript.0 (434) Directory /opt/iobroker/backups/scripte is not allowed to mirror files!

      Was soll ich hier ändern? Ich habe schon versucht das wieder auf port 8081 zu stellen aber dann geht garnichts mehr. Außerdem hat es so ja auch mal gelaufen.

      Thomas BraunT 2 Antworten Letzte Antwort
      0
      • stephan1827S stephan1827

        @thomas-braun sagte in admin interface leer:

        rectory is not allowed to be a central ioBroker directory! 2022-07-23 17:10:52.007 - error: javascript.0 (434) Directory /opt/iobroker/backups/scripte is not allowed to mirror files!

        Was soll ich hier ändern? Ich habe schon versucht das wieder auf port 8081 zu stellen aber dann geht garnichts mehr. Außerdem hat es so ja auch mal gelaufen.

        Thomas BraunT Online
        Thomas BraunT Online
        Thomas Braun
        Most Active
        schrieb am zuletzt editiert von
        #19

        @stephan1827

        Hat mit dem admin interface nix zu tun, aber du solltest nach /home/iobroker spiegeln und nicht in den /opt/iobroker-Zweig.

        Aber wie gesagt, eigentlich OT.

        Linux-Werkzeugkasten:
        https://forum.iobroker.net/topic/42952/der-kleine-iobroker-linux-werkzeugkasten
        NodeJS Fixer Skript:
        https://forum.iobroker.net/topic/68035/iob-node-fix-skript
        iob_diag: curl -sLf -o diag.sh https://iobroker.net/diag.sh && bash diag.sh

        1 Antwort Letzte Antwort
        0
        • stephan1827S stephan1827

          @thomas-braun sagte in admin interface leer:

          rectory is not allowed to be a central ioBroker directory! 2022-07-23 17:10:52.007 - error: javascript.0 (434) Directory /opt/iobroker/backups/scripte is not allowed to mirror files!

          Was soll ich hier ändern? Ich habe schon versucht das wieder auf port 8081 zu stellen aber dann geht garnichts mehr. Außerdem hat es so ja auch mal gelaufen.

          Thomas BraunT Online
          Thomas BraunT Online
          Thomas Braun
          Most Active
          schrieb am zuletzt editiert von
          #20

          @stephan1827 sagte in admin interface leer:

          Außerdem hat es so ja auch mal gelaufen.

          Dinge ändern sich und müssen angepasst werden.

          Linux-Werkzeugkasten:
          https://forum.iobroker.net/topic/42952/der-kleine-iobroker-linux-werkzeugkasten
          NodeJS Fixer Skript:
          https://forum.iobroker.net/topic/68035/iob-node-fix-skript
          iob_diag: curl -sLf -o diag.sh https://iobroker.net/diag.sh && bash diag.sh

          1 Antwort Letzte Antwort
          0
          • GlasfaserG Glasfaser

            @stephan1827 sagte in admin interface leer:

            2022-07-23 17:10:45.168 - info: admin.0 (419) starting. Version 5.3.8 in /opt/iobroker/node_modules/iobroker.admin, node: v16.16.0, js-controller: 4.0.23

            Der Admin läuft doch ... und jetzt

            stephan1827S Offline
            stephan1827S Offline
            stephan1827
            schrieb am zuletzt editiert von
            #21

            @glasfaser Noch jemand eine Idee? Ich habe node und js controller neu installiert aber auch das hat nichts gebracht.

            Thomas BraunT 1 Antwort Letzte Antwort
            0
            • stephan1827S stephan1827

              @glasfaser Noch jemand eine Idee? Ich habe node und js controller neu installiert aber auch das hat nichts gebracht.

              Thomas BraunT Online
              Thomas BraunT Online
              Thomas Braun
              Most Active
              schrieb am zuletzt editiert von
              #22

              @stephan1827

              Und was steht im Log?

              Linux-Werkzeugkasten:
              https://forum.iobroker.net/topic/42952/der-kleine-iobroker-linux-werkzeugkasten
              NodeJS Fixer Skript:
              https://forum.iobroker.net/topic/68035/iob-node-fix-skript
              iob_diag: curl -sLf -o diag.sh https://iobroker.net/diag.sh && bash diag.sh

              1 Antwort Letzte Antwort
              0
              • stephan1827S Offline
                stephan1827S Offline
                stephan1827
                schrieb am zuletzt editiert von
                #23

                @thomas-braun sagte in admin interface leer:

                @stephan1827

                Und was steht im Log?

                Die logs habe ich weiter oben gepostet, ich denke der entscheidende Eintrag ist

                oot@iobroker:/opt/iobroker# node node_modules/iobroker.admin/main.js --logs
                2022-07-23 16:08:54.937  - error: admin.0 (30576) admin.0 invalid process id scenario 30454 vs. own ID 30576. Stopping
                2022-07-23 16:08:54.939  - info: admin.0 (30576) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
                
                
                Thomas BraunT GlasfaserG 2 Antworten Letzte Antwort
                0
                • stephan1827S stephan1827

                  @thomas-braun sagte in admin interface leer:

                  @stephan1827

                  Und was steht im Log?

                  Die logs habe ich weiter oben gepostet, ich denke der entscheidende Eintrag ist

                  oot@iobroker:/opt/iobroker# node node_modules/iobroker.admin/main.js --logs
                  2022-07-23 16:08:54.937  - error: admin.0 (30576) admin.0 invalid process id scenario 30454 vs. own ID 30576. Stopping
                  2022-07-23 16:08:54.939  - info: admin.0 (30576) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
                  
                  
                  Thomas BraunT Online
                  Thomas BraunT Online
                  Thomas Braun
                  Most Active
                  schrieb am zuletzt editiert von
                  #24

                  @stephan1827

                  Was JETZT im Log steht, nicht gestern um 16 Uhr.
                  Und NICHT alle root herumeiern!

                  Linux-Werkzeugkasten:
                  https://forum.iobroker.net/topic/42952/der-kleine-iobroker-linux-werkzeugkasten
                  NodeJS Fixer Skript:
                  https://forum.iobroker.net/topic/68035/iob-node-fix-skript
                  iob_diag: curl -sLf -o diag.sh https://iobroker.net/diag.sh && bash diag.sh

                  1 Antwort Letzte Antwort
                  0
                  • stephan1827S stephan1827

                    @thomas-braun sagte in admin interface leer:

                    @stephan1827

                    Und was steht im Log?

                    Die logs habe ich weiter oben gepostet, ich denke der entscheidende Eintrag ist

                    oot@iobroker:/opt/iobroker# node node_modules/iobroker.admin/main.js --logs
                    2022-07-23 16:08:54.937  - error: admin.0 (30576) admin.0 invalid process id scenario 30454 vs. own ID 30576. Stopping
                    2022-07-23 16:08:54.939  - info: admin.0 (30576) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
                    
                    
                    GlasfaserG Offline
                    GlasfaserG Offline
                    Glasfaser
                    schrieb am zuletzt editiert von
                    #25

                    @stephan1827 sagte in admin interface leer:

                    admin.0 invalid process id scenario

                    Dazu gibt es noch das , deshalb habe ich dich oben gefragt :

                    @glasfaser sagte in admin interface leer:
                    Wie sieht es dort mit dem Docker - Netzwerk aus ... alles Identisch mit den Einstellungen zuvor !?

                    https://forum.iobroker.net/topic/36859/gelöst-keine-admin-oberfläche-nach-neuinstallation/26

                    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
                    • stephan1827S Offline
                      stephan1827S Offline
                      stephan1827
                      schrieb am zuletzt editiert von
                      #26

                      @glasfaser Habs mittlerweile durch neu installation des Dockers und einer Kombination aus diversen Backups wieder am Laufen. Keine Ahnung was die Ursache war. Einstellungen sind alle so wie vorher.

                      GlasfaserG 1 Antwort Letzte Antwort
                      0
                      • stephan1827S stephan1827

                        @glasfaser Habs mittlerweile durch neu installation des Dockers und einer Kombination aus diversen Backups wieder am Laufen. Keine Ahnung was die Ursache war. Einstellungen sind alle so wie vorher.

                        GlasfaserG Offline
                        GlasfaserG Offline
                        Glasfaser
                        schrieb am zuletzt editiert von
                        #27

                        @stephan1827 sagte in admin interface leer:

                        Keine Ahnung was die Ursache war. Einstellungen sind alle so wie vorher.

                        Ich Tippe immer noch auf ein Netzwerkproblem / Einstellungssache .

                        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

                        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

                        317

                        Online

                        32.9k

                        Benutzer

                        83.0k

                        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