# KNX write error by the node-red-contrib-knx node

**URL:** https://discourse.nodered.org/t/knx-write-error-by-the-node-red-contrib-knx-node/7798
**Category:** General
**Created:** [10 February 2019 11:10 UTC](https://discourse.nodered.org/t/knx-write-error-by-the-node-red-contrib-knx-node/7798 "2019-02-10T11:10:12Z")
**Posts on this page:** 5
**Page:** 1

<div class="post-metadata">

### Author: ![Rulevalley](https://avatars.discourse-cdn.com/v4/letter/r/3be4f8/32.png) [@Rulevalley](https://discourse.nodered.org/u/Rulevalley)
#### Post date: [10 February 2019 11:10 UTC](https://discourse.nodered.org/t/knx-write-error-by-the-node-red-contrib-knx-node/7798/1 "2019-02-10T11:10:12Z")

</div>

Hi.

I have a RPI3B and a KNX USB adaptor.  
Have installed a KNXD from micheals tech blog

> **[Raspberry Pi: EIB/KNX IP Gateway and Router with knxd](https://michlstechblog.info/blog/raspberry-pi-eibknx-ip-gateway-and-router-with-knxd/#comment-2665)**
>
> Hi,
> 
> in my previous posts EIB/KNX Router with an USB Interface and KNX/EIB Router with a TPUART module I described how to use a Raspberry PI as EIB/KNX Router with eibd.
> 
> eibd is no longer in development so I decided to give knxd, a fork of eibd, a...

Issue is that first message i Try to write to the bus, gives an error and connection timeout.

> Read failed: Connection reset by peer

Google could not help me, but I found a strange thing in the telegrams when i listen in on the traffic on the bus.

> LPDU: BC 11 04 06 00 E1 00 80 31 :L\_Data low from 1.1.4 to 0/6/0 hops: 06 T\_DATA\_XXX\_REQ A\_GroupValue\_Write (small) 00  
> LPDU: BC 11 85 06 04 F1 00 81 A5 :L\_Data low from 1.1.133 to 0/6/4 hops: 07 T\_DATA\_XXX\_REQ A\_GroupValue\_Write (small) 01  
> Read failed: Connection reset by peer  
> root@raspberrypi:/#

I see that the message get written to the bus, but with a different hops code ? What is this code, and where can i set this ?

Is this a known issue ? does anyone have a solution ?. Is it the problem ?

And even more strange, I managed to get this working for some messages, but now i will not operate at all.

---

<div class="post-metadata">

### Author: ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)
#### Post date: [10 February 2019 11:27 UTC](https://discourse.nodered.org/t/knx-write-error-by-the-node-red-contrib-knx-node/7798/2 "2019-02-10T11:27:33Z")

</div>

Is there a reason why you are running node-red as root? Generally that is not necessary and is considered a security risk as a deviant node or crash could write all over your operating system. Whether it might give problems for this node I don't know.

---

<div class="post-metadata">

### Author: ![ukmoose](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/ukmoose/32/13_2.png) [@ukmoose](https://discourse.nodered.org/u/ukmoose)
#### Post date: [10 February 2019 12:14 UTC](https://discourse.nodered.org/t/knx-write-error-by-the-node-red-contrib-knx-node/7798/3 "2019-02-10T12:14:34Z")

</div>

Given that the blog you linked to isn't a node-RED node, how are you linking to Node-RED?

Are you sure that it's a problem with Node-RED and not the knxd server you've installed?

---

<div class="post-metadata">

### Author: ![Rulevalley](https://avatars.discourse-cdn.com/v4/letter/r/3be4f8/32.png) [@Rulevalley](https://discourse.nodered.org/u/Rulevalley)
#### Post date: [14 February 2019 13:02 UTC](https://discourse.nodered.org/t/knx-write-error-by-the-node-red-contrib-knx-node/7798/4 "2019-02-14T13:02:15Z")

</div>

It`s running as root beacause I dont know better. I will look into it 😉

---

<div class="post-metadata">

### Author: ![Rulevalley](https://avatars.discourse-cdn.com/v4/letter/r/3be4f8/32.png) [@Rulevalley](https://discourse.nodered.org/u/Rulevalley)
#### Post date: [14 February 2019 13:06 UTC](https://discourse.nodered.org/t/knx-write-error-by-the-node-red-contrib-knx-node/7798/5 "2019-02-14T13:06:19Z")

</div>

I am trying to figure this out the best way I can.  
I am not sure off anything right now, I`m new to the whole thing.

But I found a way to avoid this issue. Because I was watching the buss activity and running Node red at the same time, they seem to fight over the same resources. When I do not view the bus activity at the same time as Node-red is running, It all works fine 🙂

Thanks for youre interest in helping me .
