Currently, InnerSpace only displays hardware that is active and adopted on the local UniFi console. While this works well for monitoring an existing, completed deployment, it severely limits InnerSpace’s potential as an expansion and decision-making tool.

When planning network expansion (e.g., eliminating a Wi-Fi dead zone, adding camera coverage, or moving devices around), users currently have to guess which model will suffice. While UniFi Design Center allows prospective planning, it requires recreating the floor plan from scratch, drawing walls again, and working completely outside our real-time environment.

Allowing users to temporarily drop "virtual" or "unowned" UniFi devices (Access Points, Protect Cameras, Sensors) onto their existing InnerSpace floor plans would be great!

My understanding is that DORI is the legacy standard now, whereas OODPCVS is the newer standard given what cameras can do these days.

Is there a way to automate or half automate, to draw the walls?

Within InnerSpace, it would be great to be able to add electrical outlets and circuit breaker panels. Similar to following data drops to the patch panel and switches, the outlets could be mapped to a specific circuit breaker on the panel. If someone calls IT support because multiple devices wont turn on, we could see what circuit it is connected to and direct the person to check if breaker #X has been tripped. The implementation structure is already built into InnerSpace and this would be a MASSIVE step towards overall building management.

Thank you,

Jeremy

we are currently using Unifi OS and Network / InnerSpace in folllowing Version:

Problem is, that we can only upload 10! Floorplans to InnerSpace, but we need, maybe 35, because we have one site, spanning over different campuses and floors.

Is it possible to change this to a higher number of floorplans?

Best regards

Johannes

@UI-Team : I guess it's just some SKU Forgotten. the UVC-G6-Pro-Bullet works well but not the UVC-G6-Pro-Bullet-B

Issue where floor plans are displayed across different sites.

Expected behavior

A_Site - A-1F-Floor

B_Site - B-1F-Floor

Unexpected behavior

A_Site - A-1F-Floor / B-1F-Bloor

B_Site - A-1F-Floor / B-1F-Bloor

Will this issue be fixed in the future?

Inner space version 1.3.16

I have had other UnifiOS users confirm the same behavior.

@UI-Team

Extending it to Access, Motion, and Tamper events would create a unified spatial and temporal view of site activity.

I'd like to see:

• Door Access events (open, close, unlock, lock, held open, forced entry)

• Motion sensor events (detected, cleared)

• Tamper events (devices with tamper switch inside - G6 cameras, Alarm Hub, Access Ultra Hub etc, maybe a future fence touch sensor?)

Being able to scrub through time and see these events directly on a spatial map would significantly improve investigations, incident response, and situational awareness.

With the current implementation, all floor plans are stored in a single shared InnerSpace workspace, making it difficult to manage environments with multiple sites. This creates confusion, increases administrative overhead, and reduces the ability to maintain clear separation between different locations.

Attachments:

• recording.mp4

Just upgraded from 10.0.63 to 10.3.58

Innerspace menu seems lost in outer space.

Anybody knows how to recover it ?

thank you.

PM.

while messing around in my InnerSpace, one of my U7 In-Walls shows up as an unknown device type. I've already tried re-adopting the device, but the issue still persists. Has anyone had this before, and is there a fix?

Note that the device does operate normally in real life and is added to my console as U7 In-Wall, so all is correct, except in InnerSpace. It's not broken, just annoying.