NEWS
Temperatur Sensoren + Tür und Fenster Kontakte
-
Hallo zusammen,
aus irgendwelchen unerfindlichen Gründen ist mein Zig-Bee Netz defekt und lässt sich nicht wieder aufbauen.
(Nein, es liegt nicht am defekten Debian 12 Paket)
Es ist von jetzt auf gleich zusammen gebrochen und nichts geht mehr (Sonoff Zig-Bee 3 USB Stick und diverse Aqara Sensoren) Der USB Stick wird noch erkannt, aber ich kann nichts mehr anlernen und die vorhandenen Sensoren stehen auf Disconnected, weiss der Hänker warum, ich komme nicht dahinter. Die Sensoren tuen so als wären sie verbunden und in Reichweite, aber nüschts wird angezeigt.Dieses Netz hat unseren Keller bzw meinen Technikraum überwacht. Diverse Türkontakte für Stromkästen, E3DC Türe Serverschranktüre ect. Ebenfalls wurde die Temperatur im Raum an 4 Stellen überwacht, ebenfalls mit Aqara Sensoren.
Da dies nun nicht mehr möglich ist suche ich nach einem Ersatz System. Ein Hue System ist ebenfalls vorhanden, aber die Sensoren sind mir für diesen Anwendungszweck zu teuer.
Was gibt es ausserhalb von Zig-Bee was einfach nur Temperatur Sensor und Fenster/Türkontakt sein kann?
Ich danke euch.
Lucifor -
@lucifor1976 sagte in Temperatur Sensoren + Tür und Fenster Kontakte:
Die Sensoren tuen so als wären sie verbunden und in Reichweite, aber nüschts wird angezeigt.
bitte mehr Fakten
https://forum.iobroker.net/topic/51555/hinweise-für-gute-forenbeiträge/1hast du mal Sentry deaktiviert?
-
@homoran
HeyJa habe ich, ändert nichts. Aber ich habe hier in diesem Thread nicht mit einem Versuch gerechnet den Fehler zu finden und zu beheben, eher nach Alternativen.
Gibts von Hue nicht einfache Tempsensoren, der Bewegeungssensor kann das ist aber vollkommen oversized. die Türen könnte ich mir noch mit Homematic IP gefallen lassen. Einfache Temp Sensoren gibts ja leider von Homematic nicht.
-
@lucifor1976 sagte in Temperatur Sensoren + Tür und Fenster Kontakte:
Ja habe ich
in der Instanz? nicht global!
war ein Versuch wert
@lucifor1976 sagte in Temperatur Sensoren + Tür und Fenster Kontakte:
nicht mit einem Versuch gerechnet den Fehler zu finden und zu beheben
warum nicht?
ist deine Installation so anders?warum sollte das nicht laufen?
-
Ja, Ich habe Sentry nur für den ZigBee Adapter ausgeschaltet.
Es lief ja, monatelang, von jetzt auf gleich nicht mehr und es sind alle Sensoren ausgefallen.
Ich habe schon die vermutung das der USB-Stick kaputt ist, er wird aber einwandfrei erkannt und nichts meckert das irgendetwas nicht stimmen würde.Alte, nicht mehr eingebundene Sensoren oder nagelneue lassen sich nicht einbinden, das Pairing startet, zählt herunter und wird beendet. Sensoren die gepaired werden sollen, tun so als hätte das geklappt, werden dann aber nicht im Adapter angezeigt, ebensowenig in den Objekten...
Ich fummel schon seit Wochen erfolglos daran rum ..
-
@lucifor1976 im debug-log steht nichts?
-
Ich lads mal hier rein, aber mir sagt das alles nicht so viel...
2023-07-27 17:51:34.000 - [32minfo[39m: zigbee.0 (2775) Got terminate signal TERMINATE_YOURSELF 2023-07-27 17:51:34.001 - [32minfo[39m: zigbee.0 (2775) cleaned everything up... 2023-07-27 17:51:34.001 - [32minfo[39m: zigbee.0 (2775) Zigbee: disabling joining new devices. 2023-07-27 17:51:34.094 - [32minfo[39m: host.SmartHomeServer stopInstance system.adapter.zigbee.0 send kill signal 2023-07-27 17:51:34.501 - [32minfo[39m: zigbee.0 (2775) terminating 2023-07-27 17:51:34.502 - [32minfo[39m: zigbee.0 (2775) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2023-07-27 17:51:35.130 - [32minfo[39m: host.SmartHomeServer instance system.adapter.zigbee.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2023-07-27 17:51:37.196 - [32minfo[39m: host.SmartHomeServer instance system.adapter.zigbee.0 started with pid 12892 2023-07-27 17:51:37.902 - [34mdebug[39m: zigbee.0 (12892) Redis Objects: Use Redis connection: 0.0.0.0:9001 2023-07-27 17:51:37.943 - [34mdebug[39m: zigbee.0 (12892) Objects client ready ... initialize now 2023-07-27 17:51:37.943 - [34mdebug[39m: zigbee.0 (12892) Objects create System PubSub Client 2023-07-27 17:51:37.944 - [34mdebug[39m: zigbee.0 (12892) Objects create User PubSub Client 2023-07-27 17:51:38.029 - [32minfo[39m: zigbee.0 (12892) Sets unsupported 2023-07-27 17:51:38.030 - [32minfo[39m: zigbee.0 (12892) Sets unsupported 2023-07-27 17:51:38.030 - [34mdebug[39m: zigbee.0 (12892) Objects client initialize lua scripts 2023-07-27 17:51:38.032 - [34mdebug[39m: zigbee.0 (12892) Objects connected to redis: 0.0.0.0:9001 2023-07-27 17:51:38.033 - [35msilly[39m: zigbee.0 (12892) redis psubscribe cfg.o.system.user.* 2023-07-27 17:51:38.066 - [35msilly[39m: zigbee.0 (12892) redis psubscribe cfg.o.enum.* 2023-07-27 17:51:38.068 - [35msilly[39m: zigbee.0 (12892) objectDB connected 2023-07-27 17:51:38.069 - [34mdebug[39m: zigbee.0 (12892) Redis States: Use Redis connection: 0.0.0.0:9000 2023-07-27 17:51:38.098 - [34mdebug[39m: zigbee.0 (12892) States create System PubSub Client 2023-07-27 17:51:38.098 - [34mdebug[39m: zigbee.0 (12892) States create User PubSub Client 2023-07-27 17:51:38.190 - [34mdebug[39m: zigbee.0 (12892) States connected to redis: 0.0.0.0:9000 2023-07-27 17:51:38.191 - [35msilly[39m: zigbee.0 (12892) statesDB connected 2023-07-27 17:51:38.412 - [34mdebug[39m: zigbee.0 (12892) Plugin sentry Do not initialize Plugin (enabled=false) 2023-07-27 17:51:38.415 - [34mdebug[39m: zigbee.0 (12892) Plugin sentry destroyed because not initialized correctly 2023-07-27 17:51:38.467 - [32minfo[39m: zigbee.0 (12892) starting. Version 1.8.10 in /opt/iobroker/node_modules/iobroker.zigbee, node: v16.20.1, js-controller: 4.0.23 2023-07-27 17:51:38.481 - [34mdebug[39m: zigbee.0 (12892) Using zigbee-herdsman with settings: {"network":{"panID":6754,"extendedPanID":[221,221,221,221,221,221,221,221],"channelList":[11],"networkKey":[1,3,5,7,9,11,13,15,0,2,4,6,8,10,12,13]},"databasePath":"/opt/iobroker/iobroker-data/zigbee_0/shepherd.db","backupPath":"/opt/iobroker/iobroker-data/zigbee_0/nvbackup.json","serialPort":{"baudRate":115200,"rtscts":false,"path":"/dev/ttyUSB0","adapter":"zstack"},"adapter":{"forceStartWithInconsistentAdapterConfiguration":false}} 2023-07-27 17:51:38.500 - [32minfo[39m: zigbee.0 (12892) delete old Backup files. keep only last 10 2023-07-27 17:51:38.501 - [32minfo[39m: zigbee.0 (12892) Starting Zigbee npm ... 2023-07-27 17:51:38.501 - [34mdebug[39m: zigbee.0 (12892) Starting zigbee-herdsman... 2023-07-27 17:51:38.606 - [35msilly[39m: zigbee.0 (12892) States system redis pmessage system.adapter.zigbee.0.logLevel/system.adapter.zigbee.0.logLevel:{"val":"silly","ack":true,"ts":1690473098559,"q":0,"from":"system.adapter.zigbee.0","lc":1689955089644} 2023-07-27 17:51:38.630 - [32minfo[39m: zigbee.0 (12892) Installed Version: iobroker.zigbee@1.8.10 2023-07-27 17:51:38.631 - [34mdebug[39m: zigbee.0 (12892) Backup /opt/iobroker/iobroker-data/zigbee_0/backup_2023_07_27-17_51_38.tar.gz success 2023-07-27 17:51:38.675 - [35msilly[39m: zigbee.0 (12892) States user redis pmessage zigbee.0.*/zigbee.0.info.connection:{"val":false,"ack":true,"ts":1690473098674,"q":0,"from":"system.adapter.zigbee.0","user":"system.user.admin","lc":1690473098674} 2023-07-27 17:51:38.862 - [34mdebug[39m: zigbee.0 (12892) zigbee-herdsman started 2023-07-27 17:51:38.863 - [32minfo[39m: zigbee.0 (12892) Coordinator firmware version: {"type":"zStack3x0","meta":{"transportrev":2,"product":1,"majorrel":2,"minorrel":7,"maintrel":1,"revision":20210708}} 2023-07-27 17:51:38.867 - [34mdebug[39m: zigbee.0 (12892) Zigbee network parameters: panID=6754 channel=11 extendedPanID=c379b826004b1200 2023-07-27 17:51:38.867 - [32minfo[39m: zigbee.0 (12892) Unable to disable LED, unsupported function. 2023-07-27 17:51:38.868 - [32minfo[39m: zigbee.0 (12892) --> transmitPower : normal 2023-07-27 17:51:38.871 - [32minfo[39m: zigbee.0 (12892) Currently 1 devices are joined: 2023-07-27 17:51:38.871 - [34mdebug[39m: zigbee.0 (12892) DeviceAvailability:Publish available for 0x00158d0008948298 = true 2023-07-27 17:51:38.873 - [34mdebug[39m: zigbee.0 (12892) DeviceAvailability:Publish LQ for 0x00158d0008948298 = 10 2023-07-27 17:51:38.874 - [34mdebug[39m: zigbee.0 (12892) DeviceConfigure:DeviceConfigure 0x00158d0008948298 lumi.sensor_magnet.aq2 not needed 2023-07-27 17:51:38.875 - [34mdebug[39m: zigbee.0 (12892) New device event: {"type":"device","device":{"_events":{},"_eventsCount":0,"_maxListeners":100,"ID":2,"_type":"EndDevice","_ieeeAddr":"0x00158d0008948298","_networkAddress":53583,"_manufacturerID":4151,"_endpoints":[{"_events":{},"_eventsCount":0,"_maxListeners":100,"ID":1,"profileID":260,"deviceID":24321,"inputClusters":[0,3,65535,6],"outputClusters":[0,4,65535],"deviceNetworkAddress":53583,"deviceIeeeAddress":"0x00158d0008948298","clusters":{"genBasic":{"attributes":{"65281":{"1":3065,"3":28,"4":17320,"5":49,"6":[0,1],"10":26140,"100":1},"modelId":"lumi.sensor_magnet.aq2","appVersion":3,"manufacturerName":"LUMI"}},"genOnOff":{"attributes":{"onOff":1}}},"_binds":[],"_configuredReportings":[],"meta":{},"pendingRequests":[]}],"_manufacturerName":"LUMI","_powerSource":"Battery","_modelID":"lumi.sensor_magnet.aq2","_applicationVersion":3,"_interviewCompleted":true,"_interviewing":false,"_skipDefaultResponse":false,"_skipTimeResponse":false,"meta":{"configured":-1496948516},"_lastSeen":1683903720083,"_defaultSendRequestWhen":"immediate"},"mapped":{"zigbeeModel":["lumi.sensor_magnet.aq2"],"model":"MCCGQ11LM","vendor":"Xiaomi","description":"Aqara door & window contact sensor","meta":{"battery":{"voltageToPercentage":"3V_2850_3000"}},"fromZigbee":[{"cluster":"genBasic","type":["attributeReport","readResponse"]},{"cluster":"genOnOff","type":["attributeReport","readResponse"]}],"toZigbee":[{"key":["scene_store"]},{"key":["scene_recall"]},{"key":["scene_add"]},{"key":["scene_remove"]},{"key":["scene_remove_all"]},{"key":["read"]},{"key":["write"]},{"key":["command"]},{"key":["reset"]}],"exposes":[{"type":"numeric","name":"battery","property":"battery","access":1,"unit":"%","description":"Remaining battery in %","value_min":0,"value_max":100},{"type":"binary","name":"contact","property":"contact","access":1,"value_on":false,"value_off":true,"description":"Indicates if the contact is closed (= true) or open (= false)"},{"type":"numeric","name":"device_temperature","property":"device_temperature","access":1,"unit":"°C","description":"Temperature of the device"},{"type":"numeric","name":"voltage","property":"voltage","access":1,"unit":"mV","description":"Voltage of the battery in millivolts"},{"type":"numeric","name":"power_outage_count","property":"power_outage_count","access":1,"description":"Number of power outages"},{"type":"numeric","name":"linkquality","property":"linkquality","access":1,"unit":"lqi","description":"Link quality (signal strength)","value_min":0,"value_max":255}],"options":[{"type":"numeric","name":"device_temperature_calibration","property":"device_temperature_calibration","access":2,"description":"Calibrates the device_temperature value (absolute offset), takes into effect on next report of device."}]},"name":"0x00158d0008948298"} 2023-07-27 17:51:38.875 - [32minfo[39m: zigbee.0 (12892) 0x00158d0008948298 (addr 53583): MCCGQ11LM - Xiaomi Aqara door & window contact sensor (EndDevice) 2023-07-27 17:51:38.875 - [32minfo[39m: zigbee.0 (12892) Zigbee started 2023-07-27 17:51:38.879 - [34mdebug[39m: zigbee.0 (12892) getGroups result: {} 2023-07-27 17:51:38.880 - [34mdebug[39m: zigbee.0 (12892) DeviceAvailability:register device Ping for "0x00158d0008948298" 2023-07-27 17:51:38.882 - [35msilly[39m: zigbee.0 (12892) States user redis pmessage zigbee.0.*/zigbee.0.info.connection:{"val":true,"ack":true,"ts":1690473098880,"q":0,"from":"system.adapter.zigbee.0","user":"system.user.admin","lc":1690473098880} 2023-07-27 17:51:38.914 - [35msilly[39m: zigbee.0 (12892) States user redis pmessage zigbee.0.*/zigbee.0.info.undefinedDevices:{"val":"{}","ack":true,"ts":1690473098883,"q":0,"from":"system.adapter.zigbee.0","user":"system.user.admin","lc":1687002496381}
und noch mehr davon ...
zigbee.0 20697 2023-07-27 18:01:04.298 debug DeviceAvailability:Publish available for 0x00158d0008948298 = false zigbee.0 20697 2023-07-27 18:01:04.298 debug DeviceAvailability:Non-pingable device 0x00158d0008948298 lumi.sensor_magnet.aq2 was last seen '6569944.215' seconds ago. zigbee.0 20697 2023-07-27 18:00:05.301 debug DeviceAvailability:Publish LQ for 0x00158d0008948298 = 10 zigbee.0 20697 2023-07-27 18:00:05.301 debug DeviceAvailability:Publish available for 0x00158d0008948298 = true zigbee.0 20697 2023-07-27 18:00:04.306 debug DeviceAvailability:register device Ping for "0x00158d0008948298" zigbee.0 20697 2023-07-27 18:00:04.305 debug getGroups result: {} zigbee.0 20697 2023-07-27 18:00:04.301 info Zigbee started zigbee.0 20697 2023-07-27 18:00:04.301 info 0x00158d0008948298 (addr 53583): MCCGQ11LM - Xiaomi Aqara door & window contact sensor (EndDevice) zigbee.0 20697 2023-07-27 18:00:04.301 debug New device event: {"type":"device","device":{"_events":{},"_eventsCount":0,"_maxListeners":100,"ID":2,"_type":"EndDevice","_ieeeAddr":"0x00158d0008948298","_networkAddress":53583,"_manufacturerID":4151,"_endpoints":[{"_events":{},"_eventsCount":0,"_maxListeners":100,"ID":1,"profileID":260,"deviceID":24321,"inputClusters":[0,3,65535,6],"outputClusters":[0,4,65535],"deviceNetworkAddress":53583,"deviceIeeeAddress":"0x00158d0008948298","clusters":{"genBasic":{"attributes":{"65281":{"1":3065,"3":28,"4":17320,"5":49,"6":[0,1],"10":26140,"100":1},"modelId":"lumi.sensor_magnet.aq2","appVersion":3,"manufacturerName":"LUMI"}},"genOnOff":{"attributes":{"onOff":1}}},"_binds":[],"_configuredReportings":[],"meta":{},"pendingRequests":[]}],"_manufacturerName":"LUMI","_powerSource":"Battery","_modelID":"lumi.sensor_magnet.aq2","_applicationVersion":3,"_interviewCompleted":true,"_interviewing":false,"_skipDefaultResponse":false,"_skipTimeResponse":false,"meta":{"configured":-1496948516},"_lastSeen":1683903720083,"_defaultSendRequestWhen":"immediate"},"mapped":{"zigbeeModel":["lumi.sensor_magnet.aq2"],"model":"MCCGQ11LM","vendor":"Xiaomi","description":"Aqara door & window contact sensor","meta":{"battery":{"voltageToPercentage":"3V_2850_3000"}},"fromZigbee":[{"cluster":"genBasic","type":["attributeReport","readResponse"]},{"cluster":"genOnOff","type":["attributeReport","readResponse"]}],"toZigbee":[{"key":["scene_store"]},{"key":["scene_recall"]},{"key":["scene_add"]},{"key":["scene_remove"]},{"key":["scene_remove_all"]},{"key":["read"]},{"key":["write"]},{"key":["command"]},{"key":["reset"]}],"exposes":[{"type":"numeric","name":"battery","property":"battery","access":1,"unit":"%","description":"Remaining battery in %","value_min":0,"value_max":100},{"type":"binary","name":"contact","property":"contact","access":1,"value_on":false,"value_off":true,"description":"Indicates if the contact is closed (= true) or open (= false)"},{"type":"numeric","name":"device_temperature","property":"device_temperature","access":1,"unit":"°C","description":"Temperature of the device"},{"type":"numeric","name":"voltage","property":"voltage","access":1,"unit":"mV","description":"Voltage of the battery in millivolts"},{"type":"numeric","name":"power_outage_count","property":"power_outage_count","access":1,"description":"Number of power outages"},{"type":"numeric","name":"linkquality","property":"linkquality","access":1,"unit":"lqi","description":"Link quality (signal strength)","value_min":0,"value_max":255}],"options":[{"type":"numeric","name":"device_temperature_calibration","property":"device_temperature_calibration","access":2,"description":"Calibrates the device_temperature value (absolute offset), takes into effect on next report of device."}]},"name":"0x00158d0008948298"} zigbee.0 20697 2023-07-27 18:00:04.300 debug DeviceConfigure:DeviceConfigure 0x00158d0008948298 lumi.sensor_magnet.aq2 not needed zigbee.0 20697 2023-07-27 18:00:04.298 debug DeviceAvailability:Publish LQ for 0x00158d0008948298 = 10 zigbee.0 20697 2023-07-27 18:00:04.297 debug DeviceAvailability:Publish available for 0x00158d0008948298 = true zigbee.0 20697 2023-07-27 18:00:04.297 info Currently 1 devices are joined: zigbee.0 20697 2023-07-27 18:00:04.294 info --> transmitPower : normal zigbee.0 20697 2023-07-27 18:00:04.293 info Unable to disable LED, unsupported function. zigbee.0 20697 2023-07-27 18:00:04.293 debug Zigbee network parameters: panID=6754 channel=11 extendedPanID=c379b826004b1200 zigbee.0 20697 2023-07-27 18:00:04.288 info Coordinator firmware version: {"type":"zStack3x0","meta":{"transportrev":2,"product":1,"majorrel":2,"minorrel":7,"maintrel":1,"revision":20210708}} zigbee.0 20697 2023-07-27 18:00:04.288 debug zigbee-herdsman started zigbee.0 20697 2023-07-27 18:00:04.070 debug Backup /opt/iobroker/iobroker-data/zigbee_0/backup_2023_07_27-18_00_03.tar.gz success zigbee.0 20697 2023-07-27 18:00:04.067 info Installed Version: iobroker.zigbee@1.8.10 zigbee.0 20697 2023-07-27 18:00:03.941 debug Starting zigbee-herdsman... zigbee.0 20697 2023-07-27 18:00:03.941 info Starting Zigbee npm ... zigbee.0 20697 2023-07-27 18:00:03.940 info delete old Backup files. keep only last 10 zigbee.0 20697 2023-07-27 18:00:03.922 debug Using zigbee-herdsman with settings: {"network":{"panID":6754,"extendedPanID":[221,221,221,221,221,221,221,221],"channelList":[11],"networkKey":[1,3,5,7,9,11,13,15,0,2,4,6,8,10,12,13]},"databasePath":"/opt/iobroker/iobroker-data/zigbee_0/shepherd.db","backupPath":"/opt/iobroker/iobroker-data/zigbee_0/nvbackup.json","serialPort":{"baudRate":115200,"rtscts":false,"path":"/dev/ttyUSB0","adapter":"zstack"},"adapter":{"forceStartWithInconsistentAdapterConfiguration":false}} zigbee.0 20697 2023-07-27 18:00:03.908 info starting. Version 1.8.10 in /opt/iobroker/node_modules/iobroker.zigbee, node: v16.20.1, js-controller: 4.0.23 zigbee.0 20697 2023-07-27 18:00:03.857 debug Plugin sentry destroyed because not initialized correctly zigbee.0 20697 2023-07-27 18:00:03.855 debug Plugin sentry Do not initialize Plugin (enabled=false) zigbee.0 20697 2023-07-27 18:00:03.551 debug States connected to redis: 0.0.0.0:9000 zigbee.0 20697 2023-07-27 18:00:03.443 debug States create User PubSub Client zigbee.0 20697 2023-07-27 18:00:03.442 debug States create System PubSub Client zigbee.0 20697 2023-07-27 18:00:03.374 debug Redis States: Use Redis connection: 0.0.0.0:9000 zigbee.0 20697 2023-07-27 18:00:03.340 debug Objects connected to redis: 0.0.0.0:9001 zigbee.0 20697 2023-07-27 18:00:03.339 debug Objects client initialize lua scripts zigbee.0 20697 2023-07-27 18:00:03.338 info Sets unsupported zigbee.0 20697 2023-07-27 18:00:03.338 info Sets unsupported zigbee.0 20697 2023-07-27 18:00:03.243 debug Objects create User PubSub Client zigbee.0 20697 2023-07-27 18:00:03.243 debug Objects create System PubSub Client zigbee.0 20697 2023-07-27 18:00:03.242 debug Objects client ready ... initialize now zigbee.0 20697 2023-07-27 18:00:03.198 debug Redis Objects: Use Redis connection: 0.0.0.0:9001 zigbee.0 12892 2023-07-27 17:59:59.857 info Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason zigbee.0 12892 2023-07-27 17:59:59.856 info terminating zigbee.0 12892 2023-07-27 17:59:59.356 info Zigbee: disabling joining new devices. zigbee.0 12892 2023-07-27 17:59:59.356 info cleaned everything up... zigbee.0 12892 2023-07-27 17:59:59.356 info Got terminate signal TERMINATE_YOURSELF zigbee.0 12892 2023-07-27 17:59:59.355 silly States system redis pmessage system.adapter.zigbee.0.sigKill/system.adapter.zigbee.0.sigKill:{"val":-1,"ack":false,"ts":1690473599354,"q":0,"from":"system.host.SmartHomeServer","lc":1690473599354} zigbee.0 12892 2023-07-27 17:59:38.875 debug DeviceAvailability:Non-pingable device 0x00158d0008948298 lumi.sensor_magnet.aq2 was last seen '6569858.791' seconds ago. zigbee.0 12892 2023-07-27 17:58:38.874 debug DeviceAvailability:Non-pingable device 0x00158d0008948298 lumi.sensor_magnet.aq2 was last seen '6569798.791' seconds ago. zigbee.0 12892 2023-07-27 17:57:38.874 debug DeviceAvailability:Non-pingable device 0x00158d0008948298 lumi.sensor_magnet.aq2 was last seen '6569738.791' seconds ago. zigbee.0 12892 2023-07-27 17:56:38.874 debug DeviceAvailability:Non-pingable device 0x00158d0008948298 lumi.sensor_magnet.aq2 was last seen '6569678.791' seconds ago. zigbee.0 12892 2023-07-27 17:56:24.014 silly sendTo "getBinding" to system.adapter.admin.0 from system.adapter.zigbee.0 zigbee.0 12892 2023-07-27 17:56:24.014 debug getBinding result: [] zigbee.0 12892 2023-07-27 17:56:23.973 silly sendTo "getExclude" to system.adapter.admin.0 from system.adapter.zigbee.0 zigbee.0 12892 2023-07-27 17:56:23.973 silly States user redis pmessage zigbee.0.*/zigbee.0.exclude.all:{"val":"[]","ack":true,"ts":1690473383972,"q":0,"from":"system.adapter.zigbee.0","user":"system.user.admin","lc":1687002459907} zigbee.0 12892 2023-07-27 17:56:23.971 debug getExclude result: [] zigbee.0 12892 2023-07-27 17:56:23.893 silly States system redis pmessage io.messagebox.system.adapter.zigbee.0/io.messagebox.system.adapter.zigbee.0:{"command":"getBinding","message":{},"from":"system.adapter.admin.0","callback":{"message":{},"id":215,"ack":false,"time":1690473383890},"_id":75754805} zigbee.0 12892 2023-07-27 17:56:23.891 silly States system redis pmessage io.messagebox.system.adapter.zigbee.0/io.messagebox.system.adapter.zigbee.0:{"command":"getExclude","message":{},"from":"system.adapter.admin.0","callback":{"message":{},"id":214,"ack":false,"time":1690473383890},"_id":75754804} zigbee.0 12892 2023-07-27 17:56:23.872 silly sendTo "getDevices" to system.adapter.admin.0 from system.adapter.zigbee.0
-
@lucifor1976 ich sehe da auf Anhieb auch nichts. liegt aber wahrscheinlich daran, dass ich kein Zigbee habe.
Vielleicht kann @arteck da helfen. -
@lucifor1976 stell das Debug erstmal aus..
dann adapter neu starten.. und das ganze Posten
alternative : zwave ..da kostet ein Sensor aber direkt das 10fache
@Homoran bitte lass den zigbee Adapter nicht auf Debug stellen.. das ist dann die aller letzte Möglichkeit..
die Elevated funkttion ist da besser https://github.com/ioBroker/ioBroker.zigbee/wiki/debug-messages-with-zigbee.0.info.debugmessages -
Gesagt, getan. Das kommt dabei heraus:
zigbee.0 27625 2023-07-28 19:52:21.420 info Zigbee started zigbee.0 27625 2023-07-28 19:52:21.419 info 0x00158d0008948298 (addr 53583): MCCGQ11LM - Xiaomi Aqara door & window contact sensor (EndDevice) zigbee.0 27625 2023-07-28 19:52:21.413 info Currently 1 devices are joined: zigbee.0 27625 2023-07-28 19:52:21.408 info --> transmitPower : normal zigbee.0 27625 2023-07-28 19:52:21.408 info Unable to disable LED, unsupported function. zigbee.0 27625 2023-07-28 19:52:21.402 info Coordinator firmware version: {"type":"zStack3x0","meta":{"transportrev":2,"product":1,"majorrel":2,"minorrel":7,"maintrel":1,"revision":20210708}} zigbee.0 27625 2023-07-28 19:52:21.134 info Installed Version: iobroker.zigbee@1.8.10 zigbee.0 27625 2023-07-28 19:52:21.006 info Starting Zigbee npm ... zigbee.0 27625 2023-07-28 19:52:21.005 info delete old Backup files. keep only last 10 zigbee.0 27625 2023-07-28 19:52:20.974 info starting. Version 1.8.10 in /opt/iobroker/node_modules/iobroker.zigbee, node: v16.20.1, js-controller: 4.0.23 zigbee.0 27625 2023-07-28 19:52:20.567 info Sets unsupported zigbee.0 27625 2023-07-28 19:52:20.566 info Sets unsupported zigbee.0 20697 2023-07-28 19:52:16.917 info Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason zigbee.0 20697 2023-07-28 19:52:16.916 info terminating
Wenn ich nun den letzten verbleibenden Sensor löschen möchte passiert das:
Failed to remove Error: AREQ - ZDO - mgmtLeaveRsp after 10000ms at Timeout._onTimeout (/opt/iobroker/node_modules/zigbee-herdsman/dist/utils/waitress.js:37:35) at listOnTimeout (node:internal/timers:559:17) at processTimers (node:internal/timers:502:7)
Ich danke euch schon mal für eure Hilfe
-
Nochmal ich
Ich hab nun den Adapter gelöscht, die verbleibenden Geräte zwangs gelöscht. Objekte gelöscht.
Nüx, garnüx, lässt sich Pairen, obwohl die Sensoren sofort sagen sie seien gepaired...
32244 2023-07-28 20:38:37.109 info Zigbee: stop joining 32244 2023-07-28 20:36:35.814 info Zigbee: allowing new devices to join. 32244 2023-07-28 20:36:31.973 info List of port: [{"path":"/dev/ttyUSB0","manufacturer":"Silicon Labs","serialNumber":"0001","pnpId":"usb-Silicon_Labs_Sonoff_Zigbee_3.0_USB_Dongle_Plus_0001-if00-port0","vendorId":"10c4","productId":"ea60"},{"path":"/dev/ttyS0"},{"path":"/dev/ttyS1"},{"path":"/dev/ttyS2"},{"path":"/dev/ttyS3"}] 32244 2023-07-28 20:36:15.064 info Zigbee started
-
@lucifor1976 Es gibt jetzt neue Tür-,Fensterkontakte von AVM und Philips HUE.
Dann könnte man doch über den HUE oder Fritzbox Adapter den Status auswerten und auf Zigbee komplett verzichten oder? -
@werner2000x sagte in Temperatur Sensoren + Tür und Fenster Kontakte:
HUE
hue = zigbee
die von avm laufen meine ich über DECT