MySensors 2.3.2 released

[alowhum]

2.4 will come with a set of new features some of you have been waiting for... stay tuned

Exciting! Next Christmas? :-)

Practically: will code that uses ACK still work ok? I believe the answer was 'no' earlier, but I want to make sure.

[mfalkvidd]

@alowhum the real ack still works the same way as before.

The stuff that was called ack but wasn't ack and confused the hell out of everybody still works the same way as before, except that the naming is now "echo" to better reflect what it actually does (and has been doing all along). See https://github.com/mysensors/MySensors/pull/1292 for more information.

[alowhum]

Ok, but practically: I have a lot of Candle users whose version of MySensors will auto-update. But the code they will be uploading still has:

  if( message.isAck() ){
    Serial.println(F("-Got echo"));
    return;
  }

So.. I should quickly change the code to also accomodate Echo. The question is: how?

Will this work?

  if( message.isAck() || message.isEcho()){
    Serial.println(F("-Got echo"));
    return;
  }

[tekka]

@alowhum No need to substitute isAck() - it is marked deprecated but remains fully functional in the 2.x code. However, it is advisable to use isEcho() in the future to avoid confusions.

[alowhum]

Thanks @tekka, that's a load off my mind :-)

Is there a way to use #define based on the version of the library?

[mfalkvidd]

@alowhum yes you can use the macros defined in https://github.com/mysensors/MySensors/blob/development/core/Version.h#L49

[mfalkvidd]

or https://www.mysensors.org/apidocs/group__Versiongrp.html#details

[franz-unix]

Hi guys, thanks for this release! :+1: Tested with a Pi 4 and a dual ethernet gateway (RFM69 + NRF24): it works!
My /boot/config.txt is here.

[djvl]

Hi, thanks as well! Upgraded half of all my sensor nodes without any issues so far.

[pvoj]

Thank you for the new version!
I run my network on 2.3.1. Should I update the serial gateway to 2.3.2 (or stay with 2.3.1) and leave some of my nodes on 2.3.1 and the new ones on 2.3.2?
Are they compatible?

[mfalkvidd]

@pvoj they are compatible so you can do any way you like

[keithJ]

hi, i upgraded to 2.3.2 and my serial gateway stopped working in openhab, so i had to revert back to 2.3.1.

I can only think this is because the mysensors binding also has to be upgraded?

[minousoso]

The stuff that was called ack but wasn't ack and confused the hell out of everybody still works the same way as before, except that the naming is now "echo" to better reflect what it actually does (and has been doing all along). S

[minousoso]

@mfalkvidd I can only think this is because the mysensors binding also has to be upgraded?

[mfalkvidd]

@minousoso sorry, I don't know. I don't use Openhab.

[Eme]

Upgraded MS library and my my serial gateway sketch from 2.0.0 this evening - went well. Then noticed Nodes nolonger connect... Status LEDs no longer blick. Tried updating one node to 2.3.2 but it still won't conect. Is there a step by step guide? I have over 10 other nodes that Domotics can't find.

[skywatch]

@Eme DId you erase the eeprom using the mysensors clear eeeprom program? If not then run that once and try again.

[Eme]

@skywatch thanks for the update. Should l write this sketch to the Gateway alone, on each node or on both? Are there any step by step guides to gracefully migrate with? I'm very cautious, I've nodes in faraway places, wouldn't want to have to start all over again.

[Eme]

@Eme cleared eeprom with the sketch and loaded the Gateway Serial. I now have an error for an #include <nrf.h> I've updated boards and libraries but still can't get past the error

"NRFS Radio is not supported for this platform. " does this mean my Serial GW can't be upgraded since l use NRF24 radios? What am l fling wrong? All my nodes are down. Please help.

[skywatch]

@Eme Best to post the gateway sketch you are using. I guess it is the one from 2.3.2 library and not the old one from 2.0.0. Things changed.

Also I would recommend to clear eeprom on all nodes and then reload the code modified where necessary for the new version if needed.

It is best to have everything using the same version/protocol.