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. Testing with a repeater node gives this sometimes in the log file : !TSF:RTE:100 UNKNOWN

Testing with a repeater node gives this sometimes in the log file : !TSF:RTE:100 UNKNOWN

Scheduled Pinned Locked Moved Troubleshooting
4 Posts 2 Posters 48 Views 2 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.
  • E Offline
    E Offline
    evb
    wrote on last edited by
    #1

    The logparser isn't giving more information.
    Does somebody knows what it means?

    mfalkviddM 1 Reply Last reply
    0
    • E evb

      The logparser isn't giving more information.
      Does somebody knows what it means?

      mfalkviddM Offline
      mfalkviddM Offline
      mfalkvidd
      Mod
      wrote on last edited by
      #2

      @evb if I read the code correctly, the repeater received a message with destination node 100, but the repeater does not know how to route traffic to node 100.

      Could you describe the topology of your network? Which node is sending? Where is the destination? Where is the gateway? Where is the repeater? Where is the sender?

      1 Reply Last reply
      0
      • E Offline
        E Offline
        evb
        wrote on last edited by
        #3

        @mfalkvidd, ok then I understand the error.
        Node 100 is my display node that I am also testing and it isn't connected for the moment.

        Maybe a good extension for the logparser code? --> it should mention this extra information :-)

        Thanks a lot!

        mfalkviddM 1 Reply Last reply
        1
        • E evb

          @mfalkvidd, ok then I understand the error.
          Node 100 is my display node that I am also testing and it isn't connected for the moment.

          Maybe a good extension for the logparser code? --> it should mention this extra information :-)

          Thanks a lot!

          mfalkviddM Offline
          mfalkviddM Offline
          mfalkvidd
          Mod
          wrote on last edited by
          #4

          @evb I dug into the log parser and it contains this:

          { re: "!TSF:RTE:DST (\\d+) UNKNOWN", d: "Routing for destination <b>$1</b> unknown, sending message to parent" },
          

          so it is already in the log parser, but the regex is wrong. I think it should look like this:

          { re: "!TSF:RTE:(\\d+) UNKNOWN", d: "Routing for destination <b>$1</b> unknown, sending message to parent" },
          

          With that change, the log parser looks like this for your message:
          19a5c4d3-f29c-428a-9dcf-66bf1819bf6e-image.png

          I have created https://github.com/mysensors/MySensors/pull/1462 to fix this.

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


          12

          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