RTCGQ11LM Occupancy timeout

[wolfgangkt]

seit der V1.8.16 wird der Occupancy timeout bei den Bewegungsmelder RTCGQ11LM ignoriert und der Standart von 60 sec. verwendet.

[arteck]

so komm nochmal

[Ilovegym66]

Adapter startet... aber dann.. ein Problem mit elmVal... ?

` 2023-07-31 13:42:41.769 - error: zigbee.0 (3450216) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). 2023-07-31 13:42:41.769 - error: zigbee.0 (3450216) unhandled promise rejection: Cannot read properties of undefined (reading 'elmVal') 2023-07-31 13:42:41.770 - error: zigbee.0 (3450216) TypeError: Cannot read properties of undefined (reading 'elmVal') at Zigbee.onZigbeeEvent (/opt/iobroker/node_modules/iobroker.zigbee/main.js:489:47) 2023-07-31 13:42:41.770 - error: zigbee.0 (3450216) Cannot read properties of undefined (reading 'elmVal') 2023-07-31 13:42:41.786 - info: zigbee.0 (3450216) cleaned everything up... 2023-07-31 13:42:41.846 - info: notification-manager.0 (3199530) New notification on "iobrokerS2" detected 2023-07-31 13:42:41.846 - debug: notification-manager.0 (3199530) Request notifications from "system.host.iobrokerS2" 2023-07-31 13:42:41.884 - debug: notification-manager.0 (3199530) Received notifications from "system.host.iobrokerS2": {} 2023-07-31 13:42:42.140 - info: zigbee.0 (3450216) Zigbee: disabling joining new devices. 2023-07-31 13:42:42.296 - info: zigbee.0 (3450216) terminating 2023-07-31 13:42:42.297 - warn: zigbee.0 (3450216) Terminated (UNCAUGHT_EXCEPTION): Without reason 2023-07-31 13:42:41.769 - error: zigbee.0 (3450216) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). 2023-07-31 13:42:41.769 - error: zigbee.0 (3450216) unhandled promise rejection: Cannot read properties of undefined (reading 'elmVal') 2023-07-31 13:42:41.770 - error: zigbee.0 (3450216) TypeError: Cannot read properties of undefined (reading 'elmVal') at Zigbee.onZigbeeEvent (/opt/iobroker/node_modules/iobroker.zigbee/main.js:489:47) 2023-07-31 13:42:41.770 - error: zigbee.0 (3450216) Cannot read properties of undefined (reading 'elmVal') 2023-07-31 13:42:41.786 - info: zigbee.0 (3450216) cleaned everything up... 2023-07-31 13:42:41.846 - info: notification-manager.0 (3199530) New notification on "iobrokerS2" detected 2023-07-31 13:42:41.846 - debug: notification-manager.0 (3199530) Request notifications from "system.host.iobrokerS2" 2023-07-31 13:42:41.884 - debug: notification-manager.0 (3199530) Received notifications from "system.host.iobrokerS2": {} 2023-07-31 13:42:42.140 - info: zigbee.0 (3450216) Zigbee: disabling joining new devices. 2023-07-31 13:42:42.296 - info: zigbee.0 (3450216) terminating 2023-07-31 13:42:42.297 - warn: zigbee.0 (3450216) Terminated (UNCAUGHT_EXCEPTION): Without reason 2023-07-31 13:42:42.948 - error: host.iobrokerS2 Caught by controller[0]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason: 2023-07-31 13:42:42.949 - error: host.iobrokerS2 Caught by controller[1]: TypeError: Cannot read properties of undefined (reading 'elmVal') 2023-07-31 13:42:42.949 - error: host.iobrokerS2 Caught by controller[1]: at Zigbee.onZigbeeEvent (/opt/iobroker/node_modules/iobroker.zigbee/main.js:489:47) 2023-07-31 13:42:42.949 - error: host.iobrokerS2 instance system.adapter.zigbee.0 terminated with code 6 (UNCAUGHT_EXCEPTION) 2023-07-31 13:42:42.949 - info: host.iobrokerS2 Restart adapter system.adapter.zigbee.0 because enabled 2023-07-31 13:42:42.948 - error: host.iobrokerS2 Caught by controller[0]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason: 2023-07-31 13:42:42.949 - error: host.iobrokerS2 Caught by controller[1]: TypeError: Cannot read properties of undefined (reading 'elmVal') 2023-07-31 13:42:42.949 - error: host.iobrokerS2 Caught by controller[1]: at Zigbee.onZigbeeEvent (/opt/iobroker/node_modules/iobroker.zigbee/main.js:489:47) 2023-07-31 13:42:42.949 - error: host.iobrokerS2 instance system.adapter.zigbee.0 terminated with code 6 (UNCAUGHT_EXCEPTION) 2023-07-31 13:42:42.949 - info: host.iobrokerS2 Restart adapter system.adapter.zigbee.0 because enabled

`

[arteck]

guckmal jetzt .. die Daten sind manchmal da manchmal nicht.. und wenn nicht dann knalts

[Ilovegym66]

leider startet er jetzt gar nicht, hab ihn gestoppt, gewartet... dann ein iob upload zigbee ... gewartet... gestartet... hmpf:

` 2023-07-31 14:23:12.654 - info: host.iobrokerS2 "system.adapter.zigbee.0" enabled 2023-07-31 14:23:12.689 - info: host.iobrokerS2 instance system.adapter.zigbee.0 started with pid 3501167 2023-07-31 14:23:12.806 - error: host.iobrokerS2 Caught by controller[0]: /opt/iobroker/node_modules/iobroker.zigbee/main.js:497 2023-07-31 14:23:12.806 - error: host.iobrokerS2 Caught by controller[0]: if (key == 65281 && value[1] != undefined) {) { 2023-07-31 14:23:12.806 - error: host.iobrokerS2 Caught by controller[0]: ^ 2023-07-31 14:23:12.806 - error: host.iobrokerS2 Caught by controller[0]: SyntaxError: Unexpected token ')' 2023-07-31 14:23:12.806 - error: host.iobrokerS2 Caught by controller[0]: at internalCompileFunction (node:internal/vm:73:18) 2023-07-31 14:23:12.806 - error: host.iobrokerS2 Caught by controller[0]: at wrapSafe (node:internal/modules/cjs/loader:1178:20) 2023-07-31 14:23:12.807 - error: host.iobrokerS2 Caught by controller[0]: at Module._compile (node:internal/modules/cjs/loader:1220:27) 2023-07-31 14:23:12.807 - error: host.iobrokerS2 Caught by controller[0]: at Module._extensions..js (node:internal/modules/cjs/loader:1310:10) 2023-07-31 14:23:12.807 - error: host.iobrokerS2 Caught by controller[0]: at Module.load (node:internal/modules/cjs/loader:1119:32) 2023-07-31 14:23:12.807 - error: host.iobrokerS2 Caught by controller[0]: at Module._load (node:internal/modules/cjs/loader:960:12) 2023-07-31 14:23:12.807 - error: host.iobrokerS2 Caught by controller[0]: at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:81:12) 2023-07-31 14:23:12.807 - error: host.iobrokerS2 Caught by controller[0]: at node:internal/main/run_main_module:23:47 2023-07-31 14:23:12.807 - error: host.iobrokerS2 Caught by controller[0]: Node.js v18.17.0 2023-07-31 14:23:12.807 - error: host.iobrokerS2 instance system.adapter.zigbee.0 terminated with code 1 (JS_CONTROLLER_STOPPED) 2023-07-31 14:23:12.807 - info: host.iobrokerS2 Restart adapter system.adapter.zigbee.0 because enabled 2023-07-31 14:23:18.228 - info: influxdb.0 (3463842) Store 6287 buffered influxDB history points

`

[arteck]

sry fehler meinerseits... jetzt

[wolfgangkt]

bis jetzt siehts es gut aus

[Ilovegym66]

hat erst schoen gestartet... aber dann...

` 2023-07-31 14:30:16.007 - info: zigbee.0 (3509883) starting. Version 1.8.18 (non-npm: ioBroker/ioBroker.zigbee) in /opt/iobroker/node_modules/iobroker.zigbee, node: v18.17.0, js-controller: 5.0.11 2023-07-31 14:30:16.073 - info: zigbee.0 (3509883) delete old Backup files. keep only last 10 2023-07-31 14:30:16.074 - info: zigbee.0 (3509883) Starting Zigbee npm ... 2023-07-31 14:30:16.125 - info: host.iobrokerS2 instance system.adapter.meteoalarm.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2023-07-31 14:30:16.199 - info: zigbee.0 (3509883) Installed Version: ioBroker/ioBroker.zigbee 2023-07-31 14:30:17.679 - info: zigbee.0 (3509883) Coordinator firmware version: {"type":"zStack3x0","meta":{"transportrev":2,"product":1,"majorrel":2,"minorrel":7,"maintrel":1,"revision":20220219}} 2023-07-31 14:30:17.686 - info: zigbee.0 (3509883) Unable to disable LED, unsupported function. 2023-07-31 14:30:17.694 - info: zigbee.0 (3509883) --> transmitPower : high 2023-07-31 14:30:17.831 - info: zigbee.0 (3509883) Currently 226 devices are joined: 2023-07-31 14:30:17.679 - info: zigbee.0 (3509883) Coordinator firmware version: {"type":"zStack3x0","meta":{"transportrev":2,"product":1,"majorrel":2,"minorrel":7,"maintrel":1,"revision":20220219}} 2023-07-31 14:30:17.686 - info: zigbee.0 (3509883) Unable to disable LED, unsupported function. 2023-07-31 14:30:17.694 - info: zigbee.0 (3509883) --> transmitPower : high 2023-07-31 14:30:17.831 - info: zigbee.0 (3509883) Currently 226 devices are joined: 2023-07-31 14:30:18.200 - info: zigbee.0 (3509883) 0x00158d00011083e8 (addr 50113): MFKZQ01LM - Xiaomi Mi/Aqara smart home cube (EndDevice) 2023-07-31 14:30:18.207 - info: zigbee.0 (3509883) 0x00158d00042adb71 (addr 22449): SJCGQ11LM - Xiaomi Aqara water leak sensor (EndDevice) 2023-07-31 14:30:18.208 - info: zigbee.0 (3509883) 0x00158d00022daa58 (addr 24588): MCCGQ11LM - Xiaomi Aqara door & window contact sensor (EndDevice) 2023-07-31 14:30:18.209 - info: zigbee.0 (3509883) 0x00158d00022efe8a (addr 13954): MCCGQ11LM - Xiaomi Aqara door & window contact sensor (EndDevice) 2023-07-31 14:30:18.210 - info: zigbee.0 (3509883) 0x00158d0005d10648 (addr 10084): RTCGQ11LM - Xiaomi Aqara human body movement and illuminance sensor (EndDevice) 2023-07-31 14:30:18.210 - info: zigbee.0 (3509883) 0x00158d0002325709 (addr 35136): WSDCGQ11LM - Xiaomi Aqara temperature, humidity and pressure sensor (EndDevice) 2023-07-31 14:30:18.211 - info: zigbee.0 (3509883) 0x00158d00020edd4a (addr 8213): WSDCGQ01LM - Xiaomi MiJia temperature & humidity sensor (EndDevice) 2023-07-31 14:30:18.212 - info: zigbee.0 (3509883) 0x00158d00022efe3a (addr 44959): MCCGQ11LM - Xiaomi Aqara door & window contact sensor (EndDevice) 2023-07-31 14:30:57.981 - error: zigbee.0 (3509883) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). 2023-07-31 14:30:57.981 - error: zigbee.0 (3509883) unhandled promise rejection: Cannot read properties of undefined (reading 'elmVal') 2023-07-31 14:30:57.982 - error: zigbee.0 (3509883) TypeError: Cannot read properties of undefined (reading 'elmVal') at Zigbee.onZigbeeEvent (/opt/iobroker/node_modules/iobroker.zigbee/main.js:493:51) 2023-07-31 14:30:57.982 - error: zigbee.0 (3509883) Cannot read properties of undefined (reading 'elmVal') 2023-07-31 14:30:58.073 - info: zigbee.0 (3509883) cleaned everything up... 2023-07-31 14:30:58.451 - info: notification-manager.0 (3467301) New notification on "iobrokerS2" detected 2023-07-31 14:30:58.452 - debug: notification-manager.0 (3467301) Request notifications from "system.host.iobrokerS2" 2023-07-31 14:30:58.425 - info: zigbee.0 (3509883) Zigbee: disabling joining new devices. 2023-07-31 14:30:58.573 - info: zigbee.0 (3509883) terminating 2023-07-31 14:30:58.574 - warn: zigbee.0 (3509883) Terminated (UNCAUGHT_EXCEPTION): Without reason 2023-07-31 14:30:58.629 - debug: notification-manager.0 (3467301) Received notifications from "system.host.iobrokerS2": {} 2023-07-31 14:30:57.981 - error: zigbee.0 (3509883) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). 2023-07-31 14:30:57.981 - error: zigbee.0 (3509883) unhandled promise rejection: Cannot read properties of undefined (reading 'elmVal') 2023-07-31 14:30:57.982 - error: zigbee.0 (3509883) TypeError: Cannot read properties of undefined (reading 'elmVal') at Zigbee.onZigbeeEvent (/opt/iobroker/node_modules/iobroker.zigbee/main.js:493:51) 2023-07-31 14:30:57.982 - error: zigbee.0 (3509883) Cannot read properties of undefined (reading 'elmVal') 2023-07-31 14:30:58.073 - info: zigbee.0 (3509883) cleaned everything up... 2023-07-31 14:30:58.451 - info: notification-manager.0 (3467301) New notification on "iobrokerS2" detected 2023-07-31 14:30:58.452 - debug: notification-manager.0 (3467301) Request notifications from "system.host.iobrokerS2" 2023-07-31 14:30:58.425 - info: zigbee.0 (3509883) Zigbee: disabling joining new devices. 2023-07-31 14:30:58.573 - info: zigbee.0 (3509883) terminating 2023-07-31 14:30:58.574 - warn: zigbee.0 (3509883) Terminated (UNCAUGHT_EXCEPTION): Without reason 2023-07-31 14:30:58.629 - debug: notification-manager.0 (3467301) Received notifications from "system.host.iobrokerS2": {} 2023-07-31 14:30:59.575 - info: zigbee.0 (3509883) terminating with timeout 2023-07-31 14:30:59.575 - info: zigbee.0 (3509883) terminating with timeout 2023-07-31 14:31:00.362 - info: tr-064.0 (3486099) {"NewTotalNumberSyncGroups":"2","NewSyncGroupName":"sync_dsl","NewSyncGroupMode":"VDSL","Newmax_ds":"13378875","Newmax_us":"5514500","Newds_current_bps":"14716,17710,14728,2420,3534,3742,4787,185355,163146,5347415,13106905,12689,8149,7117,9542,1776,4031,6436,763015,4589483","Newmc_current_bps":"0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0","Newus_current_bps":"27839,30933,24321,2788,7033,2877,4343,32844,867942,3777617,368014,9672,5836,5404,5740,2465,14576,7180,27793,146156","Newprio_realtime_bps":"27839,30933,24321,2764,7033,2877,4343,32844,867942,3777617,368014,9672,5836,5404,5740,2465,14576,7180,27793,146156","Newprio_high_bps":"0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0","Newprio_default_bps":"0,0,0,24,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0","Newprio_low_bps":"0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0"} 2023-07-31 14:31:00.380 - error: host.iobrokerS2 Caught by controller[0]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason: 2023-07-31 14:31:00.381 - error: host.iobrokerS2 Caught by controller[1]: TypeError: Cannot read properties of undefined (reading 'elmVal') 2023-07-31 14:31:00.381 - error: host.iobrokerS2 Caught by controller[1]: at Zigbee.onZigbeeEvent (/opt/iobroker/node_modules/iobroker.zigbee/main.js:493:51) 2023-07-31 14:31:00.381 - error: host.iobrokerS2 instance system.adapter.zigbee.0 terminated with code 6 (UNCAUGHT_EXCEPTION) 2023-07-31 14:31:00.381 - info: host.iobrokerS2 Restart adapter system.adapter.zigbee.0 because enabled

`

[arteck]

guck jetzt

sonst brauche ich den Log auszug wo ' --> BatteryValue ' drin steht.. kommt aber nur bei adapter auf Debug

@Ilovegym66 installier direkt nochmal....hab noch was hinzugefügt

[Ilovegym66]

Hurraa !! Es geht!! Es geht!! :-) Die Timeouts stimmen, keine Fehler mehr. Sogar meine SMBZ-120 kann ich manuell ansteuern.. also gleich 2 Issues erledigt.. :-)

[arteck]

wat ne geburt... beobachte es aber kann sein dass ein Gerät mal muckt.. die schrauben gerade am converter rum

ich mach zu hier.. ich erstelle dan mal ne neue version

[Ilovegym66]

Leider zu früh gefreut... Bin gerade nur per iPad verbunden, daher Screenshot..

[arteck]

so hab den nochmal angepasst... sollte jetzt das Gerät liefern.. mit dem problem

[Ilovegym66]

Schau mal:

[arteck]

jetzt...

[Ilovegym66]

Läuft, ist unter Beobachtung;-) Danke!

[Ilovegym66]

Zu früh gefreut... dauert immer n bisschen...

[arteck]

das ist ein Temperatur Sensor oder irgendwas, was Temperatur liefert

guckmal jetzt.. ansonsten brauch ich morgen ganze logs.. im screenshots kann ich nicht alles sehen

[Ilovegym66]

Ah.. hmm hab etliche.. Temperatur senden Feuermelder, Bewegungsmelder, und natürlich die Temperatur Sensoren...

[Ilovegym66]

Ja klar, ich teste mal... ja am Tablett blöd.. komm zwar in die console aber mit der App kann ich kein Text ausschneiden..

[Ilovegym66]

Ah, der Übeltäter:

Temperatur Vorratskeller ist es.. von der Sorte hab ich 4 Stück..

[arteck]

zumindest knallt der nicht mehr...die error meldung ist von mir

zeigmal die objecte zu

ich vermute ein Bug im converter... der liefert echt zero werte

installier nochmal ..dann bekommst du kein error mehr .. nur ne warning .. interessant ist ob der Werte liefert

[Ilovegym66]

Ja, da kommt ab und zu was..

[arteck]

schreib da ne 0 rein... und wenn der sich wieder meldet also warning schmeisst dann ne 1...

im converter wird da was gerechnet ich vermute das es mit der 0 nicht geht

aber das kannst nur du testen.. hab den Sensor nicht

hast mal ein Link zu dem Sensor....

[Ilovegym66]

Werte hab ich in die Kalibrierung eingetragen, mal sehen..

[arteck]

dann bis morgen :-)

[Ilovegym66]

Hab ich seit 2 Jahre, hier der [Link](Ich habe gerade diesen erstaunlichen Artikel auf AliExpress gefunden. Probiere ihn aus! 12,72€ 40％ Rabatt | 1-4 stück Tuya smart Zigbee Temperatur Feuchtigkeit Sensor Batterie Powered Geschichte Daten Lagerung Arbeit Mit Alexa Google smart leben https://a.aliexpress.com/_EwljgCT)

[Ilovegym66]

Prima, seitdem ich die Calibrations gesetzt habe, kommen weder Warnungen noch Errors, der Adapter in Version 1.8.21 laeuft super! Hab auch nicht mehr das unknown device 0000000000 .. das tauchte in frueheren Versionen ab und zu mal auf. Zur Zeit perfekt, occypancy Timeout klappt wie eingestellt (hab nur hoehere Werte ab 120 - 300)! Also jetzt ist das kapitel Zigbee fuer mich erstmal fertich, vielen Dank! Die oben genannten Temp-Sensoren sind ok, waren etwas tricky beim anlernen aber das war vor 2 Jahren.. aber die tun und sind/waren guenstiger als die original von Xiaomi.

[arteck]

das klingt schon mal super..danke dir für deine Geduld :-) aber so ist das wenn man nicht alles hier hat.. es gibt zu viel inzwischen von den Geräten..