What’s in the making… not ready for testing outside beta users…
Backup your module programming
Every Nikobus switch, dimmer and roller module keeps its complete configuration in its own memory: which button drives which output, in which mode, with which timer. Until now that data only existed inside the module and in whatever project file the installer kept. Many of us no longer have the PC software or the project file.
adds a “Backup module programming” button on the Nikobus Bridge device (also available as the nikobus.backup_modules action). It reads the full memory image of every output module and stores it under config/nikobus_backup/, one .nkm file per module plus a summary.json. Read-only on the bus, nothing is written to any module. Run it once and keep the folder somewhere safe. If a module ever fails, you have its exact programming.
Verify that your modules are healthy
Each module can report its status and a checksum it computes over its own memory. “Verify module programming” (or nikobus.verify_modules) asks every module for that, reads its memory back and compares. Results land on a new Programming health diagnostic sensor, with per-module detail in the attributes, and any module with an EEPROM error or a checksum mismatch raises a Repair issue naming it. On a real installation the checksums match bit for bit on all module types, so a mismatch means something is genuinely wrong.
PC-Link clock
The PC-Link has its own clock, used by the calendar functions of the Nikobus application. It never knew about daylight-saving changes. A new PC-Link clock diagnostic sensor shows it, with the drift against Home Assistant as an attribute, and a Sync PC-Link clock button (or nikobus.sync_pc_link_clock) sets it from Home Assistant’s local time. The sensor re-reads hourly.
Covers that stay calibrated
Any cover motion commanded from Home Assistant that ends at fully open or fully closed sends a stop frame after a configurable delay by channel. That erases the small drift the position estimate accumulates over time. Intermediate positions and an explicit Stop are unchanged.
A roller channel that still carries the discovery placeholder of 30 seconds takes its travel time from the run time programmed into the module itself, so the position model matches the hardware out of the box. A value you set on the channel yourself still wins.
Discovery improvements
Discovery now asks each module how many links it holds and reads exactly that, instead of scanning a fixed band. Dimmer ramp times are decoded as well. This needs nikobus-connect 0.35.1 or later, which HACS installs automatically.
Housekeeping
- Bridge buttons grey out while any bridge action runs. One bus action at a time.
- The device-registry deprecation warnings that Home Assistant 2027.8 and 2027.9 started logging are gone.
Upgrade notes
The three new buttons and two new sensors show up on the Nikobus Bridge device.
The backup is a plain memory image and the library documents the layout, so the files remain useful outside Home Assistant.
Restoring a backup into a module is not part of this release. It is technically within reach, but it erases the module before writing. I’m always against writting towards something undocumented, you never know, could work for me, fail for others. Why backup then ? the backup can be loaded into the official Nikobus software and then restored to your modules. To be used only when everything else as failed.
Feedback welcome, especially from installations with module types I do not have myself.
