RBgrid v1.1.8

RBgrid v1.1.8

A release on top of v1.1.7. Remote nodes get node firmware 1.5. A point can be marked as measured inside another
point. The ESP32-S3 is supported.

Remote nodes and node firmware 1.5

• Node data could stop being processed. When internal RAM was short at the hub's start, the task that books node
  data didn't start, and nothing said so: nodes read offline and their periods were not booked. The hub's node tasks
  now have memory reserved at build time; GET /api/v1/espnow shows inject_age_ms (-1 = not running).
• A current-only node input books no energy. The hub doesn't turn current alone into energy from the nominal
  voltage, because that would not be real energy. Live values still show the current.
• A node period longer than 15 minutes is kept. This is energy the node counted before it had the hub's clock.
  It goes into that period's hour, flagged OUTAGE.
• Live values from all 4 inputs of a node (was 3). Node point edits (name, role, ratings, clamp orientation,
  inside) survive a restart.
• Node firmware 1.5:
  • A node follows only the hub it is paired to. With two RBgrid hubs on one Wi-Fi channel, node 1.4 lost its clock
    sync, while energy kept arriving. A node paired under 1.4 needs no re-pairing: after the update it keeps the hub
    that answers it.
  • Periods are kept in flash until the hub has them, about 5 days, and they survive a power cut.
  • The first record covers boot → the first full 15-minute boundary.
  • All three inputs of a module are reported.
  • Moving a node to another hub needs no flash erase, also when the old hub is gone.
• Node update: over USB with all three files. 1.5 adds a flash partition for the kept periods. The image is
  rbgrid-node_v1.1.8.bin; the boot loader and partition table are in rbgrid-node_v1.1.8_full.zip.

Points measured inside other points

• A point can be marked as measured inside another one, e.g. a charger inside a metered sub-panel. The app then
  doesn't count that load twice in "unmetered".
• The hub's own totals don't change: they are taken at the input.

Security

• mqtts:// checks the broker certificate's dates. An expired certificate, or one not valid yet, is refused.
• The hub opens a TLS broker connection only once its clock is set. Plain mqtt:// is not delayed.
• Your own broker CA (e.g. Mosquitto in Home Assistant with its own certificate): POST /api/system/mqtt-ca with
  the PEM; it replaces the public CA bundle at the next restart. GET /api/system/mqtt-config → tls.state says why a
  connection is refused (expired, not_yet_valid, name_mismatch, unknown_ca, waiting_clock, …).

Platform

• ESP32-S3 (module N16R8: 16 MB flash, octal PSRAM) is supported next to the ESP32-WROVER. It is a separate
  image, main_release_s3.bin; for a first USB install, take the four files in rbgrid-hub-s3_v1.1.8_full.zip.
• ESP-IDF 5.5.1, as v1.1.7.
• The ESP32 boot loader, partition table and OTA data are byte-identical to v1.1.7. An update over the air keeps
  settings and history.

API

• GET /api/v1/system/events adds heap (internal RAM free / minimum / largest block, PSRAM free).
• GET /api/v1/schema: quality_bits names every bit the hub sets (SRC_RESTART, SRC_FW, REVERSE_LOST,
  OUTAGE), and capabilities.pointNesting: true.
• Telemetry: the input's src / present come from the real input point (an rbAmp input read adc / not present).

Full list: CHANGELOG.md. Node: node/README.md.