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. Problem with sensor route

Problem with sensor route

Scheduled Pinned Locked Moved Troubleshooting
8 Posts 4 Posters 4.0k 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.
  • T Offline
    T Offline
    Tang
    wrote on last edited by
    #1

    I created a new sensor today and tested it near my gateway.
    The sensor is supposed to be out of my gateway range (behind 3 thick walls), but installed in the place it was built for (open/close my garage door) it manages to send sometimes some messages :S
    To handle my range problem a repeater is installed just behind the first wall and is repeating messages from 3 others sensors.
    Seeing gateway messages, I saw messages from my new sensor are not using the repeater.
    What is the event that forces sensor to change its route? And is there a way to force it manually (without clearing eeprom) ?
    Thanks

    1 Reply Last reply
    0
    • barduinoB Offline
      barduinoB Offline
      barduino
      wrote on last edited by
      #2

      I think it needs to fail a couple of times before it sarts looking for another parent node.

      I have a similar situation when I'm coding near the GW or away from it and closer to the repeater, but it does find it in the end.

      1 Reply Last reply
      0
      • T Offline
        T Offline
        Tang
        wrote on last edited by Tang
        #3

        No way to make it find a new route after 4 days.
        I decided to clear eeprom and the sensor is still in bad state.
        It always display

        find parent
        send: 255-255-255-255 s=255,c=3,t=7,pt=0,l=0,sg=0,st=bc:
        find parent
        send: 255-255-255-255 s=255,c=3,t=7,pt=0,l=0,sg=0,st=bc:
        find parent
        send: 255-255-255-255 s=255,c=3,t=7,pt=0,l=0,sg=0,st=bc:
        find parent
        send: 255-255-255-255 s=255,c=3,t=7,pt=0,l=0,sg=0,st=bc:
        

        on my gateway i receive:

        0/0;INTERNAL;0;I_LOG_MESSAGE;read: 2-2-255 s=255,c=3,t=8,pt=1,l=1,sg=0:1
        0/0;INTERNAL;0;I_LOG_MESSAGE;read: 2-2-255 s=255,c=3,t=8,pt=1,l=1,sg=0:1
        0/0;INTERNAL;0;I_LOG_MESSAGE;read: 2-2-255 s=255,c=3,t=8,pt=1,l=1,sg=0:1
        0/0;INTERNAL;0;I_LOG_MESSAGE;read: 2-2-255 s=255,c=3,t=8,pt=1,l=1,sg=0:1
        

        I tried with 2 differents NRF (with 4.7µf cap)
        Before clearing eeprom, the sensors successfully sends its data directly to gateway (without passing though repeater) but gateway failed still failed to send command to sensor
        Gateway and repeater have NFR with external antenna.

        I don't know exactly where is the problem:

        • is there a communication problem between gateway and controller ?
        • is there a problem with my sensor ?

        Near my new sensor (2 meters) i have an another sensor that is working fine but it's not an actuator.
        I have another actuator that is out of gateway sensor and connected to repeater #2.

        To sum up my configuration:
        #111 (actuator) -> #2 (repeater) -> gateway ==> no pb (report state and receive command successfully)
        #1(power sensor) -> #2 (repeater) -> gateway => no pb
        #110 (temp sensor) -> #2 (repeater) -> gateway => no pb

        Is someone have some clue to investigate?

        1 Reply Last reply
        0
        • V Offline
          V Offline
          vil1driver
          wrote on last edited by
          #4

          Set the parent id in sketch.

          1 Reply Last reply
          0
          • T Offline
            T Offline
            Tang
            wrote on last edited by
            #5

            I forced the parent id as vil1driver suggested and I saw on my controller id request (give id 3) with no error

            2015-Sep-01 22:16:47.793938 [DEBUG]  => RECEIVING: 255/255;INTERNAL;0;I_ID_REQUEST;
            2015-Sep-01 22:16:47.794094 [DEBUG] Free id found: 3
            2015-Sep-01 22:16:47.794176 [DEBUG]  => SENDINGv15: 255;255;3;0;4;3<NL>
            2015-Sep-01 22:16:47.830373 [DEBUG]  => RECEIVING: 0/0;INTERNAL;0;I_LOG_MESSAGE;send: 0-0-2-255 s=255,c=3,t=4,pt=0,l=1,sg=0,st=ok:3
            

            But my sensor seems to have problem receiving the response

            req id
            255-255-2-0 s=255,c=3,t=3,pt=0,l=0,sg=0,st=fail:0
            sensor started, id=255, parent=2, distance=1
            req id
            255-255-2-0 s=255,c=3,t=3,pt=0,l=0,sg=0,st=fail:0
            req id
            255-255-2-0 s=255,c=3,t=3,pt=0,l=0,sg=0,st=fail:0
            req id
            255-255-2-0 s=255,c=3,t=3,pt=0,l=0,sg=0,st=fail:0
            req id
            255-255-2-0 s=255,c=3,t=3,pt=0,l=0,sg=0,st=fail:0
            req id
            255-255-2-0 s=255,c=3,t=3,pt=0,l=0,sg=0,st=fail:0
            

            So do you think my problem is a circuit issue?
            Is it possible to send successfully all packets and have problem receiving them?

            1 Reply Last reply
            0
            • T Offline
              T Offline
              Tang
              wrote on last edited by
              #6

              Hourra I found my problem !
              I connected directly the NRF to RAW pin instead of regulated one (VCC).
              Now everything is working fine

              Thank you guys for your help ;-)

              1 Reply Last reply
              0
              • T Offline
                T Offline
                torehc
                wrote on last edited by
                #7

                Hello, I have the same problem but do not use the raw Arduino pin. Could you put a picture of the solution? or something similar. Thank you

                1 Reply Last reply
                0
                • T Offline
                  T Offline
                  Tang
                  wrote on last edited by
                  #8

                  Hi torehc

                  vcc (3.04v)-----arduino RAW pin
                  gnd------arduino GND
                  NRF vcc-----arduino VCC (regulated 3.3 in my case)

                  If you have problem with route i suppose it is a problem with your power supply. NRF seems to be really erratic.
                  Also you must add a capacitor on nrf too.

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


                  14

                  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