Can't get sensors talking

[tekka]

@sundberg84 We do not recommend nor have the bandwidth to support and troubleshoot setups with mixed MySensors versions (i.e. 1.x and 2.x). That said, mixed setups can but are not guaranteed to function. As semantic versioning suggests, a major version increment implies API changes that are not backwards compatible: For a full list of changes in 2.0.0, please refer to the change log.

In your case, update all nodes/GW/repeaters to the most recent MySensors version, and report back if you encounter any issues.

As @Yveaux pointed out, I am working on a PR that unifies and documents all debug messages emitted from the transport layer.

[sundberg84]

@tekka - ok, thanks @tekka. I have 25+ nodes so I guess I have some work then
.. or maybe I'll just stick to 2.0b.

[tekka]

@sundberg84 Wow, how is the topology?

[sundberg84]

@tekka -

GW - 2.0b
3x Repeaters (combined with motion) - 2.0b
Nodes about 50% 1.4-1.5 and 50% 2.0b

but nevermind, I will hold on to your document is finished - no worries. I was just to eager to upgrade :)
Then I will try to upgrade the gw and see what happens.

[linus72982]

@tekka
Thanks for the explanation of the messages, that helped me quite a bit. I figured out that my gateway radio wasn't working very well so I bought an Addicore version that the reviews said was a bit more reliable. It came in today and works like a champ (and it has labeled pins which is helpful).

I eagerly await the documentation of the messages. I am writing a controller in Python and with my limited C knowledge (weird, I know, as Python is a C-based language, but it's just different enough to drive me nuts), I'm going cross-eyed trying to reverse-engineer the messages from the code. Your documentation will help immensely. Just the bit you told me up there has allowed me to write most of it. Thanks, again.

[tekka]

@linus72982 You'll find some more information here. This is a PR (still WIP) for the dev branch and applies to the upcoming 2.0.1 release.

[linus72982]

@tekka
That's good info, thank you. Quick question if you have a minute, what is the difference between CHKUPL and SANCHK? Based on the docs, they both seem to accomplish the same goal.

[tekka]

@linus72982 No, they do different things: CHKUPL checks the uplink, i.e. connection to GW whereas SANCHK is the regular radio HW sanity check (radio register verification + SPI connection).

[alexsh1]

@tekka Can we please get your info about deciphering the log in v.2 into a separate sticky thread in the Troubleshooting section?
Thank you very much for producing it

[tekka]

@alexsh1 The debug log messages are fully documented in the upcoming 2.0.1 release, see here for a preview (dev): https://ci.mysensors.org/job/Verifiers/job/MySensorsArduinoLibPR/Doxygen_HTML/

[Yveaux]

@alexsh1 more explicitly, a description of the transport state machine messages (TSM) can be found here: https://ci.mysensors.org/job/Verifiers/job/MySensorsArduinoLibPR/Doxygen_HTML/

[tekka]

@Yveaux @alexsh1 https://ci.mysensors.org/job/Verifiers/job/MySensorsArduinoLibPR/Doxygen_HTML/group__MyTransportgrp.html

[Yveaux]

@tekka ehhhrrfmmm... Copy/paste on Android didn't work as expected.... Sorry

[Cravecode]

This post is deleted!

[Quinie]

Hi All

I am working on the version 2 for the first time after being away for awhile.
The gateway is up and running.

8-10-2016 02:45:07	RX	0;255;3;0;9;TSP:SANCHK:OK

But my sensors is giving problems.

TSM:INIT
TSM:RADIO:OK
TSP:ASSIGNID:OK (ID=188)
TSM:FPAR
TSP:MSG:SEND 188-188-255-255 s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=bc:
TSM:FPAR
TSP:MSG:SEND 188-188-255-255 s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=bc:
TSM:FPAR
TSP:MSG:SEND 188-188-255-255 s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=bc:
TSM:FPAR
TSP:MSG:SEND 188-188-255-255 s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=bc:
!TSM:FPAR:FAIL
!TSM:FAILURE
TSM:PDT

I have a 4,7 capacitor in place. Any ideas?

[Quinie]

Changed the arduino.. not the radio .. from UNO to Nano (not the sensor but the gateway).. now it works...