Announcement

Collapse
No announcement yet.

Ethernet device does not appear on Unifi network

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Ethernet device does not appear on Unifi network

    I'm trying to add an 8-channel relay board to my network - as described here. I can access it on a temporary network using an old TP-link router without difficulty. It has a fixed IP address, which I can and did change, but when I plug it into my Unifi network I cannot find it. It is unreachable by ping and it does not show up on the client list. Any ideas or suggestions would be welcome.
    Mike____________________________________________________________ __________________
    HS3 Pro Edition 3.0.0.548

    HW: Stargate | NX8e | CAV6.6 | Squeezebox | PCS | WGL 800RF, Rain8Net+ | RFXCOM | QSE100D | Vantage Pro | Green-Eye | X10: XTB-232, -IIR | Edgeport/8 | Way2Call | Ecobee3

  • #2
    I'd try not using a static IP on the device ... instead let unifi find the device normally, let it assign the IP. Then setup unifi to assign a static to the device (after which you will have to reconnect the device)

    Comment


    • #3
      It only allows a static IP address. It does not have provision for DHCP assignment as far as I can determine.
      Mike____________________________________________________________ __________________
      HS3 Pro Edition 3.0.0.548

      HW: Stargate | NX8e | CAV6.6 | Squeezebox | PCS | WGL 800RF, Rain8Net+ | RFXCOM | QSE100D | Vantage Pro | Green-Eye | X10: XTB-232, -IIR | Edgeport/8 | Way2Call | Ecobee3

      Comment


      • #4
        I think you are correct and I was wrong about pfSense assigning static address. My settings of the unit using default user/pass of admin and 12345678 are below

        Click image for larger version

Name:	Capture.PNG
Views:	65
Size:	42.0 KB
ID:	1373198

        I am able to ping the device

        Click image for larger version

Name:	Capture0.PNG
Views:	50
Size:	23.3 KB
ID:	1373199

        During ping wireshark shows the following

        Click image for larger version

Name:	Capture1.PNG
Views:	50
Size:	152.5 KB
ID:	1373200
        I use Unifi AP for WiFi, but pfSense for wired router.

        Comment


        • #5
          A couple of ideas

          1) Since you are assigning a fixed address, make sure that address is outside of the DHCP assignment range.

          2) Run the command 'arp -a' on a Windows box to see if there is an entry for the fixed IP address. If necessary, go back to the temporary network, run the arp command and note the 'physical' (MAC) address. That should be the same when you go back to your main network.

          Comment


          • #6
            Originally posted by zwolfpack View Post
            1) Since you are assigning a fixed address, make sure that address is outside of the DHCP assignment range.
            It is. DHCP range is 100-150. Fixed address is 173.

            2) Run the command 'arp -a' on a Windows box to see if there is an entry for the fixed IP address. If necessary, go back to the temporary network, run the arp command and note the 'physical' (MAC) address. That should be the same when you go back to your main network.
            It does not appear on the list.

            Mike____________________________________________________________ __________________
            HS3 Pro Edition 3.0.0.548

            HW: Stargate | NX8e | CAV6.6 | Squeezebox | PCS | WGL 800RF, Rain8Net+ | RFXCOM | QSE100D | Vantage Pro | Green-Eye | X10: XTB-232, -IIR | Edgeport/8 | Way2Call | Ecobee3

            Comment


            • #7
              Originally posted by Michael McSharry View Post
              My settings of the unit using default user/pass of admin and 12345678 are below
              I use Unifi AP for WiFi, but pfSense for wired router.
              Michael,
              My settings are identical to yours with the exception that my address is 192.168.1.173 and I left the primary DNS server as it was shipped. Could the DNS server address be a factor? Since this is an Ethernet device, I would not expect the AP to matter. I wonder about the Unifi gateway, though.

              Mike____________________________________________________________ __________________
              HS3 Pro Edition 3.0.0.548

              HW: Stargate | NX8e | CAV6.6 | Squeezebox | PCS | WGL 800RF, Rain8Net+ | RFXCOM | QSE100D | Vantage Pro | Green-Eye | X10: XTB-232, -IIR | Edgeport/8 | Way2Call | Ecobee3

              Comment


              • #8
                Changing the DNS server had no effect, but I decided to try TCP even though I cannot ping the device. And, voila!
                mcsMQTT is clearly finding the relay board and communicating with it.



                Mike____________________________________________________________ __________________
                HS3 Pro Edition 3.0.0.548

                HW: Stargate | NX8e | CAV6.6 | Squeezebox | PCS | WGL 800RF, Rain8Net+ | RFXCOM | QSE100D | Vantage Pro | Green-Eye | X10: XTB-232, -IIR | Edgeport/8 | Way2Call | Ecobee3

                Comment


                • #9
                  What UniFi device are you using to add the device?

                  Can you try and put the default IP address as shipped with the device back in and test again with UniFi to see if it connects. If it does then set the new static IP within UniFi.

                  Do you also have access to this information below? :

                  Firmware V5.0.5 update:
                  - modify web pages , more humane, add fully open, fully closed operation
                  - optimized mobile access , mobile phone screen adaptation, big screen small screen are suitable ;
                  - deepen memory pool , speed up response ;
                  - Repair IE, 360 and other browsers can not control and garbled bug, yet even UCweb browsers such agents can be used ;
                  - Adding touch capabilities, and you can set the time for touch 1-255s
                  - Add MAC modify , easy LAN networking ;
                  - relay power-down state memory function, the function can be configured ;
                  - inputs and outputs can be configured association ;
                  - Firmware V5.0.6 update :
                  - secondary development can modify TCP port ;
                  - can modify the HTTP port , port mapping easier to solve the 80 and 8080 ports are shielded telecommunications issues




                  Link for software:Click iotzone.cn/download/23-cn.html
                  Default parameter:Click 192.168.1.166
                  User name:admin code:12345678

                  From here :https://www.ebay.co.uk/itm/8-Channel...-/163108997395


                  Looking at that IP, looks similar to Michael McSharry 's apart from the subnet ....................????



                  Eman.
                  The People's Advocate.

                  Comment


                  • #10
                    Originally posted by Eman View Post
                    What UniFi device are you using to add the device?
                    I don't understand this question. I connect the board to my network with a patch cable. The Unifi controller does not report it as present on the network.

                    Can you try and put the default IP address as shipped with the device back in and test again with UniFi to see if it connects. If it does then set the new static IP within UniFi.
                    Started there. The controller does not recognize its presence. It doesn't use DHCP so I don't think the Unifi gateway can assign it an address.

                    Do you also have access to this information below?
                    yes

                    Mike____________________________________________________________ __________________
                    HS3 Pro Edition 3.0.0.548

                    HW: Stargate | NX8e | CAV6.6 | Squeezebox | PCS | WGL 800RF, Rain8Net+ | RFXCOM | QSE100D | Vantage Pro | Green-Eye | X10: XTB-232, -IIR | Edgeport/8 | Way2Call | Ecobee3

                    Comment


                    • #11
                      I think this might have something to do with a bug in Unifi. There a few posts about Unifi controllers not liking certain static IP devices.
                      This might help explain: https://community.ui.com/questions/I...b-1b70826217a2
                      iCore5 Win 10 Pro x64 SSD

                      HS3 Pro Edition 3.0.0.435 Windows

                      BLOccupied:,Device History:,Yamaha:,UltraMon3:,mcsXap:,Restart:,UltraNetatmo3:, UltraM1G3:,Ultra1Wire3:,BLBackup:,Harmony Hub:,DoorBird:,UltraECM3:,Nanoleaf 3P:,UltraRachio3:,Z-Wave:,SDJ-Health:,BLGarbage:,Blue-Iris:,Chromecast:,Pushover 3P:,EasyTrigger:

                      Comment


                      • #12
                        Originally posted by mminehan View Post
                        I think this might have something to do with a bug in Unifi. There a few posts about Unifi controllers not liking certain static IP devices.
                        This might help explain: https://community.ui.com/questions/I...b-1b70826217a2
                        Thank you for the link. That sure sounds like what I'm seeing. Fortunately, I can access the relay boards by TCP, which is what I want to do. I only needed access to the web server to make configuration tweaks, which I did on a temporary network. So, as disappointing as the bug is, I can easily work around it for now.

                        Mike____________________________________________________________ __________________
                        HS3 Pro Edition 3.0.0.548

                        HW: Stargate | NX8e | CAV6.6 | Squeezebox | PCS | WGL 800RF, Rain8Net+ | RFXCOM | QSE100D | Vantage Pro | Green-Eye | X10: XTB-232, -IIR | Edgeport/8 | Way2Call | Ecobee3

                        Comment


                        • #13
                          Originally posted by Uncle Michael View Post
                          I don't understand this question. I connect the board to my network with a patch cable. The Unifi controller does not report it as present on the network.

                          Started there. The controller does not recognize its presence. It doesn't use DHCP so I don't think the Unifi gateway can assign it an address.

                          yes
                          I was thinking you have those new UDM devices. Say like if you have Vlans or setup.

                          And true if it doesn't use DHCP then it lucks the capability to shout to the local network asking for an IP address and other related information (like the gateway address, name servers etc) to be given to them.



                          Eman.
                          The People's Advocate.

                          Comment

                          Working...
                          X