I have two C7 hubs that show the same MAC in a mDNS search

I am using two C7 hubs both running 2.3.8.140.
Hub mesh is failing to link devices even though both hubs can ping each other and are on the same network (192.168.10.x). Sometimes devices show up as "Available" and sometimes not. In any case, clicking the "+" does not link the devices.

I used an mDNS browser to look at the two hubs and somehow both are using the same (incorrect) MAC address for mDNS.

This began a few months ago when I made the mistake of setting both hubs to a Static Address. I was never able to fix the trainwreck that caused so I gave up and changed both hubs to WIFI.

I believe the network settings are bashed up on both hubs and I have no way to fix them. By the way, the MAC that both hubs are using is the old ethernet MAC from hub 2, even though the Ethernet is disconnected.

Settings: Hub Details. "Hub name on LAN is" contains the mDNS name. Hubs come, factory default, as "Hubitat". They can't be the same name.

2 Likes

The hub names are different - hubitathouse.local, and hubitatbarn.local

1 Like

You could try the “network reset button” on the bottom of your hub. Just a thought.

I will try that again but I've done it so many times I'm afraid I'm going to wear it out.

2 Likes

I've tried the "Network Reset" button on both hubs. No change in symptoms.
I also did a soft reset and database restore on both hubs, with no change.

Is it possible to return a hub to its original factory condition?

If you do a simple Soft Reset (from the Diagnostic menu) then all the customization is gone. What remains are things that have no effective difference from a 'factory fresh'. The hub retains Latitude/longitude and timezone. Pushing the button on the bottom for 7 seconds, resets the network elements back to factory.

What it doesn't do is reset the Z-Radios, thus retaining all that work of joining/pairing devices.

1 Like

Can you give me an example of what you mean by "customization"? I've done the bottom button reset and the soft reset, and I do not notice any difference in function.

Here is a capture of the static IP settings for my main hub after a bottom button reset and a soft reset. The settings you see are wrong and I cannot change them.

Here is a capture of the static IP settings on my barn hub. These settings don't seem correct either but not as bad. Also I cannot change them.

At the top it's saying what IS. What your hub is using at the time of that screen cap is 192.168.10.20 via DHCP over WiFi.

You have a screen full of prior customizations :slight_smile: that will take effect IF you click that "Save and switch to static IP" button.

EDIT
and for your Barn hub, the potential changes are not fully filled out, so it would presumably bark if you tried to click the "Save and switch to static IP" button.

EDIT 2:

Presumably you know this because those 192.168.10 addresses (20 & 21) are what you're using in your browser to display those pages. You are NOT using 192.168.0.101, which is what you entered once upon a time.

So I should ignore the seemingly random settings. I was hoping that I was on to something. If the network settings are correct then I am no closer to solving my Hub Mesh problem.

Edit:
Arrgh!

I cannot duplicate this result. Today using a different mDNS browser the MAC addresses look correct. Still no joy from the Hub Mesh department.

If you can get the hubs back on ethernet you might have a better chance of reliable hub mesh. After doing a network reset you should be able to just plug in to ethernet (might need to reboot). Once the top of the network settings says you are connected via ethernet DHCP then you can disconnect the Wifi using the button on that same page.

Also, what does it look like on settings > Hub mesh for both hubs? Are they showing correct IP's?

Yes, the hubs have the appropriate IPs and they can ping each other. I will get on the ethernet thing next.

The hubs are back on ethernet. Unfortunately, while on ethernet the hubs will not connect to any network other than 192.168.0.x. This is my primary network and I don't want the hubs on it for security reasons. This is the original problem I had when I switched them to static IPs last year and is the reason I switched to WIFI.

When I try to change the Default Gateway settings in the Static IP screen I get this error: "IP address must belong to subnet 192.168.0.xxx or you will not be able to communicate with the hub"

"Good news everyone!" Switching to ethernet seems to have fixed the hub mesh problems. It took 30 minutes or so after connecting the ethernet and rebooting but the mesh finally connected and I have been able to share devices between hubs.

So it is fully working or still having the issue with not liking the network they are on?

I am guessing the Wifi you connected to was a segregated "guest" network?

The warning is correct, if you set the hubs to another subnet, you possibly will not be able to connect to them. You might be able to open something up between the two but then that defeats the purpose of segregating them doesn't it?

If you want them to get a different IP from DHCP, just set a reserved IP on the router.

Unless you are a network engineer and have business class equipment, you are better off just leaving everything on one subnet/LAN.

@rlithgow1 might be able to give some additional advice if you give us some more info.

1 Like

What is the subnet of the network you're trying to connect to? There isn't any reason why hubitat can't go on a network other than 192.168.x.x

As far as I can tell the hub mesh is fully working.

I placed the hubs on a reserved IP when I connected them to ethernet.

The other subnet is 192.168.10.xxx. How would I go about changing the subnet from the hub side?

Edit: Have you looked at the screen captures above? Why do thet contain old settings and not just blanks?