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. Ethernet Gateway and Window Sensor dont communicate.

Ethernet Gateway and Window Sensor dont communicate.

Scheduled Pinned Locked Moved Troubleshooting
6 Posts 3 Posters 1.5k Views 1 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.
  • M Offline
    M Offline
    meddie
    wrote on last edited by
    #1

    Hi together,

    yesterday i soldered an ethernet controller and a window sensor. But it seems not to work, and i ask me how to check. It looks like the modules dont send. But i dont know how to check this.

    When i connect the Controller and the Sensor to my computer on serial console i see only this output:

    Controller:

    0;0;3;0;9;gateway started, id=0, parent=0, distance=0
    

    Window Sensor:

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

    I used on them the API 1.5. On both i used the sample Sketches.

    Can you help me please, how can i check the radio is working.

    I have on both modules an arduine nano. And on the controller i have a NRF24l01p with PA and sma Connector. On the Window Sensor i have a small nrf24l01 (modell 3629)

    Thank you in Advance
    Greets Eddie

    1 Reply Last reply
    0
    • E Offline
      E Offline
      ericvdb
      wrote on last edited by
      #2

      Your sensor is requesting an ID. What controller are you using?

      1 Reply Last reply
      0
      • M Offline
        M Offline
        meddie
        wrote on last edited by
        #3

        sorry i mean the ethernet gateway.
        this one: http://www.mysensors.org/build/ethernet_gateway

        OK, but i have read at the api that the sensor get automaticaly an id from gateway.
        If not where i can configure the id?
        thank you

        1 Reply Last reply
        0
        • E Offline
          E Offline
          ericvdb
          wrote on last edited by ericvdb
          #4

          No, you are getting it wrong.

          The gateway never assigns ID to sensors, thats the task of a controller:

          sensor ---> gateway ---> controller (where controller is one of the controllers listed here

          Alternatively, you can set a static ID on your sensornode by doing

          // Assign ID 6 to sensor node
          gw.begin(NULL,6,false);
          

          instead of

          gw.begin(NULL,AUTO,false);
          
          1 Reply Last reply
          0
          • M Offline
            M Offline
            meddie
            wrote on last edited by
            #5

            Ah, ok. I use FHEM. In FHEM i have defined the gateway. In FHEM i see this:

            DEF	 10.0.0.253:5003
            DeviceName  10.0.0.253:5003
            FD 5
            NAME CUL_MySensors
            NOTIFYDEV global
            NR 41
            NTFY_ORDER 50-CUL_MySensors
            PARTIAL 
            STATE startup complete
            TYPE MYSENSORS
            ack 0
            inclusion-mode 1
            outstandingAck 0
            version 1.5.1
            
            Readings:
            
            connection  startup complete  2015-12-18 16:43:30
            state  opened  2015-12-18 16:43:30
            
            Attributes
            autocreate 1
            stateFormat connection
            

            that is what i see on serial monitor of the sensor:

            find parent
            send: 255-255-255-255 s=255,c=3,t=7,pt=0,l=0,sg=0,st=bc:
            sensor started, id=255, parent=255, distance=255
            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:
            
            1 Reply Last reply
            0
            • alexsh1A Offline
              alexsh1A Offline
              alexsh1
              wrote on last edited by
              #6

              I am not familiar with FHEM, but I think you problem is in the FHEM settings - the controller is not assigning the ID to the sensor.

              Did you try to assign the node ID manually in gw.begin?

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


              17

              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