v3.15.0 — Saving Session on the hub too

The Saving Session now shows on the front page too, not just the Energy page.

It sits in the energy card beside the Axle line, giving the window, whether you are opted in and what the extra is worth, and going amber when you are not in it. It is on the phone layout and the desktop one, which are built separately, so a row added to one and forgotten on the other is now something a test refuses.

The decision behind both pages — which session matters, whether you are in it, what it pays — has moved into one shared place instead of being worked out twice, so the front page and the Energy page cannot end up disagreeing about whether you are opted in.

The row says nothing at all when there is no session, rather than saying "none announced" the way the Axle line does. The Axle data carries a health signal and this does not, so an empty list could equally mean a quiet week or a fetch that failed, and it will not print a reassurance it cannot stand behind.

Needs SigenEnergyManager 5.108.0 or newer for the not-opted-in warning.

v3.14.0 — Saving Session banner on the Energy page

The Energy page now tells you about an Octopus Saving Session, the same way it tells you about an Axle event.

A session is announced hours ahead and pays nothing at all unless you are opted into that particular one, so the thing worth knowing is whether you are in it — and until now the page said nothing whatever.

The banner across the top names the window, says whether you are opted in, quotes what the extra is worth in pence, and turns amber when you are not in it. A session already running says so. The weekend free hour and the occasional Power Up each get their own wording, because a Power Up asks you to use MORE and the battery is deliberately not driven for one.

It reads a list of every announced session rather than the list the battery is driven from: that one holds only the sessions already joined, so a banner built on it would have gone quiet in exactly the case worth shouting about.

Inside, the bar's amber colour is now carried as a flag rather than found by searching the finished sentence for the words "Storm" and "Modbus", which no new message could ever have matched.

Needs SigenEnergyManager 5.108.0 or newer for the not-opted-in warning; with an older one the banner still shows the sessions you are in.

Dashboards 3.13.3

The bundle now carries the standard GitHub record.

Indigo plugins can carry a small note inside the bundle saying where their source lives on GitHub, spelt the way the Indigo Domotics and community plugins spell it. This one now has it, pointing at this repository. Nothing else changed.

Install: download Dashboards.indigoPlugin.zip, unzip it, and double-click Dashboards.indigoPlugin — Indigo installs it. An existing install picks the change up on the next plugin restart.

Dashboards 3.13.2

Housekeeping: the retired page builder's server side is gone

Version 2.5.0 added a visual page builder, and a hidden customPages endpoint sat behind it. The builder was retired months ago, and nothing has called the endpoint since — but it was still in the plugin, and it still wrote an always-empty custom-pages.json into the anonymous public folder every time the plugin started.

Both are gone now. The first start on 3.13.2 removes that leftover file (and any saved page definition that was mirrored beside it) from the public folder, once, and says so in the log. Anything saved in the plugin's Preferences folder is left untouched.

Nothing on a running install changes. No new settings, no new pages.

Also new since 3.13.1, on the documentation site: highsteads.github.io/Dashboards — getting started, configuration, a page of notes for every page, cameras, remote access, troubleshooting, the full version history, and a page for the complete beginner who has Indigo, a Claude subscription and nothing else.

Install: download Dashboards.indigoPlugin.zip below, unzip it, and double-click Dashboards.indigoPlugin — Indigo installs it in place.

3.13.1 — first public release

First public release

The repository is now public, rebuilt as a fresh single commit from a scrubbed tree; the earlier history stays in a private archive.

In the tree itself the changes are small: example addresses in comments and tests are now generic documentation ones, the demo fixture has been re-sanitised (credentials of every kind, e-mail addresses, Zigbee and Shelly hardware addresses and a household name are placeholders, not only IP addresses), and the fixture generator scrubs those same classes so a regenerated fixture cannot bring them back. Two new tests keep it that way: one refuses any real-looking address, hostname or e-mail anywhere in the tree, the other checks the demo fixture and the generator.

Nothing on a running install changes. Everything since 3.12.0 is described in the README's version history, including the plugin's own Claude tools (3.12.0) and the Sigenergy pages hiding themselves when that plugin is absent (3.13.0).

Install: download Dashboards.indigoPlugin.zip, unzip, double-click Dashboards.indigoPlugin.