I agree with your thoughts completely, as those were my initial thoughts as well.
After moving the hub from an Eero ethernet connection to his Verizon LAN port, he was effectively on a totally different network, and even the double NAT was eliminated.
He experienced connection problems on this new network as well, which at first thought suggests the hub is the problem and not the Eero network.
What bothers me is that the symptoms were different on the Verizon network. Although the OP had tried setting a static IP previously, I would have liked to test that theory again on the Verizon network.
I would also like to ensure that during the hub reset process, the steps and LED colors matched the official procedure.
Use the point of a pen (or other small, blunt object) to press and hold this button for at least 7 seconds.
Release the button, and the LED on the front of the hub will blink. (If the LED does not blink, return to the previous step and try again, paying attention to the timing.)
After a few more seconds, the LED will turn solid blue as the hub reboots.
Finally, after a few minutes, the LED should return to green, at which point the hub has finished rebooting and should again be accessible.
No, I totally understand, and I truly appreciate your assistance. I'm confident the network reboot steps were completed as instructed. The reset button was pressed for approximately seven seconds, released when the LED turned blue, and the device eventually returned to green status.
I also have several other Ethernet-connected devices attached to both the Eero and the Verizon router, and none of them are experiencing IP address or DNS-related issues. Given that the network configuration has been thoroughly reviewed and other devices are operating normally, that's why I believe this may be a hardware issue with the hub itself.
We could always try to see if a different hub behaves differently. We will process your Hub Protect claim and send you a replacement to try. Thanks for all your troubleshooting efforts, I can only imagine the frustration you've been through.
Otherwise, your eero gateway has one LAN port to which you have directly connected the hub. There is no place to attach any other Ethernet-connected devices.
If instead you do have switches or additional eero nodes involved, then those would have been worthy of mention.
Reading this thread I think I see what’s happening. Your eero mesh and hub are on different networks. (you should make your eero mesh passthrough to keep it all flat but that said what I’m about to say may resolve the issue)
So since you have multiple subnets going on, Hubitat only recognizes it’s own subnet. You need to add the other subnet(s) via end point…..
From a web browser, http://<Hub IP Address>/hub/allowSubnets?<Second Subnet, i.e. 123.123.123.0>,<Third Subnet>
If this doesn’t work then based on you not being able to ping outbound, something in your firewall is blocking things.
My device is back online, but I clearly have an issue with the NIC card. This may have been part of the problem in addition to the Eero update.
I am confident there is a hardware issue with the NIC because I changed Ethernet cables and the problem still exists. Additionally, if I insert the cable fully until it clicks into place, the connection stops working. I have to position the cable a certain way for the connection to remain active.
I still have not received the replacement device. I hope this delay is not typical customer service, as this has now been a three-week process.
Please provide an update on the status of the replacement device.
This version clearly documents the troubleshooting you performed and the symptoms that point to a faulty network port/NIC.
Apologies for the delay! Your case was accidentally closed after our last request for your shipping address. I’ve fixed this, and your replacement order will be placed today. Keep an eye out for a confirmation email with details shortly.