oh, yikes. that’s never been a use case. That would require significant changes to the code. Is there a particular reason you went that route?
Actually I would rather keep them separate as one station is my personal and the other is at work.
How about a simple feature, on Dashboard, to quickly toggle back-and-forth to a “guest” view of another/different Halcyon Console. I don’t mind paying for another account for my other station. ![]()
Now that I can do, that’s a good compromise. I should have something later
2.1.10 — August 1, 2026
- New: a second Halcyon license can be added under Settings → Connection. Its stations then appear in the station picker on the bottom bar beneath your own, and choosing one switches the whole dashboard over to that account — useful if you look after a family member’s station, or keep separate licenses for separate places. The list of added licenses lives only on the device where you add it and is never written into either account’s cloud settings, so no other device or dashboard ever learns about it
- Fixed: on small screens — the 800×480 Raspberry Pi touch display, a phone held upright — the text never shrank below sizes chosen with a monitor in mind, so panel rows overflowed and were clipped mid-line; the Temperature panel’s feels-like row was the usual casualty. Text now scales continuously all the way down. On anything monitor-sized or larger, nothing changes by a pixel
- The bottom bar no longer crowds itself on a phone held upright. Its clock and station name were sized against the height of the screen — generous, on a screen that is all height — and left too little width for one another
- New: a browser too old to run Halcyon is told so plainly, with a note on how to update, instead of being handed a collapsed pile of panels. In practice this means Chromium builds from before late 2022 — the sort found on a Raspberry Pi that has not seen an update in a while
I’m a bit confused on what the 2 bell curves on the astronomy panel represent. Could you elaborate in more simple terms for those that aren’t that well-versed, lol?
If you click the help icon ?, there will be some dots you can click to get info. If that still is not enough, let me know and I will fill in the blanks.
v2.1.11
- New: hail. Your Tempest has always been able to tell hail from rain by the impact signature on the sensor plate, and Halcyon has never once read that field. The Rainfall panel now turns red and says so while hail is falling, and keeps the time it happened up for the rest of the day afterwards — hail is usually over in a couple of minutes, so an indicator that only showed live would be dark almost every time you looked at it
- New: the Wind panel shows the range between the calmest and the strongest moment of each reading, and how steadily the wind has held one direction since midnight. The lull figure has been arriving from your station all along and going nowhere. A range of 11 to 41 km/h is a restless wind and 19 to 22 km/h is a settled one even though both can average the same, which is what “gusty” actually means
- Your station history now records solar radiation, UV, brightness, hail and how far away the lightning was, alongside everything it already kept. Nothing charts them yet, and history you have already imported will not have them. A way to fill in the past from observations Halcyon has already stored is coming
v2.1.12
- The Wind panel’s steadiness figure gains a second number, covering the last three hours. Steadiness since midnight tells you what kind of day it has been, which stops describing the present the moment the wind shifts — a sea breeze that turns at two in the afternoon barely dents a figure built out of fourteen hours of morning offshore. The rolling number reacts at once, so the gap between the two is the interesting part: close together means the wind has held all day, far apart means it has recently changed its mind. It appears from three in the morning onward, before which the two windows overlap too much to say anything different from one another
- Today’s strongest gust now shows the time it arrived, beside the figure itself. Your station has always recorded when the peak happened and the panel only ever showed how hard it blew. The time is what ties a gust to a cause — a shower going through, the gust front ahead of a storm, the sea breeze filling in through the afternoon, or simply the day’s wind getting up
Changelog
v2.1.13
Added
-
Sun metric for history charts. Solar radiation, UV, and brightness each get their own view under the Sun metric, available on the standard chart and as heatmaps. A new Sun card also joins the Records page, showing the sunniest day, the highest UV, and the brightest moment your station has recorded.
-
Lightning distance in history. Your station reports how far away it judged each strike to be, but until now that only ever appeared on the panel for the most recent strike. The Lightning metric can now show average distance over time — the difference between a storm that passed twenty kilometres away and one that came directly overhead, two nights that otherwise look identical on strike count alone.
Changed
- Historical backfill complete. Version 2.1.11 introduced recording of solar radiation, UV, brightness, and lightning distance, noted that nothing charted them yet, and promised a way to recover this data for already-imported history. That backfill has now run for every station, rebuilding these readings from the raw observations already stored and reaching better than 99.9% of every hour on record. The remaining gaps are hours your station genuinely reported nothing at all, and stay empty because they should. As a result, the new Sun and lightning-distance charts — and the records drawn from them — cover your history from its beginning, not just from when recording started. No action is required: no re-import, no refresh, no settings to change.
Fixed
-
Fullscreen radar freezing on open. The radar fetched imagery once when opened and never requested more, so a radar left open through a storm kept showing the sky as it looked when first opened, with no indication anything was stale. (In the case that surfaced this, the view was over an hour behind, showing clear air above a station with heavy rain falling on it at the time.) Radar now refreshes every five minutes while open, and holds the current frame until the replacement has loaded instead of blanking in between. Scrubbing back to an older frame now stays put. This also fixes animation playback coming up empty after the radar had been left open for more than fifteen minutes.
-
Max gust timestamp corruption. Today’s strongest gust ran into its arrival time in the display, so a peak of 13 km/h at 1:30 PM read as “Max 131:30 PM.” Introduced by the timestamp added in 2.1.12.
Removed
- Hail indicator on the Rainfall panel (added in 2.1.11). It was wrong, and the claim made for it at the time — that the Tempest can distinguish hail from rain by impact signature — doesn’t hold up against the data. It’s marked as experimental anyway from Weather Flow. Checking a week of one station’s readings, it flagged hail on three separate August days, twenty-five minutes in total, and every one of those minutes fell during that day’s heaviest rain. It never once used the reading that indicates rain and hail together, even while those same minutes were putting down half a millimetre of water per minute — which is rain by definition. What the sensor actually reports is how hard it’s being hit, and heavy rain hits hard; there’s no delay or threshold that separates the two, because there’s nothing in the reading to separate. Rather than leave an indicator that turns red during any downpour, it’s been removed. The underlying sensor readings are still recorded, unchanged, in case the sensor’s judgment improves.
Thanks for all your work on this app. It is awesome to see the development. I love all the upgrades and refinements.
Thanks, that means a lot! Got some exciting stuff in the works too.
If you haven’t already, a review would really help. Small app, every one counts. And if anything’s ever not working right, don’t hesitate to reach out directly, happy to sort it out.
Word of mouth goes a long way for something like this, so if it ever comes up naturally in a weather/facebook/reddit group or forum, I’d appreciate a mention.
That’s for all users.
I love the constant updates you keep making to improve this fantastic app. One thing that I’ve noticed on the Records page is that at the bottom the Temp and Wind panels, the units for the average don’t match the units that I’ve set for the display. In other words, I have the settings set for the Imperical Units but the the hours of temps show Hours > 30 Degrees Celsius rather that Hours > X degress Farenheit. Same with the Wind speeds. It shows in Km/hr instead of mph. Can those be changed to reflect the same units that users select for the main dashboard units?
Will have that fixed shortly
v2.1.19 2026-08-21
- Shared dashboards now fetch their readings rather than listening for them. Until now, everyone watching a link you shared held a live connection open for as long as their browser sat on the page, and Halcyon held one open to your station’s data on their behalf — running around the clock for any station with somebody watching, whether that was one person or three hundred. The cost of running it that way was real, and it grew with every dashboard shared rather than with how much anyone actually looked at one, which is the wrong way round. A shared dashboard now asks for the latest reading once a minute instead. That is the pace your Tempest reports at anyway, so the numbers themselves are unchanged. Nothing is asked of you: your share link still works, and there is nothing to switch on or send out again
- Worth knowing if you share your dashboard: two things are slower on a shared view than on your own. Wind steps once a minute rather than moving every three seconds, and carries the same 1-MIN mark described in 2.1.17 — your station sends wind twice over, and only the minute summary makes the trip now. And a lightning strike, or the moment rain starts, appears on the next minute’s reading rather than the instant it happens. The counts and totals themselves stay exact either way; it is only the moment they surface that moves. Your own dashboard is untouched and still live to the second
- Fixed: radar on a shared dashboard opened in high definition for any visitor who happens to own Halcyon themselves — most often you, checking your own link — while everyone else saw the standard radar. That made your own look at a share link show something your visitors would never get, which is precisely the wrong way for a preview to be wrong. Shared dashboards now always show the standard radar, so what you see when you open your link is what they see