MySensors 2.2.0 released

[user1306]

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.

[user1306]

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

[flopp]

@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

[user1306]

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).

[flopp]

@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.

[ZwaZo]

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

[maghac]

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 500

What are internal messages types 32 and 33? Can't find them in the list on https://www.mysensors.org/download/serial_api_20#internal

[Anticimex]

@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

[clio75]

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 :)

[korttoma]

@clio75 please try setting the "CommFailure" Variable to 0 under "Advanced" for your MySensors Plugin Device in Vera to see it the message disappears.

[clio75]

@korttoma
Hi,
I switch "CommFailure" to 0 And reloaded engine. and error measure disappear.

But is this a new feature that you have implemented ?

[jjk]

@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.html

Is there a way to disable these messages?

[Anticimex]

@jjk yes, by avoiding to use smartSleep: https://www.mysensors.org/apidocs/group__MySensorsCoregrp.html#gab5f84c4227e3478af4b6600d5e8d8b15