administrators

nice work @Oumuamua, thanks for reporting back.

@Rez sorry, that sketch is way too complex for me to understand.

https://www.openhardware.io/view/8227/Simple-compact-RS485-node-v2-ATmega328-MAX3485-W25X40

Welcome to the forum @Rez

That code looks like it was made for MySensors 1.x, which quite old.

Try the latest version instead: https://www.mysensors.org/build/ethernet_gateway

@Clone-Tv rssi is only defined/meaningful when receiving a message, so it must be measured when receiving. To avoid regeneration loop, do not send from within receive(). Only store the value, then send from within loop() like my sketch does.

I have no experience with mycontroller. This is what it looks like in Domoticz:

Note that the rssi value is recorded as a value of the gateway. It is not recorded as a value of the node.

@Clone-Tv no. Sorry for the confusion. message.sender is the node ID of the sender. For my gateway, I have chosen to only report received rssi for the node with node id 1. Rssi for all other nodes is ignored.

I don't recognize any of that code. Where did you find it? I don't think I've ever seen a MySensors sketch with a c++ template in it.

Sending battery level is done like this:

sendBatteryLevel(60);

(for a battery level of 60%). Documentation: https://www.mysensors.org/download/sensor_api_20#sending-data

Sending other values can be done in multiple ways. For an example sending wifi rssi and rssi of incoming MySensors message, see https://github.com/mfalkvidd/Arduino-MySensors-ESP8266-RFM69-Gateway/blob/master/Arduino-MySensors-ESP8266-RFM69-Gateway.ino#L106

MyMessage has a method setType but there is no corresponding getType. If getType was available, you should be able to use that to figure out which getter you should use (getLong, getInt, getFloat, getString and the others).

But the getString does the conversion already, if you pass it a buffer to fill. Like this:

void receive(const MyMessage &message){
  char messagestring[100];
  message.getString(messagestring);
  Serial.println(messagestring);

}

Documentation reference: https://www.mysensors.org/download/sensor_api_20#message-manipulation

@grumpazoid said in Sample sketch for test node including hardware and software acknowledgement:

I can see how to print the other parameters but not the payload itself

You could just print the raw bytes, which works for all payload types (eg https://github.com/Yveaux/Arduino_HexDump). Otherwise you have to print the contents depending on the type of data in the message.

@grumpazoid said in Sample sketch for test node including hardware and software acknowledgement:

Transportready seems to report good even when lots of hardware NACKS occur.

Transportready is just an indication that your radio is good to go. It does not depend on your link quality.

I've also seen the echo come back as good even though the ack did not.

Welcome to the wonderful world of radio communications!

A message can be correctly received by the target node, while the ack gets lost. The target node then echoes the message back to the source, which receives it correctly.
Perfectly viable scenario.