Can't add negative value in Longitude

[Junicavi]

What happened?

When trying to set my location I can't add negative values to the longitude

Same result trying to update the value directly in the config file

To Reproduce Bug

Go to the "Time and Macros" setting and try to set a negative value in the Longitude

Expected Behavior

You can enter negative values as there are negative coordinates

Install Method

Binary from WLED.me

What version of WLED?

WLED 16.0.1

Which microcontroller/board are you seeing the problem on?

ESP32

Relevant log/trace output

Anything else?

No response

Code of Conduct

• I agree to follow this project's Code of Conduct

[DedeHai]

coordinates are never negative, you choose east or west.

[Junicavi]

It does not matter if I select W (which would be the correct value), when I save, it still the minus in the coordinates and doesn't display the correct date

added a quick recording of the issue

2026-07-17.09-47-26.mp4

[DedeHai]

is your timezone correct? that is what sets the time. Latitude/Longitude calculates sunrise/sunset, not timezone.

[Junicavi]

Yes it is, I've multiple WLED instances in 15.0 that are set exacly the same and are working

[DedeHai]

@coderabbitai are there any realated code changes between 0.15 and 16.0 release? please elaborate on this issue.

[coderabbitai]

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
set -euo pipefail

repo="wled/WLED"

echo "== Issue 5740 =="
gh api "repos/$repo/issues/5740" \
  --jq '{title, state, created_at, body, comments, labels: [.labels[].name]}'

echo
echo "== Candidate release tags =="
gh api "repos/$repo/git/matching-refs/tags/v0.1" --paginate \
  --jq '.[].ref' | grep -E 'v0\.(15|16)(\.|$)' || true

echo
echo "== Compare v0.15.0...v0.16.0: relevant files =="
gh api "repos/$repo/compare/v0.15.0...v0.16.0" --paginate \
  --jq '.files[] | select(.filename | test("(^|/)(time|timezone|sun|settings|interfaces|cfg|xml|js|html)"; "i")) | [.filename, .status] | `@tsv`' \
  || true

echo
echo "== Compare commits mentioning time/zone/longitude/sun/date =="
gh api "repos/$repo/compare/v0.15.0...v0.16.0" --paginate \
  --jq '.commits[] | select((.commit.message | test("time|zone|longitude|latitude|sunrise|sunset|date"; "i"))) | [.sha[0:12], (.commit.message | split("\n")[0])] | `@tsv`' \
  || true

Length of output: 2939

---

🏁 Script executed:

#!/bin/bash
set -euo pipefail

repo="wled/WLED"

echo "== Issue comments =="
gh api "repos/$repo/issues/5740/comments" --paginate \
  --jq '.[] | {user: .user.login, created_at, body}'

echo
echo "== Releases whose tag/name mentions 16 =="
gh api "repos/$repo/releases" --paginate \
  --jq '.[] | select((.tag_name + " " + .name) | test("(^|[^0-9])16(\\.|[^0-9]|$)"; "i")) | {tag_name, name, target_commitish, published_at, prerelease, draft}' \
  || true

echo
echo "== Branches whose names mention 16/release =="
gh api "repos/$repo/branches" --paginate \
  --jq '.[] | select(.name | test("16|release"; "i")) | [.name, .commit.sha] | `@tsv`' \
  || true

echo
echo "== Local refs mentioning 0.16 and recent refs =="
git show-ref --heads --tags | grep -E '0[._-]?16|16[._-]0' || true
git branch -a --no-color | sed -n '1,120p'

echo
echo "== Candidate settings/time files in checked-out source =="
fd -t f -E .git | grep -Ei '(time|sun|cfg|settings|xml|html|js)$' | sed -n '1,180p'

echo
echo "== Exact longitude/timezone/sunrise references in checked-out source =="
rg -n -i -C 3 'longitude|latitude|timezone|sunrise|sunset' \
  -g '!**/.git/**' -g '!**/node_modules/**' | sed -n '1,280p'

Length of output: 3760

---

🏁 Script executed:

#!/bin/bash
set -euo pipefail

repo="wled/WLED"
base="v0.15.0"
head="v16.0.1"

echo "== v16.0.0 / v16.0.1 release notes =="
for tag in v16.0.0 v16.0.1; do
  echo "-- $tag --"
  gh api "repos/$repo/releases/tags/$tag" \
    --jq '{tag_name, published_at, name, body}'
done

echo
echo "== Relevant files changed from $base to $head =="
gh api "repos/$repo/compare/$base...$head" --paginate \
  --jq '.files[] | select(.filename | test("time|sun|clock|settings|cfg|json|xml|interface|web"; "i")) | [.filename, .status, .additions, .deletions] | `@tsv`' \
  || true

echo
echo "== Commits explicitly about geolocation/time settings =="
gh api "repos/$repo/compare/$base...$head" --paginate \
  --jq '.commits[] | select(.commit.message | test("longitude|latitude|geolocation|timezone|sunrise|sunset|time settings|time and macros"; "i")) | [.sha, (.commit.message | split("\n")[0])] | `@tsv`' \
  || true

echo
echo "== GitHub code search: longitude references =="
gh api -H "Accept: application/vnd.github+json" \
  "search/code?q=longitude+repo:$repo" \
  --jq '.items[] | [.path, .sha, .html_url] | `@tsv`' \
  || true

echo
echo "== GitHub code search: latitude references =="
gh api -H "Accept: application/vnd.github+json" \
  "search/code?q=latitude+repo:$repo" \
  --jq '.items[] | [.path, .sha, .html_url] | `@tsv`' \
  || true

Length of output: 18960

---

🏁 Script executed:

#!/bin/bash
set -euo pipefail

repo="wled/WLED"
base="v0.15.0"
head="v16.0.1"
tmp="$(mktemp -d)"
trap 'rm -rf "$tmp"' EXIT

fetch_file() {
  local ref="$1"
  local path="$2"
  local out="$3"
  gh api "repos/$repo/contents/$path?ref=$ref" --jq '.content' \
    | tr -d '\n' | base64 --decode > "$out"
}

echo "== PR `#5555` =="
gh api "repos/$repo/pulls/5555" \
  --jq '{number, title, state, merged_at, merge_commit_sha, base: .base.ref, head: .head.ref, body}'
echo "-- changed files --"
gh api "repos/$repo/pulls/5555/files" --paginate \
  --jq '.[] | [.filename, .status, .additions, .deletions, .patch] | `@json`'

echo
echo "== Relevant source diffs: $base -> $head =="
for path in \
  wled00/data/settings_time.htm \
  wled00/cfg.cpp \
  wled00/set.cpp \
  wled00/xml.cpp \
  wled00/ntp.cpp \
  wled00/wled.h
do
  echo
  echo "-- $path --"
  if fetch_file "$base" "$path" "$tmp/base"; then
    fetch_file "$head" "$path" "$tmp/head"
    diff -u --label "$base/$path" --label "$head/$path" "$tmp/base" "$tmp/head" \
      | grep -E -C 8 '^[+-].*(longitude|latitude|sunrise|sunset|east|west|lon|lat)|^@@' \
      || echo "(No focused matching diff lines)"
  else
    echo "Not present at $base"
  fi
done

echo
echo "== v16.0.1 settings_time.htm longitude-related code =="
fetch_file "$head" "wled00/data/settings_time.htm" "$tmp/settings_time.htm"
grep -n -i -E -C 8 'longitude|latitude|sunrise|sunset|east|west' "$tmp/settings_time.htm" || true

echo
echo "== v16.0.1 config/API longitude-related code =="
for path in wled00/cfg.cpp wled00/set.cpp wled00/xml.cpp wled00/ntp.cpp; do
  fetch_file "$head" "$path" "$tmp/file"
  echo "-- $path --"
  grep -n -i -E -C 6 'longitude|latitude|sunrise|sunset' "$tmp/file" || true
done

Length of output: 118805

---

@DedeHai, I compared v0.15.0 with v16.0.1 (the correct release tag; v0.16.0 does not exist).

What changed

• The Time and Macros page was substantially rewritten for 16.0: asynchronous loading, grouped UI, and a new dynamic timer/sunrise/sunset editor.
• There is a related-looking commit, #5555, but it only migrates legacy sunrise/sunset timer entries. It does not modify latitude or longitude.
• v16.0.1 release notes do not list a time-zone or geolocation fix.

Longitude handling itself

• The firmware still stores longitude as one signed float: interfaces.ntp.ln in cfg.json.
• A negative value is valid in the persisted config and is read directly; there is no new firmware-side clamp or conversion that rejects it.
• The E/W selector exists only in the web page:
  • on load, a negative stored longitude becomes a positive magnitude with W selected;
  • on save, W makes the submitted numeric value negative.
• That W/E ↔ signed-value conversion was already present in 0.15 and is unchanged in 16.0.1.

So this does not look like the 16.0 timer migration or the NTP/sun-calculation backend altering the longitude. However, the report—W remains selected while the numeric field displays/persists with a minus—is compatible with the rewritten 16.0 settings page getting the selector and numeric input out of sync during page initialization or submission. Since direct cfg.json editing was also reported not to stick, it would be useful to compare the actual saved interfaces.ntp.ln before/after reboot and distinguish:

1. a display-only normalization problem,
2. a settings-save request sending the wrong LN value, or
3. a later config rewrite overwriting it.

Finally, the incorrect local date/time should not be caused by longitude: currentTimezone and the UTC offset set local time. Longitude/latitude affect the displayed sunrise/sunset time and sunrise/sunset-triggered timers.

[DedeHai]

@Junicavi I do nto see the issue, longitude is set correctly. as to why your time is way off I do not know, maybe try a different time server or disable NTP as a test

[Junicavi]

I've tried all the time zones, and removing and/or disabling the ntp server, same result, the only change it's sometimes it shows 1970 as the year instead 2160.

This is an updated instance of Wales through the web client importing the 16.1 bin. Just in case this helps

[softhack007]

This is an updated instance of Wales through the web client importing the 16.1 bin.

Not sure if I understood you 🤔 Whales (where do they live) ? What kind of web client (wled app, browser page, or any other) ?

[Junicavi]

LMAO I replied back from my phone, I meant WLED. it's an updated instance of WLED from 15 to 16