MySensors 2.2.0 released
- Bug fixes - thanks to everyone who contributed in troubleshooting and tracking down problems
- Improved documentation, available at https://www.mysensors.org/apidocs/index.html
- NRF5 improvements
- A lot more, the changelog is looong For full list, see https://github.com/mysensors/MySensors/releases/tag/2.2.0 and https://github.com/mysensors/MySensors/compare/2.1.1…2.2.0
Big thanks to the following people who contributed to the release (151 commits in total):
1 bilbolodz 17 d00616 2 Dustin 3 Yveaux 1 FotoFieber 1 Frank Holtz 1 Frédéric FRANCE 1 freynder 1 Krister W 1 Lee Nelson 20 Marcelo Aquino 12 Mikael Falkvidd 16 Patrick Fallberg 1 per1234 3 Rainer Clasen 1 rejoe2 1 Soef 67 tekka 1 Thomas Mørch
Mixing different 2.x versions in the same MySensors network is OK, so you can start deploying new nodes with 2.2.0 without re-flashing your existing nodes, and you can upgrade your gateway without upgrading the nodes.
The new version should be available in the Arduino IDE
within a few daysnow.
@mfalkvidd Does this version incorporate the rssi resolution ?
@zboblamont I have no idea. What does the rssi solution do? Who has been working on it?
@mfalkvidd Sorry if I did not explain properly, signal strength reporting of nodes, it was I seem to recall intended for Rev 2.2.....
@zboblamont thanks for explaining. Looks like this is what you want?
It is included.
dbemowsk last edited by
My guess is that out would be best to update my 2.0 gateway to 2.2.0 and move out from there. Correct?
CrankyCoder last edited by
is this release still compatible with other 2.0 gateways? or do we need to upgrade gateways? Just wondering if i have to reflash everything lol
mickecarlsson last edited by mickecarlsson
On a Raspberry Pi 3 I get this warning when compiling 2.2.0
In file included from ./MySensors.h:343:0, from examples_linux/mysgw.cpp:83: ./drivers/RFM69/new/RFM69_new.cpp:663:12: warning: ‘void RFM69_ATCmode(bool, int16_t)’ defined but not used [-Wunused-function] LOCAL void RFM69_ATCmode(const bool onOff, const int16_t targetRSSI) ^
pi@mysensors-gw:~/MySensors $ lsb_release -da
No LSB modules are available.
Distributor ID: Raspbian
Description: Raspbian GNU/Linux 8.0 (jessie)
Edit: Forgot the configure line:
./configure --my-transport=rfm69 --my-is-rfm69hw --my-rfm69-frequency=868
@mickecarlsson Thansk for reporting, issue created: https://github.com/mysensors/MySensors/issues/1044
I think I reported this warning few months ago
@gohan ok. Did you also open an issue on github back then?
I think @mfalkvidd did something at the time
This is the thread gohan is referring to: https://forum.mysensors.org/post/75635
Looks like it was mentioned in https://forum.mysensors.org/topic/6526/raspberry-pi3-b-dragino-hat-rf95-rfm95-rf24_nop-error as well.
Ian Bishop last edited by
Thanks for all the hard work!
FYI, the version published to PlatformIO reports as 2.2.0-rc.2, doesn't look like there are any changes between the two revisions other than the version number.
I have tried updating the library and uninstalling/reinstalling and can't get it to bring down 2.2.0.
Users of security features (signing/encryption) need to do this to use these features from 2.2 onwards if upgrading from a previous official release.
flopp last edited by
Thank you very much. I donated USD 10 as a small thank you for all your work. I hope more people do the same.
Very nice text when you start a node, I have only tried 2.2 on my GW and it looks like some of my sending errors disappeared.
This is what you see when you start a node
__ __ ____ | \/ |_ _/ ___| ___ _ __ ___ ___ _ __ ___ | |\/| | | | \___ \ / _ \ `_ \/ __|/ _ \| `__/ __| | | | | |_| |___| | __/ | | \__ \ _ | | \__ \ |_| |_|\__, |____/ \___|_| |_|___/\___/|_| |___/ |___/ 2.2.0
Why not add two | in the "o" then i will look like this
__ __ ____ | \/ |_ _/ ___| ___ _ __ ___ ___ _ __ ___ | |\/| | | | \___ \ / _ \ `_ \/ __|/ _ \| `__/ __| | | | | |_| |___| | __/ | | \__ \ |_| | | \__ \ |_| |_|\__, |____/ \___|_| |_|___/\___/|_| |___/ |___/ 2.2.0
user1306 last edited by user1306
thank you very much for the hard work
i'm very interested in #define MY_SIGNAL_REPORT_ENABLED
So apologies for the stupid question but do i need to just enable this on the Node side or also the Gateway, or Config.h (because i saw it was commented out)?
Do you know if this is supported by Domoticz?
thanks in advance
flopp last edited by flopp
I couldn't find any Signal value in Domoticz
What I did was to send that information as a seperate Child
use variable transportGetSignalReport(SR_TX_RSSI) to get the value
@flopp There was always a RF signal level column under Devices in Domoticz, never did try to find out how it was used....
flopp last edited by flopp
It is still there, but I don't think DZ has implemented MYS RF signal, yet