Problem with setting PA_LEVEL at start of Mesh about rf24mesh HOT 5 CLOSED

Hmm, I had a feeling you'd prefer option 2 😆

I didn't realize this was fixed at the RF24 level. I guess the change isn't really required then?

from rf24mesh.

Heh, the troubling experience was always adjusting my code to set the PALevel AFTER starting the mesh and again if mesh.begin() was called, which I see is not necessary anymore.

from rf24mesh.

I prefer option 2 since it is consistent with using RF24Network::begin(). There's also a deprecated RF24Network::begin(uint8_t _channel, uint16_t _node_address) which I neglected to remove when releasing v2.0. So, I think we're a bit overdue for some breaking changes.

I seem to remember a rejected PR (#210) about this that instigated changing RF24::begin() so that the PA level was not altered every time it was called. Looking at RF24::_init_radio(), I see nRF24/RF24@8ad2886 in the git blame.

from rf24mesh.

I guess the change isn't really required then?

At a glance, no. Did you recently have some troubling experience that you attributed to this?

from rf24mesh.

I was suspecting an ebyte module; they don't seem to respect the user-specified PA level.

from rf24mesh.