MySensors 2.0.0 Released

[CrankyCoder]

running 1.6.7 and not seeing it. oh well. not a biggy

[CrankyCoder]

updated to 1.6.9 and it's there. oh well. probably needed to update anyway :)

[gloob]

I did now also update my gateway but I see two messages in the debug panel that I don't understand:

pm open,type:2 0
0;255;3;0;9;TSP:SANCHK:OK

Does anybody have an idea what that means?

[TheoL]

I've read the documentation and I'm really impressed with the great work you've guys have done. Developping sensors with MySensors had never been this easy. You guys rock!

[hugows]

I just built my first "sensor network" yesterday and I was lucky to arrive on the 2.0 version - fun times! Congrats hek and contributors.

[Koresh]

Congratulations!
I used 2.0dev last month and I'm happy to see this version get stable status. :thumbsup:

[DavidZH]

@Yveaux

I have now recompiled my node that was on 2.0DEV to 2.0Stable and it will not fly. So tomorrow I will recompile my gateway to see if that runs better.

I really have to get used to the new debug output though. But it give a lot more info!

[A Former User]

@gloob said:

I did now also update my gateway but I see two messages in the debug panel that I don't understand:

pm open,type:2 0
0;255;3;0;9;TSP:SANCHK:OK

Does anybody have an idea what that means?

I have this problem too. What does that mean?

[tbowmo]

@kenci said:

@gloob said:

I did now also update my gateway but I see two messages in the debug panel that I don't understand:

pm open,type:2 0
0;255;3;0;9;TSP:SANCHK:OK

Does anybody have an idea what that means?

I have this problem too. What does that mean?

The TSP:SANCHK:OK is a sanity check of the radio, this time it's OK. But if we fail in talking with the radio (spi failure etc) it will try to initialize the radio, and also write Fail (I believe)

It's @tekka that is the brain behind this part (and has promised to make some documentation on it :))

[A Former User]

@tbowmo Thank you for the explanation. But what does that mean pm open,type:2 0

[marekd]

Hi there.
Good work.
I was using dev ver. - should I recompile all nodes and GW to 2.0.0, to use it?

[Yveaux]

@marekd quote from the main site : "We recommend updating both gateway and sensors to the the latest release."

[AWI]

@marekd To add to @Yveaux , if you are using repeaters (or nodes with the repeater functionality switched on) these also should be updated to the latest release.

[Tore André Rosander]

Is there any plans to update the Raspberry gateway? The one where the nrf radio is connected directly to RPI gpio.
As far as i know it is version 1.4 at the moment.

[drock1985]

@Tore-André-Rosander

I think that was someone who contributed it a while back. I remember going though the thread, and at one time someone was looking for anyone to update the 1.5 base for the signing; IIRC.

Probably best to switch to another Gateway for now.

[Tore André Rosander]

@drock1985
Is there any pro/cons when choosing the esp gateway or the serial gateway (connected to Raspberry pi)?

[drock1985]

@Tore-André-Rosander

Not really; depends on what your controller supports. Personally I have Home-Assistant running the latest MySensors 2.0 Wifi (ESP) gateway no problems.

[scalz]

@Tore-André-Rosander
for pros, I think serial gw is more secure. I mean esp is wifi, serial gw is only connected to controller. Of course controller is connected to network, but esp is just one more door directly connected to mysensors. Cons, not as verstatile as esp ;)

[Fabien]

And with RFM69, ESP and MySensors 2.0 doesn't work for me. With serial gateway, it's ok. With Ethernet Gateway W5100 and MYS 1.0, I lost lot of packets (NRF radio).

[Tore André Rosander]

Thanks for the response, i tested the esp gateway and it looks good. But i think im going for the serial gateway just to eliminate the need for WiFi in my setup. So if the WiFi is messing up during the night the mysensors network still works.