RBgrid v1.1.4 is out. A fix release on top of v1.1.3: renaming a point is safe again, mains readings come from the right module, and adding the first module takes fewer steps.
Get it
- Firmware: the v1.1.4 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: at webapp.rbgrid.io it's already the latest. For the app on the hub, install
rbgrid-ui_v1.1.4.zipfrom the same page as described in Build & flash. - Already on v1.1.x? Update over the air from the app (Settings → Hub firmware) with
main_release.bin; your Wi-Fi, settings and history are kept. - All releases: github.com/robotdyn-dimmer/RBgrid/releases.
Fixed
- Renaming a point. On ESP32 chip revisions before v3, renaming a point could make it disappear after the next restart, together with its history. Renaming is safe again. If you held off renaming on v1.1.3, you can rename now.
- Mains voltage and frequency now come only from a module that sees mains. Before, a module with unwired voltage inputs (for example an STD-U3I3 used for current only) could set a wrong frequency, around 45 Hz.
Improved
- Adding the first module. On a new hub, the factory address 0x50 is an empty slot until a module is connected there. Connect one module from the box with the hub off and switch on: a new module connected at 0x50 is picked up in this slot, with no address change. The app shows this as its own step and no longer stops on the empty slot.
- Web app 1.1.4:
- with no broker set, the Home Assistant panel now says MQTT is off;
- the connect screen suggests
rbgrid-xxxx.localor the router's device list to find the hub; - on a hub with the factory example tariff, the wizard's quick tariff no longer asks before replacing it;
- the add-module dialog shows the empty-slot step, and offers Find one at another address when the module at 0x50 doesn't answer;
- removing a point now says plainly that its stored history is erased.
Full list: the changelog. User guide: rbgrid.io/webapp/docs.