estbeetoo / node-red-contrib-knx Goto Github PK

Everytime i try to send a msg to the output node, node-red crashes with this error message:

19 Jun 21:08:57 - [red] Uncaught Exception:
19 Jun 21:08:57 - TypeError: callback is not a function
at SendWrap.cb as callback (C:\Users\KNX\AppData\Roaming\npm\node_modules\node-red-contrib-knx\node_modules\knx.js\src\KnxSenderTunneling.js:40:21)
at SendWrap.afterSend as oncomplete (dgram.js:347:8)

I also tried a setup with just a test injection and it still crashes with the error above, as soon as i try to inject the msg.

Everything else (KNX connection itself & input node) is working fine.

Used version:

19 Jun 21:14:53 - [info] Node-RED version: v0.13.4
19 Jun 21:14:53 - [info] Node.js version: v4.4.5
19 Jun 21:14:53 - [info] Windows_NT 6.1.7600 x64 LE

Any help would be greatly appreciated!

Hi,

my installation runs fine for a while and the connection to the KNX Bus works without problems. After a while the connection drops and the following error is displayed:

groupAddrSend error: Error [ERR_SOCKET_DGRAM_NOT_RUNNING]: Not running
    at healthCheck (dgram.js:919:11)
    at Socket.send (dgram.js:643:3)
    at KnxSenderTunneling.SendData (/home/pi/.node-red/node_modules/knx.js/src/KnxSenderTunneling.js:43:21)
    at KnxSenderTunneling.KnxSender.Action (/home/pi/.node-red/node_modules/knx.js/src/KnxSender.js:9:10)
    at KnxConnectionTunneling.KnxConnection.Action (/home/pi/.node-red/node_modules/knx.js/src/KnxConnection.js:120:20)     
    at /home/pi/.node-red/node_modules/node-red-contrib-knx/knx.js:310:37
    at KnxControllerNode.initializeKnxConnection (/home/pi/.node-red/node_modules/node-red-contrib-knx/knx.js:37:21)
    at KnxOut.groupAddrSend (/home/pi/.node-red/node_modules/node-red-contrib-knx/knx.js:292:27)
    at KnxOut._inputCallback (/home/pi/.node-red/node_modules/node-red-contrib-knx/knx.js:107:18)
    at /usr/lib/node_modules/node-red/node_modules/@node-red/runtime/lib/nodes/Node.js:203:26 
{   code: 'ERR_SOCKET_DGRAM_NOT_RUNNING' }

Hi,

Found an issue when group addresses are higher than 15.

Example 1:
Using the KNX Output node, writing to group address 28/1/1 returns a groupAddrSend error and does not output anything on the KNX bus. This is the payload used: {"dstgad":"28/1/1", "dpt":"1", "value":1 }

Example 2:
Using the KNX Input node, a telegram send to 28/1/1 by a physical KNX actor ( in this case 15.15.251 is the address of the tunnelling adapter) is received as: {"srcphy":"15.15.251","dstgad":"12/1/1","dpt":"no_dpt","value":"1","type":"event"}
The address is misinterpreted as 12/1/1 instead of 28/1/1. Note the difference is 16 or 2^4.

Some investigation shows this behaviour is the same for all group address with a main above 15 (ie. 16/0/0 and higher). This is probably due to not correctly handling bit D15 in the KNX telegram (that is the 16th bit in the address). First generation devices didn't support the full 16-bit group address range, at that time bit D15 was 'reserved', but that was 15 years ago :-). Today all devices support it an it gets used frequently.

Best regards,
Swake

Hello

When I add my KNX Both IN and OUT nodes only KNX IN node works, it passes all data, all bus commands are displayed. But I cant send commands to KNX OUT node, when i try i get
27 Sep 07:07:56 - [info] [knx-out:Out] groupAddrSend action[write] dstgad:0/2/3, value:1, dpt:1 27 Sep 07:07:56 - [info] [knx-controller:BAOS777] already connected to knxjs server at 192.168.1.60:3671 in mode[tunnel/unicast]

When I delete KNX IN node, KNX OUT node works fine

27 Sep 07:20:17 - [info] Node-RED version: v0.17.5 27 Sep 07:20:17 - [info] Node.js version: v6.11.3 27 Sep 07:20:17 - [info] Linux 4.9.41-v7+ arm LE

I suppose i'm missing something?
ps flow export
[{"id":"14e27b21.883a85","type":"tab","label":"KNX","disabled":false,"info":""},{"id":"a9221435.2fe868","type":"knx-out","z":"14e27b21.883a85","name":"Out","controller":"40bc1d5d.22bf14","x":290,"y":100,"wires":[]},{"id":"9434c14b.2e807","type":"inject","z":"14e27b21.883a85","name":"","topic":"write","payload":"{\"srcphy\":\"1.1.3\",\"dstgad\":\"0/2/5\",\"dpt\":\"1\",\"value\":\"0\",\"type\":\"event\"}","payloadType":"json","repeat":"","crontab":"","once":false,"x":90,"y":100,"wires":[["a9221435.2fe868","88718a66.6c0a28"]]},{"id":"6d5c1c5e.f5f334","type":"debug","z":"14e27b21.883a85","name":"","active":true,"console":"false","complete":"false","x":350,"y":260,"wires":[]},{"id":"9e434a37.effeb8","type":"switch","z":"14e27b21.883a85","name":"","property":"payload.srcphy","propertyType":"msg","rules":[{"t":"eq","v":"1.1.3","vt":"str"},{"t":"eq","v":"1.1.25","vt":"str"},{"t":"nnull"}],"checkall":"false","outputs":3,"x":203.10000610351562,"y":336.20001220703125,"wires":[["6d5c1c5e.f5f334"],["155edfa3.9a2b4"],["b914b986.2a9178"]]},{"id":"155edfa3.9a2b4","type":"debug","z":"14e27b21.883a85","name":"","active":true,"console":"false","complete":"false","x":370,"y":300,"wires":[]},{"id":"438785fb.38270c","type":"inject","z":"14e27b21.883a85","name":"","topic":"write","payload":"{\"srcphy\":\"1.1.3\",\"dstgad\":\"0/2/5\",\"dpt\":\"1\",\"value\":\"1\",\"type\":\"event\"}","payloadType":"json","repeat":"","crontab":"","once":false,"x":90,"y":140,"wires":[["a9221435.2fe868","88718a66.6c0a28"]]},{"id":"b914b986.2a9178","type":"debug","z":"14e27b21.883a85","name":"","active":false,"console":"false","complete":"false","x":353.1000061035156,"y":365.20001220703125,"wires":[]},{"id":"88718a66.6c0a28","type":"debug","z":"14e27b21.883a85","name":"","active":true,"console":"false","complete":"payload","x":410,"y":20,"wires":[]},{"id":"34303f19.38944","type":"inject","z":"14e27b21.883a85","name":"","topic":"write","payload":"{\"dstgad\":\"0/2/3\",\"value\":0,\"dpt\":1}","payloadType":"json","repeat":"","crontab":"","once":false,"x":90,"y":60,"wires":[["88718a66.6c0a28","a9221435.2fe868"]]},{"id":"943c998c.714ca8","type":"inject","z":"14e27b21.883a85","name":"","topic":"write","payload":"{\"dstgad\":\"0/2/3\",\"value\":1,\"dpt\":1}","payloadType":"json","repeat":"","crontab":"","once":false,"x":90,"y":20,"wires":[["88718a66.6c0a28","a9221435.2fe868"]]},{"id":"6b1117c4.0f3428","type":"inject","z":"14e27b21.883a85","name":"","topic":"write","payload":"{\"dstgad\":\"0/2/3\",\"dpt\":\"1\"}","payloadType":"json","repeat":"","crontab":"","once":false,"x":90,"y":180,"wires":[["88718a66.6c0a28","a9221435.2fe868"]]},{"id":"16bb3659.cc6dda","type":"knx-in","z":"14e27b21.883a85","name":"","controller":"40bc1d5d.22bf14","x":60,"y":291,"wires":[["9e434a37.effeb8"]]},{"id":"40bc1d5d.22bf14","type":"knx-controller","z":"","name":"BAOS777","host":"192.168.1.60","port":"3671","mode":"tunnel/unicast"}]

may you put the DPT list on your wiki?
its of help with knx...

i googled them for me:
https://github.com/andreek/node-eibd
http://www.loxone.com/dede/service/dokumentation/loxone-config/eib-knx/datentypen.html

Is it possible to add these two?

Guys thanks for great work

Testing with old Gira 1030 - (Siemens clone) works well so far.
Have a BAOS771 too so will test later with that.
And if I can blag one, will try it with latest Gira IP interface

One small issue function node example shows "dpt":"DPT1", should be an integer "dpt":1,

var knxmsg = {  
   "topic":"write",
   "payload":{  
      "srcphy":"1.1.100",
      "dstgad":"15/1/0",
      "dpt":1,
      "value":1
   }
}
return knxmsg;

Hello! I get an error when I try to send a DPT9 float value, DPT1 and 5 work!

Thank you for your work, this is exactly what I needed for my home automation!

12 Sep 15:56:19 - [info] [knx-out:ee54a9f7.d0b0e8] knxout.onInput, msg[{ topic: '',
payload: { dstgad: '2/2/3', value: '23.1', dpt: '9' },
_msgid: 'b1f39066.4e0c7' }]
12 Sep 15:56:19 - [info] [knx-out:ee54a9f7.d0b0e8] groupAddrSend action[write] dstgad:2/2/3, value:23.1, dpt:9
12 Sep 15:56:19 - [info] [knx-controller:3d6dbfcc.b2ac48] connecting to knxjs server at 192.168.0.11:3671 in mode[tunnel/unicast]
12 Sep 15:56:19 - [info] [knx-out:ee54a9f7.d0b0e8] sendAPDU: 23.1
12 Sep 15:56:19 - [error] [knx-out:ee54a9f7.d0b0e8] error calling groupAddrSend: TypeError: Cannot read property 'writeFloatLE' of null
12 Sep 15:56:19 - [error] [knx-out:ee54a9f7.d0b0e8] groupAddrSend error: [TypeError: Cannot read property 'writeFloatLE' of null]
12 Sep 15:56:19 - [info] [knx-controller:3d6dbfcc.b2ac48] Knx: successfully connected to 192.168.0.11:3671 in mode[tunnel/unicast]

I like to write a knx address to the bus so i add a injector with the following json payload:
{"dstgad":"2/1/19", "value":"0", "dpt":"1"}

But then i receive an error, see atteched screenshot.

How to solve this?

Thanks for this great node!
But after using it for about 2 years now, i can't control the lights in my house anymore from Node-Red.

Issue:

After updating nodejs 10.x.x to nodejs 11.6.0 (11.7.0 now) the KNX-out gives errors when sending a message. KNX-in works though.

Setup:

I'm running Node-Red on a raspberry pi2 and an orangepipc. Both have an up to date Arch linux installation.

Topic: knx:write
Payload: { "srcphy": "15.15.249", "dstgad": "1/1/51", "dpt": "1", "value": "1", "type": "event" }

Errors:

Jan 20 02:57:56 orangepipc Node-RED[282]: 20 Jan 02:57:56 - [error] [knx-out:KNX-out (tunnel)] error calling groupAddrSend: TypeError [ERR_INVALID_ARG_TYPE]: The "byteLength" argument must be of type number. Received type undefined
Jan 20 02:57:56 orangepipc Node-RED[282]: 20 Jan 02:57:56 - [error] [knx-out:KNX-out (tunnel)] groupAddrSend error: TypeError [ERR_INVALID_ARG_TYPE]: The "byteLength" argument must be of type number. Received type undefined
Jan 20 02:57:56 orangepipc Node-RED[282]: at validateNumber (internal/validators.js:130:11)
Jan 20 02:57:56 orangepipc Node-RED[282]: at boundsError (internal/buffer.js:51:5)
Jan 20 02:57:56 orangepipc Node-RED[282]: at Buffer.writeIntLE (internal/buffer.js:691:3)
Jan 20 02:57:56 orangepipc Node-RED[282]: at KnxConnectionTunneling.KnxConnection.Action (/home/nodered/node_modules/knx.js/src/KnxConnection.js:87:21)
Jan 20 02:57:56 orangepipc Node-RED[282]: at /home/nodered/node_modules/node-red-contrib-knx/knx.js:260:37
Jan 20 02:57:56 orangepipc Node-RED[282]: at KnxControllerNode.initializeKnxConnection (/home/nodered/node_modules/node-red-contrib-knx/knx.js:37:21)
Jan 20 02:57:56 orangepipc Node-RED[282]: at KnxOut.groupAddrSend (/home/nodered/node_modules/node-red-contrib-knx/knx.js:242:27)
Jan 20 02:57:56 orangepipc Node-RED[282]: at KnxOut.<anonymous> (/home/nodered/node_modules/node-red-contrib-knx/knx.js:107:18)
Jan 20 02:57:56 orangepipc Node-RED[282]: at KnxOut.emit (events.js:188:13)
Jan 20 02:57:56 orangepipc Node-RED[282]: at KnxOut.Node.receive (/home/nodered/node_modules/node-red/red/runtime/nodes/Node.js:215:14)
Jan 20 02:57:56 orangepipc Node-RED[282]: at InjectNode.Node.send (/home/nodered/node_modules/node-red/red/runtime/nodes/Node.js:137:22)
Jan 20 02:57:56 orangepipc Node-RED[282]: at InjectNode.<anonymous> (/home/nodered/node_modules/node-red/nodes/core/core/20-inject.js:78:26)
Jan 20 02:57:56 orangepipc Node-RED[282]: at InjectNode.emit (events.js:188:13)
Jan 20 02:57:56 orangepipc Node-RED[282]: at InjectNode.Node.receive (/home/nodered/node_modules/node-red/red/runtime/nodes/Node.js:215:14)
Jan 20 02:57:56 orangepipc Node-RED[282]: at /home/nodered/node_modules/node-red/nodes/core/core/20-inject.js:117:22
Jan 20 02:57:56 orangepipc Node-RED[282]: at Layer.handle [as handle_request] (/home/nodered/node_modules/express/lib/router/layer.js:95:5)

I hope this can be fixed, because i really don't know how to fix this myself.
Thanks very much

Edit:

Huumm, looks like i managed to debug this a bit myself.
It seems like the issue is in file KnxConnection.js from package knx.js line 87.
I changed buf.writeIntLE(data ? 1 : 0); to buf.writeInt8(data ? 1 : 0); and things seem to work again.
See this change to nodejs
Hopefully this is the right thing to change.

How to update status of a switch trigged by a phisical button?

• Create controller node to connect to failed (nont-exists, for example) KNX iface
• Deploy
• Reconfigure controller node to another one (working one) KNX iface
• Deploy
• Look at the log: it trying to connect to old one, failing KNX iface

Hi,

I'm testing the node on my project. When I pun only the "out node" on the flow it connects and communicates with the KNX bus without any problem. If I put only the "in node" it connects without problem but I'm not reading any data from the bus, Ok, the testing bus has only the power supply, gateway and switch actuator but no signals from them. Till now good as it can be.

But, when I set both nodes on the flow "in" and "out" (as is described) they don't connect to the bus.

The configuration is set for both as described: ip address 192.168.1.19, port 3671

What I'm doing wrong??

I'm using iKNiX gateway ver 2.

Is it possible to write a knx output as a function of a knx entry?
I want to create a (fictional) KNX-device in Node-RED that can send responses on read requests.

Thanks

hi,
wonderful module. i am playing with it.
not much in google about creating functions, i am not so good in programming.

😃 may you help me out with describing an example function to get the value
of a specific GA(group-adress) in a timed interval? 😃

the code of knx-parse function is a sample from another flow.
i wanted to modify it, but i am a little bit alone in space ....

anyhelp very appreciated, thhaaannks a lot...

I have installed the node-red plugin from the master branch but I have multiple issues.

At one point I was able to get it to connect and receive incoming telegrams just fine. However, after a few seconds it claimed to lose connection and tries to reconnect.

KnxReceiverTunneling: Received connection state response - No active connection with channel ID 0 udp sent, err[no_err]
connection stale, so disconnect and then try to reconnect again

But after that I seem to have two listeners since I now get to messages in the node-red flow for each telegram. From here on, I still see the same reconnection attempts in the log, however, the listeners never seem to increase above 2.

Now, after removing all Controllers in node-red and trying to start over it's even more confusing. It connects but I can only receive one certain datagram:
{ "topic": "knx:event", "payload": { "srcphy": "1.1.80", "dstgad": "4/1/15", "dpt": "no_dpt", "value": "0", "type": "event" }, "_msgid": "f9c1020f.063f" }. However, after adding debug logs to knx.js I see ProcessDatagram logs for all messages. But they don't seem to come through. And then, also, I get a whole bunch of cannot connect to knxjs server messages.

I'm so confused as how to get this plugin to properly connect to my KNX interface. I have two interfaces, one KNX Gateway/Router and one Eibport. I have tried both.

Hi guys

I've used to run knx.js with the version, that came with the node-red Ui palette installer. At that time, sent values with dpt 5.001 worked well. Some days ago i've pulled the latest one from the git repo and now those values stopped working.
Looking at the code, one would assume, that all dpt cases before 10 (time) run into this case and get interpreted as time input. Is this intended?

case '5':    //8-bit unsigned value               1 Byte                  EIS 6         DPT 5    0...255
case '5.001':    //8-bit unsigned value               1 Byte                  DPT 5.001    DPT 5.001    0...100
case '6':    //8-bit signed value                 1 Byte                  EIS 14        DPT 6    -128...127
case '7':    //16-bit unsigned value              2 Byte                  EIS 10        DPT 7    0...65535
case '8':    //16-bit signed value                2 Byte                  DPT 8         DPT 8    -32768...32767
case '10':   //Time                               3 Byte                  EIS 3         DPT 10    Day [0..7] Hour [0..23] Minutes [0..59] Seconds [0..59]
  var day = 0;

May I also kindly request to reopen issue 6 - I've added a comment there.
Thank you very much for your effort to this project!

Best
jo3ran

Node-Red flow:

[{"id":"42d0b1e5.a4a3c","type":"inject","z":"f1b75694.9fa55","name":"2/1/1 dim value 10%","topic":"write","payload":"{\"dstgad\":\"2/1/1\",\"dpt\":\"5\",\"value\":10}","payloadType":"str","repeat":"","crontab":"","once":false,"x":502,"y":220.79998779296875,"wires":[["a5e67070.b931e8","290ccdf7.86a14a"]]},{"id":"a5e67070.b931e8","type":"knx-out","z":"f1b75694.9fa55","name":"KNX OUT","controller":"3a1c430d.b6143c","x":842,"y":74,"wires":[]},{"id":"3a1c430d.b6143c","type":"knx-controller","z":"","name":"KNX Interface","host":"192.168.1.5","port":"3671","mode":"tunnel/unicast"}]

pi@emonpi(rw):~$ node -v
v6.10.0
pi@emonpi(rw):~$ npm -v
node3.10.10
pi@emonpi(rw):~$ node-red -v
26 Feb 20:39:01 - [info]

Welcome to Node-RED
===================

26 Feb 20:39:01 - [info] Node-RED version: v0.16.2
26 Feb 20:39:01 - [info] Node.js  version: v6.10.0
26 Feb 20:39:01 - [info] Linux 4.4.38-v7+ arm LE
26 Feb 20:39:02 - [info] Loading palette nodes

When I inject this node I get an error:

26-2-2017 21:39:36node: KNX OUTmsg : error
"ReferenceError: data is not defined"
26-2-2017 21:39:36node: 290ccdf7.86a14awrite : msg : Object
object
_msgid: "8fb84222.ae273"
topic: "write"
payload: "{"dstgad":"2/1/1","dpt":"5","value":10}"

When I use a DPT1 all is working fine, but DPT5 or DPT 5.001 isn't working.

Hello,

I'm running node-red (v0.15.3) in a Multitech Conduit Hardware, and it's returning the next error:

I did again a npm install

Then I restart de node-red and then the log command:

Here's the post in node-red forum for more information: https://discourse.nodered.org/t/remove-node-from-node-red/5217

Which could be the error?

Why is it that you set the DPT of received telegrams to no_dpt?

I wanted to install this node on fresh node-red but dependency was not found

28 verbose node v12.18.4
29 verbose npm v6.14.6
30 error code ETARGET
31 error notarget No matching version found for knx.js@^0.7.5.
32 error notarget In most cases you or one of your dependencies are requesting
32 error notarget a package version that doesn't exist.
32 error notarget
32 error notarget It was specified as a dependency of 'node-red-contrib-knx'

I cant read DPT values 14*

[{"id":"c9914937.ff4f2","type":"inject","z":"f49561bb.b5b9e8","name":"read status","topic":"read","payload":"{"dstgad":"4/0/0","dpt":"14"}","payloadType":"json","repeat":"","crontab":"","once":false,"x":101,"y":245,"wires":[["b9239637.2f38a8","ab0abf9b.e1f0f"]]}]

topic: 'read',
payload: { dstgad: '4/0/0', dpt: '14' } }]
25 Jan 23:36:44 - [info] [knx-out:b9239637.2f38a8] groupAddrSend action[read] dstgad:4/0/0, value:undefined, dpt:14
25 Jan 23:36:44 - [info] [knx-controller:cf83bf76.25995] already connected to knxjs server at 192.168.1.3:3671 in mode[tunnel/unicast]
25 Jan 23:36:44 - [info] [knx-out:b9239637.2f38a8] sendAPDU: undefined
25 Jan 23:36:49 - [info] [knx-out:b9239637.2f38a8] knxout.onInput, msg[{ _msgid: 'abaae82.abcea18',

Inject string:
{"dstgad":"0/1/0","dpt":"1","value":0}

8-11-2016 19:55:00Nieuwe KNX OUTmsg : string [75]error calling groupAddrSend: TypeError: Object � has no method 'writeIntLE'
8-11-2016 19:55:00Nieuwe KNX OUTmsg : string [69]groupAddrSend error: [TypeError: Object � has no method 'writeIntLE']

Node-RED flow:
[{"id":"61c0d192.cdc99","type":"knx-out","z":"b5ff6476.19e4b8","name":"Nieuwe KNX OUT","controller":"498caeb8.491b6","x":385,"y":85,"wires":[]},{"id":"e5cc3fd1.b1752","type":"inject","z":"b5ff6476.19e4b8","name":"write 0/1/0","topic":"write","payload":"{"dstgad":"0/1/0","dpt":"1","value":0}","payloadType":"json","repeat":"","crontab":"","once":false,"x":133,"y":85,"wires":[["61c0d192.cdc99"]]},{"id":"498caeb8.491b6","type":"knx-controller","z":"","name":"KNX IP Interface","host":"192.168.1.5","port":"3671","mode":"tunnel/unicast"}]

Any idea what I do wrong?

node v0.10.29
npm v1.4.21
Node-RED v0.15.2

Hello, it should be nice if user could choose to logs received and sent events like theses ones:

• https://github.com/estbeetoo/node-red-contrib-knx/blob/master/knx.js#L465 knx event gad
• https://github.com/estbeetoo/node-red-contrib-knx/blob/master/knx.js#L480 knx status gad
• https://github.com/estbeetoo/node-red-contrib-knx/blob/master/knx.js#L78 knxout.onInput, msg
• https://github.com/estbeetoo/node-red-contrib-knx/blob/master/knx.js#L178 groupAddrSend action

Maybe as a checkbox in the knx-controller (config) node "Log all events"? Or in knx-in and knx-out nodes?

I can dig on it and propose a merge request if you think is is a good idea. Let me know 😉

Hi, first - nice work! :) However I faced an issue. When the node can't connect to the KNX gateway for one reason or another (e.g. in my case the Weinzierl Ethernet gateway allows only one simultaneous connection and it was used) it gives this:

2015-09-08 07:32:18: new KnxControllerNode, config: {"id":"2f4a6847.d0b598","type":"knx-controller","host":"192.168.80.101","port":"3761","mode":"tunnel/unicast"}
2015-09-08 07:32:18: new KNX-IN, config: {"id":"ae26c971.51d938","type":"knx-in","name":"KNX IN","controller":"2f4a6847.d0b598","x":145,"y":229,"z":"26009041.d9ff7","wires":[["9d6e1baa.6291e8"]]}
2015-09-08 07:32:18: connecting to knxjs server at 192.168.80.101:3761 in mode[tunnel/unicast]
2015-09-08 07:32:18: new Knx-OUT, config: {"id":"38d3b5c8.c72c4a","type":"knx-out","name":"KNX OUT","controller":"2f4a6847.d0b598","x":681,"y":438,"z":"26009041.d9ff7","wires":[]}
8 Sep 10:32:18 - [info] Started flows
2015-09-08 07:32:23: connecting to knxjs server at 192.168.80.101:3761 in mode[tunnel/unicast]
2015-09-08 07:32:43: connecting to knxjs server at 192.168.80.101:3761 in mode[tunnel/unicast]
2015-09-08 07:33:03: connecting to knxjs server at 192.168.80.101:3761 in mode[tunnel/unicast]
2015-09-08 07:33:23: connecting to knxjs server at 192.168.80.101:3761 in mode[tunnel/unicast]
2015-09-08 07:33:43: connecting to knxjs server at 192.168.80.101:3761 in mode[tunnel/unicast]
2015-09-08 07:34:03: connecting to knxjs server at 192.168.80.101:3761 in mode[tunnel/unicast]
2015-09-08 07:34:23: connecting to knxjs server at 192.168.80.101:3761 in mode[tunnel/unicast]
2015-09-08 07:34:43: connecting to knxjs server at 192.168.80.101:3761 in mode[tunnel/unicast]
2015-09-08 07:35:03: connecting to knxjs server at 192.168.80.101:3761 in mode[tunnel/unicast]
(node) warning: possible EventEmitter memory leak detected. 11 connected listeners added. Use emitter.setMaxListeners() to increase limit.
Trace
    at KnxConnectionTunneling.addListener (events.js:179:15)
    at KnxConnectionTunneling.once (events.js:204:8)
    at KnxConnectionTunneling.Connect (/Users/Misho/.node-red/node_modules/node-red-contrib-knx/node_modules/knx.js/src/KnxConnectionTunneling.js:94:10)
    at null.<anonymous> (/Users/Misho/.node-red/node_modules/node-red-contrib-knx/node_modules/knx.js/src/KnxConnectionTunneling.js:90:22)
    at Timer.listOnTimeout (timers.js:110:15)
2015-09-08 07:35:23: connecting to knxjs server at 192.168.80.101:3761 in mode[tunnel/unicast]
(node) warning: possible EventEmitter memory leak detected. 11 event listeners added. Use emitter.setMaxListeners() to increase limit.
Trace
    at KnxConnectionTunneling.addListener (events.js:179:15)
    at /Users/Misho/.node-red/node_modules/node-red-contrib-knx/knx.js:275:29
    at /Users/Misho/.node-red/node_modules/node-red-contrib-knx/knx.js:57:29
    at KnxConnectionTunneling.<anonymous> (/Users/Misho/.node-red/node_modules/node-red-contrib-knx/node_modules/knx.js/src/KnxConnectionTunneling.js:84:25)
    at KnxConnectionTunneling.g (events.js:199:16)
    at KnxConnectionTunneling.emit (events.js:104:17)
    at /Users/Misho/.node-red/node_modules/node-red-contrib-knx/node_modules/knx.js/src/KnxConnectionTunneling.js:163:22
    at tryCallOne (/Users/Misho/.node-red/node_modules/node-red-contrib-knx/node_modules/knx.js/node_modules/promise/lib/core.js:37:12)
    at /Users/Misho/.node-red/node_modules/node-red-contrib-knx/node_modules/knx.js/node_modules/promise/lib/core.js:103:15
    at flush (/Users/Misho/.node-red/node_modules/node-red-contrib-knx/node_modules/knx.js/node_modules/promise/node_modules/asap/raw.js:50:29)
(node) warning: possible EventEmitter memory leak detected. 11 status listeners added. Use emitter.setMaxListeners() to increase limit.
Trace
    at KnxConnectionTunneling.addListener (events.js:179:15)
    at /Users/Misho/.node-red/node_modules/node-red-contrib-knx/knx.js:276:29
    at /Users/Misho/.node-red/node_modules/node-red-contrib-knx/knx.js:57:29
    at KnxConnectionTunneling.<anonymous> (/Users/Misho/.node-red/node_modules/node-red-contrib-knx/node_modules/knx.js/src/KnxConnectionTunneling.js:84:25)
    at KnxConnectionTunneling.g (events.js:199:16)
    at KnxConnectionTunneling.emit (events.js:104:17)
    at /Users/Misho/.node-red/node_modules/node-red-contrib-knx/node_modules/knx.js/src/KnxConnectionTunneling.js:163:22
    at tryCallOne (/Users/Misho/.node-red/node_modules/node-red-contrib-knx/node_modules/knx.js/node_modules/promise/lib/core.js:37:12)
    at /Users/Misho/.node-red/node_modules/node-red-contrib-knx/node_modules/knx.js/node_modules/promise/lib/core.js:103:15
    at flush (/Users/Misho/.node-red/node_modules/node-red-contrib-knx/node_modules/knx.js/node_modules/promise/node_modules/asap/raw.js:50:29)