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?
#define MY_SIGNAL_REPORT_ENABLED
It is included.
-
My guess is that out would be best to update my 2.0 gateway to 2.2.0 and move out from there. Correct?
-
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
-
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)
Release: 8.0
Codename: 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.
-
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.
-
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
-
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
-
@user1306
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 valuesend(RSSIMsg.set(transportGetSignalReport(SR_TX_RSSI)));
-
@flopp There was always a RF signal level column under Devices in Domoticz, never did try to find out how it was used....
-
@zboblamont
It is still there, but I don't think DZ has implemented MYS RF signal, yet
-
Thanks all for the help
@flopp i added the line like you mentioned.
i added it as S_SOUND, V_LEVEL seem to be working fine, thanks. Lets hope Domoticz will include it soon.
-
i have another simple question regarding the RF24_PA level.
in the config file i see that its default to RF24_PA_MAX. does this mean that if i dont include anything in my sketch the node will default to MAX?
i read somewhere that this could cause the node to fail sometimes if there's not enough current going through, since most of my nodes are run on battery i would like to know if its necessary to modify this?Thanks
-
@user1306
Correct, if you don't define RF24_PA LEVEL in your sketch it will use default values from Config, which in your case seems to be MAX
-
Really appreciate your help thanks @flopp
just wondering for normal nrf24l01+ not the PA LNA one, what level are you using? (no sure if mine are original since i bought them from Aliexpress i have my doubts).
-
@user1306
I am using LOW and HIGH. LOW should be enough. I was testing HIGH with some nodes but I dont know if that helped.I also using nRF from AliE.
I think most of MYS users are using nRF from China, i don't know how to see if it is real or fake.
-
Hello,
I have a Strange problem appearing since I have started to upgrade my network from 2.1.1 to 2.2.0
I am using a Domoticz v.3.8153 / Raspbian + a serial GW on NRF.
Some of the devices are communicating to the GW through a repeater node equipped with a nrf24l01 PA LNA since they are just too far from the GW.Not all of the nodes are upgraded to 2.2.0, some are still running 2.1.1
-
the battery level reporting disappeared from all of the connected node (but one is still working : a senserblender micro with the original TempHum sketch)
-
The repeater node sometime stopped relaying the connection to the GW (on random time ?). Only thing I found is to restart this node)
Any ideas ?
Thanks a lot.
Jef
-
-
Hi,
I've noticed that since the upgrade to 2.2.0 my nodes are now sending some new internal messages every now and then. I'm using a MQTT gateway and sometimes I see these messages coming through:mysensors-out/1/255/3/0/33 600000
mysensors-out/1/255/3/0/32 500What are internal messages types 32 and 33? Can't find them in the list on https://www.mysensors.org/download/serial_api_20#internal
-
@maghac Hi,
documentation is best found here: https://www.mysensors.org/apidocs/
It is always covering the latest release. Specifically, for message types: https://www.mysensors.org/apidocs/group__MyMessagegrp.html
-
Hi,
Thanx for 2.2.0
But I have a new feature that I did not have before.
I'm using VERA edge and my plugin reports that i don't have any connection to the Gateway.
Please advice
-
@clio75 please try setting the "CommFailure" Variable to 0 under "Advanced" for your MySensors Plugin Device in Vera to see it the message disappears.
-
@korttoma
Hi,
I switch "CommFailure" to 0 And reloaded engine. and error measure disappear.But is this a new feature that you have implemented ?
-
@anticimex said in MySensors 2.2.0 released:
@maghac Hi,
documentation is best found here: https://www.mysensors.org/apidocs/
It is always covering the latest release. Specifically, for message types: https://www.mysensors.org/apidocs/group__MyMessagegrp.htmlIs there a way to disable these messages?
-
@jjk yes, by avoiding to use smartSleep: https://www.mysensors.org/apidocs/group__MySensorsCoregrp.html#gab5f84c4227e3478af4b6600d5e8d8b15