Admin

@skywatch arrays indexes in c/c++ always start at 0.
int myarray[5] would have positions 0 thorugh 4. Position 5 would be outside the array. In the code above, position 0 is never used.

So either make the array 1 element larger than actually needed (with position 0 unused), or let i start at 0:

int value[4];
for (i=0; i<4; i++){
  value[i] = debouncer[i].read();
}

@APL2017

Perhaps a broadcast once an hour, with "I'm here and I'm alive". I'm doing this with all my sensors, even battery powered ones.

@bramz you’ll need 2.4.0, not 2.4.1.

Edit: sorry, my bad. 2.4.1 is the confirmed version. Maybe the Arduino IDE must be restarted after downgrading?

I like the rfid/nfc idea. More information can be stored. How small can the rfid chips be?

@skywatch not if the 0th position is skipped

@alowhum it's SPI, so can probably share it's bus with nrf24/rfm69, only one extra pin for CS is needed.

The main thing mqtt has (that MySensors doesn’t) is ”packet identifier” in mqtt lingo. It is similar to tcp’s sequence number.

Mqtt also assumes that

• the broker (I guess the analogue is the MySensors gateway) has persistent storage, or at least sufficient ram to buffer all messages until they have been marked as delivered
• everything is single hop (no repeaters)
• there is a DUP flag
• clients have sufficient ram to buffer all outgoing messages until they have been marked as delivered, and has timers to retransmit messages

I am not sure how mqtt handles ordering of messages. I think mqtt doesn’t guarantee ordering, regardless of qos level.

@alowhum said in MySensors gateway and network reliability:

Very interesting! If I don't call wait() manually, when does the library process messages? Also at the end of the loop?

Correct

@alowhum MySensors resets the watchdog every time loop() is exited, so there is no need to call wdt_reset() unless you do something that takes a long time. If you do stuff that takes a long time you should call wait() instead, so messages can be processed.

@alowhum most of these questions are way too advanced for me to answer, but I know that wait() calls _process() which processes messages and kicks the watchdog (through doYield()). See https://github.com/mysensors/MySensors/blob/development/core/MySensorsCore.cpp#L565

while (hwMillis() - enteringMS < waitingMS) {
_process();
}

By default, nrf24-based nodes do not use interrupts for message handling.

There is nothing done in parallell.