Neuer Blogbeitrag: Monatsrückblick - Dezember 2025 🎄

[Asgothian]

@michihorn da muss sich was tun in dem moment wo du auf die Zigbee Tab Ansicht wechselst.

A.

[michihorn]

@asgothian Was genau meinst Du mit Tab Ansicht?

Mir fällt gerade mal auf das der Tab Einstellungen fehlt

[arteck]

@michihorn quack...klicke und staune

[Asgothian]

@michihorn in der Ansicht die du da offen hast den Tab "Geräte" öffnen, abwarten

A.

[michihorn]

@arteck sagte in Zigbee Update:

@michihorn quack...klicke und staune

Ach ja, das hatte ich schon richtig gemacht, ich wunderte mich nur, dass die von Asgothian gewünschten Resultate nicht im LOG erschienen sind.

[michihorn]

@asgothian Hallo Asgothian, ich habe soeben noch einmal den Log kopiert

zigbee.0	2022-05-19 16:13:28.137	debug	(10732) DeviceAvailability:Non-pingable device 0x00158d000549dc7f lumi.sensor_ht was last seen '2923.336' seconds ago.
zigbee.0	2022-05-19 16:13:28.133	debug	(10732) DeviceAvailability:Non-pingable device 0x0c4314fffe84e6d8 TS0042 was last seen '2750.699' seconds ago.
zigbee.0	2022-05-19 16:13:28.132	debug	(10732) DeviceAvailability:Non-pingable device 0x00158d000253e897 lumi.sensor_motion.aq2 was last seen '1361.011' seconds ago.
zigbee.0	2022-05-19 16:13:28.131	debug	(10732) DeviceAvailability:Non-pingable device 0x00158d0001e09c1a lumi.weather was last seen '286.45' seconds ago.
zigbee.0	2022-05-19 16:13:28.130	debug	(10732) DeviceAvailability:Non-pingable device 0x00158d000444cb23 lumi.weather was last seen '715.348' seconds ago.
zigbee.0	2022-05-19 16:13:28.129	debug	(10732) DeviceAvailability:Non-pingable device 0x00158d00028d6fc4 lumi.sensor_magnet.aq2 was last seen '2892.854' seconds ago.
zigbee.0	2022-05-19 16:13:28.127	debug	(10732) DeviceAvailability:Non-pingable device 0x00158d0001e0821b lumi.weather was last seen '198.681' seconds ago.
zigbee.0	2022-05-19 16:13:28.126	debug	(10732) DeviceAvailability:Non-pingable device 0x00158d0001e13db7 lumi.weather was last seen '377.39' seconds ago.
zigbee.0	2022-05-19 16:13:28.126	debug	(10732) DeviceAvailability:Non-pingable device 0x00158d0007b6e4bd lumi.sensor_magnet.aq2 was last seen '3203.55' seconds ago.
zigbee.0	2022-05-19 16:13:28.125	debug	(10732) DeviceAvailability:Non-pingable device 0x00158d0007f851b6 lumi.sensor_magnet.aq2 was last seen '2805.106' seconds ago.
zigbee.0	2022-05-19 16:13:28.124	debug	(10732) DeviceAvailability:Non-pingable device 0x00158d0007e0590a lumi.sensor_magnet.aq2 was last seen '6675251.656' seconds ago.
zigbee.0	2022-05-19 16:13:28.124	debug	(10732) DeviceAvailability:Non-pingable device 0x00158d0007e033e1 lumi.sensor_magnet.aq2 was last seen '3610.205' seconds ago.
zigbee.0	2022-05-19 16:13:28.114	debug	(10732) DeviceAvailability:Non-pingable device 0x00158d0007b7cdce lumi.sensor_magnet.aq2 was last seen '467.92' seconds ago.
zigbee.0	2022-05-19 16:13:28.112	debug	(10732) DeviceAvailability:Non-pingable device 0x00158d000476bd65 lumi.sensor_magnet.aq2 was last seen '1787.034' seconds ago.
zigbee.0	2022-05-19 16:13:28.112	debug	(10732) DeviceAvailability:Non-pingable device 0x00158d00069ac702 lumi.sensor_magnet.aq2 was last seen '13714.272' seconds ago.
zigbee.0	2022-05-19 16:13:28.112	debug	(10732) DeviceAvailability:Non-pingable device 0x00158d0006becb12 lumi.sensor_magnet.aq2 was last seen '6675029.851' seconds ago.
zigbee.0	2022-05-19 16:13:28.112	debug	(10732) DeviceAvailability:Non-pingable device 0x00158d000423bfd0 lumi.sensor_motion.aq2 was last seen '3552.448' seconds ago.
zigbee.0	2022-05-19 16:13:28.111	debug	(10732) DeviceAvailability:Non-pingable device 0x00158d0007e3ac5e lumi.weather was last seen '2046.879' seconds ago.
zigbee.0	2022-05-19 16:13:28.111	debug	(10732) DeviceAvailability:Non-pingable device 0x00158d0007e20084 lumi.weather was last seen '219.109' seconds ago.
zigbee.0	2022-05-19 16:12:58.777	debug	2
zigbee.0	2022-05-19 16:12:58.777	debug	(10732) getBinding result: []
zigbee.0	2022-05-19 16:12:58.807	debug	(10732) getExclude result: []
zigbee.0	2022-05-19 16:12:58.777	debug	(10732) getBinding result: []
zigbee.0	2022-05-19 16:12:58.362	debug	(10732) getDevices result: [{"_id":"0x00124b001cd47927","icon":"img/unknown.png","paired":true,"info":{"type":"device","device":{"_events":{},"_eventsCount":0,"_maxListeners":100,"ID":1,"_type":"Coord
zigbee.0	2022-05-19 16:12:58.160	debug	(10732) getMap result: {"lqis":[{"parent":"0x00124b001cd47927","networkAddress":47520,"ieeeAddr":"0x0c4314fffe84e6d8","lqi":78,"relationship":1,"depth":1,"status":"online"},{"parent":"0x00124b001cd479
zigbee.0	2022-05-19 16:12:58.160	debug	(10732) Get map succeeded [{"parent":"0x00124b001cd47927","networkAddress":47520,"ieeeAddr":"0x0c4314fffe84e6d8","lqi":78,"relationship":1,"depth":1,"status":"online"},{"parent":"0x00124b001cd47927","
zigbee.0	2022-05-19 16:12:58.160	debug	(10732) Routing table succeeded for 'Coordinator'
zigbee.0	2022-05-19 16:12:58.159	debug	(10732) Routing for 'Coordinator': {"table":[]}
zigbee.0	2022-05-19 16:12:58.150	debug	(10732) LQI succeeded for 'Coordinator'
zigbee.0	2022-05-19 16:12:58.086	debug	(10732) getGroups result: {}
zigbee.0	2022-05-19 16:12:58.080	debug	(10732) getCoorinatorInfo result: {"installSource":"iobroker.zigbee@1.6.18","channel":"11","port":"COM3","type":"zStack3x0","revision":20210708,"version":"2-1.2.7.1."}
zigbee.0	2022-05-19 16:12:58.078	debug	(10732) List of ports: [{"comName":"COM3"},{"comName":"COM4"}]

Mehr kann ich nicht bieten
Gruß
M.

[Asgothian]

@michihorn Der text ist drin, aber unvollständig. Du kannst den Text nicht aus der Oberfläche kopieren sondern musst das Log über "log herunterladen" als Text laden und die entscheidenden Zeilen kopieren.

Das was ich suche ist nach geschätzt 120 Zeichen abgeschnitten:

getDevices result: [{"_id":"0x00124b001cd47927","icon":"img/unknown.png","paired":true,"info":{"type":"device","device":{"_events":{},"_eventsCount":0,"_maxListeners":100,"ID":1,"_type":"Coord

A.

[michihorn]

@asgothian Ich würde dir super gerne das LOG runterladen, ich habe aber keinen Button mehr

[Asgothian]

@michihorn du kannst auch die Datei direkt öffnen

/opt/iobroker/log/iobroker.current.log

A.

[TT-Tom]

@asgothian

Ich nochmal, könnte es auch an der Admin-Oberfläche liegen. Er nutzt noch die alte Oberfläche. Ist bei einigen Adapter jetzt schon Probleme aufgetreten, wenn noch die alte Ansicht aktiv war.

[Thomas Braun]

@tt-tom sagte in Zigbee Update:

könnte es auch an der Admin-Oberfläche liegen.

Ja.

[michihorn]

@asgothian
iobroker.2022-05-20.log.zip

Der LOG Download ist tatsächlich in dem neuen UI sichtbar.
Gruß
M.