i think i finally get it.
It is impossible... well the only way to let nodes communicate with each other is when a gateway is available (directly or trough other nodes) when the node is starting up.
This forum discussion is explaining me the most..
a solution may be.. transform the node that is always on to an gateway. And use antoher channel.. Sidenode; then you can't tell the controller what the status is.
Is there realy no way that this can supported? Node to node comunication without the need of an gateway inside the network? Skipping the registration and just send the message around.
perhaps i will dive into the source one day and change the registration behavior.
Thanks anyway for the help and the very fast responding.
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
@DavidZH - I really hate our electrical system here, but that is coming from an electronics guy, not a electrician. I like the idea of low voltage in the switches, however its AC. I would prefer to see DC, but the voltage drops might be something that they're attempting to avoid by sending AC instead. Yes, i agree about those damn rings and we also don't have the room here in the UK like you mentioned about the NL.
Hi all,
Should anyone face the same problem, I found the root cause: brownout threshold. I burned a new bootloader (Optiboot 8.0) without such trigger and the node has been working with used batteries (~2.7V) since May.
Hope this helps.
@acb
Hi @acb and others, regarding "Do you know if there is a version of this board that is pad-compatible with the C-versions of these HopeRF RFM69s before I go searching? (Since I believe the C-versions are also pad-compatible with the RFM95sā¦)" - did you find any alternative?
I'm in the same boat looking for an adapter from NRF24 to the footprint of RFM69*C = RFM95/96.
Thanks, Joost