ok, now caught up.. i think
1 Like
In the network application, make sure that Multicast DNS is turned on. I have IGMP Snooping also turned on, but I'm not certain it is necessary.
1 Like
Multicast is checked. I was wondering about IGMP snooping ..
1 Like
I recommened DISABLING the Automatic updates of both the UDR7 and Network App software. Ubiquiti is pretty good about putting out good code, but every once in a while, there is an issue for some users. Waking up to a broken home network, and wondering what happened, is never a good feeling. Especially if people in the house depend on the network to work from home.
3 Likes
Good idea, fixed!
2 Likes
@bobbyD or @gopher.ny would one of you be able to help me figure out why my hub mesh is not reconnecting ?
1 Like
I'm still trying to figure this out. I have since moved about half my automations to the devices hub (side note, there is a noticeable improvement in activation for the motion based automations).
Just spit balling ideas here. the POE Ubiquiti flex 2.5gb POE switch I bought didn't work, it would just down when I plugged the second hub into it. I am guessing the POE port on the UDR7 wasn't strong enough to run It. I had to go back to my MokerLink POE switch, at least temporarily. Ubiquiti does not actually see that switch (it doesn't even show up in the topology or devce list). Only the devices (currently three hubs) the devices that are plugged into it are showing. Could that be why the mesh isn't syncing up? I did order the power adapter for the switch and should have it tomorrow to test this theory. but I'm curious if anyone has any thoughts about it.
Correct, the UDR7's 1 PoE port is only standard PoE and the Flex 2.5 requires PoE+++ which most Unifi routers currently don't even support. Crazy that the power supply is a separate purchase but once you install it should be good to go.
1 Like
The Flex 2.5 PoE can be powered by PoE+++, PoE++, or PoE+. The maximum PoE output is a function of the power supply.
1 Like
Sorry but have to disagree, your screenshot is for outputs, unless I am misreading their hardware specs
1 Like
The table show the maximum Total PoE Power output based on how the switch is provided with input power.
I am powering one of these switches using PoE++, with no issues whatsoever.
1 Like
Hum then I find the list confusing given a separate spec for power method.
I still believe the underpowered UDR7 might be causing the issue for @lcw731 given it has a single PoE (not PoE+) port (unlike the UDR6) and only has 15.4W.
1 Like
I totally agree that the UDR 7’s single “PoE” port cannot power the Flex 2.5G PoE switch. The minimum appears to be at least PoE+.
I also agree that the documentation is a little confusing. 
2 Likes
So, the two questions that sorta baffle me , hopefuly one of you guys more experienced with uniquiti could shed some light on for me. Why does it not at least see the 'other' switch, even if just a generic POE switch (supposed to be a managed POE , but in the case seems to be functionis as essentially an unmanaged switch)? There doesn't appear to be an IP address assigned to it , and the hubs that are plugged into it appear in the topology as though they are connected directly to the router. Also, why are the hubs not finding each other this way? It's the same switch they were plugged into with the old router? This is more curiosity and trying to understand at this point.
I'll have the adapter tomorrow, and hopefully that will solve the issue (except I won't be moving any rules that rely onj motion back, yeah that much of a difference) All the rest of the time/mode/presence rules wil go back to the old way.
It actually can, just not with more than one hub or device attached. One hub, it rflected the swtich and the hub off the switch. When I added the second hub it was lights out (literally).
I've also noticed exporting and importing rules doesn't work as seemlessly as one would hope. There is still a significant amount of tinkering which needs to be done whe rules are imported. I
Ubiquiti UniFi can only “see” other UniFi hardware. That’s just the way it works. There is no industry standard that I am aware of that allows hardware from dissimilar vendors to communicate details such as network topology.
Are you trying to power the HE hubs using a PoE splitter? If so, the PoE output of the UDR7 is just not capable or providing enough power to passthrough to the devices.
If not using PoE to power the HE Hubs, then the UDR7’s PoE port is not even powerful enough to truly power the Flex 2.5G PoE at all. Being able to use only one out of eight client ports means the switch cannot even operate as a switch.
3 Likes
Hub mesh uses mDNS/Bonjour, but there's a manual backup endpoints for when it fails, too.
/hub/advanced/setInitialHubMeshPeers?192.168.0.2,192.168.0.3 will set the "seed" values for the hub mesh. It will still try discovering hubs, but these will be "known good" IPs. Replace sample IPs with actual hubs' IPs.
/hub/advanced/getInitialHubMeshPeers will show the settings' current value.
6 Likes
This worked! Thank you!
2 Likes
I am guessing that your new unifi router wasn’t playing nicely with this switch and the mDNS packets weren’t getting forwarded to the hubs that were connected to it.
2 Likes
Sounds logical. The end points @gopher.ny worked. A few hours later i got the adapter for the switch so the Mokerlink switch is retired now and most everything is running off the POE switch.
1 Like
