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. MySensors SenseBender GW + W5100

MySensors SenseBender GW + W5100

Scheduled Pinned Locked Moved Troubleshooting
4 Posts 2 Posters 1.2k 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.
  • J Offline
    J Offline
    JWB
    wrote on last edited by
    #1

    I am a newbe on this forum so hopefully I won't stumble too many times!

    I have a MYSensors GW with a W5100 Ethernet module that I am trying to bring up.

    I started with operating the GW as a serial GW talking to either MyController.org or Homeassistant Controllers.

    This setup works fine with no issues between the controller and GW or any RF nodes.

    I then migrated the GW to Ethernet using the MYSensors Webserver sketch to checkout the W5100.

    Everything worked fine. No issues. I used nmap to query the W5100 @ 192.168.1.99 and I see that port 80 /tcp is open and the service is http. This is good.

    I then loaded the MYSensors GW sketch and tried running the Homeassistant Controller app.

    The Controller keeps trying to connect to the GW, but, fails. This scenario keeps repeating.

    I then tried the MYController.org app and I see a similar connection failure.

    So at this time both controller apps are unable to talk to the GW via Ethernet.

    I can ping the GW so I know it is there.

    I used nmap and it shows port 5003 is closed, service =filemaker.

    I was expecting port 5003 to be open, not closed!

    I suspect this is why the Controller apps are unable to communicate with the GW.

    I checked the sketch and I see where port 5003 is defined, but, I do not understand why the port is closed.

    I believe at this point the h/w is OK and the issue is with the s/w.

    I am not a s/w expert so I am in need of some help tracking down why the Ethernet is not working.

    I have uploaded the sketch I am using as well as the IDE compiler log.

    My IDE is version 1.8.2.

    0_1497553226117_sketch_jun05a_SenseBender_Gateway_Ethernet.ino

    0_1497553530246_Sketch_jun05a_SB_GW_Ethernet_Compile_Log.txt

    J 1 Reply Last reply
    0
    • J JWB

      I am a newbe on this forum so hopefully I won't stumble too many times!

      I have a MYSensors GW with a W5100 Ethernet module that I am trying to bring up.

      I started with operating the GW as a serial GW talking to either MyController.org or Homeassistant Controllers.

      This setup works fine with no issues between the controller and GW or any RF nodes.

      I then migrated the GW to Ethernet using the MYSensors Webserver sketch to checkout the W5100.

      Everything worked fine. No issues. I used nmap to query the W5100 @ 192.168.1.99 and I see that port 80 /tcp is open and the service is http. This is good.

      I then loaded the MYSensors GW sketch and tried running the Homeassistant Controller app.

      The Controller keeps trying to connect to the GW, but, fails. This scenario keeps repeating.

      I then tried the MYController.org app and I see a similar connection failure.

      So at this time both controller apps are unable to talk to the GW via Ethernet.

      I can ping the GW so I know it is there.

      I used nmap and it shows port 5003 is closed, service =filemaker.

      I was expecting port 5003 to be open, not closed!

      I suspect this is why the Controller apps are unable to communicate with the GW.

      I checked the sketch and I see where port 5003 is defined, but, I do not understand why the port is closed.

      I believe at this point the h/w is OK and the issue is with the s/w.

      I am not a s/w expert so I am in need of some help tracking down why the Ethernet is not working.

      I have uploaded the sketch I am using as well as the IDE compiler log.

      My IDE is version 1.8.2.

      0_1497553226117_sketch_jun05a_SenseBender_Gateway_Ethernet.ino

      0_1497553530246_Sketch_jun05a_SB_GW_Ethernet_Compile_Log.txt

      J Offline
      J Offline
      JWB
      wrote on last edited by
      #2

      @JWB said in MySensors SenseBender GW + W5100:

      I am a newbe on this forum so hopefully I won't stumble too many times!

      I have a MYSensors GW with a W5100 Ethernet module that I am trying to bring up.

      I started with operating the GW as a serial GW talking to either MyController.org or Homeassistant Controllers.

      This setup works fine with no issues between the controller and GW or any RF nodes.

      I then migrated the GW to Ethernet using the MYSensors Webserver sketch to checkout the W5100.

      Everything worked fine. No issues. I used nmap to query the W5100 @ 192.168.1.99 and I see that port 80 /tcp is open and the service is http. This is good.

      I then loaded the MYSensors GW sketch and tried running the Homeassistant Controller app.

      The Controller keeps trying to connect to the GW, but, fails. This scenario keeps repeating.

      I then tried the MYController.org app and I see a similar connection failure.

      So at this time both controller apps are unable to talk to the GW via Ethernet.

      I can ping the GW so I know it is there.

      I used nmap and it shows port 5003 is closed, service =filemaker.

      I was expecting port 5003 to be open, not closed!

      I suspect this is why the Controller apps are unable to communicate with the GW.

      I checked the sketch and I see where port 5003 is defined, but, I do not understand why the port is closed.

      I believe at this point the h/w is OK and the issue is with the s/w.

      I am not a s/w expert so I am in need of some help tracking down why the Ethernet is not working.

      I have uploaded the sketch I am using as well as the IDE compiler log.

      My IDE is version 1.8.2.

      0_1497553226117_sketch_jun05a_SenseBender_Gateway_Ethernet.ino

      0_1497553530246_Sketch_jun05a_SB_GW_Ethernet_Compile_Log.txt

      Here is the serial log from the GW.0_1497554846818_GW Ethernet Serial Log.txt

      1 Reply Last reply
      0
      • J Offline
        J Offline
        JWB
        wrote on last edited by
        #3

        I did some further troubleshooting and I believe I figured out why the Ethernet is failing. I was using the following in the sketch and I think I misunderstood what it was used for:
        "// Controller ip address. Enables client mode (default is "server" mode).
        // Also enable this if MY_USE_UDP is used and you want sensor data sent somewhere.
        #define MY_CONTROLLER_IP_ADDRESS 192,168,1,68"
        I thought this was used to tell the GW where the Controller was located. However, with this enabled, the Controller cannot talk to the GW. I also see a minor error pop up when this feature is enabled.
        "C:\Users\JB's_Quad_PC\AppData\Local\Arduino15\packages\MySensors\hardware\samd\1.0.5\libraries\Ethernet\src\utility\socket.cpp:365:6: warning: unused parameter 's' [-Wunused-parameter]

        void flush(SOCKET s)
        " .
        I really don't know what this error is or if it is an indication of some other compiler error that is not clearly shown.
        After disabling "MY_CONTROLLER_IP_ADDRESS" I was able to finally make an Ethernet connection between Homeassistant and the GW. YES!
        I used nmap and it also showed port 5003 was open now. YES!
        Time to move on....

        1 Reply Last reply
        0
        • T Offline
          T Offline
          tbowmo
          Admin
          wrote on last edited by
          #4

          @JWB

          That setting is turning the gateway into a "client" which needs to connect to a server (which is your controller). Without this set it is running as a "server" which accepts incoming connections from other devices on the network (like your controller)

          1 Reply Last reply
          0

          Hello! It looks like you're interested in this conversation, but you don't have an account yet.

          Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

          With your input, this post could be even better 💗

          Register Login
          Reply
          • Reply as topic
          Log in to reply
          • Oldest to Newest
          • Newest to Oldest
          • Most Votes


          58

          Online

          12.0k

          Users

          11.2k

          Topics

          113.4k

          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