High sensitivity: down to -148 dBm.
From the datasheet. There probably needs to be some margin, but my experience with Sigfox shows that -130 is quite reliable. After that, packets start go missing. I would guess LoRa is similar.
Oh, I never even thought of that as a possibility.
I really like KiCad, and it's my preference. For a while I had Eagle for work, but even then I still preferred KiCad whenever I was given a choice.
There are also other solutions that have I2C bus pins on the shield and if you are going to make a battery powered node, I'd suggest to use an I2C sensor as it will be much more battery friendly
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
I will answer myself after some testing done today:
How can I change network id for gateway (mysgw)?
It is possible to change MY_RFM69_NETWORKID for mysgw by exporting CPPFLAGS variable with the option set before running ./configure:
example:
export CPPFLAGS='-DMY_RFM69_NETWORKID="101"'
./configure --my-gateway=serial --my-transport=rfm69 --my-rfm69-frequency=868 --my-is-rfm69hw --my-serial-is-pty --my-serial-port=/dev/ttyUSB-MysGW --my-serial-groupname=dialout
make
Is it possible to create another RFM69 network on new hardware, just for the test, while my current RFM69 network keeps running on current gateway/controller?
As soon as I started another RFM69 gateway (mysgw) on new hw, even with different network id (101), most of the sensors connected to my other (production) gateway running on old hw with default network id (100) stopped communicating... so it seems it is not possible to run multiple RFM69 gateways in the same range (on the same freq).
