Can't get sensors talking
-
@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.
@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.Controller: Proxmox VM - Home Assistant
MySensors GW: Arduino Uno - W5100 Ethernet, Gw Shield Nrf24l01+ 2,4Ghz
MySensors GW: Arduino Uno - Gw Shield RFM69, 433mhz
RFLink GW - Arduino Mega + RFLink Shield, 433mhz -
-
@tekka -
GW - 2.0b
3x Repeaters (combined with motion) - 2.0b
Nodes about 50% 1.4-1.5 and 50% 2.0bbut 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 looks like you have an issue with your GW radio:
0;255;3;0;9;!TSP:SANCHK:FAILGW and repeater nodes have by default regular sanity checks enabled. In your case, the sanity check fails, most likely due to cable and/or power issues. Try fixing/reseating the radio cables and/or add a larger cap to the GW radio.
Also, please post the node sketch for further analysis.
As for the debug messages, here the most important ones:
TSM:FPAR => Transport State Machine:Find PARent
!TSM:UPL FAIL, SNP => Uplink failed, Search New Parent
!TSP:SEND:TNR => Transport:SEND:Transport Not Ready
TSM:PDT => PowerDown TransportI'm currently working on a PR to unify and document all transport debug log messages for troubleshooting
In your case, this is what happened:
- Node initializes and assigns ID 3, then it fails to find a parent...
TSM:INIT TSM:RADIO:OK TSP:ASSIGNID:OK (ID=3) TSM:FPAR TSP:MSG:SEND 3-3-255-255 s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=bc: TSM:FPAR TSP:MSG:SEND 3-3-255-255 s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=bc: TSM:FPAR TSP:MSG:SEND 3-3-255-255 s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=bc: TSM:FPAR TSP:MSG:SEND 3-3-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- Later on it receives a response to the find parent request from node ID 0 (=GW)
TSP:MSG:FPAR RES (ID=0, dist=0) TSP:MSG:PAR OK (ID=0, dist=1) TSM:FPAR:OK- and finally, the TSM is fully operational.
TSM:READY- Then the node starts sending the presentation messages...
TSP:MSG:SEND 3-3-0-0 s=255,c=3,t=15,pt=6,l=2,sg=0,ft=0,st=ok:0100 TSP:MSG:SEND 3-3-0-0 s=255,c=0,t=17,pt=0,l=5,sg=0,ft=0,st=ok:2.0.0 TSP:MSG:SEND 3-3-0-0 s=255,c=3,t=6,pt=1,l=1,sg=0,ft=0,st=ok:0- ...and fails again to (successfully) send the messages to the GW
!TSP:MSG:SEND 3-3-0-0 s=255,c=3,t=11,pt=0,l=13,sg=0,ft=0,st=fail:Binary Sensor !TSP:MSG:SEND 3-3-0-0 s=255,c=3,t=12,pt=0,l=3,sg=0,ft=1,st=fail:1.0 !TSP:MSG:SEND 3-3-0-0 s=3,c=0,t=0,pt=0,l=0,sg=0,ft=2,st=fail: !TSP:MSG:SEND 3-3-0-0 s=4,c=0,t=0,pt=0,l=0,sg=0,ft=3,st=fail:- Hence, start searching for a new parent...
!TSM:UPL FAIL, SNP TSM:FPAR TSP:MSG:SEND 3-3-255-255 s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=bc:- ...and (again) no reply from the GW, therefore...
!TSP:SEND:TNR- Transport not ready, and starting from the beginning...
@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
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.
-
@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.
-
@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. -
@linus72982 looks like you have an issue with your GW radio:
0;255;3;0;9;!TSP:SANCHK:FAILGW and repeater nodes have by default regular sanity checks enabled. In your case, the sanity check fails, most likely due to cable and/or power issues. Try fixing/reseating the radio cables and/or add a larger cap to the GW radio.
Also, please post the node sketch for further analysis.
As for the debug messages, here the most important ones:
TSM:FPAR => Transport State Machine:Find PARent
!TSM:UPL FAIL, SNP => Uplink failed, Search New Parent
!TSP:SEND:TNR => Transport:SEND:Transport Not Ready
TSM:PDT => PowerDown TransportI'm currently working on a PR to unify and document all transport debug log messages for troubleshooting
In your case, this is what happened:
- Node initializes and assigns ID 3, then it fails to find a parent...
TSM:INIT TSM:RADIO:OK TSP:ASSIGNID:OK (ID=3) TSM:FPAR TSP:MSG:SEND 3-3-255-255 s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=bc: TSM:FPAR TSP:MSG:SEND 3-3-255-255 s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=bc: TSM:FPAR TSP:MSG:SEND 3-3-255-255 s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=bc: TSM:FPAR TSP:MSG:SEND 3-3-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- Later on it receives a response to the find parent request from node ID 0 (=GW)
TSP:MSG:FPAR RES (ID=0, dist=0) TSP:MSG:PAR OK (ID=0, dist=1) TSM:FPAR:OK- and finally, the TSM is fully operational.
TSM:READY- Then the node starts sending the presentation messages...
TSP:MSG:SEND 3-3-0-0 s=255,c=3,t=15,pt=6,l=2,sg=0,ft=0,st=ok:0100 TSP:MSG:SEND 3-3-0-0 s=255,c=0,t=17,pt=0,l=5,sg=0,ft=0,st=ok:2.0.0 TSP:MSG:SEND 3-3-0-0 s=255,c=3,t=6,pt=1,l=1,sg=0,ft=0,st=ok:0- ...and fails again to (successfully) send the messages to the GW
!TSP:MSG:SEND 3-3-0-0 s=255,c=3,t=11,pt=0,l=13,sg=0,ft=0,st=fail:Binary Sensor !TSP:MSG:SEND 3-3-0-0 s=255,c=3,t=12,pt=0,l=3,sg=0,ft=1,st=fail:1.0 !TSP:MSG:SEND 3-3-0-0 s=3,c=0,t=0,pt=0,l=0,sg=0,ft=2,st=fail: !TSP:MSG:SEND 3-3-0-0 s=4,c=0,t=0,pt=0,l=0,sg=0,ft=3,st=fail:- Hence, start searching for a new parent...
!TSM:UPL FAIL, SNP TSM:FPAR TSP:MSG:SEND 3-3-255-255 s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=bc:- ...and (again) no reply from the GW, therefore...
!TSP:SEND:TNR- Transport not ready, and starting from the beginning...
-
@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 -
@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/
-
@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/
-
-
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:OKBut 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:PDTI have a 4,7 capacitor in place. Any ideas?
