RBgrid v1.1.6 is out. Two changes stand out: the hub keeps your clock settings through a restart, and a three-phase input metered per phase is now read as one input everywhere the app shows a period.
Get it
- Firmware: the v1.1.6 release has the image set for a fresh USB flash, each file with its SHA-256, and
main_release.binfor an over-the-air update. - Web app: install
rbgrid-ui_v1.1.6.zipfrom the same page as described in Build & flash, or use the hosted app at webapp.rbgrid.io. - Already on v1.1.x? Update over the air from the app (Settings → Hub firmware) with
main_release.bin; your Wi-Fi, settings, points and history are kept. - All releases: github.com/robotdyn-dimmer/RBgrid/releases.
Fixed: your time settings survive a restart
This one is worth a minute even if nothing in your setup looks wrong.
On v1.1.5 and earlier the hub saved the Time panel as one whole file, while the app sends only the fields you actually changed. So saving the time zone on its own — step 3 of the setup wizard, and the first thing most people change — left the hub with no NTP servers. It kept the right time until the next restart, and then came back never syncing again: the clock stayed unset, history waited for a real date, and energy was priced from whatever time the hub thought it was.
v1.1.6 merges what the app sends into what is already stored, so a partial save is just a partial save.
A hub in that state repairs itself at its first boot on v1.1.6: the saved time zone is kept, and the servers go back to pool.ntp.org and time.nist.gov. One thing to do after updating: open Settings → Time and check the zone. If the hub restarted more than once while it was in that state, the zone went too — set it again, and the clock will sync by itself.
If a hub of yours has to stay on older firmware, install the new app package anyway: it sends that panel in full to a hub on v1.1.5 or earlier, so the servers survive a save there too.
And a second fix on the same page, for hubs with no internet at all. Setting the clock with Use this device's time now counts as a synchronization: the panel reads synchronized with source MANUAL, the setup wizard's time step is satisfied, and the hub files its records under real dates. On v1.1.5 and earlier it didn't — a hub on Wi-Fi that couldn't reach a time server went on reporting not synchronized with no source, and its stored records kept waiting for a date they would never get. The clock still drifts, because nothing corrects it afterwards; what has changed is that the hub now accepts it. Settings → Time also used to fail to open about one time in three on such a hub, while it was retrying NTP. It doesn't now.
While you are on that page: the Resync interval now has to be between 60 and 86400 seconds, because a value outside that range used to turn time sync off at the next restart. The app won't save one any more, and a hub still carrying one is brought back into range when it boots. That closes a known issue these pages have carried since v1.1.0.
New: a three-phase input read as one input
Since v1.1.5 a three-phase input can be metered as one point per phase, each phase keeping its own import and export. The catch was that the app could then only show you one of them per period: the Economics balance, the Overview month, "vs yesterday" and the energy chart all read a single phase point, while live values and the hub's own totals were the full sum. It was in the v1.1.5 release note as a known limitation.
The hub now serves the grid input as one summed series, and the app reads it. With the matching app package, these cover the whole input again:
- the Overview's today by hour and its yesterday ghost, today vs yesterday, month to date and the month forecast;
- Economics with the input selected: the totals, Imported at the input in the balance, generation, and the per-zone cost and export value.
The History page still shows each phase separately — L1, L2 and L3 with their own charts, tables and CSV files. That is deliberate: the summed view is for "what did my house use", the per-point view is for "what is each phase doing", and a per-phase input is the one setup where you need both.
Nothing to switch on. The hub advertises the summed series, and an app that finds it uses it; one that doesn't, or a hub on older firmware, reads the main point as before.
🔖 Going back to one point still erases the phase points' history. The summed series can only sum what is on the hub, so for the period a split input was in use, it keeps L1 alone afterwards. If those records matter, download them from History before you regroup.
Changed: deleting a point clears its net-metering record
Deleting a point now takes its net-metering record with it — the credit bank and the running period balance — so a point bound later under the same ID starts its credit at zero. On earlier versions a reused ID carried on the removed point's credit, which is only ever right if the channel still feeds the same thing. If that is what you want, keep the ID; if the channel now feeds a different load, give it a new one.
Changed: a second update inside the confirm minute says so
For about a minute after an update the hub is still confirming the image it just installed, and it refuses another one in that window. It used to fail with a generic error; now the panel says what is happening — "Failed: The hub is still confirming the firmware installed less than a minute ago. Try again in about a minute." — and that is all that is wrong. Wait a minute and install again.
🔴 While you are waiting, don't restart the hub. That confirmation minute is also why: a restart inside it — by hand, or by pulling the power — rolls the hub back to the firmware it had before. This has always been true; it is now written down, because it is easy to do while wondering why an update "didn't take".
Web app 1.1.6
- The summed input above, and the whole time config sent to hubs on older firmware.
- Settings → Time checks what you type before it will save: the NTP servers as host names ("A server name, without spaces or "/", up to 63 characters"), the resync interval as whole seconds between 60 and 86400. The error sits under the field and Save stays disabled until it's gone.
- Switching a three-phase input between one point and one point per phase now reports back on the module card you pressed — with Restart now there, and the mode buttons hidden until you do. The result used to appear above the module list, often off the top of the screen, which made the restart easy to miss entirely.
Full list: the changelog. User guide: rbgrid.io/webapp/docs.