PaxCounter transmit power not changeable

[paddlix]

Hello,
I have a problem with my PaxCounter. The issue is the following: If I change the value for "txpower" in the paxcounter.conf, this has no effect on the transmit power of the PaxCounter. The changed value is stored on the device (picture, red circle - external readout of the configuration via TheThingsNetwork), but the device seems to ignore it and transmits with the default value txpower = 14 instead (picture, green circle - display of the PaxCounter). It does not matter which value is entered in paxcounter.conf. Neither 0, nor 255, nor any value in between has any effect.
Is there a software solution to this problem or is this a hardware malfunction?

The PaxCounter is a LILYGO TTGO ESP32 PaxCounter. It is set for use in the EU.

Thanks!

[Verkehrsrot]

1. Settings in paxcounter.conf define factory settings and only affect new builds. Settings are loaded during power up in NVRAM and thus persist, even if you flash a new build. Thus, if you changed factory settings, you need to manually clear NVRAM to avoid that previous values are loaded during startup. Use pio run -t erase to clear NVRAM manually.
2. Better option to tailor runtime settings is to use rcommands, see readme.md
3. TXpower is limited if ADR is active (which is the default), thus the radio driver will accept changes only by network, not by hand.

Open question is, why "25" is sent by the decive to the backend. This is probably a bug, because the administrative value is sent to the backend, while display is showing the actual (= effectice) radio driver's value (limited by ADR).

It's not a hardware issue.

Anyway, if you change TX power by hand, you should know your local frequency regulations limits. Usually, for EU channels 14dBm is maximum.