I am unsure if this is user error or needs implementation. As per the title the U7-IW not showing link to downstream devices on Ports 1 & 2

Steps to Reproduce:

Add a U7-IW to your floorpan.

Set uplink (port 3) to a POE+ port on a switch

Add device to Port 1 - (in this case a USW-Ultra)

The U7-IW edit pane correctly shows 9W draw over POE. (Image Item 2 and 4)

Switch to Topology map.

connected device is not shown inline with U7-IW and is floating off by itself. (Image item 3)

If you select the USW-Ultra and try to set an uplink the U7-IW is not selectable. (Image item 1)

Let me know if you need anything more to help reproduce.

Suggestion: When selecting multiple devices per floor plan, allow bulk renaming and auto numbering as per screenshot. Or even in the topology view with multi-device select.

I manually changed this, but then the cable connected to the top switch in the rack, and when I changed the uplink, the cable automatically re-routed to the previous long path going up.

Why does this happen, and how can I fix it?

A very useful suite for designing deployments. However, I have encountered some strange behaviour specifically with the U7 In Wall access points.

Setting for the U7 IW APs is lacking port links.

In reality the U7 IW is uplinked via the port on the rear that accepts PoE+ in and this is termed "Port 3" in the Unifi Network application live environment.

Port 1 and Port 2 on the U7 IW are for downstream devices, with Port 2 allowing passthrough PoE if enabled.

However in the Design Centre:

The U7 IW uplinks on Port 1 not Port 3 as in reality.

And most troublesome is that both downlink ports don't seem to take into account PoE in the Design Centre.

Eg. connecting a Flex mini to the U7 IW - The Design Centre does not flag or give the option to include a PoE injector. It seems to assume both ports on the U7 IW are PoE.

Eg. Connecting a Flex Mini on both ports of the U7 IW - The Design Centre seems to think PoE is provided via both and there is no option to include a PoE injector if using a PoE powered downstream device on the non-PoE port.

(Unlike in other scenarios - eg. If one connects a PoE Doorbell to Port 4 on a Flex Mini - Design Centre will flag this as a PoE powered device connected to a non-PoE port and provide a toggle to include an injector. But this is entirely lacking with the ports on the U7 IW within design centre).

In summary the U7 IW APs in design centre are lacking the options to granularly set ports, PoE and links in the same way one can have fine granular control with other switches.

I have a couple plans in my Design Center that load ok on the web browser interface and recently checked the iOS app, after downloading the newest UniFi Design Center (on an iPad Pro 11 3rd Gen running iPadOS 26.6) and saw my plans show up in the list.

So picked the first one, the smaller building on campus, and it loaded up fine.

I then tried our main larger building plan (a large octagon 120 feet across) and it just shows a blank page/view. I keep pressing the zoom in and out buttons and the ‘center’ buttons to no effect. And the WiFi and Camera display buttons just show a uniform color across the whole view. Any ideas? I’ll check again on my browser to be sure it loads OK (usually Google Chrome on macOS). Maybe the plans in a ‘illegal’ image format?

They both have 2 ‘pages’, one is an ‘upgrades’ setup (small building) and the other is an attempt at an ‘attic’/2nd floor view (the one that doesn’t work, for either page).

I also have a second account (for my personal/family setup) and that works fine for all plans that show up there.

I’d love to see custom tags work the same way. Imagine creating tags like 'Security', 'Existing', 'Stage 1', 'Solar' etc. Then, toggle them on or off, just like the built-in apps. That way, we don’t need to duplicate floor plans just to show different views. It would make exports for different installers or for different project phases so much cleaner. As projects get bigger, this could be a single source of truth instead of multiple duplicated plans.

What do others think? Would that be useful for your projects too?

My project is a multi-building site connected by underground fiber conduits and conduits running underground alongside perimeter fences and under the carpark. I’ve aligned the ground floor, first floor, and an underground conduit layer, drew cable routes on that underground layer, and added tunnels where the conduits enter each building, expecting the cable to follow those paths. Instead, it takes a different route.

Is that I’m using tunnels wrong? is there a missing workflow? or is this a bug or limitation?

Or, if it’s simply not supported - I’d like to suggest it as a feature request.

Underground conduit aware routing feels like a natural extension for schools, childcares, hotels, apartments, and commercial sites.

I'M new in this community ,,,

And now I have design Project for Smart School with 4 Floor's and more than 800 End Device's , So I ask about Estimated Cable Length in Design Center >>>>

Is A true Estimated Cable Length & Estimated Cable Routes ?

Design Center is a good Calculation Length Cables ?

Who is try that in Really Project >>>> Can Help me , Please ?

Attachments:

• Screenshot From 2026-06-14 23-37-43.png

My goal is for the UX7 to function as a wired AP, meaning:

• Ethernet port active
• Ability to plug in a switch
• Ability to use multiple SSIDs
• Full VLAN trunking
• No wireless mesh mode

Is there any way to wirelessly link the UX7 to the UDR7 without using mesh, so that the UX7 behaves like it’s wired?

If not, what hardware or setup would allow me to create a wireless Layer‑2 bridge so the UX7 can operate as a fully wired AP?

Thanks in advance.