@OldSurferDude jus request counter states from controller on each reset, worked fine with Domoticz...
or save in eeprom but increase location every write, on power up/reset search eeprom for largest value stored and carry on from that location, one long integer will fit 256 times in atmega328(p) eeprom, is that long enough for you ?
Over 4 years on, and my node ran continuously sending 4 messages every 5 minutes.
It's 700mAh LiFePo4 battery voltage dropped from initial 3.45V to 3.24V, according to LiFePo4 voltge/SoC tables It's just under 40% left.
700*60% = 420mAh. 100 mAH per year. using library 2.40 and blob message I could cut usage to ~25mAh/year, not bad
@mfalkvidd Yes, I understand that 253 is the software limit. I was wondering about the hardware limit.
For example, my Asus router has a software limit of 253 devices. But when I get 20-25 WiFi devices trying to connect, the network goes haywire. (pun intended ) I am quite convinced that this is a hardware limitation of the router because the router has to carry some information about each connection.
If the gateway is dumb, that is, carries no information about any connection, then it could truly have 253 connections. After a bit of contemplation, I realize that the name, gateway, implies this.
If that is the case, it is good news for the DiY'er in that this very inexpensive and cheap hardware could stand in for a LoRaWAN, again, with a number of compromises.
