MySensors 2.0.0 Released

[tbowmo]

Actually sensebender sketch is moved to the same repository as the hardware files for the SensebenderMicro.

Problem is that we do not want to have external dependencies on the examples in the MySensors library, as they are not distributed together anymore. That's why examples with external dependencies have been moved to a new repository. Except the sensebender sketch, which we/I decided to relocate to the SensebenderMicro repository, as it's a bit special, and belongs to that hardware..

[Tore André Rosander]

I have been using the beta for some time now, to use the stable version do i just download the zip from github and replace the mysensors folder in arduino -> libraries ?

[tbowmo]

@Tore-André-Rosander

That should do it, until we get online in the arduino library manager..

[tbowmo]

And now we are online in the Arduino Library manager..

So people can "easily" update to the latest and greatest MySensors release..

[DavidZH]

I have just done as said above and works a treat! I was still running on Arduino 1.6.1 but this was enough reason to update!

One question: my serial gateway is still running on 1.5, do I have to update that to 2.0?
I have one node running on 2.0b and that talks just fine. New nodes will follow soon (PCBs are being printed now...) so they will be on 2.0 as well.

[Yveaux]

@DavidZH See here:

"It should be fully backward compatible with your controller (serial api hasn't been changed since 1.5).
We recommend updating both gateway and sensors to the the latest release."

[CrankyCoder]

not a big deal, but is there something i should do to get the mysensors to show up in my manage library?

[Yveaux]

@Jason-Brunk here you can find the official "installation description"!
It should be that easy ;-)

[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."