knxd with tpuart busware and sending address w or w/o ETS increases

[K.I. T.T.]

Hi,

I installed knxd and status seems to be oK.

But when I am sending a groupswrite to a group address the sending address is increasing continuously. This can be seen at groupocketlisten as well as in bus/group monitor in ETS.

in /etc/knxd.conf my line shows:

KNXD_OPTS="-e 0.0.1 -E 1.1.1:210 -u /tmp/eib -D -T -R -S -b tpuarts:/dev/knx1"

IN addition, the found knxd interface is frequently found and lost in ETS.

Do you have any explications?

Best regards,

Peter

[K.I. T.T.]

I forgot: I installed on Raspberry 4 with buster

[Matthias Urlichs]

> Do you have any explications?

"Explanations". :-P

You have allocated 210 addresses to clients. knxd cycles through them. This is intentional (if you're doing messages to physical addresses you don't want to get misdirected replies) and not a problem.

I have no idea why your ETS loses the interface. It's not supposed to (obviously) and I don't experience that here.

[K.I. T.T.]

Ha ha "explication". My brain is still in year end mode ;-).

The configuration of my physical addresses had been made by my former owner of my flat. He has chosen 1.1.1.-1.1.18 for Sensors, 1.1.19 for Smart Terminal, 1.1.20 for Heating actor, 1.1.21 in ETS (but not used I believe), 1.1.22 shutter actor , 1.1.23 alarm actor (not in use I believe), 1.1.111-1.1.121 for dimming actors, 1.1.151-1.1.153 for shutter actors and 1.1.201-1.1.204 for switching actors.

That's why I had chosen 1.1.1.-1.1.210 physical addresses.

Is it possible to configure knxd correspondingly to my situation or can I only define subsequent addresses?

But my problem I wanted to describe was something different: When I repeat my groupswrite several times, for each telegram the knxd groupsocketlisten shows a new subsequent increasing physical address as sending address (from 1.1.4 to 1.1.8 in the enclosed picture) as sending address although -e is 0.0.1. In ETS the host physical address is shown as 0.0.1 and the physical address is chosen by ETS as 1.1.1. Is this behaviour normal? Or is there a wrong configuration? Can you help me?

Many thanks for your reply.

Peter

[Matthias Urlichs]

Hi,

> The configuration of my physical addresses had been made by my former owner of my flat. He has chosen 1.1.1.-1.1.18 for Sensors, 1.1.19 for Smart Terminal, 1.1.20 for Heating actor, 1.1.21 in ETS (but not used I believe), 1.1.22 shutter actor , 1.1.23 alarm actor (not in use I believe), 1.1.111-1.1.121 for dimming actors, 1.1.151-1.1.153 for shutter actors and 1.1.201-1.1.204 for switching actors.

>

> That's why I had chosen 1.1.1.-1.1.210 physical addresses.

You didn't read and/or understand the documentation and/or you need to supply a patch to clarify it.

Addresses must not overlap. Please use '-E 0.0.2:30' or whatever.

[K.I. T.T.]

I understood that I have to configure knxd corresponding to my existing topology of my KNX installation. and -E shall reflect this installation. That's why I had chosen 1.1.1-1.1.210.

What did I wrong?

[trun...@bluewin.ch]

You have a wrong understanding of -E, please read and follow what Matthias has written. knxd operates its own set of physical addresses which must not collide with the physical addresses on the bus. Therefore it does not matter what address knxd uses when sending messages.

[K.I. T.T.]

Thanks a lot to both of you. I was trying and searching since more than a week. No it works. :-) Thanks again.

I definitely understood it wrong.