@yoonie said:
For the pro mini version, should i create another Openhardware project, or should i put it here, in the already existing project?
Might be better to create a new project as they uses a different set of design files.
Hi @chey, no, with the pro minis and MySensors lib I couldn't get less.
Didn't measure with yet another multimeter though...
My battery sensors are working now for about a year and the battery levels are between 65% and 70%.
The sensor furthest from the gateway is at 65% and the 3 others at 70%.
Not bad I think.
https://forum.mysensors.org/topic/11499/checking-mechanical-locked-doors-by-a-battery-based-windows-door-sensor-node
@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?
@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
