[BUG] Bug report: v15.6.3 regression — DE panel does not display station callsign / location (backend config OK)

[on6zq]

Bug report: v15.6.3 regression — DE panel does not display station callsign / location (backend config OK)

Summary

After updating from 15.6.2 to 15.6.3, the DE panel no longer shows my callsign and station location (grid/lat/lon), even though the backend reports the correct configuration via /api/config.

This is a regression: with 15.6.2 everything displays correctly, repeatedly verified using a fresh Tor Browser session each time (to eliminate cache/localStorage effects).

Versions / known-good vs bad

• Known-good commit: eff8dac62ae8c0f17fbd38ac7a308037923bc951 → package.json version 15.6.2. ([GitHub][1])
• Bad version: package.json version 15.6.3 (current main). ([GitHub][2])

Expected behavior

DE panel should display the configured station identity and location (callsign + locator / coordinates). README describes “Your station (DE) — A labeled marker at your configured location with your callsign.” ([GitHub][3])

Actual behavior (v15.6.3)

• DE panel is missing/blank for callsign and station location (not shown).
• At the same time, /api/config returns correct station values (callsign, locator, latitude, longitude).
  (I can paste the full JSON if requested.)

Environment

• Self-hosted via Docker + reverse proxy (Caddy)

• Browser: reproducible across browsers, including fresh Tor Browser restarts

• Station configured via env vars (examples):

  • CALLSIGN=ON6ZQ
  • LOCATOR=JO20eq

Steps to reproduce

1. Build/run OpenHamClock 15.6.3 (e.g., from main) with CALLSIGN and LOCATOR set.
2. Open UI in a fresh browser session (Tor Browser restart).
3. Observe DE panel: callsign and station location are not displayed.
4. Confirm backend config is correct: GET /api/config shows correct callsign/locator/lat/lon.

Regression confirmation

1. Checkout/build 15.6.2 at commit eff8dac62ae8c0f17fbd38ac7a308037923bc951 (same env vars).
2. Open UI in fresh Tor Browser session.
3. DE panel displays station callsign and location correctly.

Suspected related change

There was refactoring work around DE/DX location rendering: “Break out DE Location and DX Location rendering into separate render modules…” (PR #217). ([GitHub][4])
This seems like a plausible area for a DE-panel-only regression.

Notes / troubleshooting already done

• Not a backend parsing problem: /api/config has correct station values in 15.6.3.
• Not a browser cache problem: reproduced with fresh Tor Browser sessions.
• Reverse proxy returns the correct /api/config from the public hostname.

[alanhargreaves]

In the Current Staging environment it looks ike this

There is definitely no callsign, but Grid Locator is there.

Given that the callsign is displayed in the panel above, is there a need to display it in the DE Panel?

e.g.
Modern:

Dockable:

[on6zq]

In docker-compose.yml, I have

openhamclock:
container_name: openhamclock
environment:
- CALLSIGN=ON6ZQ | AC6ZQ
- LOCATOR=JO20eq

So the callsign and locator from the environment should be used. It was so up to 15.6.2.

[dk5cr]

Hi!
Same with me... Just made a fresh install with current version 15.6.3 on a fresh micro SD card on Raspi 5. .env file is okay, rights are properly set to the file.
:3001/api/config shows the right callsign, but starting OHC with :3001 there's the genuine callsign N0CALL and the wrong locator.

I can't really say, if it was better in 15.6.2 cause i just installed it for the first time.

When editing callsign and locator in the webinterface, changes won't be stored even if i'd pressed "save" or so.

[echo-gravitas]

/assign

[echo-gravitas]

Thanks for the report. I was able to reproduce and verify the issue, and it is now fixed.

Current behavior is now:

• On startup, callsign and locator are loaded from .env.
• Those values are then available in the browser config/local state.
• If a user later changes settings in the Settings panel, those values are saved in localStorage and correctly take priority over .env values.

Pull request #627 was created.