Skip to content
  • MySensors
  • OpenHardware.io
  • Categories
  • Recent
  • Tags
  • Popular
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Brand Logo
  1. Home
  2. Troubleshooting
  3. I got a st=fail:2.0.0 which won't go !!

I got a st=fail:2.0.0 which won't go !!

Scheduled Pinned Locked Moved Troubleshooting
6 Posts 3 Posters 1.4k Views 3 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • frenchoF Offline
    frenchoF Offline
    frencho
    wrote on last edited by
    #1

    Hi,
    I'm having a problem with both RFM69 and NRF24 radio between node and gateway !
    First I tried with RFM69, then wanted to check if still had the same FAIL with NRF24 : bingo, same st=fail

    On the doc I found about the debug message, I undstand st=Fail means that the gateway doesn't send Ack
    I really don't understand how it could be possible that with 2 differents radio type (NRF24 and RFM69) I get the same problem.

    does anyone have an idea where this st=fail could come from ?

    see below the log on the node side with NRF24 module.
    TSP:PING:SEND (dest=0)
    TSP:MSG:SEND 165-165-0-0 s=255,c=3,t=24,pt=1,l=1,sg=0,ft=0,st=ok:1
    TSP:MSG:READ 0-0-165 s=255,c=3,t=25,pt=1,l=1,sg=0:1
    TSP:MSG:PONG RECV (hops=1)
    TSP:CHKUPL:OK
    TSM:UPL:OK
    TSM:READY
    TSP:MSG:SEND 165-165-0-0 s=255,c=3,t=15,pt=6,l=2,sg=0,ft=0,st=ok:0100
    !TSP:MSG:SEND 165-165-0-0 s=255,c=0,t=17,pt=0,l=5,sg=0,ft=0,st=fail:2.0.0
    TSP:MSG:SEND 165-165-0-0 s=255,c=3,t=6,pt=1,l=1,sg=0,ft=1,st=ok:0
    TSP:MSG:SEND 165-165-0-0 s=255,c=3,t=11,pt=0,l=18,sg=0,ft=0,st=ok:Temperature Sensor
    TSP:MSG:SEND 165-165-0-0 s=255,c=3,t=12,pt=0,l=3,sg=0,ft=0,st=ok:1.1
    TSP:MSG:SEND 165-165-0-0 s=0,c=0,t=6,pt=0,l=0,sg=0,ft=0,st=ok:
    Request registration...
    TSP:MSG:SEND 165-165-0-0 s=255,c=3,t=26,pt=1,l=1,sg=0,ft=0,st=ok:2
    TSP:MSG:READ 0-0-165 s=255,c=3,t=27,pt=1,l=1,sg=0:1
    Node registration=1
    Init complete, id=165, parent=0, distance=1, registration=1

    Your second life begins when you understand you only have one !

    TheoLT 1 Reply Last reply
    0
    • frenchoF frencho

      Hi,
      I'm having a problem with both RFM69 and NRF24 radio between node and gateway !
      First I tried with RFM69, then wanted to check if still had the same FAIL with NRF24 : bingo, same st=fail

      On the doc I found about the debug message, I undstand st=Fail means that the gateway doesn't send Ack
      I really don't understand how it could be possible that with 2 differents radio type (NRF24 and RFM69) I get the same problem.

      does anyone have an idea where this st=fail could come from ?

      see below the log on the node side with NRF24 module.
      TSP:PING:SEND (dest=0)
      TSP:MSG:SEND 165-165-0-0 s=255,c=3,t=24,pt=1,l=1,sg=0,ft=0,st=ok:1
      TSP:MSG:READ 0-0-165 s=255,c=3,t=25,pt=1,l=1,sg=0:1
      TSP:MSG:PONG RECV (hops=1)
      TSP:CHKUPL:OK
      TSM:UPL:OK
      TSM:READY
      TSP:MSG:SEND 165-165-0-0 s=255,c=3,t=15,pt=6,l=2,sg=0,ft=0,st=ok:0100
      !TSP:MSG:SEND 165-165-0-0 s=255,c=0,t=17,pt=0,l=5,sg=0,ft=0,st=fail:2.0.0
      TSP:MSG:SEND 165-165-0-0 s=255,c=3,t=6,pt=1,l=1,sg=0,ft=1,st=ok:0
      TSP:MSG:SEND 165-165-0-0 s=255,c=3,t=11,pt=0,l=18,sg=0,ft=0,st=ok:Temperature Sensor
      TSP:MSG:SEND 165-165-0-0 s=255,c=3,t=12,pt=0,l=3,sg=0,ft=0,st=ok:1.1
      TSP:MSG:SEND 165-165-0-0 s=0,c=0,t=6,pt=0,l=0,sg=0,ft=0,st=ok:
      Request registration...
      TSP:MSG:SEND 165-165-0-0 s=255,c=3,t=26,pt=1,l=1,sg=0,ft=0,st=ok:2
      TSP:MSG:READ 0-0-165 s=255,c=3,t=27,pt=1,l=1,sg=0:1
      Node registration=1
      Init complete, id=165, parent=0, distance=1, registration=1

      TheoLT Offline
      TheoLT Offline
      TheoL
      Contest Winner
      wrote on last edited by
      #2

      @frencho I've seen this one also. It occurs only when a node is being powered on. It think it's because it's sending the messages during the handshake to fast after each other. Because when I turn on debug and a lot of serial.print statements it doesn't occur. But when I remove them I always see the red led on my gateway blink one time. But regardless of that the Node continuous to connect to the gateway correctly.

      I've also noticed that you shouldn't use a request before the presentation method has been executed fully. The node will report errors if you do.

      frenchoF 1 Reply Last reply
      0
      • TheoLT TheoL

        @frencho I've seen this one also. It occurs only when a node is being powered on. It think it's because it's sending the messages during the handshake to fast after each other. Because when I turn on debug and a lot of serial.print statements it doesn't occur. But when I remove them I always see the red led on my gateway blink one time. But regardless of that the Node continuous to connect to the gateway correctly.

        I've also noticed that you shouldn't use a request before the presentation method has been executed fully. The node will report errors if you do.

        frenchoF Offline
        frenchoF Offline
        frencho
        wrote on last edited by
        #3

        @TheoL you mean send request registration before init complete ?

        But that's the mysensors core which handle all that part, I didn't do anything ?
        I'm using the master, and I have been told that there could be a bug. I'll try tonight the dev branch and see if I have the same behavior

        Your second life begins when you understand you only have one !

        1 Reply Last reply
        0
        • korttomaK Offline
          korttomaK Offline
          korttoma
          Hero Member
          wrote on last edited by
          #4

          This looks similar to what I experienced -> https://forum.mysensors.org/topic/5109/rfm69-based-nodes-unable-to-report-lib-version

          • Tomas
          frenchoF 1 Reply Last reply
          0
          • korttomaK korttoma

            This looks similar to what I experienced -> https://forum.mysensors.org/topic/5109/rfm69-based-nodes-unable-to-report-lib-version

            frenchoF Offline
            frenchoF Offline
            frencho
            wrote on last edited by
            #5

            @korttoma if you solved your pb, how did you do it ?

            Your second life begins when you understand you only have one !

            1 Reply Last reply
            0
            • korttomaK Offline
              korttomaK Offline
              korttoma
              Hero Member
              wrote on last edited by
              #6

              I have not solved it yet.

              • Tomas
              1 Reply Last reply
              0
              Reply
              • Reply as topic
              Log in to reply
              • Oldest to Newest
              • Newest to Oldest
              • Most Votes


              22

              Online

              11.7k

              Users

              11.2k

              Topics

              113.1k

              Posts


              Copyright 2025 TBD   |   Forum Guidelines   |   Privacy Policy   |   Terms of Service
              • Login

              • Don't have an account? Register

              • Login or register to search.
              • First post
                Last post
              0
              • MySensors
              • OpenHardware.io
              • Categories
              • Recent
              • Tags
              • Popular