I’m using release 2.4.2 5b45303 on a DIY V1 device.
When I connect it via a browser with its IP and examine the Lora configuration, I notice that it is not possible to set a power higher than 12 dBm (28dBm for example).
The DIY V1 device has a 30 dBm module.
On the other hand, I can’t see where the “Ham licence” flag is in the GUI.
Connected via BT, this flag is set to “true”.
Is this a known bug? Should I use another version?
Thanks
Its quite possible that when the LoRa module itself is set to 12dBm that the power amplifier is then boosting the output power to 30dBm.
Have you measured the actual RF output power ?
I had previously used an older version with this module and was able to switch to 22dBm. With this one, it doesn’t seem possible.
Another strange thing is that the GUI doesn’t offer me the “USER” item. It’s in this menu that the “is_licensed” option is normally positioned.
I think 2.4.2 has a bug in the power setting.
Please note that I use the EU_433 profile.
As for power, I don’t have any equipment capable of measuring it.
Here is what I see in the “Radio settings” of the documentation :
"Power limits will generally be lifted in the software if
is_licensed is set to true . See HAM Mode for more
information."
I don’t know what “generally” means. 
Neither do I.
But with LoRa modules that have power amplifiers on them there is very likely no direct relationship between the configured output power and the actual output power.
Feed 12dBm into the power amplifier on the LoRa module and I would be surprised if it did not output 30dBm to the antenna.
Which LoRa module are you telling Meshtastic you are using ?
The module used is an Ebyte E22 400M 30S specified at 30 dBm.
And does Meshtastic have a specific configuration setting for that exact module ?
No, there is no special configuration for this module.
Simply, as indicated in the documentation, holding an amateur radio license “generally” allows you to override the 12 dBm limitation.
Problem: the GUI doesn’t offer the possibility of setting “is_licensed” to “true” because the “USER” menu item is missing in this 2.4.2 release.
Well in the case of the E22 what you need to know is what power level to set the LoRa device to and what power level then comes out of the antenna socket.
That information does no appear in the E22 datasheet.
This Lora module IS NOT an amplifier where one RF signal is input and another is output, amplified by its gain. In fact, if you look at the pin assignment, you’ll see that there is no RF input.
The reason for this is that the RF signal is generated inside the E22 and is therefore not accessible for measurement.
The real problem lies in the absence of the USER menu item, which allows you to set “is_licensed” to exceed the 12dBm limit.
What would be the reason for this absence in version 2.4.2 5b45303 ?
What you would normally do, is set the LoRa device to say, 5dBm, 10dBm and 15dBm and then measure the RF power coming out of the antenna socket.
The RF power output of the LoRa module will be fed (on the module) to the input of a separate power amplifier which in turn is connected to the modules antenna socket.
Indeed, it would be possible if, on the one hand, I had the means to measure RF power and, on the other, if I could go beyond 12dBm.
The spectral density of Lora modulation means that conventional equipment (Bird, for example) can’t be used. The only thing I can do is to use an SDR receiver, set it to 250khZ bandwidth, note the power peak during a transmission and compare the different values. This is not a measurement !!!
In any case, the problem is solved, as I’ve found that the “USER” menu, which doesn’t exist when I access the device via the browser, is present if I use the Bluetooth application.
I was thus able to set “is_lisenced”.
As a result, the power value in the “LORA” menu remains at the value entered (e.g. 25dBm) instead of returning to 12 dBm systematically.
The signal appears much more stronger on my SDR receiver.
“is_licensed” disables encryption, unless you alter the firmware to remove that. an easier fix is to alter the firmware to raise the power limit in that region setting, then rebuild and reflash. it will then give you the full power the hardware is capable of supplying, while retaining encryption.
Indeed, that’s one solution, but what’s more important for me is to be able to use the full power of the Lora module.
The 12dBm allows some experimentation, but not enough range to be fully exploitable.
But I’ll keep the idea in mind.
changing the output in the firmware does give you full output.
How do you make this change? I didn’t see it in the GUI ?
You can’t modify the firmware in the GUI. Forget i said anything.