How to pull logs before contacting support

If you need to reach out to support at helioclock.com about something
that isn’t covered above, grabbing the actual log first makes a real
difference in how fast it can get sorted out.

Click the HC-SERVER status indicator in the bottom bar to open a live
log viewer – it shows everything the server has logged: solar data
fetches, NTP sync, weather polling, alert processing, and more. You
can filter by source or level using the buttons across the top. Press
Copy Log to copy the currently filtered view to your clipboard, ready
to paste into an email. Press Escape or the close button to exit. Most
of this lives in a rolling in-memory buffer capped at 500 entries and
resets on server restart – so if something happened a while ago, it
may already be gone from this view (see Crash Reporting below for
things that need to survive a restart).

Crash Reporting is off by default (turn it on in Settings). Once
enabled, any error Helioclock’s own code doesn’t catch gets written to
the device’s log automatically – the error message, stack trace, and
which view was active at the time. This matters most on a kiosk
display, where there’s no way to pop open a browser console to see
what actually happened. Unlike the regular log, crash reports are
written to disk and survive a restart, so a crash from hours earlier
is still there when you check. To pull one: open the log viewer,
filter the source to CRASH, press Copy Log, and paste the result into
your email to support. Nothing is ever sent off your device
automatically – it stays local until you choose to copy and share it.