[Neuer Adapter] nextcloud talk messenger

[hydrotec]

@johen

Ich hab es raus gefunden was da schief gelaufen ist.
Bei den Einstellungen hatte ich "https://meine.domain" anstatt "meine.domain" eingetragen.
Die "chat rooms" werden sofort erkannt, und in den Objekten eingetragen.

Entschuldige bitte die entstandenen Verwirrungen.

Angenehmen Tag noch
Gruß, Karsten

[hydrotec]

@johen

Erste Testläufe bestanden
Funktioniert in beide Richtungen ohne Probleme.

Vielen Dank noch einmal für deine Mühen die du in den Adapter gesteckt hast.

Gruß, Karsten

Edit 06.01.2022
Keine Ahnung warum dieser Beitrag negativ bewertet wird.
(inderessiera würd's mi scho no )
Der Adapter funktioniert bei mir weiterhin ohne Probleme.
Und ich bin Jochen auch weiterhin Dankbar für seine Zeit, und Arbeit, die er in diesen Adapter gesteckt hat.

[johen]

@hydrotec Super freut mich - ein Host URL Format check nehm ich mal mit in die Todos.

Hab inzwischen schnell mal noch mehr debug outputs hinzugefügt, hoffe dabei ist nichts gebrochen.
Zum Aktivierren muss DebugLog konfiguriert werden und zusätzlich (hatte ich nicht auf dem Schirm) das Log Level des Adapter angepasst werden. Werde dies auch nochmal vereinfachen.

[hydrotec]

@johen sagte in [Neuer Adapter] nextcloud talk messenger:

...ein Host URL Format check nehm ich mal mit in die Todos.

Ist sicherlich kein Fehler, nicht das noch einer so bescheuert ist wie ich, und das Protokoll,
welches ja in den Einstellungen rechts oben ausgewählt werden kann, noch einmal unter der Host-Adresse einfügt.

Hab inzwischen schnell mal noch mehr debug outputs hinzugefügt, hoffe dabei ist nichts gebrochen.

Hab mir gleich mal die v0.2.0 geladen.
Bis jetzt ist die Funktion wie bei der v0.1.0, zumindest funktioniert senden/empfangen wie es soll.

Und für dich, zur Info, noch das Log nach einem Neustart von ioBroker mit aktivierter debug Ausgabe.

Spoiler

2021-11-23 11:44:16.261 - info: host.iobroker iobroker.js-controller version 3.3.18 js-controller starting
2021-11-23 11:44:16.263 - info: host.iobroker Copyright (c) 2014-2021 bluefox, 2014 hobbyquaker
2021-11-23 11:44:16.263 - info: host.iobroker hostname: iobroker, node: v14.18.1
2021-11-23 11:44:16.263 - info: host.iobroker ip addresses: 192.168.78.132 2001:16b8:240a:8000:216:3eff:fe69:c509 fe80::216:3eff:fe69:c509
2021-11-23 11:44:16.463 - info: host.iobroker connected to Objects and States
2021-11-23 11:44:16.505 - info: host.iobroker added notifications configuration of host
2021-11-23 11:44:16.517 - warn: host.iobroker logger mqtt.1.zigbee2mqtt.bridge.logging was deleted
2021-11-23 11:44:16.742 - info: host.iobroker 32 instances found
2021-11-23 11:44:16.761 - info: host.iobroker starting 30 instances
2021-11-23 11:44:16.799 - info: host.iobroker instance system.adapter.admin.0 started with pid 291
2021-11-23 11:44:17.433 - info: admin.0 (291) starting. Version 5.1.25 in /opt/iobroker/node_modules/iobroker.admin, node: v14.18.1, js-controller: 3.3.18
2021-11-23 11:44:17.454 - info: admin.0 (291) requesting all states
2021-11-23 11:44:17.454 - info: admin.0 (291) requesting all objects
2021-11-23 11:44:17.784 - info: admin.0 (291) received all objects
2021-11-23 11:44:17.893 - info: admin.0 (291) http server listening on port 8081
2021-11-23 11:44:17.893 - info: admin.0 (291) Use link "http://localhost:8081" to configure.
2021-11-23 11:44:20.793 - info: host.iobroker instance system.adapter.javascript.0 started with pid 428
2021-11-23 11:44:21.673 - info: javascript.0 (428) starting. Version 5.2.13 in /opt/iobroker/node_modules/iobroker.javascript, node: v14.18.1, js-controller: 3.3.18
2021-11-23 11:44:21.727 - info: javascript.0 (428) requesting all states
2021-11-23 11:44:21.727 - info: javascript.0 (428) requesting all objects
2021-11-23 11:44:22.056 - info: javascript.0 (428) received all objects
2021-11-23 11:44:22.084 - info: javascript.0 (428) received all states
2021-11-23 11:44:22.210 - info: javascript.0 (428) Start javascript script.js.g_office.z_office_general.sonos_group_office
2021-11-23 11:44:22.232 - info: javascript.0 (428) script.js.g_office.z_office_general.sonos_group_office: registered 3 subscriptions and 0 schedules
2021-11-23 11:44:22.232 - info: javascript.0 (428) Start javascript script.js.g_bedroom.z_bedroom_general.sonos_group_bedroom
2021-11-23 11:44:22.233 - info: javascript.0 (428) script.js.g_bedroom.z_bedroom_general.sonos_group_bedroom: registered 1 subscription and 0 schedules
2021-11-23 11:44:22.234 - info: javascript.0 (428) Start javascript script.js.g_livingroom.z_livingroom_ambience.z_livingroom_ambience_switch
2021-11-23 11:44:22.239 - info: javascript.0 (428) script.js.g_livingroom.z_livingroom_ambience.z_livingroom_ambience_switch: registered 2 subscriptions and 0 schedules
2021-11-23 11:44:22.239 - info: javascript.0 (428) Start javascript script.js.g_hallway.z_hallway_ceiling.z_hallway_ceiling_switch
2021-11-23 11:44:22.240 - info: javascript.0 (428) script.js.g_hallway.z_hallway_ceiling.z_hallway_ceiling_switch: registered 3 subscriptions and 0 schedules
2021-11-23 11:44:22.241 - info: javascript.0 (428) Start javascript script.js.g_office.z_office_ceiling.z_office_ceiling_switch
2021-11-23 11:44:22.242 - info: javascript.0 (428) script.js.g_office.z_office_ceiling.z_office_ceiling_switch: registered 2 subscriptions and 0 schedules
2021-11-23 11:44:22.244 - info: javascript.0 (428) Start javascript script.js.g_bathroom.z_bathroom_mirror.z_bathroom_mirror_switch
2021-11-23 11:44:22.245 - info: javascript.0 (428) script.js.g_bathroom.z_bathroom_mirror.z_bathroom_mirror_switch: registered 2 subscriptions and 0 schedules
2021-11-23 11:44:22.245 - info: javascript.0 (428) Start javascript script.js.g_kitchen.z_kitchen_countertop.z_kitchen_countertop_switch
2021-11-23 11:44:22.247 - info: javascript.0 (428) script.js.g_kitchen.z_kitchen_countertop.z_kitchen_countertop_switch: registered 2 subscriptions and 0 schedules
2021-11-23 11:44:22.247 - info: javascript.0 (428) Start javascript script.js.g_hallway.z_hallway_apartment_door.z_hallway_apartment_doorbell
2021-11-23 11:44:22.248 - info: javascript.0 (428) script.js.g_hallway.z_hallway_apartment_door.z_hallway_apartment_doorbell: registered 1 subscription and 0 schedules
2021-11-23 11:44:22.248 - info: javascript.0 (428) Start javascript script.js.g_livingroom.z_livingroom_tv.z_livingroom_tv_switch_light
2021-11-23 11:44:22.250 - info: javascript.0 (428) script.js.g_livingroom.z_livingroom_tv.z_livingroom_tv_switch_light: registered 1 subscription and 0 schedules
2021-11-23 11:44:22.250 - info: javascript.0 (428) Start javascript script.js.g_bedroom.z_bedroom_ambience.z_bedroom_ambience_switch
2021-11-23 11:44:22.251 - info: javascript.0 (428) script.js.g_bedroom.z_bedroom_ambience.z_bedroom_ambience_switch: registered 2 subscriptions and 0 schedules
2021-11-23 11:44:22.252 - info: javascript.0 (428) Start javascript script.js.g_hallway.z_hallway_tablet.z_hallway_tablet_switch
2021-11-23 11:44:22.253 - info: javascript.0 (428) script.js.g_hallway.z_hallway_tablet.z_hallway_tablet_switch: registered 1 subscription and 0 schedules
2021-11-23 11:44:22.253 - info: javascript.0 (428) Start javascript script.js.g_hallway.z_hallway_tablet.z_hallway_tablet_dp_mqtt
2021-11-23 11:44:22.255 - info: javascript.0 (428) script.js.g_hallway.z_hallway_tablet.z_hallway_tablet_dp_mqtt: registered 2 subscriptions and 0 schedules
2021-11-23 11:44:22.255 - info: javascript.0 (428) Start javascript script.js.g_kitchen.z_kitchen_ceiling.z_kitchen_ceiling_switch
2021-11-23 11:44:22.257 - info: javascript.0 (428) script.js.g_kitchen.z_kitchen_ceiling.z_kitchen_ceiling_switch: registered 1 subscription and 0 schedules
2021-11-23 11:44:22.258 - info: javascript.0 (428) Start javascript script.js.g_livingroom.z_livingroom_window_north.z_livingroom_window_north_dp_isday
2021-11-23 11:44:22.259 - info: javascript.0 (428) script.js.g_livingroom.z_livingroom_window_north.z_livingroom_window_north_dp_isday: registered 1 subscription and 0 schedules
2021-11-23 11:44:22.260 - info: javascript.0 (428) Start javascript script.js.g_general.z_general_presence.z_general_presence_iCal_4_Anwesenheit_dp_timer
2021-11-23 11:44:22.287 - info: javascript.0 (428) script.js.g_general.z_general_presence.z_general_presence_iCal_4_Anwesenheit_dp_timer: registered 0 subscriptions and 7 schedules
2021-11-23 11:44:22.287 - info: javascript.0 (428) Start javascript script.js.g_general.z_general_presence.z_general_presence_iCal_4_Anwesenheit_dp_state
2021-11-23 11:44:22.289 - info: javascript.0 (428) script.js.g_general.z_general_presence.z_general_presence_iCal_4_Anwesenheit_dp_state: registered 1 subscription and 0 schedules
2021-11-23 11:44:22.289 - info: javascript.0 (428) Start javascript script.js.g_general.z_general_telegram.z_general_telegram_chat
2021-11-23 11:44:22.290 - info: javascript.0 (428) script.js.g_general.z_general_telegram.z_general_telegram_chat: registered 1 subscription and 0 schedules
2021-11-23 11:44:22.291 - info: javascript.0 (428) Start javascript script.js.g_hallway.z_hallway_apartment_door.z_hallway_apartment_dafang_01
2021-11-23 11:44:22.292 - info: javascript.0 (428) script.js.g_hallway.z_hallway_apartment_door.z_hallway_apartment_dafang_01: registered 1 subscription and 0 schedules
2021-11-23 11:44:22.292 - info: javascript.0 (428) Start javascript script.js.g_bedroom.z_bedroom_ceiling.z_bedroom_ceiling_switch
2021-11-23 11:44:22.293 - info: javascript.0 (428) script.js.g_bedroom.z_bedroom_ceiling.z_bedroom_ceiling_switch: registered 1 subscription and 0 schedules
2021-11-23 11:44:22.293 - info: javascript.0 (428) Start javascript script.js.g_general.z_general_presence.z_general_presence_MyPhone11Pro_presence_Siedle_light
2021-11-23 11:44:22.295 - info: javascript.0 (428) script.js.g_general.z_general_presence.z_general_presence_MyPhone11Pro_presence_Siedle_light: registered 1 subscription and 0 schedules
2021-11-23 11:44:22.295 - info: javascript.0 (428) Start javascript script.js.g_office.z_office_window.z_office_window_dp_state
2021-11-23 11:44:22.296 - info: javascript.0 (428) script.js.g_office.z_office_window.z_office_window_dp_state: registered 1 subscription and 0 schedules
2021-11-23 11:44:22.296 - info: javascript.0 (428) Start javascript script.js.g_kitchen.z_kitchen_window.z_kitchen_window_dp_state
2021-11-23 11:44:22.298 - info: javascript.0 (428) script.js.g_kitchen.z_kitchen_window.z_kitchen_window_dp_state: registered 1 subscription and 0 schedules
2021-11-23 11:44:22.298 - info: javascript.0 (428) Start javascript script.js.g_bathroom.z_bathroom_window.z_bathroom_window_dp_state
2021-11-23 11:44:22.299 - info: javascript.0 (428) script.js.g_bathroom.z_bathroom_window.z_bathroom_window_dp_state: registered 1 subscription and 0 schedules
2021-11-23 11:44:22.299 - info: javascript.0 (428) Start javascript script.js.g_toilet.z_toilet_window.z_toilet_window_dp_state
2021-11-23 11:44:22.300 - info: javascript.0 (428) script.js.g_toilet.z_toilet_window.z_toilet_window_dp_state: registered 1 subscription and 0 schedules
2021-11-23 11:44:22.301 - info: javascript.0 (428) Start javascript script.js.g_livingroom.z_livingroom_window_north.z_livingroom_window_north_dp_state
2021-11-23 11:44:22.302 - info: javascript.0 (428) script.js.g_livingroom.z_livingroom_window_north.z_livingroom_window_north_dp_state: registered 1 subscription and 0 schedules
2021-11-23 11:44:22.302 - info: javascript.0 (428) Start javascript script.js.g_livingroom.z_livingroom_window_east.z_livingroom_window_east_dp_state
2021-11-23 11:44:22.303 - info: javascript.0 (428) script.js.g_livingroom.z_livingroom_window_east.z_livingroom_window_east_dp_state: registered 1 subscription and 0 schedules
2021-11-23 11:44:22.304 - info: javascript.0 (428) Start javascript script.js.g_bedroom.z_bedroom_window.z_bedroom_window_dp_state
2021-11-23 11:44:22.305 - info: javascript.0 (428) script.js.g_bedroom.z_bedroom_window.z_bedroom_window_dp_state: registered 1 subscription and 0 schedules
2021-11-23 11:44:22.305 - info: javascript.0 (428) Start javascript script.js.g_bedroom.z_bedroom_window.z_bedroom_window_dp_isday
2021-11-23 11:44:22.306 - info: javascript.0 (428) script.js.g_bedroom.z_bedroom_window.z_bedroom_window_dp_isday: registered 1 subscription and 0 schedules
2021-11-23 11:44:22.306 - info: javascript.0 (428) Start javascript script.js.g_toilet.z_toilet_ceiling.z_toilet_ceiling_switch
2021-11-23 11:44:22.308 - info: javascript.0 (428) script.js.g_toilet.z_toilet_ceiling.z_toilet_ceiling_switch: registered 1 subscription and 0 schedules
2021-11-23 11:44:22.308 - info: javascript.0 (428) Start javascript script.js.g_general.z_general_fuelprice.z_general_fuelprice_dp_cheapest
2021-11-23 11:44:22.309 - info: javascript.0 (428) script.js.g_general.z_general_fuelprice.z_general_fuelprice_dp_cheapest: registered 1 subscription and 0 schedules
2021-11-23 11:44:22.309 - info: javascript.0 (428) Start javascript script.js.g_general.z_general_windows.z_general_contact_dp_windows_anyopen
2021-11-23 11:44:22.379 - info: javascript.0 (428) script.js.g_general.z_general_windows.z_general_contact_dp_windows_anyopen: registered 7 subscriptions and 0 schedules
2021-11-23 11:44:22.379 - info: javascript.0 (428) Start javascript script.js.g_general.z_general_sweepingweek.z_general_sweepingweek_iCal_3_dp
2021-11-23 11:44:22.381 - info: javascript.0 (428) script.js.g_general.z_general_sweepingweek.z_general_sweepingweek_iCal_3_dp: registered 1 subscription and 0 schedules
2021-11-23 11:44:22.387 - info: javascript.0 (428) Start javascript script.js.g_general.z_general_date.z_general_date_kw_current
2021-11-23 11:44:22.389 - info: javascript.0 (428) script.js.g_general.z_general_date.z_general_date_kw_current: registered 0 subscriptions and 0 schedules
2021-11-23 11:44:22.389 - warn: javascript.0 (428) script.js.g_general.z_general_date.z_general_date_kw_current: 47
2021-11-23 11:44:22.390 - info: javascript.0 (428) Start javascript script.js.g_general.z_general_date.z_general_calendar_monthly
2021-11-23 11:44:22.392 - info: javascript.0 (428) script.js.g_general.z_general_date.z_general_calendar_monthly: registered 0 subscriptions and 1 schedule
2021-11-23 11:44:22.392 - info: javascript.0 (428) Start javascript script.js.g_general.z_general_telegram.z_general_telegram_system_info_updates
2021-11-23 11:44:22.394 - info: javascript.0 (428) script.js.g_general.z_general_telegram.z_general_telegram_system_info_updates: registered 1 subscription and 0 schedules
2021-11-23 11:44:22.394 - info: javascript.0 (428) Start javascript script.js.g_general.z_general_netatmo.z_general_netatmo_dp_vis_date_time
2021-11-23 11:44:22.395 - info: javascript.0 (428) script.js.g_general.z_general_netatmo.z_general_netatmo_dp_vis_date_time: registered 1 subscription and 0 schedules
2021-11-23 11:44:22.395 - info: javascript.0 (428) Start javascript script.js.g_general.z_general_homecloud.z_general_homecloud_chat
2021-11-23 11:44:22.396 - info: javascript.0 (428) script.js.g_general.z_general_homecloud.z_general_homecloud_chat: registered 1 subscription and 0 schedules
2021-11-23 11:44:24.794 - info: host.iobroker instance system.adapter.telegram.0 started with pid 443
2021-11-23 11:44:25.424 - info: telegram.0 (443) starting. Version 1.10.0 in /opt/iobroker/node_modules/iobroker.telegram, node: v14.18.1, js-controller: 3.3.18
2021-11-23 11:44:28.795 - info: host.iobroker instance system.adapter.tr-064.0 started with pid 458
2021-11-23 11:44:29.381 - info: tr-064.0 (458) starting. Version 4.2.14 in /opt/iobroker/node_modules/iobroker.tr-064, node: v14.18.1, js-controller: 3.3.18
2021-11-23 11:44:32.795 - info: host.iobroker instance system.adapter.hue.0 started with pid 481
2021-11-23 11:44:36.795 - info: host.iobroker instance system.adapter.mqtt.0 started with pid 496
2021-11-23 11:44:37.239 - info: mqtt.0 (496) starting. Version 2.4.0 in /opt/iobroker/node_modules/iobroker.mqtt, node: v14.18.1, js-controller: 3.3.18
2021-11-23 11:44:37.340 - info: mqtt.0 (496) Try to connect to mqtt://XXX:*******************@192.168.78.131:1883?clientId=iobroker00
2021-11-23 11:44:37.369 - info: mqtt.0 (496) Connected to 192.168.78.131
2021-11-23 11:44:37.370 - info: mqtt.0 (496) Subscribe on: "siedle/#"
2021-11-23 11:44:40.793 - info: host.iobroker instance system.adapter.mqtt.1 started with pid 511
2021-11-23 11:44:41.262 - info: mqtt.1 (511) starting. Version 2.4.0 in /opt/iobroker/node_modules/iobroker.mqtt, node: v14.18.1, js-controller: 3.3.18
2021-11-23 11:44:41.368 - info: mqtt.1 (511) Try to connect to mqtt://XXX:*******************@192.168.78.131:1883?clientId=iobroker01
2021-11-23 11:44:41.392 - info: mqtt.1 (511) Connected to 192.168.78.131
2021-11-23 11:44:41.392 - info: mqtt.1 (511) Subscribe on: "zigbee2mqtt/#"
2021-11-23 11:44:44.793 - info: host.iobroker instance system.adapter.mqtt.2 started with pid 526
2021-11-23 11:44:45.250 - info: mqtt.2 (526) starting. Version 2.4.0 in /opt/iobroker/node_modules/iobroker.mqtt, node: v14.18.1, js-controller: 3.3.18
2021-11-23 11:44:45.342 - info: mqtt.2 (526) Try to connect to mqtt://XXX:*******************@192.168.78.131:1883?clientId=iobroker02
2021-11-23 11:44:45.370 - info: mqtt.2 (526) Connected to 192.168.78.131
2021-11-23 11:44:45.370 - info: mqtt.2 (526) Subscribe on: "wallpanel/myxperia/#"
2021-11-23 11:44:48.802 - info: host.iobroker instance scheduled system.adapter.ical.0 5 0 * * *
2021-11-23 11:44:48.812 - info: host.iobroker instance system.adapter.ical.0 started with pid 541
2021-11-23 11:44:49.419 - info: ical.0 (541) starting. Version 1.11.5 in /opt/iobroker/node_modules/iobroker.ical, node: v14.18.1, js-controller: 3.3.18
2021-11-23 11:44:50.123 - info: ical.0 (541) processing URL: Geburtstage https://XXX.XXX.XXX/remote.php/dav/calendars/XXX/contact_birthdays/?export
2021-11-23 11:44:52.785 - info: host.iobroker instance scheduled system.adapter.ical.1 0,30 * * * *
2021-11-23 11:44:52.795 - info: host.iobroker instance system.adapter.ical.1 started with pid 556
2021-11-23 11:44:53.378 - info: ical.1 (556) starting. Version 1.11.5 in /opt/iobroker/node_modules/iobroker.ical, node: v14.18.1, js-controller: 3.3.18
2021-11-23 11:44:54.518 - info: ical.1 (556) processing URL: Zeitumstellung https://XXX.XXX.XXX/remote.php/dav/calendars/XXX/zeitumstellung/?export
2021-11-23 11:44:54.610 - info: ical.1 (556) processing URL: Formel1 https://XXX.XXX.XXX/remote.php/dav/calendars/XXX/formel1/?export
2021-11-23 11:44:54.816 - info: ical.1 (556) processing URL: DTM https://XXX.XXX.XXX/remote.php/dav/calendars/XXX/dtm/?export
2021-11-23 11:44:54.818 - info: ical.1 (556) processing URL: NFL https://XXX.XXX.XXX/remote.php/dav/calendars/XXX/nfl/?export
2021-11-23 11:44:55.129 - info: ical.1 (556) processing URL: Persönlich https://XXX.XXX.XXX/remote.php/dav/calendars/XXX/personal/?export
2021-11-23 11:44:55.278 - info: ical.0 (541) Terminated (NO_ERROR): Without reason
2021-11-23 11:44:55.820 - info: host.iobroker instance system.adapter.ical.0 terminated with code 0 (NO_ERROR)
2021-11-23 11:44:56.782 - info: host.iobroker instance scheduled system.adapter.ical.2 7 0 * * *
2021-11-23 11:44:56.792 - info: host.iobroker instance system.adapter.ical.2 started with pid 571
2021-11-23 11:44:57.393 - info: ical.2 (571) starting. Version 1.11.5 in /opt/iobroker/node_modules/iobroker.ical, node: v14.18.1, js-controller: 3.3.18
2021-11-23 11:44:58.134 - info: ical.2 (571) processing URL: Leerung https://XXX.XXX.XXX/remote.php/dav/calendars/XXX/leerung/?export
2021-11-23 11:45:00.234 - info: ical.1 (556) Terminated (NO_ERROR): Without reason
2021-11-23 11:45:00.771 - info: host.iobroker instance system.adapter.ical.1 terminated with code 0 (NO_ERROR)
2021-11-23 11:45:00.798 - info: host.iobroker instance system.adapter.ping.0 started with pid 586
2021-11-23 11:45:01.240 - info: ping.0 (586) starting. Version 1.5.0 in /opt/iobroker/node_modules/iobroker.ping, node: v14.18.1, js-controller: 3.3.18
2021-11-23 11:45:03.279 - info: ical.2 (571) Terminated (NO_ERROR): Without reason
2021-11-23 11:45:03.812 - info: host.iobroker instance system.adapter.ical.2 terminated with code 0 (NO_ERROR)
2021-11-23 11:45:04.784 - info: host.iobroker instance scheduled system.adapter.ical.3 9 0 * * *
2021-11-23 11:45:04.794 - info: host.iobroker instance system.adapter.ical.3 started with pid 602
2021-11-23 11:45:05.375 - info: ical.3 (602) starting. Version 1.11.5 in /opt/iobroker/node_modules/iobroker.ical, node: v14.18.1, js-controller: 3.3.18
2021-11-23 11:45:05.930 - info: ical.3 (602) processing URL: Kehrwoche https://XXX.XXX.XXX/remote.php/dav/calendars/XXX/kehrwoche/?export
2021-11-23 11:45:08.784 - info: host.iobroker instance scheduled system.adapter.ical.4 0,30 * * * *
2021-11-23 11:45:08.793 - info: host.iobroker instance system.adapter.ical.4 started with pid 617
2021-11-23 11:45:09.380 - info: ical.4 (617) starting. Version 1.11.5 in /opt/iobroker/node_modules/iobroker.ical, node: v14.18.1, js-controller: 3.3.18
2021-11-23 11:45:10.112 - info: ical.4 (617) processing URL: Anwesenheit https://XXX.XXX.XXX/remote.php/dav/calendars/XXX/anwesenheit/?export
2021-11-23 11:45:10.948 - info: ical.3 (602) Terminated (NO_ERROR): Without reason
2021-11-23 11:45:11.483 - info: host.iobroker instance system.adapter.ical.3 terminated with code 0 (NO_ERROR)
2021-11-23 11:45:12.785 - info: host.iobroker instance scheduled system.adapter.ical.5 13 0 * * *
2021-11-23 11:45:12.794 - info: host.iobroker instance system.adapter.ical.5 started with pid 632
2021-11-23 11:45:13.377 - info: ical.5 (632) starting. Version 1.11.5 in /opt/iobroker/node_modules/iobroker.ical, node: v14.18.1, js-controller: 3.3.18
2021-11-23 11:45:13.929 - info: ical.5 (632) processing URL: Feiertage https://XXX.XXX.XXX/remote.php/dav/calendars/XXX/feiertage/?export
2021-11-23 11:45:15.197 - info: ical.4 (617) Terminated (NO_ERROR): Without reason
2021-11-23 11:45:15.735 - info: host.iobroker instance system.adapter.ical.4 terminated with code 0 (NO_ERROR)
2021-11-23 11:45:16.780 - info: host.iobroker instance system.adapter.backitup.0 started with pid 647
2021-11-23 11:45:17.303 - info: backitup.0 (647) starting. Version 2.2.2 in /opt/iobroker/node_modules/iobroker.backitup, node: v14.18.1, js-controller: 3.3.18
2021-11-23 11:45:17.324 - info: backitup.0 (647) [iobroker] backup was activated at 02:40 every 1 day(s)
2021-11-23 11:45:18.958 - info: ical.5 (632) Terminated (NO_ERROR): Without reason
2021-11-23 11:45:19.491 - info: host.iobroker instance system.adapter.ical.5 terminated with code 0 (NO_ERROR)
2021-11-23 11:45:20.794 - info: host.iobroker instance system.adapter.info.0 started with pid 662
2021-11-23 11:45:21.570 - info: info.0 (662) starting. Version 1.9.8 in /opt/iobroker/node_modules/iobroker.info, node: v14.18.1, js-controller: 3.3.18
2021-11-23 11:45:21.603 - info: info.0 (662) Reading/updating systemdata.
2021-11-23 11:45:22.013 - info: info.0 (662) cpu Temp res = {"main":33.9,"cores":[],"max":33.9,"socket":[],"chipset":null}
2021-11-23 11:45:24.796 - info: host.iobroker instance system.adapter.web.0 started with pid 1036
2021-11-23 11:45:25.289 - info: web.0 (1036) starting. Version 3.4.9 in /opt/iobroker/node_modules/iobroker.web, node: v14.18.1, js-controller: 3.3.18
2021-11-23 11:45:25.422 - info: web.0 (1036) socket.io server listening on port 8082
2021-11-23 11:45:25.424 - info: web.0 (1036) http server listening on port 8082
2021-11-23 11:45:26.426 - warn: web.0 (1036) State "web.0.info.connection" has no existing object, this might lead to an error in future versions
2021-11-23 11:45:29.144 - info: vis.0 (1051) starting. Version 1.4.5 in /opt/iobroker/node_modules/iobroker.vis, node: v14.18.1, js-controller: 3.3.18
2021-11-23 11:45:29.282 - info: vis.0 (1051) vis license is OK.
2021-11-23 11:45:29.966 - info: vis.0 (1051) Terminated (NO_ERROR): Without reason
2021-11-23 11:45:30.083 - info: web.0 (1036) ==>Connected system.user.admin from ::ffff:192.168.78.60
2021-11-23 11:45:30.499 - info: host.iobroker instance system.adapter.vis.0 terminated while should be started once
2021-11-23 11:45:31.086 - warn: web.0 (1036) State "web.0.info.connection" has no existing object, this might lead to an error in future versions
2021-11-23 11:45:32.789 - info: host.iobroker instance scheduled system.adapter.netatmo-crawler.0 */5 * * * *
2021-11-23 11:45:32.799 - info: host.iobroker instance system.adapter.netatmo-crawler.0 started with pid 1066
2021-11-23 11:45:33.312 - info: netatmo-crawler.0 (1066) starting. Version 0.6.0 in /opt/iobroker/node_modules/iobroker.netatmo-crawler, node: v14.18.1, js-controller: 3.3.18
2021-11-23 11:45:33.334 - info: netatmo-crawler.0 (1066) Getting data for stationid:70:ee:50:14:81:ae
2021-11-23 11:45:33.990 - info: netatmo-crawler.0 (1066) Terminated (ADAPTER_REQUESTED_TERMINATION): Everything done. Going to terminate till next schedule
2021-11-23 11:45:34.525 - info: host.iobroker instance system.adapter.netatmo-crawler.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
2021-11-23 11:45:36.795 - info: host.iobroker instance system.adapter.vis-inventwo.0 started with pid 1081
2021-11-23 11:45:37.159 - info: vis-inventwo.0 (1081) starting. Version 3.2.0 in /opt/iobroker/node_modules/iobroker.vis-inventwo, node: v14.18.1, js-controller: 3.3.18
2021-11-23 11:45:40.797 - info: host.iobroker instance system.adapter.sonos.0 started with pid 1096
2021-11-23 11:45:41.188 - info: sonos.0 (1096) starting. Version 2.1.1 in /opt/iobroker/node_modules/iobroker.sonos, node: v14.18.1, js-controller: 3.3.18
2021-11-23 11:45:41.530 - info: sonos.0 (1096) State value to set for "sonos.0.root.192_168_78_115.favorites_list_array" has to be stringified but received type "object"
2021-11-23 11:45:41.530 - info: sonos.0 (1096) State value to set for "sonos.0.root.192_168_78_111.favorites_list_array" has to be stringified but received type "object"
2021-11-23 11:45:41.530 - info: sonos.0 (1096) State value to set for "sonos.0.root.192_168_78_113.favorites_list_array" has to be stringified but received type "object"
2021-11-23 11:45:41.531 - info: sonos.0 (1096) State value to set for "sonos.0.root.192_168_78_112.favorites_list_array" has to be stringified but received type "object"
2021-11-23 11:45:41.540 - info: sonos.0 (1096) State value to set for "sonos.0.root.192_168_78_115.favorites_list_array" has to be stringified but received type "object"
2021-11-23 11:45:41.540 - info: sonos.0 (1096) State value to set for "sonos.0.root.192_168_78_111.favorites_list_array" has to be stringified but received type "object"
2021-11-23 11:45:41.540 - info: sonos.0 (1096) State value to set for "sonos.0.root.192_168_78_113.favorites_list_array" has to be stringified but received type "object"
2021-11-23 11:45:41.540 - info: sonos.0 (1096) State value to set for "sonos.0.root.192_168_78_112.favorites_list_array" has to be stringified but received type "object"
2021-11-23 11:45:41.606 - warn: sonos.0 (1096) State "sonos.0.root.192_168_78_115.queue" has no existing object, this might lead to an error in future versions
2021-11-23 11:45:42.497 - info: sonos.0 (1096) State value to set for "sonos.0.root.192_168_78_115.favorites_list_array" has to be stringified but received type "object"
2021-11-23 11:45:42.498 - info: sonos.0 (1096) State value to set for "sonos.0.root.192_168_78_111.favorites_list_array" has to be stringified but received type "object"
2021-11-23 11:45:42.498 - info: sonos.0 (1096) State value to set for "sonos.0.root.192_168_78_113.favorites_list_array" has to be stringified but received type "object"
2021-11-23 11:45:42.499 - info: sonos.0 (1096) State value to set for "sonos.0.root.192_168_78_112.favorites_list_array" has to be stringified but received type "object"
2021-11-23 11:45:44.770 - info: host.iobroker instance scheduled system.adapter.daswetter.0 */15 * * * *
2021-11-23 11:45:44.781 - info: host.iobroker instance system.adapter.daswetter.0 started with pid 1111
2021-11-23 11:45:45.218 - info: daswetter.0 (1111) starting. Version 3.0.9 in /opt/iobroker/node_modules/iobroker.daswetter, node: v14.18.1, js-controller: 3.3.18
2021-11-23 11:45:48.773 - info: host.iobroker instance system.adapter.tankerkoenig.0 started with pid 1126
2021-11-23 11:45:49.698 - info: tankerkoenig.0 (1126) starting. Version 2.1.1 in /opt/iobroker/node_modules/iobroker.tankerkoenig, node: v14.18.1, js-controller: 3.3.18
2021-11-23 11:45:49.712 - info: tankerkoenig.0 (1126) Sync time set to 5 minutes or 300000 ms
2021-11-23 11:45:50.417 - info: daswetter.0 (1111) still wrong data structure from server received! repaired...
2021-11-23 11:45:51.633 - info: daswetter.0 (1111) Terminated (ADAPTER_REQUESTED_TERMINATION): All data handled, adapter stopped until next scheduled moment
2021-11-23 11:45:52.143 - info: daswetter.0 (1111) cleaned everything up...
2021-11-23 11:45:52.172 - info: host.iobroker instance system.adapter.daswetter.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
2021-11-23 11:45:52.793 - info: host.iobroker instance system.adapter.sayit.0 started with pid 1141
2021-11-23 11:45:53.274 - info: sayit.0 (1141) starting. Version 1.12.3 in /opt/iobroker/node_modules/iobroker.sayit, node: v14.18.1, js-controller: 3.3.18
2021-11-23 11:45:53.286 - info: sayit.0 (1141) Upload announce mp3 files
2021-11-23 11:45:53.310 - info: sayit.0 (1141) All files uploaded
2021-11-23 11:45:56.794 - info: host.iobroker instance system.adapter.yahka.0 started with pid 1156
2021-11-23 11:45:57.305 - info: yahka.0 (1156) starting. Version 0.13.1 in /opt/iobroker/node_modules/iobroker.yahka, node: v14.18.1, js-controller: 3.3.18
2021-11-23 11:45:57.321 - info: yahka.0 (1156) adapter ready, checking config
2021-11-23 11:45:57.329 - info: yahka.0 (1156) adding MyPhone11Pro presence with UUID: a4b2fad2-691f-441a-b6b0-9cbb083b937f
2021-11-23 11:45:57.333 - info: yahka.0 (1156) adding Aussen with UUID: adfa2135-431d-4d86-b000-784330c18bd1
2021-11-23 11:45:57.335 - info: yahka.0 (1156) adding Innen with UUID: 26480b79-e092-44f3-b052-2d90ac9b44b6
2021-11-23 11:45:57.336 - info: yahka.0 (1156) publishing bridge Yahka on 0.0.0.0 using ciao
2021-11-23 11:46:00.795 - info: host.iobroker instance system.adapter.sql.0 started with pid 1171
2021-11-23 11:46:01.300 - info: sql.0 (1171) starting. Version 1.15.7 in /opt/iobroker/node_modules/iobroker.sql, node: v14.18.1, js-controller: 3.3.18
2021-11-23 11:46:01.381 - info: sql.0 (1171) Connected to mysql
2021-11-23 11:46:01.393 - info: sql.0 (1171) enabled logging of mqtt.1.zigbee2mqtt.xi_sensor_light_01.illuminance, Alias=false, 1 points now activated
2021-11-23 11:46:01.393 - info: sql.0 (1171) enabled logging of mqtt.1.zigbee2mqtt.xi_sensor_light_02.illuminance, Alias=false, 2 points now activated
2021-11-23 11:46:01.394 - info: sql.0 (1171) enabled logging of tankerkoenig.0.stations.4.e5.short, Alias=false, 3 points now activated
2021-11-23 11:46:01.394 - info: sql.0 (1171) enabled logging of tankerkoenig.0.stations.3.e5.short, Alias=false, 4 points now activated
2021-11-23 11:46:01.394 - info: sql.0 (1171) enabled logging of tankerkoenig.0.stations.2.e5.short, Alias=false, 5 points now activated
2021-11-23 11:46:01.394 - info: sql.0 (1171) enabled logging of tankerkoenig.0.stations.1.e5.short, Alias=false, 6 points now activated
2021-11-23 11:46:01.394 - info: sql.0 (1171) enabled logging of tankerkoenig.0.stations.0.e5.short, Alias=false, 7 points now activated
2021-11-23 11:46:04.780 - info: host.iobroker instance system.adapter.echarts.0 started with pid 1188
2021-11-23 11:46:05.172 - info: echarts.0 (1188) starting. Version 1.0.3 in /opt/iobroker/node_modules/iobroker.echarts, node: v14.18.1, js-controller: 3.3.18
2021-11-23 11:46:08.795 - info: host.iobroker instance system.adapter.nctalk.0 started with pid 1203
2021-11-23 11:46:09.050 - debug: nctalk.0 (1203) Redis Objects: Use Redis connection: 127.0.0.1:9001
2021-11-23 11:46:09.061 - debug: nctalk.0 (1203) Objects client ready ... initialize now
2021-11-23 11:46:09.062 - debug: nctalk.0 (1203) Objects create System PubSub Client
2021-11-23 11:46:09.062 - debug: nctalk.0 (1203) Objects create User PubSub Client
2021-11-23 11:46:09.062 - debug: nctalk.0 (1203) Objects client initialize lua scripts
2021-11-23 11:46:09.070 - debug: nctalk.0 (1203) Objects connected to redis: 127.0.0.1:9001
2021-11-23 11:46:09.073 - debug: nctalk.0 (1203) objectDB connected
2021-11-23 11:46:09.073 - debug: nctalk.0 (1203) Redis States: Use Redis connection: 127.0.0.1:9000
2021-11-23 11:46:09.077 - debug: nctalk.0 (1203) States create System PubSub Client
2021-11-23 11:46:09.077 - debug: nctalk.0 (1203) States create User PubSub Client
2021-11-23 11:46:09.080 - debug: nctalk.0 (1203) States connected to redis: 127.0.0.1:9000
2021-11-23 11:46:09.081 - debug: nctalk.0 (1203) statesDB connected
2021-11-23 11:46:09.197 - info: nctalk.0 (1203) starting. Version 0.2.0 in /opt/iobroker/node_modules/iobroker.nctalk, node: v14.18.1, js-controller: 3.3.18
2021-11-23 11:46:09.712 - debug: nctalk.0 (1203) Debug Event START
2021-11-23 11:46:09.713 - debug: nctalk.0 (1203) Debug Event Get capabilities
2021-11-23 11:46:10.232 - debug: nctalk.0 (1203) Debug Event {"ocs":{"meta":{"status":"ok","statuscode":100,"message":"OK","totalitems":"","itemsperpage":""},"data":{"version":{"major":21,"minor":0,"micro":5,"string":"21.0.5 Enterprise","edition":"","extendedSupport":false},"capabilities":{"core":{"pollinterval":60,"webdav-root":"remote.php\/webdav"},"bruteforce":{"delay":0},"files":{"bigfilechunking":true,"blacklisted_files":[".htaccess"],"directEditing":{"url":"https:\/\/XXX.XXX.XXX\/ocs\/v2.php\/apps\/files\/api\/v1\/directEditing","etag":"XXX"},"comments":true,"undelete":true,"versioning":true},"activity":{"apiv2":["filters","filters-api","previews","rich-strings"]},"ocm":{"enabled":true,"apiVersion":"1.0-proposal1","endPoint":"https:\/\/XXX.XXX.XXX\/index.php\/ocm","resourceTypes":[{"name":"file","shareTypes":["user","group"],"protocols":{"webdav":"\/public.php\/webdav\/"}}]},"dav":{"chunking":"1.0"},"deck":{"version":"1.4.7","canCreateBoards":true,"apiVersions":["1.0","1.1"]},"notes":{"api_version":["0.2","1.2"],"version":"4.2.0"},"notifications":{"ocs-endpoints":["list","get","delete","delete-all","icons","rich-strings","action-web","user-status"],"push":["devices","object-data","delete"],"admin-notifications":["ocs","cli"]},"password_policy":{"minLength":8,"enforceNonCommonPassword":true,"enforceNumericCharacters":false,"enforceSpecialCharacters":false,"enforceUpperLowerCase":false,"api":{"generate":"https:\/\/XXX.XXX.XXX\/ocs\/v2.php\/apps\/password_policy\/api\/v1\/generate","validate":"https:\/\/XXX.XXX.XXX\/ocs\/v2.php\/apps\/password_policy\/api\/v1\/validate"}},"provisioning_api":{"version":"1.11.0","AccountPropertyScopesVersion":2,"AccountPropertyScopesFederationEnabled":true},"quicknotes":{"version":"0.7.2","api_version":"1.0"},"files_sharing":{"sharebymail":{"enabled":true,"upload_files_drop":{"enabled":true},"password":{"enabled":true,"enforced":false},"expire_date":{"enabled":true}},"api_enabled":true,"public":{"enabled":true,"password":{"enforced":true,"askForOptionalPassword":false},"expire_date":{"enabled":true,"days":"7","enforced":false},"multiple_links":true,"expire_date_internal":{"enabled":true,"days":"7","enforced":false},"send_mail":false,"upload":true,"upload_files_drop":true},"resharing":true,"user":{"send_mail":false,"expire_date":{"enabled":true}},"group_sharing":true,"group":{"enabled":true,"expire_date":{"enabled":true}},"default_permissions":31,"federation":{"outgoing":true,"incoming":true,"expire_date":{"enabled":true}},"sharee":{"query_lookup_default":false,"always_show_unique":true}},"spreed":{"features":["audio","video","chat-v2","conversation-v2","guest-signaling","empty-group-room","guest-display-names","multi-room-users","favorites","last-room-activity","no-ping","system-messages","delete-messages","mention-flag","in-call-flags","conversation-call-flags","notification-levels","invite-groups-and-mails","locked-one-to-one-rooms","read-only-rooms","listable-rooms","chat-read-marker","webinary-lobby","start-call-flag","chat-replies","circles-support","force-mute","conversation-v3","sip-support","chat-read-status","phonebook-search","raise-hand","room-description","rich-object-sharing","temp-user-avatar-api","chat-reference-id"],"config":{"attachments":{"allowed":true,"folder":"\/Talk"},"chat":{"max-length":32000,"read-privacy":0},"conversations":{"can-create":true},"previews":{"max-gif-size":3145728}}},"theming":{"name":"XXX","url":"https:\/\/www.ionos.de","slogan":"","color":"#808080","color-text":"#ffffff","color-element":"#808080","color-element-bright":"#808080","color-element-dark":"#808080","logo":"https:\/\/XXX.XXX.XXX\/index.php\/apps\/theming\/image\/logo?useSvg=1&v=20","background":"https:\/\/XXX.XXX.XXX\/index.php\/apps\/theming\/image\/background?v=20","background-plain":false,"background-default":false,"logoheader":"https:\/\/XXX.XXX.XXX\/index.php\/apps\/theming\/image\/logo?useSvg=1&v=20","favicon":"https:\/\/XXX.XXX.XXX\/index.php\/apps\/theming\/image\/logo?useSvg=1&v=20"},"user_status":{"enabled":true,"supports_emoji":true},"weather_status":{"enabled":true}}}}}
2021-11-23 11:46:10.232 - debug: nctalk.0 (1203) Debug Event Get capabilities done
2021-11-23 11:46:10.232 - debug: nctalk.0 (1203) Debug Event Get Rooms
2021-11-23 11:46:10.717 - debug: nctalk.0 (1203) Debug Event {"ocs":{"meta":{"status":"ok","statuscode":200,"message":"OK"},"data":[{"id":11,"token":"XXX","type":4,"name":"XXX","displayName":"Talk Aktualisierungen \u2705","objectType":"","objectId":"","participantType":3,"participantFlags":0,"readOnly":1,"hasPassword":false,"hasCall":false,"canStartCall":true,"lastActivity":1637476508,"lastReadMessage":259,"unreadMessages":0,"unreadMention":false,"isFavorite":false,"canLeaveConversation":true,"canDeleteConversation":false,"notificationLevel":2,"lobbyState":0,"lobbyTimer":0,"lastPing":0,"sessionId":"0","guestList":"","lastMessage":{"id":259,"token":"XXX","actorType":"bots","actorId":"changelog","actorDisplayName":"Talk Aktualisierungen \u2705","timestamp":1637476508,"message":"- Heben Sie Ihre Hand in einem Anruf durch dr\u00fccken der Taste R","messageParameters":[],"systemMessage":"","messageType":"comment","isReplyable":false,"referenceId":""},"callFlag":0},{"id":12,"token":"XXX","type":1,"name":"karsten","displayName":"karsten","objectType":"","objectId":"","participantType":1,"participantFlags":0,"readOnly":0,"hasPassword":false,"hasCall":false,"canStartCall":true,"lastActivity":1637664026,"lastReadMessage":285,"unreadMessages":0,"unreadMention":false,"isFavorite":false,"canLeaveConversation":true,"canDeleteConversation":false,"notificationLevel":1,"lobbyState":0,"lobbyTimer":0,"lastPing":0,"sessionId":"0","guestList":"","lastMessage":{"id":285,"token":"XXX","actorType":"users","actorId":"karsten","actorDisplayName":"karsten","timestamp":1637664026,"message":"Hallo \ud83d\ude00","messageParameters":[],"systemMessage":"","messageType":"comment","isReplyable":true,"referenceId":"XXX"},"callFlag":0}]}}
2021-11-23 11:46:10.718 - info: nctalk.0 (1203) Talk client is ready and has fetched capabilities and room information
2021-11-23 11:46:10.727 - debug: nctalk.0 (1203) Debug Event Get rooms done
2021-11-23 11:46:11.495 - debug: nctalk.0 (1203) mqtt.1.zigbee2mqtt.bridge: logging {"level":"info","message":"MQTT publish: topic 'zigbee2mqtt/hue_sensor_motion_01/battery', payload '52'"}
2021-11-23 11:46:11.500 - debug: nctalk.0 (1203) mqtt.1.zigbee2mqtt.bridge: logging {"level":"info","message":"MQTT publish: topic 'zigbee2mqtt/hue_sensor_motion_01/occupancy_timeout', payload '0'"}
2021-11-23 11:46:11.503 - debug: nctalk.0 (1203) mqtt.1.zigbee2mqtt.bridge: logging {"level":"info","message":"MQTT publish: topic 'zigbee2mqtt/hue_sensor_motion_01/occupancy', payload 'true'"}
2021-11-23 11:46:11.506 - debug: nctalk.0 (1203) mqtt.1.zigbee2mqtt.bridge: logging {"level":"info","message":"MQTT publish: topic 'zigbee2mqtt/hue_sensor_motion_01/motion_sensitivity', payload 'high'"}
2021-11-23 11:46:11.509 - debug: nctalk.0 (1203) mqtt.1.zigbee2mqtt.bridge: logging {"level":"info","message":"MQTT publish: topic 'zigbee2mqtt/hue_sensor_motion_01/temperature', payload '20.2'"}
2021-11-23 11:46:11.511 - debug: nctalk.0 (1203) mqtt.1.zigbee2mqtt.bridge: logging {"level":"info","message":"MQTT publish: topic 'zigbee2mqtt/hue_sensor_motion_01/illuminance', payload '14941'"}
2021-11-23 11:46:11.517 - debug: nctalk.0 (1203) mqtt.1.zigbee2mqtt.bridge: logging {"level":"info","message":"MQTT publish: topic 'zigbee2mqtt/hue_sensor_motion_01/illuminance_lux', payload '31.18889584093937'"}
2021-11-23 11:46:11.520 - debug: nctalk.0 (1203) mqtt.1.zigbee2mqtt.bridge: logging {"level":"info","message":"MQTT publish: topic 'zigbee2mqtt/hue_sensor_motion_01/update-state', payload 'idle'"}
2021-11-23 11:46:11.523 - debug: nctalk.0 (1203) mqtt.1.zigbee2mqtt.bridge: logging {"level":"info","message":"MQTT publish: topic 'zigbee2mqtt/hue_sensor_motion_01/linkquality', payload '117'"}
2021-11-23 11:46:15.555 - debug: nctalk.0 (1203) mqtt.1.zigbee2mqtt.bridge: logging {"level":"info","message":"MQTT publish: topic 'zigbee2mqtt/hue_sensor_motion_01/battery', payload '52'"}
2021-11-23 11:46:15.558 - debug: nctalk.0 (1203) mqtt.1.zigbee2mqtt.bridge: logging {"level":"info","message":"MQTT publish: topic 'zigbee2mqtt/hue_sensor_motion_01/occupancy_timeout', payload '0'"}
2021-11-23 11:46:15.561 - debug: nctalk.0 (1203) mqtt.1.zigbee2mqtt.bridge: logging {"level":"info","message":"MQTT publish: topic 'zigbee2mqtt/hue_sensor_motion_01/occupancy', payload 'false'"}
2021-11-23 11:46:15.565 - debug: nctalk.0 (1203) mqtt.1.zigbee2mqtt.bridge: logging {"level":"info","message":"MQTT publish: topic 'zigbee2mqtt/hue_sensor_motion_01/motion_sensitivity', payload 'high'"}
2021-11-23 11:46:15.569 - debug: nctalk.0 (1203) mqtt.1.zigbee2mqtt.bridge: logging {"level":"info","message":"MQTT publish: topic 'zigbee2mqtt/hue_sensor_motion_01/temperature', payload '20.2'"}
2021-11-23 11:46:15.572 - debug: nctalk.0 (1203) mqtt.1.zigbee2mqtt.bridge: logging {"level":"info","message":"MQTT publish: topic 'zigbee2mqtt/hue_sensor_motion_01/illuminance', payload '14941'"}
2021-11-23 11:46:15.575 - debug: nctalk.0 (1203) mqtt.1.zigbee2mqtt.bridge: logging {"level":"info","message":"MQTT publish: topic 'zigbee2mqtt/hue_sensor_motion_01/illuminance_lux', payload '31.18889584093937'"}
2021-11-23 11:46:15.578 - debug: nctalk.0 (1203) mqtt.1.zigbee2mqtt.bridge: logging {"level":"info","message":"MQTT publish: topic 'zigbee2mqtt/hue_sensor_motion_01/update-state', payload 'idle'"}
2021-11-23 11:46:15.580 - debug: nctalk.0 (1203) mqtt.1.zigbee2mqtt.bridge: logging {"level":"info","message":"MQTT publish: topic 'zigbee2mqtt/hue_sensor_motion_01/linkquality', payload '117'"}
2021-11-23 11:46:21.404 - debug: nctalk.0 (1203) mqtt.1.zigbee2mqtt.bridge: logging {"level":"info","message":"MQTT publish: topic 'zigbee2mqtt/hue_sensor_motion_01/battery', payload '52'"}
2021-11-23 11:46:21.413 - debug: nctalk.0 (1203) mqtt.1.zigbee2mqtt.bridge: logging {"level":"info","message":"MQTT publish: topic 'zigbee2mqtt/hue_sensor_motion_01/occupancy_timeout', payload '0'"}
2021-11-23 11:46:21.425 - debug: nctalk.0 (1203) mqtt.1.zigbee2mqtt.bridge: logging {"level":"info","message":"MQTT publish: topic 'zigbee2mqtt/hue_sensor_motion_01/occupancy', payload 'false'"}
2021-11-23 11:46:21.432 - debug: nctalk.0 (1203) mqtt.1.zigbee2mqtt.bridge: logging {"level":"info","message":"MQTT publish: topic 'zigbee2mqtt/hue_sensor_motion_01/motion_sensitivity', payload 'high'"}
2021-11-23 11:46:21.438 - debug: nctalk.0 (1203) mqtt.1.zigbee2mqtt.bridge: logging {"level":"info","message":"MQTT publish: topic 'zigbee2mqtt/hue_sensor_motion_01/temperature', payload '20.2'"}
2021-11-23 11:46:21.445 - debug: nctalk.0 (1203) mqtt.1.zigbee2mqtt.bridge: logging {"level":"info","message":"MQTT publish: topic 'zigbee2mqtt/hue_sensor_motion_01/illuminance', payload '14956'"}
2021-11-23 11:46:21.450 - debug: nctalk.0 (1203) mqtt.1.zigbee2mqtt.bridge: logging {"level":"info","message":"MQTT publish: topic 'zigbee2mqtt/hue_sensor_motion_01/illuminance_lux', payload '31.296804715636693'"}
2021-11-23 11:46:21.453 - debug: nctalk.0 (1203) mqtt.1.zigbee2mqtt.bridge: logging {"level":"info","message":"MQTT publish: topic 'zigbee2mqtt/hue_sensor_motion_01/update-state', payload 'idle'"}
2021-11-23 11:46:21.458 - debug: nctalk.0 (1203) mqtt.1.zigbee2mqtt.bridge: logging {"level":"info","message":"MQTT publish: topic 'zigbee2mqtt/hue_sensor_motion_01/linkquality', payload '123'"}
2021-11-23 11:46:38.889 - debug: nctalk.0 (1203) mqtt.1.zigbee2mqtt.bridge: logging {"level":"info","message":"MQTT publish: topic 'zigbee2mqtt/hue_sensor_motion_01/battery', payload '52'"}
2021-11-23 11:46:38.894 - debug: nctalk.0 (1203) mqtt.1.zigbee2mqtt.bridge: logging {"level":"info","message":"MQTT publish: topic 'zigbee2mqtt/hue_sensor_motion_01/occupancy_timeout', payload '0'"}
2021-11-23 11:46:38.898 - debug: nctalk.0 (1203) mqtt.1.zigbee2mqtt.bridge: logging {"level":"info","message":"MQTT publish: topic 'zigbee2mqtt/hue_sensor_motion_01/occupancy', payload 'true'"}
2021-11-23 11:46:38.902 - debug: nctalk.0 (1203) mqtt.1.zigbee2mqtt.bridge: logging {"level":"info","message":"MQTT publish: topic 'zigbee2mqtt/hue_sensor_motion_01/motion_sensitivity', payload 'high'"}
2021-11-23 11:46:38.906 - debug: nctalk.0 (1203) mqtt.1.zigbee2mqtt.bridge: logging {"level":"info","message":"MQTT publish: topic 'zigbee2mqtt/hue_sensor_motion_01/temperature', payload '20.2'"}
2021-11-23 11:46:38.911 - debug: nctalk.0 (1203) mqtt.1.zigbee2mqtt.bridge: logging {"level":"info","message":"MQTT publish: topic 'zigbee2mqtt/hue_sensor_motion_01/illuminance', payload '14956'"}
2021-11-23 11:46:38.927 - debug: nctalk.0 (1203) mqtt.1.zigbee2mqtt.bridge: logging {"level":"info","message":"MQTT publish: topic 'zigbee2mqtt/hue_sensor_motion_01/illuminance_lux', payload '31.296804715636693'"}
2021-11-23 11:46:38.933 - debug: nctalk.0 (1203) mqtt.1.zigbee2mqtt.bridge: logging {"level":"info","message":"MQTT publish: topic 'zigbee2mqtt/hue_sensor_motion_01/update-state', payload 'idle'"}
2021-11-23 11:46:38.937 - debug: nctalk.0 (1203) mqtt.1.zigbee2mqtt.bridge: logging {"level":"info","message":"MQTT publish: topic 'zigbee2mqtt/hue_sensor_motion_01/linkquality', payload '123'"}
2021-11-23 11:46:38.941 - debug: nctalk.0 (1203) mqtt.1.zigbee2mqtt.bridge: logging {"level":"info","message":"MQTT publish: topic 'zigbee2mqtt/hue_sensor_motion_01/battery', payload '52'"}
2021-11-23 11:46:38.944 - debug: nctalk.0 (1203) mqtt.1.zigbee2mqtt.bridge: logging {"level":"info","message":"MQTT publish: topic 'zigbee2mqtt/hue_sensor_motion_01/occupancy_timeout', payload '0'"}
2021-11-23 11:46:38.949 - debug: nctalk.0 (1203) mqtt.1.zigbee2mqtt.bridge: logging {"level":"info","message":"MQTT publish: topic 'zigbee2mqtt/hue_sensor_motion_01/occupancy', payload 'true'"}
2021-11-23 11:46:38.952 - debug: nctalk.0 (1203) mqtt.1.zigbee2mqtt.bridge: logging {"level":"info","message":"MQTT publish: topic 'zigbee2mqtt/hue_sensor_motion_01/motion_sensitivity', payload 'high'"}
2021-11-23 11:46:38.955 - debug: nctalk.0 (1203) mqtt.1.zigbee2mqtt.bridge: logging {"level":"info","message":"MQTT publish: topic 'zigbee2mqtt/hue_sensor_motion_01/temperature', payload '20.2'"}
2021-11-23 11:46:38.958 - debug: nctalk.0 (1203) mqtt.1.zigbee2mqtt.bridge: logging {"level":"info","message":"MQTT publish: topic 'zigbee2mqtt/hue_sensor_motion_01/illuminance', payload '14910'"}
2021-11-23 11:46:38.962 - debug: nctalk.0 (1203) mqtt.1.zigbee2mqtt.bridge: logging {"level":"info","message":"MQTT publish: topic 'zigbee2mqtt/hue_sensor_motion_01/illuminance_lux', payload '30.967061741707724'"}
2021-11-23 11:46:38.966 - debug: nctalk.0 (1203) mqtt.1.zigbee2mqtt.bridge: logging {"level":"info","message":"MQTT publish: topic 'zigbee2mqtt/hue_sensor_motion_01/update-state', payload 'idle'"}
2021-11-23 11:46:38.968 - debug: nctalk.0 (1203) mqtt.1.zigbee2mqtt.bridge: logging {"level":"info","message":"MQTT publish: topic 'zigbee2mqtt/hue_sensor_motion_01/linkquality', payload '123'"}
2021-11-23 11:46:41.255 - debug: nctalk.0 (1203) Debug Event WaitNewMessages - Talk timeout empty reply after no new message was received
2021-11-23 11:46:41.256 - debug: nctalk.0 (1203) Debug Event WaitNewMessages done
2021-11-23 11:46:41.258 - debug: nctalk.0 (1203) Debug Event WaitNewMessages - Talk timeout empty reply after no new message was received
2021-11-23 11:46:41.258 - debug: nctalk.0 (1203) Debug Event WaitNewMessages done
2021-11-23 11:46:45.769 - debug: nctalk.0 (1203) Debug Event [object Object]
2021-11-23 11:46:45.770 - debug: nctalk.0 (1203) Debug Event WaitNewMessages done
2021-11-23 11:46:45.829 - debug: nctalk.0 (1203) Debug Event SendMessage done
2021-11-23 11:46:48.926 - debug: nctalk.0 (1203) mqtt.1.zigbee2mqtt.bridge: logging {"level":"info","message":"MQTT publish: topic 'zigbee2mqtt/hue_sensor_motion_01/battery', payload '52'"}
2021-11-23 11:46:48.933 - debug: nctalk.0 (1203) mqtt.1.zigbee2mqtt.bridge: logging {"level":"info","message":"MQTT publish: topic 'zigbee2mqtt/hue_sensor_motion_01/occupancy_timeout', payload '0'"}
2021-11-23 11:46:48.938 - debug: nctalk.0 (1203) mqtt.1.zigbee2mqtt.bridge: logging {"level":"info","message":"MQTT publish: topic 'zigbee2mqtt/hue_sensor_motion_01/occupancy', payload 'true'"}
2021-11-23 11:46:48.944 - debug: nctalk.0 (1203) mqtt.1.zigbee2mqtt.bridge: logging {"level":"info","message":"MQTT publish: topic 'zigbee2mqtt/hue_sensor_motion_01/motion_sensitivity', payload 'high'"}
2021-11-23 11:46:48.948 - debug: nctalk.0 (1203) mqtt.1.zigbee2mqtt.bridge: logging {"level":"info","message":"MQTT publish: topic 'zigbee2mqtt/hue_sensor_motion_01/temperature', payload '20.2'"}
2021-11-23 11:46:48.956 - debug: nctalk.0 (1203) mqtt.1.zigbee2mqtt.bridge: logging {"level":"info","message":"MQTT publish: topic 'zigbee2mqtt/hue_sensor_motion_01/illuminance', payload '14926'"}
2021-11-23 11:46:48.957 - debug: nctalk.0 (1203) mqtt.1.zigbee2mqtt.bridge: logging {"level":"info","message":"MQTT publish: topic 'zigbee2mqtt/hue_sensor_motion_01/illuminance_lux', payload '31.08135902739475'"}
2021-11-23 11:46:48.959 - debug: nctalk.0 (1203) mqtt.1.zigbee2mqtt.bridge: logging {"level":"info","message":"MQTT publish: topic 'zigbee2mqtt/hue_sensor_motion_01/update-state', payload 'idle'"}
2021-11-23 11:46:48.962 - debug: nctalk.0 (1203) mqtt.1.zigbee2mqtt.bridge: logging {"level":"info","message":"MQTT publish: topic 'zigbee2mqtt/hue_sensor_motion_01/linkquality', payload '120'"}
2021-11-23 11:46:58.854 - debug: nctalk.0 (1203) mqtt.1.zigbee2mqtt.bridge: logging {"level":"info","message":"MQTT publish: topic 'zigbee2mqtt/hue_sensor_motion_01/battery', payload '52'"}
2021-11-23 11:46:58.858 - debug: nctalk.0 (1203) mqtt.1.zigbee2mqtt.bridge: logging {"level":"info","message":"MQTT publish: topic 'zigbee2mqtt/hue_sensor_motion_01/occupancy_timeout', payload '0'"}
2021-11-23 11:46:58.863 - debug: nctalk.0 (1203) mqtt.1.zigbee2mqtt.bridge: logging {"level":"info","message":"MQTT publish: topic 'zigbee2mqtt/hue_sensor_motion_01/occupancy', payload 'true'"}
2021-11-23 11:46:58.867 - debug: nctalk.0 (1203) mqtt.1.zigbee2mqtt.bridge: logging {"level":"info","message":"MQTT publish: topic 'zigbee2mqtt/hue_sensor_motion_01/motion_sensitivity', payload 'high'"}
2021-11-23 11:46:58.870 - debug: nctalk.0 (1203) mqtt.1.zigbee2mqtt.bridge: logging {"level":"info","message":"MQTT publish: topic 'zigbee2mqtt/hue_sensor_motion_01/temperature', payload '20.2'"}
2021-11-23 11:46:58.873 - debug: nctalk.0 (1203) mqtt.1.zigbee2mqtt.bridge: logging {"level":"info","message":"MQTT publish: topic 'zigbee2mqtt/hue_sensor_motion_01/illuminance', payload '14941'"}
2021-11-23 11:46:58.877 - debug: nctalk.0 (1203) mqtt.1.zigbee2mqtt.bridge: logging {"level":"info","message":"MQTT publish: topic 'zigbee2mqtt/hue_sensor_motion_01/illuminance_lux', payload '31.18889584093937'"}
2021-11-23 11:46:58.882 - debug: nctalk.0 (1203) mqtt.1.zigbee2mqtt.bridge: logging {"level":"info","message":"MQTT publish: topic 'zigbee2mqtt/hue_sensor_motion_01/update-state', payload 'idle'"}
2021-11-23 11:46:58.887 - debug: nctalk.0 (1203) mqtt.1.zigbee2mqtt.bridge: logging {"level":"info","message":"MQTT publish: topic 'zigbee2mqtt/hue_sensor_motion_01/linkquality', payload '123'"}
2021-11-23 11:46:59.316 - debug: nctalk.0 (1203) mqtt.1.zigbee2mqtt.bridge: logging {"level":"info","message":"MQTT publish: topic 'zigbee2mqtt/xi_sensor_temperature_01/temperature', payload '21.7'"}
2021-11-23 11:46:59.318 - debug: nctalk.0 (1203) mqtt.1.zigbee2mqtt.bridge: logging {"level":"info","message":"MQTT publish: topic 'zigbee2mqtt/xi_sensor_temperature_01/humidity', payload '41.4'"}
2021-11-23 11:46:59.321 - debug: nctalk.0 (1203) mqtt.1.zigbee2mqtt.bridge: logging {"level":"info","message":"MQTT publish: topic 'zigbee2mqtt/xi_sensor_temperature_01/voltage', payload '3015'"}
2021-11-23 11:46:59.324 - debug: nctalk.0 (1203) mqtt.1.zigbee2mqtt.bridge: logging {"level":"info","message":"MQTT publish: topic 'zigbee2mqtt/xi_sensor_temperature_01/battery', payload '100'"}
2021-11-23 11:46:59.328 - debug: nctalk.0 (1203) mqtt.1.zigbee2mqtt.bridge: logging {"level":"info","message":"MQTT publish: topic 'zigbee2mqtt/xi_sensor_temperature_01/linkquality', payload '132'"}
2021-11-23 11:47:02.924 - debug: nctalk.0 (1203) mqtt.1.zigbee2mqtt.bridge: logging {"level":"info","message":"MQTT publish: topic 'zigbee2mqtt/hue_sensor_motion_01/battery', payload '52'"}
2021-11-23 11:47:02.928 - debug: nctalk.0 (1203) mqtt.1.zigbee2mqtt.bridge: logging {"level":"info","message":"MQTT publish: topic 'zigbee2mqtt/hue_sensor_motion_01/occupancy_timeout', payload '0'"}
2021-11-23 11:47:02.931 - debug: nctalk.0 (1203) mqtt.1.zigbee2mqtt.bridge: logging {"level":"info","message":"MQTT publish: topic 'zigbee2mqtt/hue_sensor_motion_01/occupancy', payload 'false'"}
2021-11-23 11:47:02.934 - debug: nctalk.0 (1203) mqtt.1.zigbee2mqtt.bridge: logging {"level":"info","message":"MQTT publish: topic 'zigbee2mqtt/hue_sensor_motion_01/motion_sensitivity', payload 'high'"}
2021-11-23 11:47:02.939 - debug: nctalk.0 (1203) mqtt.1.zigbee2mqtt.bridge: logging {"level":"info","message":"MQTT publish: topic 'zigbee2mqtt/hue_sensor_motion_01/temperature', payload '20.2'"}
2021-11-23 11:47:02.942 - debug: nctalk.0 (1203) mqtt.1.zigbee2mqtt.bridge: logging {"level":"info","message":"MQTT publish: topic 'zigbee2mqtt/hue_sensor_motion_01/illuminance', payload '14941'"}
2021-11-23 11:47:02.945 - debug: nctalk.0 (1203) mqtt.1.zigbee2mqtt.bridge: logging {"level":"info","message":"MQTT publish: topic 'zigbee2mqtt/hue_sensor_motion_01/illuminance_lux', payload '31.18889584093937'"}
2021-11-23 11:47:02.949 - debug: nctalk.0 (1203) mqtt.1.zigbee2mqtt.bridge: logging {"level":"info","message":"MQTT publish: topic 'zigbee2mqtt/hue_sensor_motion_01/update-state', payload 'idle'"}
2021-11-23 11:47:02.953 - debug: nctalk.0 (1203) mqtt.1.zigbee2mqtt.bridge: logging {"level":"info","message":"MQTT publish: topic 'zigbee2mqtt/hue_sensor_motion_01/linkquality', payload '123'"}
2021-11-23 11:47:07.250 - debug: nctalk.0 (1203) Debug Event [object Object]
2021-11-23 11:47:07.253 - debug: nctalk.0 (1203) Debug Event WaitNewMessages done
2021-11-23 11:47:08.669 - debug: nctalk.0 (1203) mqtt.1.zigbee2mqtt.bridge: logging {"level":"info","message":"MQTT publish: topic 'zigbee2mqtt/xi_switch_04/voltage', payload '3045'"}
2021-11-23 11:47:08.672 - debug: nctalk.0 (1203) mqtt.1.zigbee2mqtt.bridge: logging {"level":"info","message":"MQTT publish: topic 'zigbee2mqtt/xi_switch_04/battery', payload '100'"}
2021-11-23 11:47:08.677 - debug: nctalk.0 (1203) mqtt.1.zigbee2mqtt.bridge: logging {"level":"info","message":"MQTT publish: topic 'zigbee2mqtt/xi_switch_04/linkquality', payload '120'"}
2021-11-23 11:47:08.773 - debug: nctalk.0 (1203) mqtt.1.zigbee2mqtt.bridge: logging {"level":"info","message":"MQTT publish: topic 'zigbee2mqtt/hue_sensor_motion_01/battery', payload '52'"}
2021-11-23 11:47:08.779 - debug: nctalk.0 (1203) mqtt.1.zigbee2mqtt.bridge: logging {"level":"info","message":"MQTT publish: topic 'zigbee2mqtt/hue_sensor_motion_01/occupancy_timeout', payload '0'"}
2021-11-23 11:47:08.782 - debug: nctalk.0 (1203) mqtt.1.zigbee2mqtt.bridge: logging {"level":"info","message":"MQTT publish: topic 'zigbee2mqtt/hue_sensor_motion_01/occupancy', payload 'false'"}
2021-11-23 11:47:08.785 - debug: nctalk.0 (1203) mqtt.1.zigbee2mqtt.bridge: logging {"level":"info","message":"MQTT publish: topic 'zigbee2mqtt/hue_sensor_motion_01/motion_sensitivity', payload 'high'"}
2021-11-23 11:47:08.790 - debug: nctalk.0 (1203) mqtt.1.zigbee2mqtt.bridge: logging {"level":"info","message":"MQTT publish: topic 'zigbee2mqtt/hue_sensor_motion_01/temperature', payload '20.2'"}
2021-11-23 11:47:08.793 - debug: nctalk.0 (1203) mqtt.1.zigbee2mqtt.bridge: logging {"level":"info","message":"MQTT publish: topic 'zigbee2mqtt/hue_sensor_motion_01/illuminance', payload '14926'"}
2021-11-23 11:47:08.797 - debug: nctalk.0 (1203) mqtt.1.zigbee2mqtt.bridge: logging {"level":"info","message":"MQTT publish: topic 'zigbee2mqtt/hue_sensor_motion_01/illuminance_lux', payload '31.08135902739475'"}
2021-11-23 11:47:08.800 - debug: nctalk.0 (1203) mqtt.1.zigbee2mqtt.bridge: logging {"level":"info","message":"MQTT publish: topic 'zigbee2mqtt/hue_sensor_motion_01/update-state', payload 'idle'"}
2021-11-23 11:47:08.832 - debug: nctalk.0 (1203) mqtt.1.zigbee2mqtt.bridge: logging {"level":"info","message":"MQTT publish: topic 'zigbee2mqtt/hue_sensor_motion_01/linkquality', payload '123'"}
2021-11-23 11:47:11.823 - debug: nctalk.0 (1203) Debug Event WaitNewMessages - Talk timeout empty reply after no new message was received
2021-11-23 11:47:11.823 - debug: nctalk.0 (1203) Debug Event WaitNewMessages done
2021-11-23 11:47:13.667 - debug: nctalk.0 (1203) mqtt.1.zigbee2mqtt.bridge: logging {"level":"info","message":"MQTT publish: topic 'zigbee2mqtt/hue_sensor_motion_01/battery', payload '52'"}
2021-11-23 11:47:13.672 - debug: nctalk.0 (1203) mqtt.1.zigbee2mqtt.bridge: logging {"level":"info","message":"MQTT publish: topic 'zigbee2mqtt/hue_sensor_motion_01/occupancy_timeout', payload '0'"}
2021-11-23 11:47:13.677 - debug: nctalk.0 (1203) mqtt.1.zigbee2mqtt.bridge: logging {"level":"info","message":"MQTT publish: topic 'zigbee2mqtt/hue_sensor_motion_01/occupancy', payload 'true'"}
2021-11-23 11:47:13.683 - debug: nctalk.0 (1203) mqtt.1.zigbee2mqtt.bridge: logging {"level":"info","message":"MQTT publish: topic 'zigbee2mqtt/hue_sensor_motion_01/motion_sensitivity', payload 'high'"}
2021-11-23 11:47:13.686 - debug: nctalk.0 (1203) mqtt.1.zigbee2mqtt.bridge: logging {"level":"info","message":"MQTT publish: topic 'zigbee2mqtt/hue_sensor_motion_01/temperature', payload '20.2'"}
2021-11-23 11:47:13.689 - debug: nctalk.0 (1203) mqtt.1.zigbee2mqtt.bridge: logging {"level":"info","message":"MQTT publish: topic 'zigbee2mqtt/hue_sensor_motion_01/illuminance', payload '14926'"}
2021-11-23 11:47:13.695 - debug: nctalk.0 (1203) mqtt.1.zigbee2mqtt.bridge: logging {"level":"info","message":"MQTT publish: topic 'zigbee2mqtt/hue_sensor_motion_01/illuminance_lux', payload '31.08135902739475'"}
2021-11-23 11:47:13.696 - debug: nctalk.0 (1203) mqtt.1.zigbee2mqtt.bridge: logging {"level":"info","message":"MQTT publish: topic 'zigbee2mqtt/hue_sensor_motion_01/update-state', payload 'idle'"}
2021-11-23 11:47:13.699 - debug: nctalk.0 (1203) mqtt.1.zigbee2mqtt.bridge: logging {"level":"info","message":"MQTT publish: topic 'zigbee2mqtt/hue_sensor_motion_01/linkquality', payload '117'"}
2021-11-23 11:47:23.620 - debug: nctalk.0 (1203) mqtt.1.zigbee2mqtt.bridge: logging {"level":"info","message":"MQTT publish: topic 'zigbee2mqtt/hue_sensor_motion_01/battery', payload '52'"}
2021-11-23 11:47:23.624 - debug: nctalk.0 (1203) mqtt.1.zigbee2mqtt.bridge: logging {"level":"info","message":"MQTT publish: topic 'zigbee2mqtt/hue_sensor_motion_01/occupancy_timeout', payload '0'"}
2021-11-23 11:47:23.629 - debug: nctalk.0 (1203) mqtt.1.zigbee2mqtt.bridge: logging {"level":"info","message":"MQTT publish: topic 'zigbee2mqtt/hue_sensor_motion_01/occupancy', payload 'false'"}
2021-11-23 11:47:23.633 - debug: nctalk.0 (1203) mqtt.1.zigbee2mqtt.bridge: logging {"level":"info","message":"MQTT publish: topic 'zigbee2mqtt/hue_sensor_motion_01/motion_sensitivity', payload 'high'"}
2021-11-23 11:47:23.638 - debug: nctalk.0 (1203) mqtt.1.zigbee2mqtt.bridge: logging {"level":"info","message":"MQTT publish: topic 'zigbee2mqtt/hue_sensor_motion_01/temperature', payload '20.2'"}
2021-11-23 11:47:23.641 - debug: nctalk.0 (1203) mqtt.1.zigbee2mqtt.bridge: logging {"level":"info","message":"MQTT publish: topic 'zigbee2mqtt/hue_sensor_motion_01/illuminance', payload '14926'"}
2021-11-23 11:47:23.644 - debug: nctalk.0 (1203) mqtt.1.zigbee2mqtt.bridge: logging {"level":"info","message":"MQTT publish: topic 'zigbee2mqtt/hue_sensor_motion_01/illuminance_lux', payload '31.08135902739475'"}
2021-11-23 11:47:23.647 - debug: nctalk.0 (1203) mqtt.1.zigbee2mqtt.bridge: logging {"level":"info","message":"MQTT publish: topic 'zigbee2mqtt/hue_sensor_motion_01/update-state', payload 'idle'"}
2021-11-23 11:47:23.650 - debug: nctalk.0 (1203) mqtt.1.zigbee2mqtt.bridge: logging {"level":"info","message":"MQTT publish: topic 'zigbee2mqtt/hue_sensor_motion_01/linkquality', payload '123'"}
2021-11-23 11:47:23.673 - debug: nctalk.0 (1203) mqtt.1.zigbee2mqtt.bridge: logging {"level":"info","message":"MQTT publish: topic 'zigbee2mqtt/hue_sensor_motion_01/battery', payload '52'"}
2021-11-23 11:47:23.676 - debug: nctalk.0 (1203) mqtt.1.zigbee2mqtt.bridge: logging {"level":"info","message":"MQTT publish: topic 'zigbee2mqtt/hue_sensor_motion_01/occupancy_timeout', payload '0'"}
2021-11-23 11:47:23.679 - debug: nctalk.0 (1203) mqtt.1.zigbee2mqtt.bridge: logging {"level":"info","message":"MQTT publish: topic 'zigbee2mqtt/hue_sensor_motion_01/occupancy', payload 'false'"}
2021-11-23 11:47:23.683 - debug: nctalk.0 (1203) mqtt.1.zigbee2mqtt.bridge: logging {"level":"info","message":"MQTT publish: topic 'zigbee2mqtt/hue_sensor_motion_01/motion_sensitivity', payload 'high'"}
2021-11-23 11:47:23.685 - debug: nctalk.0 (1203) mqtt.1.zigbee2mqtt.bridge: logging {"level":"info","message":"MQTT publish: topic 'zigbee2mqtt/hue_sensor_motion_01/temperature', payload '20.2'"}
2021-11-23 11:47:23.715 - debug: nctalk.0 (1203) mqtt.1.zigbee2mqtt.bridge: logging {"level":"info","message":"MQTT publish: topic 'zigbee2mqtt/hue_sensor_motion_01/illuminance', payload '14910'"}
2021-11-23 11:47:23.720 - debug: nctalk.0 (1203) mqtt.1.zigbee2mqtt.bridge: logging {"level":"info","message":"MQTT publish: topic 'zigbee2mqtt/hue_sensor_motion_01/illuminance_lux', payload '30.967061741707724'"}
2021-11-23 11:47:23.723 - debug: nctalk.0 (1203) mqtt.1.zigbee2mqtt.bridge: logging {"level":"info","message":"MQTT publish: topic 'zigbee2mqtt/hue_sensor_motion_01/update-state', payload 'idle'"}
2021-11-23 11:47:23.726 - debug: nctalk.0 (1203) mqtt.1.zigbee2mqtt.bridge: logging {"level":"info","message":"MQTT publish: topic 'zigbee2mqtt/hue_sensor_motion_01/linkquality', payload '123'"}

Dazu hätte ich noch eine Frage, ist es von dir gewünscht, das bei "debug: nctalk.0" auch die Meldungen zu mqtt erscheinen?

Auch wenn ich mich wiederhole, Danke dir zu dem Adapter.
Ich weiß ja nicht was du für die Zukunft geplant hast, doch das wäre ein Kandidat um telegram abzulösen.

Gruß, Karsten

[johen]

@hydrotec said in [Neuer Adapter] nextcloud talk messenger:

Dazu hätte ich noch eine Frage, ist es von dir gewünscht, das bei "debug: nctalk.0" auch die Meldungen zu mqtt erscheinen?

Nein mit mqtt wird nichts gemacht und bei mir taucht auch nichts vergleichbares auf, hab auch eine mqtt Instanz bei mir laufen.
Irgendwie scheint es so als ob bei diesen Logs nctalk.0 (1203) mqtt.1.zigbee2mqtt.bridge:... nicht richtig ist / falsch dargestellt / nicht richtig aufgelöst wird.
Wüsste auch nicht wo in meinem Code die angezeigten Strings herkommen soll / erzeugt werden soll.
Kannst ja mal zum Test bei deiner mqtt.1 Instanz die Debug logs abschalten oder die Instanz stoppen und schauen ob Sie dann verschwinden bzw wie es sich dann verhält.

Zu telegram ja die Idee ist schon einige Funktionen mit nctalk ebenfalls umzusetzen - hab aber den Adapter noch nicht verwenden nur kurz in den Code reingeschaut um ein paar Anwendungsideen zu bekommen. Z.b. text2command
Vielleicht hast du ja konkrete Anwendungsideen...

Aktuell verwende ich Node Red um Kommandos und Status Meldungen zu implementieren.

[hydrotec]

@johen sagte in [Neuer Adapter] nextcloud talk messenger:

Kannst ja mal zum Test bei deiner mqtt.1 Instanz die Debug logs abschalten oder die Instanz stoppen und schauen ob Sie dann verschwinden bzw wie es sich dann verhält.

Die Instanz mqtt.1 ist Log-Stufe "Info" gewesen.


Hab noch ein paar Versuche gestartet, und da ist mir noch aufgefallen, das es wirklich nur die Instanz mqtt.1 betrifft.
Von den Instanzen mqtt.0/mqtt.2 erscheinen keine Meldungen in dem Logfile (hab extra welche provoziert).

Eine Frage noch zu den Einstellungen, dort hast du ja auch einen DebugLog zum anhaken mit eingebaut.

Spoiler

Wozu ist der gedacht?
Egal ob ich den Haken setze oder nicht, in dem Logfile erkenne ich keine Änderung.

Vielleicht hast du ja konkrete Anwendungsideen...

Oje, da fragst du den Richtigen.
Was ich bei telegram ganz nützlich finde,
ist das Einblenden einer Art Menüstruktur (damit man sich die shortcuts/keywords nicht merken muss).
Ob das mit Talk auch gehen würde, weiß ich nicht.
Kenne mich mit Talk nicht wirklich aus, hab das erst in Verbindung mit deinem Adapter in Betrieb genommen.
Die Nextcloud Talk API hab ich nur kurz überflogen.

Aktuell verwende ich Node Red um Kommandos und Status Meldungen zu implementieren.

Theoretisch kann man das ja jetzt schon mit Hilfe von script/blockly umsetzen.
Auswertung von keywords und dementsprechend eine Aktion ausführen.
(braucht man weder text2command noch NodeRed)

Muss das Ganze mal etwas sacken lassen, vielleicht fällt mir ja das ein oder Andere noch ein.
Eventuell findet sich ja noch jemand, der ein paar Ideen hat.

Gruß, Karsten

[hydrotec]

@johen

Hallo johen,
was auch noch ganz nützlich wäre, wenn man auch Bilder/Fotos versenden könnte.

Angenehmes Wochenende
Gruß, Karsten

[-cs-]

@johen

Hi,
als ich das hier gesehen habe, musste ich gleich testen, Super.

Bei mir läuft ja ioBroker auf einem NUC / Proxmox / VM Debian / ioBroker mit Admin 5.

Nextcloud als Version: 21.0.7.

Schaut gut aus.

Wie @hydrotec schon erwähnte, wenn jetzt noch Bilder versendet werden könnten, würde ich mich von Telegramm verabschieden.

Danke und schöne Grüße
Christian

[johen]

Bilder senden ist geplant, hat in einem Test außerhalb vom ioBroker auch schon funktioniert.
Habt ihr Ideen wie die Schnittstelle für Bilddaten im ioBroker am besten umgesetzt werden sollte? Bzw wie macht es der Telegram Adapter?

Werden da die Bilddaten direkt übergeben oder nur eine Refernz z.b. zu einem Link (z.b. zum Videoüberwachungserver)...

[-cs-]

@johen

Bei mir is es vorrangig das Bild einer Cam darum hab ich mir ein kleines Blockly ähnlich diesem hier (rechts oben) erstellt.

Es wird z.B. das Bild der Cam in einen Ordner gespeichert, der Inhalt (immer nur die aktuelle Datei) dann mit dem senden Blockly versendet.

Genaueres kann ich nicht dazu sagen, da bin ich schon wieder raus.

[hydrotec]

@johen

Auch bei mir ist es, wie bei Christian, hauptsächlich ein snapshot der Kamera über Blockly.

Spoiler

   if (telegram_message == 'Dafang01') {
     exec('wget --quiet --output-document /opt/iobroker/iobroker-data/tmp/dafang01/dafang01.jpg --user xxx --password xxx https://192.168.78.86/cgi-bin/currentpic.cgi --no-check-certificate', async function (error, result, stderr) {
         sendTo("telegram.0", "send", {
           text: '/opt/iobroker/iobroker-data/tmp/dafang01/dafang01.jpg',
           user: telegram_sender
       });
     });

Wie das intern im Adapter verwaltet wird weiß ich nicht.
In den Objekten kann man nichts erkennen, ob es ein Bild oder Text ist.

Gruß, Karsten

[-cs-]

@johen

vorhin ist mir Nextcloud (habe keinen eigenen Server, sondern Managed Nextcloud bei einem Hoster) abgeschmiert, da der Adapter zu viel zugegriffen hat, eigentlich ununterbrochen.

Hier der (anonymiserte?) Auszug vom Hoster:

xx.xxx.xxx.x - iob [01/Dec/2021:13:22:53 +0000] "GET /ocs/v2.php/apps/spreed/api/v1/chat/9jhbeusnj?lookIntoFuture=1&setReadMarker=1&format=json&lastKnownMessageId=87 HTTP/1.1" 502 150 "-" "-"
xx.xxx.xxx.x - iob [01/Dec/2021:13:22:53 +0000] "GET /ocs/v2.php/apps/spreed/api/v1/chat/4gbs78mw?lookIntoFuture=1&setReadMarker=1&format=json&lastKnownMessageId=116 HTTP/1.1" 502 150 "-" "-"
xx.xxx.xxx.x - iob [01/Dec/2021:13:22:53 +0000] "GET /ocs/v2.php/apps/spreed/api/v1/chat/9jhbeusnj?lookIntoFuture=1&setReadMarker=1&format=json&lastKnownMessageId=87 HTTP/1.1" 502 150 "-" "-"
xx.xxx.xxx.x - iob [01/Dec/2021:13:22:53 +0000] "GET /ocs/v2.php/apps/spreed/api/v1/chat/4gbs78mw?lookIntoFuture=1&setReadMarker=1&format=json&lastKnownMessageId=116 HTTP/1.1" 502 150 "-" "-"

Christian

[johen]

@csr
Ja ist bei mir auch schon aufgetreten und bin da dran....

[johen]

Hab im nctalkclient ein Bug bei der http timeout Behandlung gefixt (neue Version 1.2.0), was meiner Meinung nach das Problem verursacht hat.
Wenn der iobroker.nctalk nochmal installiert wird sollte er sich den neusten nctalkclient ziehen.

Alternativ:
Adapter stoppen
npm update nctalkclient

Version prüfen:
/opt/iobroker# npm list | grep talk
│ ├── @serialport/parser-cctalk@9.0.7
├─┬ iobroker.nctalk@0.2.0 (github:jjqoie/iobroker.nctalk#57589398191d574048a44947585da36f7c871fd5)
│ └── nctalkclient@1.2.0

EDIT: Leider ist gerade das Problem trotzdem wieder gekommen
Update: Der Patch behebt ein Teil des Problems- nach durchschauen der Logs, kam es diesmal zum Problemen wenn auf Grund von vielen Anfragen an nextcloud (bei mir war es Fotos anschauen), eine Anfrage vom Adapter mit http 502 beantwortet wird.

[johen]

Fehler ist nun behoben und neue Version 1.3.0 vom nctalkclient ist verfügbar.

[hydrotec]

@johen

Hallo Jochen,
kurze Rückmeldung.

Spoiler

XXX@iobroker:/opt/iobroker$ npm list | grep talk
│   ├── @serialport/parser-cctalk@9.2.4
├─┬ iobroker.nctalk@0.2.0 (github:jjqoie/iobroker.nctalk#57589398191d574048a44947585da36f7c871fd5)
│ └── nctalkclient@1.3.0
XXX@iobroker:/opt/iobroker$

Läuft seit ein paar Tagen unauffällig. (Hatte vorher auch keine Probleme)
Hab mal über das WebUI bei Nextcloud eine Diashow am laufen gehabt,
nctalk funktioniert mit senden/empfangen von Textnachrichten (auch größere Listen) ohne Probleme.

Danke noch einmal für deine Arbeit.
Gruß, Karsten

Edit (10.12.2021):
Heute zum ersten mal ERROR Meldung im Log gefunden.
(2021-12-10 07:00:13.281)

Spoiler

2021-12-10 06:50:01.852 - info: host.iobroker instance system.adapter.netatmo-crawler.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
2021-12-10 06:55:00.027 - info: host.iobroker instance system.adapter.netatmo-crawler.0 started with pid 32556
2021-12-10 06:55:00.602 - info: netatmo-crawler.0 (32556) starting. Version 0.6.0 in /opt/iobroker/node_modules/iobroker.netatmo-crawler, node: v14.18.2, js-controller: 3.3.21
2021-12-10 06:55:00.620 - info: netatmo-crawler.0 (32556) Getting data for stationid:70:ee:50:14:81:ae
2021-12-10 06:55:01.322 - info: netatmo-crawler.0 (32556) Terminated (ADAPTER_REQUESTED_TERMINATION): Everything done. Going to terminate till next schedule
2021-12-10 06:55:01.842 - info: host.iobroker instance system.adapter.netatmo-crawler.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
2021-12-10 07:00:00.045 - info: host.iobroker instance system.adapter.netatmo-crawler.0 started with pid 32577
2021-12-10 07:00:00.613 - info: netatmo-crawler.0 (32577) starting. Version 0.6.0 in /opt/iobroker/node_modules/iobroker.netatmo-crawler, node: v14.18.2, js-controller: 3.3.21
2021-12-10 07:00:00.633 - info: netatmo-crawler.0 (32577) Getting data for stationid:70:ee:50:14:81:ae
2021-12-10 07:00:01.432 - info: netatmo-crawler.0 (32577) Terminated (ADAPTER_REQUESTED_TERMINATION): Everything done. Going to terminate till next schedule
2021-12-10 07:00:01.952 - info: host.iobroker instance system.adapter.netatmo-crawler.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
2021-12-10 07:00:04.060 - info: host.iobroker instance system.adapter.daswetter.0 started with pid 32592
2021-12-10 07:00:04.544 - info: daswetter.0 (32592) starting. Version 3.0.9 in /opt/iobroker/node_modules/iobroker.daswetter, node: v14.18.2, js-controller: 3.3.21
2021-12-10 07:00:08.069 - info: host.iobroker instance system.adapter.ical.4 started with pid 32607
2021-12-10 07:00:08.781 - info: ical.4 (32607) starting. Version 1.11.5 in /opt/iobroker/node_modules/iobroker.ical, node: v14.18.2, js-controller: 3.3.21
2021-12-10 07:00:09.591 - info: ical.4 (32607) processing URL: Anwesenheit https://XXX.XXX.XXX/remote.php/dav/calendars/XXX/anwesenheit/?export
2021-12-10 07:00:09.859 - info: daswetter.0 (32592) still wrong data structure from server received! repaired...
2021-12-10 07:00:11.084 - info: daswetter.0 (32592) Terminated (ADAPTER_REQUESTED_TERMINATION): All data handled, adapter stopped until next scheduled moment
2021-12-10 07:00:11.592 - info: daswetter.0 (32592) cleaned everything up...
2021-12-10 07:00:11.599 - info: host.iobroker instance system.adapter.daswetter.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
2021-12-10 07:00:12.086 - info: host.iobroker instance system.adapter.ical.1 started with pid 32622
2021-12-10 07:00:12.695 - info: ical.1 (32622) starting. Version 1.11.5 in /opt/iobroker/node_modules/iobroker.ical, node: v14.18.2, js-controller: 3.3.21
2021-12-10 07:00:13.281 - error: nctalk.0 (12245) Error Event Error unknown http statusCode - 502
2021-12-10 07:00:13.282 - error: nctalk.0 (12245) Error Event Error unknown http statusCode - 502
2021-12-10 07:00:13.388 - error: nctalk.0 (12245) Error Event Error unknown http statusCode - 502
2021-12-10 07:00:13.389 - error: nctalk.0 (12245) Error Event Error unknown http statusCode - 502
2021-12-10 07:00:14.167 - info: ical.1 (32622) processing URL: Zeitumstellung https://XXX.XXX.XXX/remote.php/dav/calendars/XXX/zeitumstellung/?export
2021-12-10 07:00:14.211 - info: ical.1 (32622) processing URL: Formel1 https://XXX.XXX.XXX/remote.php/dav/calendars/XXX/formel1/?export
2021-12-10 07:00:14.262 - info: ical.1 (32622) processing URL: DTM https://XXX.XXX.XXX/remote.php/dav/calendars/XXX/dtm/?export
2021-12-10 07:00:14.456 - info: ical.1 (32622) processing URL: NFL https://XXX.XXX.XXX/remote.php/dav/calendars/XXX/nfl/?export
2021-12-10 07:00:14.687 - info: ical.4 (32607) Terminated (NO_ERROR): Without reason
2021-12-10 07:00:14.689 - info: ical.1 (32622) processing URL: Persönlich https://XXX.XXX.XXX/remote.php/dav/calendars/XXX/personal/?export
2021-12-10 07:00:15.200 - info: host.iobroker instance system.adapter.ical.4 terminated with code 0 (NO_ERROR)
2021-12-10 07:00:19.799 - info: ical.1 (32622) Terminated (NO_ERROR): Without reason
2021-12-10 07:00:20.319 - info: host.iobroker instance system.adapter.ical.1 terminated with code 0 (NO_ERROR)
2021-12-10 07:05:00.028 - info: host.iobroker instance system.adapter.netatmo-crawler.0 started with pid 32644

Funktion weiterhin ohne Einschränkung

[johen]

@hydrotec

Wieviel "chat rooms" hast du, welche abgefragt werden?

Genau das ist die Ursache (nextcloud bzw reverse proxy gibt http 502 zurück), warum der Adapter vor dem bugfix aus dem Tritt kam. 502 wurde nicht als Fehler erkannt und der Adapter hat gleich wieder die "WaitNewMessage" API aufgerufen und wieder kam sofort 502 und so weiter....
In meinen alten (bevor es den Adapter gab) logs von meinem Reverse Proxy gab es auch schon damals immer wieder mal 502 - d.h. dieses Thema kommt nicht vom Adapter.
Jetzt wird 502 ausgewertet und mit einem Error log angezeigt (warning log wäre warscheinlich besser) und nach ein längern Wartezeit 30sek geprüft ob der Nextcloud Service wieder verfügbar ist.

PS: Zu 502 https://www.ionos.de/digitalguide/hosting/hosting-technik/was-bedeutet-502-bad-gateway-erklaerung-loesung/

[johen]

https://github.com/nextcloud/docker/issues/1385

supermar1010 created this issue in nextcloud/docker

closed Client shows occasional 502 Bad Gateway, nextcloud server log shows success, reverse proxy log shows error #1385

[hydrotec]

@johen sagte in [Neuer Adapter] nextcloud talk messenger:

@hydrotec

Wieviel "chat rooms" hast du, welche abgefragt werden?

Grundsätzlich noch die selbe Einstellung wie hier beschrieben.
(Log Ausgabe auf Info eingestellt, sonst keine Änderung)

Genau das ist die Ursache (nextcloud bzw reverse proxy gibt http 502 zurück), warum der Adapter vor dem bugfix aus dem Tritt kam. ...

Ist, vermutlich von mir, missverständlich ausgedrückt gewesen.
Wollte damit eigentlich nur aufzeigen, das seit dem Update (nctalkclient@1.3.0),
zum ersten mal eine Meldung im Log gab.
Dennoch Dankeschön für deine ausführliche Erklärung zu dem HTTP-Statuscode.

Wie gesagt, was Textnachrichten versenden/empfangen angeht, funktioniert der Adapter einwandfrei.
(Sobald die Übertragung von Bildern funktioniert, ist telegram auf meinem System verschwunden )

Gruß, Karsten

[johen]

An alle die Performance Probleme (stark verlängerte Reaktionszeiten bis zu 30sec) mit Ihrer Nextcloud Instance sehen, sollten unbedingt ihre FPM Einstellungen prüfen, vor allem wenn die offizielle docker compose Installation mit NGINX (https://github.com/nextcloud/docker) verwendet wurde. Hier sind die Standardeinstellungen für max_children gleich 5, was für Talk zu wenig ist.

Im fpm_app container ist die Config hier zu finden. Bitte beachten, dass mit der Config unten auch mal 8GB RAM benötigt wird vor allem beim Bilder anschauen.
/usr/local/etc/php-fpm.d/www.conf

pm = dynamic
pm.max_children = 32
pm.start_servers = 12
pm.min_spare_servers = 8
pm.max_spare_servers = 16
pm.max_requests = 1000

Weiterführende Links:
https://help.nextcloud.com/t/nextcloudpi-and-talk-configuration-incompatible/79469
https://www.technik-blog.eu/2018/08/php-fpm-einstellungen-optimieren.html
https://www.kinamo.be/en/support/faq/determining-the-correct-number-of-child-processes-for-php-fpm-on-nginx