openclaw - 💡(How to fix) Fix Control UI: Reports tab timezone not matching Interface tab (GMT+8 vs GMT+0) [1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openclaw/openclaw#58666Fetched 2026-04-08 01:59:29
View on GitHub
Comments
0
Participants
1
Timeline
0
Reactions
0
Participants
RAW_BUFFERClick to expand / collapse

Bug Description\n\nThe OpenClaw Control UI shows different timezones across tabs:\n\n- Interface tab: Shows GMT+8 ✓\n- Reports tab: Shows GMT+0 ✗\n- Generated reports: Shows UTC time ✗\n\n## Expected Behavior\n\nAll tabs should show consistent timezone (GMT+8 / Asia/Hong_Kong).\n\n## Environment\n- OpenClaw version: 2026.3.31\n- Node: v20.20.0\n- macOS: Darwin 21.6.0\n\n## Additional Issue\n\nThe Interfaces tab is also not showing 'Interface Statistics' - the content area appears empty.

extent analysis

TL;DR

The most likely fix involves configuring the timezone consistently across all tabs and reports in the OpenClaw Control UI.

Guidance

  • Verify the timezone settings in the OpenClaw configuration to ensure it is set to GMT+8 or Asia/Hong_Kong consistently.
  • Check the code or configuration files for any hardcoded timezone values (e.g., UTC) that might be causing the inconsistency.
  • Investigate the 'Interface Statistics' issue separately, as it might be unrelated to the timezone problem, and check for any errors or missing data that could be causing the empty content area.
  • Review the documentation for OpenClaw version 2026.3.31 to see if there are any known issues or configuration options related to timezone handling.

Example

No specific code snippet can be provided without more context, but checking configuration files for lines similar to timezone: 'UTC' and updating them to timezone: 'Asia/Hong_Kong' might be a starting point.

Notes

The fix might require updates to the OpenClaw configuration, code changes, or adjustments to the environment settings. Without more specific details about the configuration and codebase, it's challenging to provide a precise solution.

Recommendation

Apply a workaround by manually configuring the timezone in the OpenClaw Control UI settings to GMT+8 or Asia/Hong_Kong, if possible, to achieve consistency across tabs and reports until a more permanent fix can be implemented.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

openclaw - 💡(How to fix) Fix Control UI: Reports tab timezone not matching Interface tab (GMT+8 vs GMT+0) [1 participants]