@zeblong, you can generate these from the board files, however i'm leaving this one for @Ivan-Z to discuss with you as this is his device and he knows all details regarding this.
@Mishka Very nice work indeed. One question though: I don't see an antenna of any kind built into the PCB. Maybe I'm just not seeing it, or is there none? I do see a connection for an off-board near field antenna, but off-hand I don't see where the antenna is for 2.4Ghz RF.
Oh, I see it now. You're using a chip antenna. Got it.
Well, now that you've been using it for a while, how is the Raybeacon working out for you?
Yes. Correct. call BME.begin() every time and the subroutine only at the beginning.
And you are also correct about the library. I use the "blue" lib, from Sparkfun. As i can recall correct (it's been over a year since I built the damn thing) I have tried both, and found the Sparkfun more stable.
And you CAN switch off power for this module, but after conversion it goes to sleep and uses less than 1uA. Hardly worth the effort, because the current can find a way over the data lines, and that's a pain in the behind to solve (I tried!).
@monte, I've implemented in PR https://github.com/mysensors/NodeManager/pull/517 something going in the direction you pointed out. Before explaining just a simple assumption first: NodeManager is intended to run on a number of different boards, most of them with limited memory so this capability has to take this constraint into consideration (hence no json parsing, reuse of existing communication mechanism, capability disabled by default, etc.)
Apart from this, I found a sort of compromise to enable/disable sensors, even remotely and optionally persisting the status across a reboot. All the implementation details are within the PR (down below, the PR also include other enhancements) feel free to provide comments here or on Github. Hope it could be useful to avoid reimplementing the entire logic from scratch