Test Adapter KNX v2.x
-
@blacksheep587 sagte in Test Adapter KNX v2.x:
@peer69 war leider auch nicht erfolgreich. Wenn ich eine neue Instanz hinzufüge, dann funktioniert diese. Die alte aber nachwievor nicht. Ich habe mal noch die Logstufe vom KNX-Adapter erweitert:
2023-11-17 12:34:08.811 - [32minfo[39m: host.raspberrypi instance system.adapter.knx.0 started with pid 31285 2023-11-17 12:34:12.629 - [34mdebug[39m: knx.0 (31285) Redis Objects: Use Redis connection: 127.0.0.1:9001 2023-11-17 12:34:12.708 - [34mdebug[39m: knx.0 (31285) Objects client ready ... initialize now 2023-11-17 12:34:12.712 - [34mdebug[39m: knx.0 (31285) Objects create System PubSub Client 2023-11-17 12:34:12.714 - [34mdebug[39m: knx.0 (31285) Objects create User PubSub Client 2023-11-17 12:34:12.774 - [34mdebug[39m: knx.0 (31285) Objects client initialize lua scripts 2023-11-17 12:34:12.785 - [34mdebug[39m: knx.0 (31285) Objects connected to redis: 127.0.0.1:9001 2023-11-17 12:34:12.834 - [34mdebug[39m: knx.0 (31285) Redis States: Use Redis connection: 127.0.0.1:9000 2023-11-17 12:34:12.853 - [34mdebug[39m: knx.0 (31285) States create System PubSub Client 2023-11-17 12:34:12.855 - [34mdebug[39m: knx.0 (31285) States create User PubSub Client 2023-11-17 12:34:12.932 - [34mdebug[39m: knx.0 (31285) States connected to redis: 127.0.0.1:9000 2023-11-17 12:34:12.985 - [34mdebug[39m: knx.0 (31285) Plugin sentry Initialize Plugin (enabled=true) 2023-11-17 12:34:13.795 - [32minfo[39m: knx.0 (31285) starting. Version 2.0.23 in /opt/iobroker/node_modules/iobroker.knx, node: v18.18.2, js-controller: 5.0.16 2023-11-17 12:34:20.308 - [32minfo[39m: host.raspberrypi stopInstance system.adapter.knx.0 (force=false, process=true) 2023-11-17 12:34:20.417 - [32minfo[39m: knx.0 (31285) Got terminate signal TERMINATE_YOURSELF 2023-11-17 12:34:20.425 - [32minfo[39m: host.raspberrypi stopInstance system.adapter.knx.0 send kill signal 2023-11-17 12:34:20.424 - [34mdebug[39m: knx.0 (31285) Adapter close 2023-11-17 12:34:20.426 - [32minfo[39m: knx.0 (31285) terminating 2023-11-17 12:34:20.427 - [34mdebug[39m: knx.0 (31285) Plugin sentry destroyed 2023-11-17 12:34:20.428 - [32minfo[39m: knx.0 (31285) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2023-11-17 12:34:20.930 - [32minfo[39m: knx.0 (31285) terminating 2023-11-17 12:34:20.951 - [31merror[39m: knx.0 (31285) Cannot get objects: Error: Connection is closed. 2023-11-17 12:34:21.069 - [32minfo[39m: host.raspberrypi instance system.adapter.knx.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2023-11-17 12:34:23.688 - [32minfo[39m: host.raspberrypi instance system.adapter.knx.0 started with pid 31300 2023-11-17 12:34:27.588 - [34mdebug[39m: knx.0 (31300) Redis Objects: Use Redis connection: 127.0.0.1:9001 2023-11-17 12:34:27.662 - [34mdebug[39m: knx.0 (31300) Objects client ready ... initialize now 2023-11-17 12:34:27.666 - [34mdebug[39m: knx.0 (31300) Objects create System PubSub Client 2023-11-17 12:34:27.668 - [34mdebug[39m: knx.0 (31300) Objects create User PubSub Client 2023-11-17 12:34:27.727 - [34mdebug[39m: knx.0 (31300) Objects client initialize lua scripts 2023-11-17 12:34:27.737 - [34mdebug[39m: knx.0 (31300) Objects connected to redis: 127.0.0.1:9001 2023-11-17 12:34:27.786 - [34mdebug[39m: knx.0 (31300) Redis States: Use Redis connection: 127.0.0.1:9000 2023-11-17 12:34:27.806 - [34mdebug[39m: knx.0 (31300) States create System PubSub Client 2023-11-17 12:34:27.808 - [34mdebug[39m: knx.0 (31300) States create User PubSub Client 2023-11-17 12:34:27.888 - [34mdebug[39m: knx.0 (31300) States connected to redis: 127.0.0.1:9000 2023-11-17 12:34:27.943 - [34mdebug[39m: knx.0 (31300) Plugin sentry Initialize Plugin (enabled=true) 2023-11-17 12:34:28.821 - [32minfo[39m: knx.0 (31300) starting. Version 2.0.23 in /opt/iobroker/node_modules/iobroker.knx, node: v18.18.2, js-controller: 5.0.16 2023-11-17 12:34:38.769 - [33mwarn[39m: knx.0 (31300) stateChange: not ready 2023-11-17 12:34:40.283 - [33mwarn[39m: knx.0 (31300) stateChange: not ready 2023-11-17 12:34:40.361 - [33mwarn[39m: knx.0 (31300) stateChange: not ready 2023-11-17 12:34:49.161 - [32minfo[39m: knx.0 (31300) knx license is OK. 2023-11-17 12:34:49.164 - [32minfo[39m: knx.0 (31300) Connecting to knx GW: 192.168.178.100:3671 with phy. Adr: 1.0.7 2023-11-17 12:34:49.176 - [32minfo[39m: knx.0 (31300) Debuglevel: 2 3 2023-11-17 12:34:49.182 - [32minfo[39m: knx.0 (31300) Event : UDP - listening 2023-11-17 12:34:49.188 - [32minfo[39m: knx.0 (31300) Connected - local UDP Server listening on 192.168.178.59:51521 2023-11-17 12:34:49.192 - [32minfo[39m: knx.0 (31300) Send : description Request : 06 10 02 03 00 0e 08 01 c0 a8 b2 3b c9 41 sent to 192.168.178.100:3671 2023-11-17 12:34:49.203 - [32minfo[39m: knx.0 (31300) Send : searchReqExt Request : 06 10 02 0b 00 14 08 01 c0 a8 b2 3b c9 41 06 04 01 02 08 06 sent to 192.168.178.100:3671 2023-11-17 12:34:49.204 - [32minfo[39m: knx.0 (31300) STATE_SEARCH_EXT_REQUEST : no defined handling for transition from State: STATE_DESCRIPTION_RESPONSE(18) to STATE_SEARCH_EXT_REQUEST(19). 2023-11-17 12:34:49.209 - [32minfo[39m: knx.0 (31300) receiving descrExtResp 2023-11-17 12:34:49.211 - [32minfo[39m: knx.0 (31300) Send : UDP Connection Request : 06 10 02 05 00 1a 08 01 c0 a8 b2 3b c9 41 08 01 00 00 00 00 c9 41 04 04 02 00 sent to 192.168.178.100:3671 2023-11-17 12:34:49.222 - [32minfo[39m: knx.0 (31300) Received CONNECTION_RESPONSE : 06 10 02 06 00 14 02 00 08 01 c0 a8 b2 64 0e 57 04 04 10 04 GW-IP: 192.168.178.100:3671 - ChannelID: 2 cnt IN/OUT: 0/0 #Hier wurden dann diverse Datenpunkte erzeugt... 2023-11-17 12:34:49.306 - [32minfo[39m: knx.0 (31300) Connected! :-) 2023-11-17 12:34:49.542 - [32minfo[39m: knx.0 (31300) Has todo still 309 tasks, just processing : false 2023-11-17 12:34:49.545 - [32minfo[39m: knx.0 (31300) ( 1 ) Sending : GroupValueRead : 06 10 04 20 00 15 04 02 00 00 11 00 bc e0 10 07 38 01 01 00 00 sent to 192.168.178.100:3671 ChID: 2 SeqCntIN : 0 SeqCntOUT : 0 GA : 7/0/1 conCheck.conected : true 2023-11-17 12:34:49.547 - [32minfo[39m: knx.0 (31300) easy-knx: task.data : 06 10 04 20 00 15 04 02 00 00 11 00 bc e0 10 07 38 01 01 00 00 byteLen : 21 2023-11-17 12:34:49.549 - [32minfo[39m: knx.0 (31300) ( 2 ) Received TUNNEL_ACK : 06 10 04 21 00 0a 04 02 00 00 from 192.168.178.100:3671 SeqCntIN : 0 SeqCntOUT : 1 GA : 0/0/0 2023-11-17 12:34:49.550 - [32minfo[39m: knx.0 (31300) ==> successful acknowledged previous package... processing next of 308 2023-11-17 12:34:49.551 - [32minfo[39m: knx.0 (31300) ==> easy-knx.js: signal runtime : 0s 7.266345ms 2023-11-17 12:34:49.552 - [32minfo[39m: knx.0 (31300) Has todo still 308 tasks, just processing : false 2023-11-17 12:34:49.587 - [32minfo[39m: knx.0 (31300) ( 3.6a ) Received L_DATA.con 06 10 04 20 00 15 04 02 00 00 2e 00 bc e0 10 07 38 01 01 00 00 was successfully processed by receiver. 2023-11-17 12:34:49.588 - [32minfo[39m: knx.0 (31300) =====> STATE_TUNNELING_ACK 2023-11-17 12:34:49.597 - [32minfo[39m: knx.0 (31300) ( 4 ) Sending Tunnel_Request ACK : 06 10 04 21 00 0a 04 02 00 00 ChID : 2 SeqCntIN : 0 SeqCntOUT : 1 queue length : 308 2023-11-17 12:34:49.598 - [32minfo[39m: knx.0 (31300) ( 4.b ) return to STATE_READY, processing : false 2023-11-17 12:34:49.599 - [32minfo[39m: knx.0 (31300) Has todo still 308 tasks, just processing : false 2023-11-17 12:34:49.600 - [32minfo[39m: knx.0 (31300) ( 3.2 ) Received TUNNEL_REQUEST (WRITE - send ACK ) : 06 10 04 20 00 17 04 02 01 00 29 00 bc e0 10 1e 10 01 03 00 80 00 2e ChID: 2 2023-11-17 12:34:49.607 - [32minfo[39m: knx.0 (31300) WRITE : mappedName : Warmwasserzapftemperatur-soll dest : 2/0/1 val: 46 (DPT7.000) Warmwasserzapftemperatur-soll 2023-11-17 12:34:49.610 - [32minfo[39m: knx.0 (31300) =====> STATE_TUNNELING_ACK 2023-11-17 12:34:49.612 - [32minfo[39m: knx.0 (31300) ( 4 ) Sending Tunnel_Request ACK : 06 10 04 21 00 0a 04 02 01 00 ChID : 2 SeqCntIN : 1 SeqCntOUT : 1 queue length : 308 2023-11-17 12:34:49.612 - [32minfo[39m: knx.0 (31300) ( 4.b ) return to STATE_READY, processing : false 2023-11-17 12:34:49.613 - [32minfo[39m: knx.0 (31300) Has todo still 308 tasks, just processing : false 2023-11-17 12:34:49.622 - [32minfo[39m: knx.0 (31300) ( 3.2 ) Received TUNNEL_REQUEST (WRITE - send ACK ) : 06 10 04 20 00 17 04 02 02 00 29 00 bc e0 10 1e 10 0d 03 00 80 00 00 ChID: 2 2023-11-17 12:34:49.624 - [32minfo[39m: knx.0 (31300) WRITE : mappedName : Waermepumpe Stoerung Puls dest : 2/0/13 val: 0 (DPT7.001) Waermepumpe_Stoerung_Puls 2023-11-17 12:34:49.625 - [32minfo[39m: knx.0 (31300) =====> STATE_TUNNELING_ACK 2023-11-17 12:34:49.627 - [32minfo[39m: knx.0 (31300) ( 4 ) Sending Tunnel_Request ACK : 06 10 04 21 00 0a 04 02 02 00 ChID : 2 SeqCntIN : 2 SeqCntOUT : 1 queue length : 308 2023-11-17 12:34:49.628 - [32minfo[39m: knx.0 (31300) ( 4.b ) return to STATE_READY, processing : false 2023-11-17 12:34:49.628 - [32minfo[39m: knx.0 (31300) Has todo still 308 tasks, just processing : false 2023-11-17 12:34:49.633 - [32minfo[39m: knx.0 (31300) main.js : tGA.write on Statechange : 2/0/51 P-032E-0_GA-1378 typeof val: number 5.475 DPT9.024 2023-11-17 12:34:49.642 - [32minfo[39m: knx.0 (31300) easy-knx.js groupValueWrite value: 5.475 dpt : DPT9.024{"type":"Buffer","data":[6,16,4,32,0,23,4,2,1,0,17,0,188,224,16,7,16,51,3,0,128,2,35]} 2023-11-17 12:34:49.651 - [32minfo[39m: knx.0 (31300) ( 1 ) Sending : GroupValueRead : 06 10 04 20 00 15 04 02 01 00 11 00 bc e0 10 07 38 02 01 00 00 sent to 192.168.178.100:3671 ChID: 2 SeqCntIN : 2 SeqCntOUT : 1 GA : 7/0/2 conCheck.conected : true 2023-11-17 12:34:49.652 - [32minfo[39m: knx.0 (31300) easy-knx: task.data : 06 10 04 20 00 15 04 02 01 00 11 00 bc e0 10 07 38 02 01 00 00 byteLen : 21 2023-11-17 12:34:49.656 - [32minfo[39m: knx.0 (31300) ( 3.2 ) Received TUNNEL_REQUEST (WRITE - send ACK ) : 06 10 04 20 00 17 04 02 03 00 29 00 bc e0 10 1e 10 05 03 00 80 00 01 ChID: 2 2023-11-17 12:34:49.657 - [32minfo[39m: knx.0 (31300) WRITE : mappedName : Heizkreis A Betriebsart dest : 2/0/5 val: 1 (DPT7.000) Heizkreis_A_Betriebsart 2023-11-17 12:34:49.659 - [32minfo[39m: knx.0 (31300) =====> STATE_TUNNELING_ACK newState: deferred 2023-11-17 12:34:49.660 - [32minfo[39m: knx.0 (31300) ( 4 ) Sending Tunnel_Request ACK : 06 10 04 21 00 0a 04 02 03 00 ChID : 2 SeqCntIN : 3 SeqCntOUT : 2 queue length : 308 2023-11-17 12:34:49.661 - [32minfo[39m: knx.0 (31300) ( 4.b ) return to STATE_READY, processing : false 2023-11-17 12:34:49.662 - [32minfo[39m: knx.0 (31300) Has todo still 308 tasks, just processing : false 2023-11-17 12:34:49.662 - [32minfo[39m: knx.0 (31300) ( 2 ) Received TUNNEL_ACK : 06 10 04 21 00 0a 04 02 01 00 from 192.168.178.100:3671 SeqCntIN : 3 SeqCntOUT : 2 GA : 0/0/0 2023-11-17 12:34:49.663 - [32minfo[39m: knx.0 (31300) ==> successful acknowledged previous package... processing next of 308 2023-11-17 12:34:49.664 - [32minfo[39m: knx.0 (31300) ==> easy-knx.js: signal runtime : 0s 13.023492ms 2023-11-17 12:34:49.665 - [32minfo[39m: knx.0 (31300) Has todo still 308 tasks, just processing : false 2023-11-17 12:34:49.666 - [32minfo[39m: knx.0 (31300) ( 3.2 ) Received TUNNEL_REQUEST (WRITE - send ACK ) : 06 10 04 20 00 15 04 02 04 00 29 00 bc e0 10 03 10 0e 01 00 80 ChID: 2 2023-11-17 12:34:49.668 - [32minfo[39m: knx.0 (31300) WRITE : mappedName : Waermepumpe Stoerung bool dest : 2/0/14 val: 0 (DPT1.001) Waermepumpe_Stoerung_bool 2023-11-17 12:34:49.670 - [32minfo[39m: knx.0 (31300) =====> STATE_TUNNELING_ACK 2023-11-17 12:34:49.671 - [32minfo[39m: knx.0 (31300) ( 4 ) Sending Tunnel_Request ACK : 06 10 04 21 00 0a 04 02 04 00 ChID : 2 SeqCntIN : 4 SeqCntOUT : 2 queue length : 308 2023-11-17 12:34:49.671 - [32minfo[39m: knx.0 (31300) ( 4.b ) return to STATE_READY, processing : false 2023-11-17 12:34:49.672 - [32minfo[39m: knx.0 (31300) Has todo still 308 tasks, just processing : false 2023-11-17 12:34:49.683 - [32minfo[39m: knx.0 (31300) easy-knx.js groupValueWrite value: 5 dpt : DPT9.000{"type":"Buffer","data":[6,16,4,32,0,23,4,2,2,0,17,0,188,224,16,7,3,1,3,0,128,1,244]} 2023-11-17 12:34:49.687 - [32minfo[39m: knx.0 (31300) easy-knx.js groupValueWrite value: 23 dpt : DPT9.000{"type":"Buffer","data":[6,16,4,32,0,23,4,2,2,0,17,0,188,224,16,7,3,0,3,0,128,12,126]} 2023-11-17 12:34:49.690 - [32minfo[39m: knx.0 (31300) easy-knx.js groupValueWrite value: 0 dpt : DPT9.009{"type":"Buffer","data":[6,16,4,32,0,23,4,2,2,0,17,0,188,224,16,7,3,9,3,0,128,0,0]} 2023-11-17 12:34:49.693 - [32minfo[39m: knx.0 (31300) easy-knx.js groupValueWrite value: 0.562 dpt : DPT14.076{"type":"Buffer","data":[6,16,4,32,0,25,4,2,2,0,17,0,188,224,16,7,3,7,5,0,128,63,15,223,59]} 2023-11-17 12:34:49.696 - [32minfo[39m: knx.0 (31300) easy-knx.js groupValueWrite value: 80 dpt : DPT9.007{"type":"Buffer","data":[6,16,4,32,0,23,4,2,2,0,17,0,188,224,16,7,3,8,3,0,128,23,208]} 2023-11-17 12:34:49.698 - [32minfo[39m: knx.0 (31300) easy-knx.js groupValueWrite value: 365 dpt : DPT9.000{"type":"Buffer","data":[6,16,4,32,0,23,4,2,2,0,17,0,188,224,16,7,3,17,3,0,128,44,116]} 2023-11-17 12:34:49.700 - [32minfo[39m: knx.0 (31300) easy-knx.js groupValueWrite value: 99 dpt : DPT9.000{"type":"Buffer","data":[6,16,4,32,0,23,4,2,2,0,17,0,188,224,16,7,3,16,3,0,128,28,213]} 2023-11-17 12:34:49.703 - [32minfo[39m: knx.0 (31300) easy-knx.js groupValueWrite value: 685 dpt : DPT9.000{"type":"Buffer","data":[6,16,4,32,0,23,4,2,2,0,17,0,188,224,16,7,3,4,3,0,128,52,46]} 2023-11-17 12:34:49.706 - [32minfo[39m: knx.0 (31300) easy-knx.js groupValueWrite value: 0 dpt : DPT9.000{"type":"Buffer","data":[6,16,4,32,0,23,4,2,2,0,17,0,188,224,16,7,3,2,3,0,128,0,0]} 2023-11-17 12:34:49.709 - [32minfo[39m: knx.0 (31300) easy-knx.js groupValueWrite value: 0 dpt : DPT9.000{"type":"Buffer","data":[6,16,4,32,0,23,4,2,2,0,17,0,188,224,16,7,3,3,3,0,128,0,0]} 2023-11-17 12:34:49.724 - [31merror[39m: knx.0 (31300) uncaught exception: Cannot read properties of null (reading 'val') 2023-11-17 12:34:49.725 - [31merror[39m: knx.0 (31300) TypeError: Cannot read properties of null (reading 'val') at Immediate.<anonymous> (/opt/iobroker/node_modules/iobroker.knx/knx.js:1:380948) at processImmediate (node:internal/timers:478:21) 2023-11-17 12:34:49.725 - [31merror[39m: knx.0 (31300) Cannot read properties of null (reading 'val') 2023-11-17 12:34:49.752 - [31merror[39m: knx.0 (31300) uncaught exception: Cannot read properties of null (reading 'val') 2023-11-17 12:34:49.753 - [31merror[39m: knx.0 (31300) TypeError: Cannot read properties of null (reading 'val') at Immediate.<anonymous> (/opt/iobroker/node_modules/iobroker.knx/knx.js:1:380948) at processImmediate (node:internal/timers:478:21) 2023-11-17 12:34:49.753 - [31merror[39m: knx.0 (31300) Cannot read properties of null (reading 'val') 2023-11-17 12:34:49.757 - [31merror[39m: knx.0 (31300) uncaught exception: Cannot read properties of null (reading 'val') 2023-11-17 12:34:49.757 - [31merror[39m: knx.0 (31300) TypeError: Cannot read properties of null (reading 'val') at Immediate.<anonymous> (/opt/iobroker/node_modules/iobroker.knx/knx.js:1:380948) at processImmediate (node:internal/timers:478:21) 2023-11-17 12:34:49.758 - [31merror[39m: knx.0 (31300) Cannot read properties of null (reading 'val') 2023-11-17 12:34:49.761 - [31merror[39m: knx.0 (31300) uncaught exception: Cannot read properties of null (reading 'val') 2023-11-17 12:34:49.762 - [31merror[39m: knx.0 (31300) TypeError: Cannot read properties of null (reading 'val') at Immediate.<anonymous> (/opt/iobroker/node_modules/iobroker.knx/knx.js:1:380948) at processImmediate (node:internal/timers:478:21) 2023-11-17 12:34:49.762 - [31merror[39m: knx.0 (31300) Cannot read properties of null (reading 'val') 2023-11-17 12:34:49.765 - [31merror[39m: knx.0 (31300) uncaught exception: Cannot read properties of null (reading 'val') 2023-11-17 12:34:49.765 - [31merror[39m: knx.0 (31300) TypeError: Cannot read properties of null (reading 'val') at Immediate.<anonymous> (/opt/iobroker/node_modules/iobroker.knx/knx.js:1:380948) at processImmediate (node:internal/timers:478:21) 2023-11-17 12:34:49.766 - [31merror[39m: knx.0 (31300) Cannot read properties of null (reading 'val') 2023-11-17 12:34:49.770 - [32minfo[39m: knx.0 (31300) easy-knx.js groupValueWrite value: 12 dpt : DPT9.001{"type":"Buffer","data":[6,16,4,32,0,23,4,2,2,0,17,0,188,224,16,7,2,13,3,0,128,4,176]} 2023-11-17 12:34:49.771 - [32minfo[39m: knx.0 (31300) ( 1 ) Sending : GroupValueRead : 06 10 04 20 00 15 04 02 02 00 11 00 bc e0 10 07 38 04 01 00 00 sent to 192.168.178.100:3671 ChID: 2 SeqCntIN : 4 SeqCntOUT : 2 GA : 7/0/4 conCheck.conected : true 2023-11-17 12:34:49.773 - [32minfo[39m: knx.0 (31300) easy-knx: task.data : 06 10 04 20 00 15 04 02 02 00 11 00 bc e0 10 07 38 04 01 00 00 byteLen : 21 2023-11-17 12:34:49.776 - [32minfo[39m: knx.0 (31300) easy-knx.js groupValueWrite value: 80 dpt : DPT9.007{"type":"Buffer","data":[6,16,4,32,0,23,4,2,3,0,17,0,188,224,16,7,2,15,3,0,128,23,208]} 2023-11-17 12:34:49.779 - [32minfo[39m: knx.0 (31300) easy-knx.js groupValueWrite value: 1758 dpt : DPT9.004{"type":"Buffer","data":[6,16,4,32,0,23,4,2,3,0,17,0,188,224,16,7,2,12,3,0,128,61,93]} 2023-11-17 12:34:49.783 - [32minfo[39m: knx.0 (31300) easy-knx.js groupValueWrite value: 13 dpt : DPT9.001{"type":"Buffer","data":[6,16,4,32,0,23,4,2,3,0,17,0,188,224,16,7,2,11,3,0,128,5,20]} 2023-11-17 12:34:49.785 - [32minfo[39m: knx.0 (31300) easy-knx.js groupValueWrite value: 30 dpt : DPT9.007{"type":"Buffer","data":[6,16,4,32,0,23,4,2,3,0,17,0,188,224,16,7,2,10,3,0,128,13,220]} 2023-11-17 12:34:49.787 - [32minfo[39m: knx.0 (31300) easy-knx.js groupValueWrite value: 57 dpt : DPT9.007{"type":"Buffer","data":[6,16,4,32,0,23,4,2,3,0,17,0,188,224,16,7,2,16,3,0,128,21,145]} 2023-11-17 12:34:49.789 - [32minfo[39m: knx.0 (31300) easy-knx.js groupValueWrite value: 4 dpt : DPT9.001{"type":"Buffer","data":[6,16,4,32,0,23,4,2,3,0,17,0,188,224,16,7,2,23,3,0,128,1,144]} 2023-11-17 12:34:49.791 - [32minfo[39m: knx.0 (31300) easy-knx.js groupValueWrite value: 90 dpt : DPT9.007{"type":"Buffer","data":[6,16,4,32,0,23,4,2,3,0,17,0,188,224,16,7,2,25,3,0,128,28,101]} 2023-11-17 12:34:49.793 - [32minfo[39m: knx.0 (31300) easy-knx.js groupValueWrite value: 0 dpt : DPT9.004{"type":"Buffer","data":[6,16,4,32,0,23,4,2,3,0,17,0,188,224,16,7,2,22,3,0,128,0,0]} 2023-11-17 12:34:49.795 - [32minfo[39m: knx.0 (31300) easy-knx.js groupValueWrite value: 8 dpt : DPT9.001{"type":"Buffer","data":[6,16,4,32,0,23,4,2,3,0,17,0,188,224,16,7,2,21,3,0,128,3,32]} 2023-11-17 12:34:49.798 - [32minfo[39m: knx.0 (31300) easy-knx.js groupValueWrite value: 85 dpt : DPT9.007{"type":"Buffer","data":[6,16,4,32,0,23,4,2,3,0,17,0,188,224,16,7,2,20,3,0,128,28,38]} 2023-11-17 12:34:49.801 - [32minfo[39m: knx.0 (31300) easy-knx.js groupValueWrite value: 0 dpt : DPT9.007{"type":"Buffer","data":[6,16,4,32,0,23,4,2,3,0,17,0,188,224,16,7,2,26,3,0,128,0,0]} 2023-11-17 12:34:49.803 - [32minfo[39m: knx.0 (31300) easy-knx.js groupValueWrite value: 50 dpt : DPT9.007{"type":"Buffer","data":[6,16,4,32,0,23,4,2,3,0,17,0,188,224,16,7,2,35,3,0,128,20,226]} 2023-11-17 12:34:49.805 - [32minfo[39m: knx.0 (31300) easy-knx.js groupValueWrite value: 12 dpt : DPT9.001{"type":"Buffer","data":[6,16,4,32,0,23,4,2,3,0,17,0,188,224,16,7,2,31,3,0,128,4,176]} 2023-11-17 12:34:49.807 - [32minfo[39m: knx.0 (31300) easy-knx.js groupValueWrite value: 0 dpt : DPT9.007{"type":"Buffer","data":[6,16,4,32,0,23,4,2,3,0,17,0,188,224,16,7,2,30,3,0,128,0,0]} 2023-11-17 12:34:49.809 - [32minfo[39m: knx.0 (31300) easy-knx.js groupValueWrite value: 12 dpt : DPT9.007{"type":"Buffer","data":[6,16,4,32,0,23,4,2,3,0,17,0,188,224,16,7,2,36,3,0,128,4,176]} 2023-11-17 12:34:49.811 - [32minfo[39m: knx.0 (31300) easy-knx.js groupValueWrite value: 60 dpt : DPT9.007{"type":"Buffer","data":[6,16,4,32,0,23,4,2,3,0,17,0,188,224,16,7,2,45,3,0,128,21,220]} 2023-11-17 12:34:49.820 - [32minfo[39m: knx.0 (31300) ( 3.2 ) Received TUNNEL_REQUEST (WRITE - send ACK ) : 06 10 04 20 00 17 04 02 05 00 29 00 bc e0 10 1e 10 09 03 00 80 00 01 ChID: 2 2023-11-17 12:34:49.821 - [32minfo[39m: knx.0 (31300) WRITE : mappedName : Zonenmodul Modus dest : 2/0/9 val: 1 (DPT7.000) Zonenmodul_Modus 2023-11-17 12:34:49.822 - [32minfo[39m: knx.0 (31300) =====> STATE_TUNNELING_ACK newState: deferred 2023-11-17 12:34:49.823 - [32minfo[39m: knx.0 (31300) ( 4 ) Sending Tunnel_Request ACK : 06 10 04 21 00 0a 04 02 05 00 ChID : 2 SeqCntIN : 5 SeqCntOUT : 3 queue length : 334 2023-11-17 12:34:49.824 - [32minfo[39m: knx.0 (31300) ( 4.b ) return to STATE_READY, processing : false 2023-11-17 12:34:49.824 - [32minfo[39m: knx.0 (31300) Has todo still 334 tasks, just processing : false 2023-11-17 12:34:49.825 - [32minfo[39m: knx.0 (31300) ( 2 ) Received TUNNEL_ACK : 06 10 04 21 00 0a 04 02 02 00 from 192.168.178.100:3671 SeqCntIN : 5 SeqCntOUT : 3 GA : 0/0/0 2023-11-17 12:34:49.826 - [32minfo[39m: knx.0 (31300) ==> successful acknowledged previous package... processing next of 334 2023-11-17 12:34:49.826 - [32minfo[39m: knx.0 (31300) ==> easy-knx.js: signal runtime : 0s 55.111437ms 2023-11-17 12:34:49.827 - [32minfo[39m: knx.0 (31300) Has todo still 334 tasks, just processing : false 2023-11-17 12:34:49.828 - [32minfo[39m: knx.0 (31300) ( 3.6a ) Received L_DATA.con 06 10 04 20 00 15 04 02 06 00 2e 00 bc e0 10 07 38 02 01 00 00 was successfully processed by receiver. 2023-11-17 12:34:49.828 - [32minfo[39m: knx.0 (31300) =====> STATE_TUNNELING_ACK 2023-11-17 12:34:49.829 - [32minfo[39m: knx.0 (31300) ( 4 ) Sending Tunnel_Request ACK : 06 10 04 21 00 0a 04 02 06 00 ChID : 2 SeqCntIN : 6 SeqCntOUT : 3 queue length : 334 2023-11-17 12:34:49.830 - [32minfo[39m: knx.0 (31300) ( 4.b ) return to STATE_READY, processing : false 2023-11-17 12:34:49.830 - [32minfo[39m: knx.0 (31300) Has todo still 334 tasks, just processing : false 2023-11-17 12:34:49.831 - [32minfo[39m: knx.0 (31300) ( 3.3 ) Received TUNNEL_REQUEST (RESPONSE - send ACK) : 06 10 04 20 00 17 04 02 07 00 29 00 bc d0 11 0a 38 01 03 00 40 0c b6 2 2023-11-17 12:34:49.833 - [32minfo[39m: knx.0 (31300) main.js: onGroupValue_Response from 7/0/1 2023-11-17 12:34:49.834 - [32minfo[39m: knx.0 (31300) RESPONSE : mappedName : Windgeschwindigkeit dest : 7/0/1 val: 24.12 (DPT9.005) Windgeschwindigkeit 2023-11-17 12:34:49.835 - [32minfo[39m: knx.0 (31300) RESPONSE single-array value : 24.12 auf knx.0.Wetter.Wetterstation.Windgeschwindigkeit 2023-11-17 12:34:49.836 - [32minfo[39m: knx.0 (31300) ( 3.4 ) Received TUNNEL_REQUEST for unexpected address 2023-11-17 12:34:49.837 - [32minfo[39m: knx.0 (31300) =====> STATE_TUNNELING_ACK 2023-11-17 12:34:49.838 - [32minfo[39m: knx.0 (31300) ( 4 ) Sending Tunnel_Request ACK : 06 10 04 21 00 0a 04 02 07 00 ChID : 2 SeqCntIN : 7 SeqCntOUT : 3 queue length : 334 2023-11-17 12:34:49.839 - [32minfo[39m: knx.0 (31300) ( 4.b ) return to STATE_READY, processing : false 2023-11-17 12:34:49.839 - [32minfo[39m: knx.0 (31300) Has todo still 334 tasks, just processing : false 2023-11-17 12:34:49.841 - [32minfo[39m: knx.0 (31300) ( 3.2 ) Received TUNNEL_REQUEST (WRITE - send ACK ) : 06 10 04 20 00 17 04 02 08 00 29 00 bc e0 10 1e 12 03 03 00 80 0c 1a ChID: 2 2023-11-17 12:34:49.842 - [32minfo[39m: knx.0 (31300) WRITE : mappedName : A3_Raumtemperatur EG Flur -Soll dest : 2/2/3 val: 21 (DPT9.001) A3_Raumtemperatur_EG_Flur_-Soll 2023-11-17 12:34:49.843 - [32minfo[39m: knx.0 (31300) =====> STATE_TUNNELING_ACK 2023-11-17 12:34:49.844 - [32minfo[39m: knx.0 (31300) ( 4 ) Sending Tunnel_Request ACK : 06 10 04 21 00 0a 04 02 08 00 ChID : 2 SeqCntIN : 8 SeqCntOUT : 3 queue length : 334 2023-11-17 12:34:49.845 - [32minfo[39m: knx.0 (31300) ( 4.b ) return to STATE_READY, processing : false 2023-11-17 12:34:49.846 - [32minfo[39m: knx.0 (31300) Has todo still 334 tasks, just processing : false 2023-11-17 12:34:49.847 - [32minfo[39m: knx.0 (31300) ( 3.2 ) Received TUNNEL_REQUEST (WRITE - send ACK ) : 06 10 04 20 00 17 04 02 09 00 29 00 bc e0 10 1e 12 04 03 00 80 07 6c ChID: 2 2023-11-17 12:34:49.848 - [32minfo[39m: knx.0 (31300) WRITE : mappedName : A4_Raumtemperatur EG WC -Soll dest : 2/2/4 val: 19 (DPT9.001) A4_Raumtemperatur_EG_WC_-Soll 2023-11-17 12:34:49.848 - [32minfo[39m: knx.0 (31300) =====> STATE_TUNNELING_ACK 2023-11-17 12:34:49.850 - [32minfo[39m: knx.0 (31300) ( 4 ) Sending Tunnel_Request ACK : 06 10 04 21 00 0a 04 02 09 00 ChID : 2 SeqCntIN : 9 SeqCntOUT : 3 queue length : 334 2023-11-17 12:34:49.850 - [32minfo[39m: knx.0 (31300) ( 4.b ) return to STATE_READY, processing : false 2023-11-17 12:34:49.851 - [32minfo[39m: knx.0 (31300) Has todo still 334 tasks, just processing : false 2023-11-17 12:34:49.852 - [32minfo[39m: knx.0 (31300) ( 3.6a ) Received L_DATA.con 06 10 04 20 00 15 04 02 0a 00 2e 00 bc e0 10 07 38 04 01 00 00 was successfully processed by receiver. 2023-11-17 12:34:49.852 - [32minfo[39m: knx.0 (31300) =====> STATE_TUNNELING_ACK 2023-11-17 12:34:49.854 - [32minfo[39m: knx.0 (31300) ( 4 ) Sending Tunnel_Request ACK : 06 10 04 21 00 0a 04 02 0a 00 ChID : 2 SeqCntIN : 10 SeqCntOUT : 3 queue length : 334 2023-11-17 12:34:49.855 - [32minfo[39m: knx.0 (31300) ( 4.b ) return to STATE_READY, processing : false 2023-11-17 12:34:49.855 - [32minfo[39m: knx.0 (31300) Has todo still 334 tasks, just processing : false 2023-11-17 12:34:49.856 - [32minfo[39m: knx.0 (31300) ( 3.2 ) Received TUNNEL_REQUEST (WRITE - send ACK ) : 06 10 04 20 00 17 04 02 0b 00 29 00 bc e0 10 1e 10 34 03 00 80 00 00 ChID: 2 2023-11-17 12:34:49.857 - [32minfo[39m: knx.0 (31300) WRITE : mappedName : PV_WP_Elektrische_Leistungsaufnahme dest : 2/0/52 val: 0 (DPT9.001) PV_WP_Elektrische_Leistungsaufnahme 2023-11-17 12:34:49.858 - [32minfo[39m: knx.0 (31300) =====> STATE_TUNNELING_ACK 2023-11-17 12:34:49.859 - [32minfo[39m: knx.0 (31300) ( 4 ) Sending Tunnel_Request ACK : 06 10 04 21 00 0a 04 02 0b 00 ChID : 2 SeqCntIN : 11 SeqCntOUT : 3 queue length : 334 2023-11-17 12:34:49.860 - [32minfo[39m: knx.0 (31300) ( 4.b ) return to STATE_READY, processing : false 2023-11-17 12:34:49.860 - [32minfo[39m: knx.0 (31300) Has todo still 334 tasks, just processing : false 2023-11-17 12:34:49.871 - [32minfo[39m: knx.0 (31300) Connection persists.....closing now 2023-11-17 12:34:49.872 - [32minfo[39m: knx.0 (31300) ... not able to close connection, because already closed 2023-11-17 12:34:49.873 - [32minfo[39m: knx.0 (31300) STATE_NOT_CONNECTED : Try to connect / reconnect : STATE_READY(7) to STATE_NOT_CONNECTED(0). 2023-11-17 12:34:49.874 - [34mdebug[39m: knx.0 (31300) Adapter close 2023-11-17 12:34:49.875 - [32minfo[39m: knx.0 (31300) terminating 2023-11-17 12:34:49.876 - [34mdebug[39m: knx.0 (31300) Plugin sentry destroyed 2023-11-17 12:34:49.876 - [33mwarn[39m: knx.0 (31300) Terminated (UNCAUGHT_EXCEPTION): Without reason 2023-11-17 12:34:49.878 - [32minfo[39m: knx.0 (31300) ( END ) Sending DISCONNECT_REQUEST : 06 10 02 09 00 10 02 00 08 01 c0 a8 b2 3b c9 41 ChID : 0 SeqCntIN : 11 SeqCntOUT : 3 msgCode : [object Object] 2023-11-17 12:34:49.879 - [32minfo[39m: knx.0 (31300) STATE_DISCONNECT_REQUEST : Transition from State: STATE_NOT_CONNECTED(0) to STATE_DISCONNECT_REQUEST(15) not possible because of cancelled connection. 2023-11-17 12:34:49.879 - [32minfo[39m: knx.0 (31300) Connection persists.....closing now 2023-11-17 12:34:49.880 - [32minfo[39m: knx.0 (31300) ... not able to close connection, because already closed 2023-11-17 12:34:49.881 - [32minfo[39m: knx.0 (31300) STATE_NOT_CONNECTED : Stop connection : STATE_DISCONNECT_REQUEST(15) to STATE_NOT_CONNECTED(0). 2023-11-17 12:34:49.914 - [32minfo[39m: knx.0 (31300) easy-knx.js groupValueWrite value: 11 dpt : DPT9.001{"type":"Buffer","data":[6,16,4,32,0,23,4,2,3,0,17,0,188,224,16,7,2,41,3,0,128,4,76]} 2023-11-17 12:34:49.916 - [32minfo[39m: knx.0 (31300) easy-knx.js groupValueWrite value: 60 dpt : DPT9.007{"type":"Buffer","data":[6,16,4,32,0,23,4,2,3,0,17,0,188,224,16,7,2,40,3,0,128,21,220]} 2023-11-17 12:34:49.919 - [32minfo[39m: knx.0 (31300) easy-knx.js groupValueWrite value: 51 dpt : DPT9.007{"type":"Buffer","data":[6,16,4,32,0,23,4,2,3,0,17,0,188,224,16,7,2,46,3,0,128,20,251]} 2023-11-17 12:34:49.922 - [32minfo[39m: knx.0 (31300) easy-knx.js groupValueWrite value: 0.055 dpt : DPT9.024{"type":"Buffer","data":[6,16,4,32,0,23,4,2,3,0,17,0,188,224,16,7,16,50,3,0,128,0,5]} 2023-11-17 12:34:49.925 - [32minfo[39m: knx.0 (31300) easy-knx.js groupValueWrite value: 5.475 dpt : DPT9.024{"type":"Buffer","data":[6,16,4,32,0,23,4,2,3,0,17,0,188,224,16,7,16,51,3,0,128,2,35]} 2023-11-17 12:34:49.935 - [32minfo[39m: knx.0 (31300) STATE_DISCONNECT_RESPONSE : from State: STATE_NOT_CONNECTED(0) to STATE_DISCONNECT_RESPONSE(16) ... connection closed 2023-11-17 12:34:49.936 - [32minfo[39m: knx.0 (31300) Received DISCONNECT_RESPONSE06 10 02 0a 00 08 02 00 2023-11-17 12:34:49.937 - [32minfo[39m: knx.0 (31300) Connection persists.....closing now 2023-11-17 12:34:49.939 - [32minfo[39m: knx.0 (31300) ... not able to close connection, because already closed 2023-11-17 12:34:49.940 - [32minfo[39m: knx.0 (31300) STATE_NOT_CONNECTED : Stop connection : STATE_DISCONNECT_RESPONSE(16) to STATE_NOT_CONNECTED(0). 2023-11-17 12:34:50.418 - [31merror[39m: host.raspberrypi Caught by controller[0]: TypeError: Cannot read properties of null (reading 'val') 2023-11-17 12:34:50.420 - [31merror[39m: host.raspberrypi Caught by controller[0]: at Immediate.<anonymous> (/opt/iobroker/node_modules/iobroker.knx/knx.js:1:380948) 2023-11-17 12:34:50.420 - [31merror[39m: host.raspberrypi Caught by controller[0]: at processImmediate (node:internal/timers:478:21) 2023-11-17 12:34:50.420 - [31merror[39m: host.raspberrypi Caught by controller[1]: TypeError: Cannot read properties of null (reading 'val') 2023-11-17 12:34:50.420 - [31merror[39m: host.raspberrypi Caught by controller[1]: at Immediate.<anonymous> (/opt/iobroker/node_modules/iobroker.knx/knx.js:1:380948) 2023-11-17 12:34:50.420 - [31merror[39m: host.raspberrypi Caught by controller[1]: at processImmediate (node:internal/timers:478:21) 2023-11-17 12:34:50.420 - [31merror[39m: host.raspberrypi Caught by controller[2]: TypeError: Cannot read properties of null (reading 'val') 2023-11-17 12:34:50.421 - [31merror[39m: host.raspberrypi Caught by controller[2]: at Immediate.<anonymous> (/opt/iobroker/node_modules/iobroker.knx/knx.js:1:380948) 2023-11-17 12:34:50.421 - [31merror[39m: host.raspberrypi Caught by controller[2]: at processImmediate (node:internal/timers:478:21) 2023-11-17 12:34:50.421 - [31merror[39m: host.raspberrypi Caught by controller[3]: TypeError: Cannot read properties of null (reading 'val') 2023-11-17 12:34:50.421 - [31merror[39m: host.raspberrypi Caught by controller[3]: at Immediate.<anonymous> (/opt/iobroker/node_modules/iobroker.knx/knx.js:1:380948) 2023-11-17 12:34:50.421 - [31merror[39m: host.raspberrypi Caught by controller[3]: at processImmediate (node:internal/timers:478:21) 2023-11-17 12:34:50.421 - [31merror[39m: host.raspberrypi Caught by controller[4]: TypeError: Cannot read properties of null (reading 'val') 2023-11-17 12:34:50.422 - [31merror[39m: host.raspberrypi Caught by controller[4]: at Immediate.<anonymous> (/opt/iobroker/node_modules/iobroker.knx/knx.js:1:380948) 2023-11-17 12:34:50.422 - [31merror[39m: host.raspberrypi Caught by controller[4]: at processImmediate (node:internal/timers:478:21) 2023-11-17 12:34:50.422 - [31merror[39m: host.raspberrypi instance system.adapter.knx.0 terminated with code 1 (JS_CONTROLLER_STOPPED) 2023-11-17 12:34:50.422 - [32minfo[39m: host.raspberrypi Restart adapter system.adapter.knx.0 because enabledes sieht so aus also er sich hier komplett zerschossen hat, da eine 2te Instanz geht waehre es eine option die fehlerhafte zu löschen und neu an zu legen ?
-
@dutchman Ja, das habe ich gerade gemacht. Es hat aber nicht geholfen, die 0er Instanz zu deinstallieren und eine neue 0er zu erstellen. Ich baue jetzt auf 1. Instanz auf. Jetzt die Frage: kann ich InfluxDB Logs umhängen in eine andere Instanz?
-
@blacksheep587 sagte in Test Adapter KNX v2.x:
@dutchman Ja, das habe ich gerade gemacht. Es hat aber nicht geholfen, die 0er Instanz zu deinstallieren und eine neue 0er zu erstellen. Ich baue jetzt auf 1. Instanz auf. Jetzt die Frage: kann ich InfluxDB Logs umhängen in eine andere Instanz?
hmm ja aber damit bekämpfen wir ein symptom und mache es komplex da wir mit aliassen arbeiten müssen.
(die Datenpunkte ändern sich nämlich von knx.0 nach knx.1)
Wieso lässt sich die erste Instanz nicht löschen, kommt da was im log oder ? -
@dutchman said in Test Adapter KNX v2.x:
Wieso lässt sich die erste Instanz nicht löschen, kommt da was im log oder ?
Ja, ich bekomme die gleiche Logschleife wie vorher.
-
@blacksheep587 sagte in Test Adapter KNX v2.x:
@dutchman said in Test Adapter KNX v2.x:
Wieso lässt sich die erste Instanz nicht löschen, kommt da was im log oder ?
Ja, ich bekomme die gleiche Logschleife wie vorher.
@ChefSache behällt der Adapter noch irgendwo anders Daten? Kannst du eventueel helfen als maintainer des Adapter ?
@blacksheep587 alternatief koelte ich dich dabei unterstützen es auf einen knx.1 Instanz um zu setzen.
Wen du Datenpunkte mit logging aktiv hast, muesste diese auf dem 2ten wieder aktiviert werden un der vorige als alias eingetragen (damit laufen das logging auf deine Datenbank weiter wie gehabt, sonst werden es neue Einträge)eventuelle scripte, visu Verweisungen usw müssten auch geändert werden. das das eventuell viel aufwand ist doch die frage ob wir die Instanz 0 nicht reanimieren/neu aufsetzen koennten
-
@dutchman ja, das wäre gut, wenn wir die InfluxDB über Aliase umhängen könnten. Die Skripte habe ich gestern bereits geändert und als Visu habe ich eine native KNX Umgebung, da gibts nichts zu tun.
-
@blacksheep587 sagte in Test Adapter KNX v2.x:
@dutchman ja, das wäre gut, wenn wir die InfluxDB über Aliase umhängen könnten. Die Skripte habe ich gestern bereits geändert und als Visu habe ich eine native KNX Umgebung, da gibts nichts zu tun.
Wie wollen wir vorgehen? Bin gerne bereit dich hier im Forum, also das wir die Schritte durchgehen auch zum mitlesen für anderen, oder per discord/Teams dabei zu unterstützen
-
Hallo zusammen
enventuel gibt es ja hier eine ANtwort zu meinem Problem:ich habe in meinem KNX Projekt über die Jahre einige GAs umbenannt oder gelöscht, im Objektbaum des ioBroker sind aber noch alle vorhanden und noch schlimmer ist, dass umbenannte GAs quasi nochmal im Objektbaum angelegt werden aber das neue Objekt hört nicht auf die GA, sondern immer das alte.
Das möchtre ich gern so einfach wie möglich bereinigen.
Welche Optionen habe ich dafür?
ganzen KNX adapter Objektbaum löschen und neu anlegen? Bleiben dabei verbindungen zB in Blockly bestehen oder muss ich alle neu anlegen?
Gibt es bessere Möglichkeiten? über 2000 GAs einzeln durchgehen ist sehr ineffektiv. -
@mibr85 ich denke die einfachste Methode ist tatsächlich ganzen Baum löschen und Instanz neu starten.
Die Objekte in den Blockly werden beibehalten.
Eine andere Variante wäre ein Script zu schreiben um im KNX Baum nach Objekten zu suchen die seit einem bestimmten Datum nie mehr aktualisiert wurden. Sicher aufwändiger und je nachdem nicht so zuverlässig wie das löschen des Baums
-
@marlan99 said in Test Adapter KNX v2.x:
@mibr85 ich denke die einfachste Methode ist tatsächlich ganzen Baum löschen und Instanz neu starten.
Die Objekte in den Blockly werden beibehalten.
Eine andere Variante wäre ein Script zu schreiben um im KNX Baum nach Objekten zu suchen die seit einem bestimmten Datum nie mehr aktualisiert wurden. Sicher aufwändiger und je nachdem nicht so zuverlässig wie das löschen des Baums
Ich habe das selbe Problem. Ich habe das löschen und neu anlegen lassen mal versucht(IOB Kopie) ging leider schief.
In vielen KNX Datenpunkten waren die Flags danach falsch. Bei knapp 1000DP machts das keinen Spaß. Solch eine Funktion gehört in den Adapter rein.
-
@mpl1338 wenn die Flags nach dem Import falsch sind, dann ist es bereits in der ETS nicht korrekt gesetzt. Ist eine Mordsarbeit, aber seither passt es bei jedem Import perfekt.
-
@marlan99
wie genau bist du denn vorgegangen beim setzen deiner Flags?
welche KOs haben bei dir welche Flags bekommen? -
Hier meine Notizen, die ich dann in der ETS konsequent angewendet hatte. Die Info habe ich vom KNX Adapter Entwickler irgendwo in den Weiten des Internets gefunden.
KNX Flags
Pro Datenobjekt darf nur 1 Leseflag gesetzt sein !!!
Standard Flags:
-Lichttaster: S Ü A
-Lichttaster LED: S A
-Taster sperre: S
-Lichtaktor Schalten: S
-Lichtaktor Schaltstatus: L Ü-Rollladentaster: S Ü
-Rollladenaktor Schalten: S (A)
-Rollladenaktor Stati: L Ü (A)———————————————————-
K-Flag: Kommunikation ist eingeschaltetL-Flag:
S-Flag: LED soll geschaltet werden, wenn jemand auf den Bus schreibt
Ü-Flag: Sollte die LED irgendwie intern geschaltet werden, zum Beispiel durch drücken einer Taste, soll der Zustand auf den Bus geschrieben (übertragen) werden.
A-Flag: Falls ein Gerät auf dem Bus die Adresse abfragt (also liest) soll der Zustand der LED auch Aktualisiert werden.
—————————————————
ioBroker KNX Importregeln
-
@marlan99 said in Test Adapter KNX v2.x:
@mpl1338 wenn die Flags nach dem Import falsch sind, dann ist es bereits in der ETS nicht korrekt gesetzt. Ist eine Mordsarbeit, aber seither passt es bei jedem Import perfekt.
eben nicht
8 GAs', 8 Aktorausgänge 1/1/0 - 1/1/7(DT 1001), Status 6/1/0 - 6/1/7(DT 1011) und trotzdem schafft es der Adapter den ein oder anderen Ausgang als Eingang zu deklaieren.
Mit Rollläden hatte ich die meisten Probleme.
Rollladen Zimmer XXX fahren absolute Position (flag schreiben )
Rollladen Zimmer XXX status absolute Position (flag lesen/übertragen)nach dem Import kann ich "fahren absolute Position" nicht mehr beschreiben
-
@dutchman
Ich habe das Problem jetzt zusammen mit chefkoch009 gelöst;
irgendwo gab es ein Problem beim Import meiner GAs auf Grund von falsch gesetzten Flags in der ETS;
Wir haben die kompletten GAs der 0er Instanz gelöscht Flags korrigiert und neu eingelesen; die Influx-DB habe ich somit auch wieder an die alten Datenpunkte hängen können.
Vielen Dank trotzdem für eure Unterstützung! -
@blacksheep587 sagte in Test Adapter KNX v2.x:
@dutchman
Ich habe das Problem jetzt zusammen mit chefkoch009 gelöst;
irgendwo gab es ein Problem beim Import meiner GAs auf Grund von falsch gesetzten Flags in der ETS;
Wir haben die kompletten GAs der 0er Instanz gelöscht Flags korrigiert und neu eingelesen; die Influx-DB habe ich somit auch wieder an die alten Datenpunkte hängen können.
Vielen Dank trotzdem für eure Unterstützung!super freut mich und damit auch vielen dank an @ChefSache fuer den support
-
Hallo Zusammen
ich habe ein Problem mit meinem KNX Adapter:
alle 5-10 Tage habe ich festgestellt, dass die CPU Last meines Synology NAS (ioBroker läuft hierauf im Docker) plötzlich um 20-30% ansteigt.
Jetzt habe ich im Ressourcenmanager geschaut was diesen Anstieg auslöst:
Wenn ich die KNX Instanz im ioBroker stoppe, läuft dieser Prozess trotzdem weiter.
wenn ich die KNX Instanz neustarte wird ein neuer Prozess gestartet:
so sieht es im Docker aus:
ich konnte den Prozess nur mit sudo kill -9 io.knx.0 stoppen
Wie kann ich den Prozess stoppen?
Wie kann ich herausfinden was zu diesem verhalten führt?Auszug aus iob diag:
Skript v.2023-10-10 *** BASE SYSTEM *** Hardware Vendor : Synology Kernel : x86_64 Userland : amd64 Docker : v9.0.1 Virtualization : Docker Kernel : x86_64 Userland : amd64 Systemuptime and Load: 02:36:03 up 13 days, 16:08, 0 user, load average: 1.24, 2.29, 3.05 CPU threads: 4 *** Time and Time Zones *** Mon Dec 11 01:36:03 UTC 2023 Mon Dec 11 02:36:03 CET 2023 CET +0100 Etc/UTC *** User and Groups *** root /root root *** X-Server-Setup *** X-Server: false Desktop: Terminal: *** MEMORY *** total used free shared buff/cache available Mem: 8.2G 4.0G 259M 182M 4.4G 4.2G Swap: 7.1G 1.8G 5.3G Total: 15G 5.7G 5.6G 7802 M total memory 3797 M used memory 3200 M active memory 2819 M inactive memory 247 M free memory 16 M buffer memory 4211 M swap cache 6731 M total swap 1673 M used swap 5058 M free swap *** FILESYSTEM *** Filesystem Type Size Used Avail Use% Mounted on /dev/mapper/cachedev_0 btrfs 5.3T 3.4T 2.0T 64% / tmpfs tmpfs 64M 0 64M 0% /dev tmpfs tmpfs 3.9G 0 3.9G 0% /sys/fs/cgroup shm tmpfs 64M 0 64M 0% /dev/shm /dev/mapper/cachedev_0 btrfs 5.3T 3.4T 2.0T 64% /opt/iobroker tmpfs tmpfs 3.9G 0 3.9G 0% /proc/acpi tmpfs tmpfs 3.9G 0 3.9G 0% /proc/scsi tmpfs tmpfs 3.9G 0 3.9G 0% /sys/firmware Messages concerning ext4 filesystem in dmesg: [Mon Nov 27 10:27:58 2023] EXT4-fs (md0): couldn't mount as ext3 due to feature incompatibilities [Mon Nov 27 10:27:58 2023] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null) [Mon Nov 27 10:27:58 2023] EXT4-fs (md0): couldn't mount as ext3 due to feature incompatibilities [Mon Nov 27 10:27:58 2023] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: barrier=1 [Mon Nov 27 10:27:58 2023] EXT4-fs (sdd2): couldn't mount as ext3 due to feature incompatibilities [Mon Nov 27 10:27:58 2023] EXT4-fs (sdd2): mounted filesystem with ordered data mode. Opts: (null) [Mon Nov 27 10:29:23 2023] EXT4-fs (md0): couldn't mount as ext3 due to feature incompatibilities [Mon Nov 27 10:29:23 2023] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null) [Mon Nov 27 10:29:23 2023] EXT4-fs (md0): couldn't mount as ext3 due to feature incompatibilities [Mon Nov 27 10:29:23 2023] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: barrier=1 Show mounted filesystems \(real ones only\): TARGET SOURCE FSTYPE OPTIONS / /dev/mapper/cachedev_0[/@syno/@docker/btrfs/subvolumes/1ced23e2edec353cde2fe4d9270f5dcb50e5ee8b10733174734586bded77cb77] btrfs rw,nodev,relatime,ssd,synoacl,space_cache=v2,auto_reclaim_space,metadata_ratio=50,syno_allocator,subvolid=865,subvol=/@syno/@docker/btrfs/subvolumes/1ced23e2edec353cde2fe4d9270f5dcb50e5ee8b10733174734586bded77cb77 |-/opt/iobroker /dev/mapper/cachedev_0[/@syno/@docker/volumes/iobrokerVolume/_data] btrfs rw,nodev,relatime,ssd,synoacl,space_cache=v2,auto_reclaim_space,metadata_ratio=50,syno_allocator,subvolid=257,subvol=/@syno |-/etc/resolv.conf /dev/mapper/cachedev_0[/@syno/@docker/containers/2d62f9c4b750cc523ec5c6240dcefc599d288730892369546e93bb18b849868b/resolv.conf] btrfs rw,nodev,relatime,ssd,synoacl,space_cache=v2,auto_reclaim_space,metadata_ratio=50,syno_allocator,subvolid=257,subvol=/@syno |-/etc/hostname /dev/mapper/cachedev_0[/@syno/@docker/containers/2d62f9c4b750cc523ec5c6240dcefc599d288730892369546e93bb18b849868b/hostname] btrfs rw,nodev,relatime,ssd,synoacl,space_cache=v2,auto_reclaim_space,metadata_ratio=50,syno_allocator,subvolid=257,subvol=/@syno `-/etc/hosts /dev/mapper/cachedev_0[/@syno/@docker/containers/2d62f9c4b750cc523ec5c6240dcefc599d288730892369546e93bb18b849868b/hosts] btrfs rw,nodev,relatime,ssd,synoacl,space_cache=v2,auto_reclaim_space,metadata_ratio=50,syno_allocator,subvolid=257,subvol=/@syno Files in neuralgic directories: /var: 34M /var/ 32M /var/lib 19M /var/lib/apt/lists 19M /var/lib/apt 13M /var/lib/dpkg /opt/iobroker/backups: 38M /opt/iobroker/backups/ /opt/iobroker/iobroker-data: 368M /opt/iobroker/iobroker-data/ 224M /opt/iobroker/iobroker-data/files 84M /opt/iobroker/iobroker-data/backup-objects 67M /opt/iobroker/iobroker-data/files/javascript.admin 48M /opt/iobroker/iobroker-data/files/javascript.admin/static The five largest files in iobroker-data are: 36M /opt/iobroker/iobroker-data/objects.jsonl 33M /opt/iobroker/iobroker-data/files/iot.admin/static/js/main.1797d034.js.map 26M /opt/iobroker/iobroker-data/states.jsonl 21M /opt/iobroker/iobroker-data/files/web.admin/static/js/main.aaea95f8.js.map 18M /opt/iobroker/iobroker-data/files/text2command.admin/static/js/main.274a4d8d.js.map USB-Devices by-id: USB-Sticks - Avoid direct links to /dev/* in your adapter setups, please always prefer the links 'by-id': find: '/dev/serial/by-id/': No such file or directory *** NodeJS-Installation *** /usr/bin/nodejs v18.18.2 /usr/bin/node v18.18.2 /usr/bin/npm 9.8.1 /usr/bin/npx 9.8.1 /usr/bin/corepack 0.19.0 nodejs: Installed: 18.18.2-1nodesource1 Candidate: 18.18.2-1nodesource1 Version table: *** 18.18.2-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 100 /var/lib/dpkg/status 18.18.1-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.18.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.17.1-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.17.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.16.1-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.16.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.15.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.14.2-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.14.1-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.14.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.13.0+dfsg1-1 500 500 http://deb.debian.org/debian bookworm/main amd64 Packages 18.13.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.12.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.11.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.10.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.9.1-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.9.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.8.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.7.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.6.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.5.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.4.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.3.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.2.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.1.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.0.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages Temp directories causing npm8 problem: 0 No problems detected Errors in npm tree: *** ioBroker-Installation *** ioBroker Status iobroker is running on this host. Objects type: jsonl States type: jsonl Core adapters versions js-controller: 5.0.16 admin: 6.12.0 javascript: 7.1.6 Adapters from github: 0 Adapter State + system.adapter.admin.0 : admin : MIBR-DS - enabled, port: 8081, bind: 0.0.0.0, run as: admin + system.adapter.backitup.0 : backitup : MIBR-DS - enabled + system.adapter.discovery.0 : discovery : MIBR-DS - enabled + system.adapter.doorbird.0 : doorbird : MIBR-DS - enabled + system.adapter.e3dc-rscp.0 : e3dc-rscp : MIBR-DS - enabled + system.adapter.gruenbeck.0 : gruenbeck : MIBR-DS - enabled + system.adapter.hue.0 : hue : MIBR-DS - enabled, port: 443 + system.adapter.hue.1 : hue : MIBR-DS - enabled, port: 443 system.adapter.ical.0 : ical : MIBR-DS - enabled + system.adapter.info.0 : info : MIBR-DS - enabled + system.adapter.iot.0 : iot : MIBR-DS - enabled + system.adapter.javascript.0 : javascript : MIBR-DS - enabled + system.adapter.klf200.0 : klf200 : MIBR-DS - enabled system.adapter.knx.0 : knx : MIBR-DS - disabled system.adapter.lg-thinq.0 : lg-thinq : MIBR-DS - disabled + system.adapter.mihome-vacuum.0 : mihome-vacuum : MIBR-DS - enabled, port: 54321 + system.adapter.mqtt-client.0 : mqtt-client : MIBR-DS - enabled, port: 1883 system.adapter.node-red.0 : node-red : MIBR-DS - disabled, port: 1880, bind: 0.0.0.0 + system.adapter.procon-ip.0 : procon-ip : MIBR-DS - enabled + system.adapter.pvforecast.0 : pvforecast : MIBR-DS - enabled + system.adapter.scenes.0 : scenes : MIBR-DS - enabled + system.adapter.shelly.0 : shelly : MIBR-DS - enabled, port: 1882, bind: 0.0.0.0 + system.adapter.statistics.0 : statistics : MIBR-DS - enabled + system.adapter.synology.0 : synology : MIBR-DS - enabled, port: 5001 + system.adapter.telegram.0 : telegram : MIBR-DS - enabled, port: 8443, bind: 0.0.0.0 + system.adapter.telegram.1 : telegram : MIBR-DS - enabled, port: 8443, bind: 0.0.0.0 + system.adapter.text2command.0 : text2command : MIBR-DS - enabled + system.adapter.unifi.0 : unifi : MIBR-DS - enabled + system.adapter.viessmannapi.0 : viessmannapi : MIBR-DS - enabled + system.adapter.web.0 : web : MIBR-DS - enabled, port: 8082, bind: 0.0.0.0, run as: admin system.adapter.yahka.0 : yahka : MIBR-DS - disabled + instance is alive Enabled adapters with bindings + system.adapter.admin.0 : admin : MIBR-DS - enabled, port: 8081, bind: 0.0.0.0, run as: admin + system.adapter.hue.0 : hue : MIBR-DS - enabled, port: 443 + system.adapter.hue.1 : hue : MIBR-DS - enabled, port: 443 + system.adapter.mihome-vacuum.0 : mihome-vacuum : MIBR-DS - enabled, port: 54321 + system.adapter.mqtt-client.0 : mqtt-client : MIBR-DS - enabled, port: 1883 + system.adapter.shelly.0 : shelly : MIBR-DS - enabled, port: 1882, bind: 0.0.0.0 + system.adapter.synology.0 : synology : MIBR-DS - enabled, port: 5001 + system.adapter.telegram.0 : telegram : MIBR-DS - enabled, port: 8443, bind: 0.0.0.0 + system.adapter.telegram.1 : telegram : MIBR-DS - enabled, port: 8443, bind: 0.0.0.0 + system.adapter.web.0 : web : MIBR-DS - enabled, port: 8082, bind: 0.0.0.0, run as: admin ioBroker-Repositories stable : http://download.iobroker.net/sources-dist.json beta : http://download.iobroker.net/sources-dist-latest.json Active repo(s): stable Installed ioBroker-Instances Used repository: stable Adapter "admin" : 6.12.0 , installed 6.12.0 Adapter "backitup" : 2.8.7 , installed 2.8.7 Adapter "discovery" : 4.2.0 , installed 4.2.0 Adapter "doorbird" : 1.3.0 , installed 1.3.0 Adapter "e3dc-rscp" : 1.2.5 , installed 1.2.5 Adapter "gruenbeck" : 0.0.42 , installed 0.0.42 Adapter "hue" : 3.10.1 , installed 3.10.1 Adapter "ical" : 1.13.3 , installed 1.13.3 Adapter "info" : 2.0.0 , installed 2.0.0 Adapter "iot" : 2.0.11 , installed 2.0.11 Adapter "javascript" : 7.1.6 , installed 7.1.6 Controller "js-controller": 5.0.16 , installed 5.0.16 Adapter "klf200" : 1.1.2 , installed 1.1.2 Adapter "knx" : 2.0.23 , installed 2.0.23 Adapter "lg-thinq" : 0.1.4 , installed 0.1.4 Adapter "mihome-vacuum": 4.1.0 , installed 4.1.0 Adapter "mqtt-client" : 1.7.0 , installed 1.7.0 Adapter "node-red" : 4.0.3 , installed 4.0.3 Adapter "procon-ip" : 1.5.1 , installed 1.5.1 Adapter "pvforecast" : 2.9.0 , installed 2.9.0 Adapter "scenes" : 2.3.9 , installed 2.3.9 Adapter "shelly" : 6.6.1 , installed 6.6.1 Adapter "simple-api" : 2.7.2 , installed 2.7.2 Adapter "socketio" : 6.6.0 , installed 6.6.0 Adapter "statistics" : 2.4.0 , installed 2.4.0 Adapter "synology" : 3.0.1 , installed 3.0.1 Adapter "telegram" : 3.0.0 , installed 3.0.0 Adapter "text2command" : 3.0.2 , installed 3.0.2 Adapter "unifi" : 0.6.6 , installed 0.6.6 Adapter "viessmannapi" : 2.3.0 , installed 2.3.0 Adapter "web" : 6.1.10 , installed 6.1.10 Adapter "ws" : 2.5.8 , installed 2.5.8 Adapter "yahka" : 1.0.3 , installed 1.0.3 Objects and States Please stand by - This may take a while Objects: 32437 -
Wenn der Adapter normal läuft schreiben mir diese meldungen den Log voll, wie kann ich die meldungen interpretieren und vermeiden:
-
@mibr85 die "NOT CONNECTED" Meldungen habe ich mit der aktuellsten KNX Adapter Version auch immer wieder einmal, allerdings nicht so sehr häufig. Die Instanz verbindet sich dann auch wieder und läuft weiter.
Die zwei Meldungen im Log "Value received on unknown GA" bedeutet, dass auf diesem GA (7/1/12) etwas gesendet wurde, in deiner knx Instanz auf dem iob aber nicht bekannt sind. Hier evtl. das ETS Projekt noch einmal importieren und die Option aktivieren, dass nur die neuen GA übernommen werden.
Dein Problem mit einem hängenden Prozess konnte ich bei mir allerdings bisher noch nie feststellen (iob auf Raspi 4B)
-
Leider kommt es immer wieder dazu, dass sich der KNX Adapter, wie oben beschrieben aufhängt.
Wie kann ich denn eine tiefere Diagnose durchführen um den Fehler zu finden?
