[bug] Indoor floorplan selection UI is inconsistent for new indoor locations

[4f4d]

Describe the bug
While testing openwisp-controller#1339, I found a separate issue that appears to be independent from the remove/re-add inline bug.

For a new indoor location, the Indoor coordinates UI behaves inconsistently:

• Floorplan selection defaults to New
• trying to switch it to Existing does not expose a clear usable existing-floorplan flow
• the UI effectively remains on the New path, which makes the intended behavior unclear

I am opening this as a separate issue because it seems distinct from #1339.

Steps To Reproduce
Steps to reproduce the behavior:

1. Go to the device admin add form in the local django-loci test app
2. In Geographic information, keep Location selection = New
3. Change Type to Indoor
4. Scroll down to the Indoor coordinates section
5. Try changing Floorplan selection from New to Existing
6. Observe that the UI does not expose a clear usable existing-floorplan flow and effectively remains on the New path

Expected behavior
I am not fully sure what the intended behavior should be here, so I am reporting this mainly as a reproducible UI issue and asking for clarification.

From a UI perspective, I would expect one of these to happen consistently:

• if Existing is valid here, the UI should expose a usable existing-floorplan flow
• if Existing is not valid when Location selection = New, the UI should make that explicit instead of presenting a confusing selector state

Screenshots
I am attaching a short video showing the behavior.

indoor_UI_bug.mp4

System Information:

• OS: macOS 15.7.7
• Python Version: Python 3.12.13
• Django Version: Django 5.2.14
• Browser and Browser Version (if applicable): Google Chrome 148.0.7778.179

[nemesifier]

@4f4d are there any exsiting floorplans in this environment that you're showcasing in your bug report?

Maybe the problem is caused by the fact that there's no existing floorplans to show and this breaks the JS?

[4f4d]

@nemesifier the bug report above didn't have any existing floorplans.

So I tested this again on my local setup with both cases.

• with no existing floorplans: selecting Existing leaves the floorplan UI in the same inconsistent state
• after creating a valid indoor location and one floorplan: selecting Existing still behaves the same way and does not properly switch/show the existing floorplan flow

So it does not seem limited to the empty floorplan list case. The floorplan selection state itself still looks broken even when an existing floorplan is available.

Screen.Recording.2026-06-09.at.08.54.37.mp4

---

PS
Update after further testing:

I tested this again with an existing indoor location that already has a floorplan.

In that flow, if I select Location selection -> Existing, choose the existing indoor location, and then go to Indoor coordinates, the floorplan UI behaves correctly: I can choose between New and Existing, and the Existing path shows the saved floorplan as expected.

So this issue seems narrower than my first report. The problematic behavior appears in the Location selection -> New -> Indoor path, where the floorplan section is shown even though no saved indoor location/floorplan context exists yet. In that state, selecting Existing is confusing/broken because there is no existing floorplan tied to the unsaved new location.

I’m attaching an updated video showing both paths:

1. New -> Indoor: problematic/confusing floorplan UI state.
2. Existing -> existing indoor location with floorplan: expected behavior works.

Screen.Recording.2026-06-09.at.21.36.28.mp4

So the question is probably what the intended UX should be for the New -> Indoor path: should the existing floorplan option be hidden/disabled until a saved indoor location exists, or should the floorplan section behave differently there?

[4f4d]

Also, while setting up the test data, I also noticed a separate issue: adding a location in the admin can hit a 500 because geo_location.is_estimated is required by the DB but not supplied by the active form/model path.

I’m keeping this separate from the floorplan issue and will open a new issue for it.

Steps of reproduction:

1. Open Geographic Info -> Locations -> Add location
2. Fill org, name, type, address
3. Press Save
4. Server Error (500)

terminal traceback line:

null value in column "is_estimated" of relation "geo_location" violates not-null constraint

---

I used a local DB default only to unblock reproduction:

from django.db import connection
with connection.cursor() as cursor:
    cursor.execute("ALTER TABLE geo_location ALTER COLUMN is_estimated SET DEFAULT false;")

The proper fix is likely in the model/admin/migration path so is_estimated is consistently set on location creation.

Another observation: Pressing Enter in the address field can submit the form before the map/address flow is completed, which triggers the same failure.