KNX Create device Error

[jakub.jezek 370]

If I add device Called "Světlo JJ", I receive an error. If I add device with no diacritics, e.g. svetlo JJ, then it is correct.

 

It seems like the issue is in the name/diacritics, in my case character ě.

 

Device itself its added, but it then instantly looses any configuration I put in.

 

Error:

[12.02.2026] [14:21:29] [WARNING] [KNX]: [ZmqServer] Error while handling message[12.02.2026] [14:21:29]

[WARNING] [KNX]: [] Traceback (most recent call last): File "src/rpc/zmq_server.py", line 74, in handle_message_ File "src/device_management/device_service.py", line 89, in handle_action File "src/device_management/device_service.py", line 94, in call_action File "src/device_management/devices/device.py", line 48, in action File "src/device_management/devices/knx_engine.py", line 71, in action_ File "src/device_management/devices/knx_engine.py", line 125, in create_device File "src/device_management/device_service.py", line 32, in create_device File "src/device_management/device_factory.py", line 58, in create_device File "/usr/lib/python3.13/json/__init__.py", line 346, in loads File "/usr/lib/python3.13/json/decoder.py", line 345, in decode File "/usr/lib/python3.13/json/decoder.py", line 361, in raw_decode json.decoder.JSONDecodeError: Invalid control character at: line 1 column 264 (char 263)[12.02.2026]

[m.roszak 763]

Thanks for the report, we will try to push it to 5.203 beta. 

[trob 7]

We should push it to 5.202beta
Meanwhile please avoid using diacritics. If such a device is present and gateway is restarted it may cause more serious trouble.

[Willem-Jan 8]

I setup a small demo with KNX (Jung IP interface IPS300SREG). 
After setting the connection (tunnel to not encryted) it works to I get a connection.

The status shows connected.

 

I've added the first group address and that worked.

 

However after a while it stopped working. Not communication with the KNX setup anymore.

I've rebooted the HC3 and then it shows dead device.

[KNX]: [KNX] Connection state: DISCONNECTED

[KNX]: [KnxEngine] Setting devices dead==False

 

Any idea why it first worked and then stopped?

 

Update: it works now, but some issues with group addess 0/0/1 and status 0/0/2

Edited February 25 by Willem-Jan

[jakub.jezek 370]

Hi @Willem-Jan,

 

Please, create different topic, this one is about diacritics in device names in YUBII KNX integration.

 

Now, regarding your issue with 0/0/1 and 0/0/2.

 

Try 0/0/1 and 0/0/2 in your Home Center 3 and connect to same network via Wireshark. Then test it again. Wireshark can detect KNX/IP protocol and you should see if your Home Center sends commands correctly or with any issues. I did the same with Wireshark when I created my KNX switch Quick App. Also Group monitor in ETS should help to see if there is something comming from Home Center or not.

[trob 7]

@Willem-Jan
What I noticed is that ip-router sometimes doesn't drop broken connections. It has limit of parallel connections (in our case 2) and when something goes wrong and connection is dropped and reinitialized, old one still "counts" as active and new connections are refused, because limit is reached.

We probably will introduce ip-routing (and maybe also ip-secure support) soon.

Also:
What do you mean by: "it works now, but some issues with group addess 0/0/1 and status 0/0/2"?

[Willem-Jan 8]

On 3/2/2026 at 11:48 AM, trob said:

@Willem-Jan
What I noticed is that ip-router sometimes doesn't drop broken connections. It has limit of parallel connections (in our case 2) and when something goes wrong and connection is dropped and reinitialized, old one still "counts" as active and new connections are refused, because limit is reached.

We probably will introduce ip-routing (and maybe also ip-secure support) soon.

Also:
What do you mean by: "it works now, but some issues with group addess 0/0/1 and status 0/0/2"?

The issue with 0/0/1 and 0/0/2 has been solved when I restarted and reconnected the KNX demo set.
Not sure what the cause of this was. Maybe indeed the active connections which did not get dropped until a longer power down.

Thanks anyway.