Hubitat causing router diagnostic errors

Hi,
Why would my internet service provider router diagnostics, generate an error when the Hubitat is connected?

Background

  • The router provided by my Internet provider has a Network Diagnostic tool.
  • One of the tests is "Checking Ethernet Connections"
  • When the Hubitat is not connected, the test completes with 100% success
  • When the Hubitat is connected I receive the message "Your home network has a few problems."

Configuration

  • Hubtiat version C-7
  • Platform version 2.3.3.130
  • Hubitat is plugged directly into rear of router

Tests so far

  • Tried different port on router
  • Changed ethernet cable between Hubitat and router
  • Changed network setting from auto-negotitate and 100mbps
  • Hubitat has fixed IP
  • Restarted router and Hubitat

Anything else I shoud try?

Cheers

Strange indeed. I would leave hubiat at Auto though, not fixed. (Fixed 100 has cause problems with packet speed). I'm wondering if for some odd reason it's expecting 1gb vs 100mb and it thinks something is off. Either way it seems if it's on the router end. In the end if everything is working as expected I wouldn't worry about it. Also curious, does it say what the problem is? If not that's a crappy diagnostic tool.

2 Likes

Not sure what that means. Did you change it to 100, fixed? Which end, HE or router? If one end is set to autonegotiate, the other (fixed) end must also be set to half duplex, or you'll have issues.

Do you mean an address reservation in the router, or a static IP assigned in the HE?

I suspect your router is just wrong, and not made to expect anything outside a simplistic DHCP only network which it controls.

Welcome to the community!

I'm going to go with @rlithgow1 and @mikes suggestion that the router may just be dumb enough to see a problem where there isn't one. My switches will show these as a color other than green (colorblind so I'm not sure what they actually are, maybe yellow or just a lighter green? All a mystery to me other than they are different), but won't actually identify them as needing attention.

One thing you could do is validate there is no packet loss... ping your router from another device for a while and see if it generates any errors. A crude test but if there is a serious problem it should show up.

1 Like

Possibly because they're 100mb instead of 1000mb?

1 Like

Oh yes absolutely. The mystery to me is only the color they appear.

1 Like

Boiled Pea green while the ones on the left are more of a grass green

3 Likes

Update

  • I repatched the Hubitat into a switch which is connected to the router and the diagnostics test is now successful, which for me is not optimal but I can live with it

Answer to queries

  • auto-negotitate : in Network Setup I changed the setting for internet speed from "Auto Negotiated" to "Fix 100mbps" and back again. Test result was the same
  • Fixed IP : Hubitat has a static IP address and is not using DHCP. On the router I have reserved a range of IP number, so that I can assign a fixed IP number when required. I have verified that the assigned number is within this range and also confirmed that the number is not assigned to another device.
  • Router port Speed - I have not been able to find a way to change the port speed on the router

Find attached samples of a failed diagnostics test and a successful one.


I'd bet my next paycheck that they hard coded anything below 1 GB as being a "problem."

4 Likes

It should auto-negotiate down to 100mb which the Hubitat runs at.

1 Like

@user2845

What @FriedCheese2006 has written is right on the mark! The "error" provided by your router's interface confirms it ....

Error with Hubitat

Hubitat's ethernet interface is limited to 100 Mbps, which is more than sufficient for its use, and off course, this will have zero impact on the rest of the devices on your LAN.

But your router doesn't know that the Hubitat hub is not something like an ethernet switch. And, if it were a switch, the 100 mbps interface would be limiting for all the devices connected to that switch - especially if those devices were capable of gigabit networking.

If I were you, I would connect the Hubitat directly to your router, ignore the error, and go on using it. It will have zero impact on your LAN. In this instance, that error is irrelevant.

3 Likes

Be glad that you don't have a RadioRA 2 Main Repeater. It's a got a 10Mbps ethernet connection. Possible router message: "Come on old man!"

6 Likes

Comes with a BNC connector and terminating resistor?

(Dating myself badly.)

6 Likes

I'll join you in the 10Base2 memory lane .... I wrote a packet driver for an 8-bit Cabletron card. Can no longer remember the model number :rofl:

2 Likes

10BASE5, commonly called thicknet, anyone? We used that to connect to our NetWare server.

I moved to another company after that where we used thinnet (10BASE2) running LANtastic. It was cheap, but it got the job done.

Our central office had a tokenring setup. The rest of us used sneaker-net.

Lol. MIS used token ring for the AS400s. They also connected Ethernet to it. They gave us, Engineering, our own segment in the Ethernet network. After we were up and running their system administrator told us we were the only portion of the network that had “enough traffic to measure”.

1 Like

Was just last year I purged an old Bay Networks token ring switch I had up on a shelf. Forgot I even had it until we were moving. Heh, I should have sold it on antiques road show...LOL. Though back in the 90's I used 10 Base T to run my bbs that I had (Wow, I had 2 bbs's over the course of a decade...I'm farking old....)

3 Likes

Now that brings back memories. I ran LANTastic at home. With 3com 3C509 ethernet cards.

3 Likes

I beta tested one ofArtisoft's new ethernet cards back in the day. They were going for a package. Concept died on the table once windows 3.1 WFW came out.