Another solution to this which seems a lot cleaner IMO is to change the antenna gain in the config.json file such that when the system substracts the commanded TX power (coming from the server) with the antenna gain, it finds a valid RF power in the lookup table. So in my case, if I set the antenna gain to 8 dBi, then the server would go and find the parameters corresponding to 20 dBm (which is tx_lut_11): "tx_lut_11": { "pa_gain": 3, "mix_gain": 9, "rf_power": 20, "dig_gain": 0 } This was suggested to me by Tony over on the Chirpstack forum: https://forum.chirpstack.io/t/configure-gw-tx-power-on-a-per-gw-basis/8997/9?u=danalvarez Thanks Tony!

@Eric73 Oh wow, that makes sense... So it actually is transmitting at max power, as expected. That's good to know. Thanks so much for your insight! @catalin @Xykon would you be able to confirm this? If so I think it's important to change the documentation in https://docs.pycom.io/firmwareapi/pycom/network/lora/. Thanks!

@dan Well, don't understand why it is like that. Due to a research project I have had to "hack" the libraries to allow changing the transmission power. Should anyone need it, send me a PM (I have just programmed a "dirty" workaround so not even daring to push a change to github or something like that!)

@pwest We've found out how. On iBeacon, when you read the data you get an Array. You need to do int(lastHexValue, 16) and then -256. This results in the set TxPower the BLE Beacon has Edit: this site explains very well how the iBeacon protocoll is built, aswell as to where to find the TxPower: http://www.warski.org/blog/2014/01/how-ibeacons-work/