Back to Inovelli Guides
Inovelli

How to Fix Inovelli Switch Losing Configuration After Power Outage

Inovelli GuideSmart Switches
medium difficulty 15-25 minutes 26 views 0 found helpful Where this fix applies: North America, Selected international markets Updated
This guide applies to: Inovelli Inovelli Post-Outage Recovery (Inovelli switch parameter persistence)
At a glance — most common causes
  • Perceived loss (config persists in NVM) — actually state/LED
  • Power-restore state making it look reset
  • Hub lost sync, not the device
15-25 minutes13 solutions coveredmedium level

Expert Review & Technical Scope

DeviceInovelli Inovelli Post-Outage Recovery
Model CoverageInovelli switch parameter persistence
Fix Time15-25 minutes
DifficultyMedium
Required Toolshub admin, config notes
Network / ProtocolWi-Fi / app-based troubleshooting context

Problem Description

Your Inovelli switch appears to lose its configuration (LED color, dimming speed, Smart Bulb Mode) after a power outage. Most parameters are stored in non-volatile memory and should survive outages. The issue is usually the Power Restore parameter controlling the on/off/dim state after power returns, or an NVM write corruption bug in early firmware versions that can reset parameters during rapid power flicker.

Why This Happens in Real Homes

An Inovelli switch appearing to lose its configuration after a power outage is usually a misperception — the switch stores its parameters in non-volatile memory, so they persist through power loss. What actually changes is often the load/LED state on power restore (the power-on default), or the hub losing sync with the device, making it look like the config reset.

Confirm the parameters are actually intact on the device (re-interview to read them back), and set the power-restore state so the switch's behavior on power return matches your expectation — that's usually what "changed." Re-sync the hub if it lost track of the state, and re-apply any single parameter that genuinely didn't persist (which can happen if it was never fully written before the outage). Firmware updates and surge protection round it out; the config itself is retained.

Symptoms

  • Appears to lose config after an outage
  • Settings reset after power loss
  • Config gone after an outage
  • Parameters seem lost
  • LED/behavior changed after outage
  • Config not retained
  • Reverts after power loss
  • Settings lost on power return

Recognize these? Here's what usually causes it.

Common Causes

  • Perceived loss (config persists in NVM) — actually state/LED
  • Power-restore state making it look reset
  • Hub lost sync, not the device
  • A parameter that didn't persist
  • Firmware issue
  • Load state defaulting after outage
  • Config never actually written before the outage
  • Brownout corrupting a write

Most fixes happen in the first 3 steps.

Warning

Do not assume all parameters persist across every firmware version.

Tools & Requirements

hub adminconfig notes

Step-by-Step Solution

1

Check what settings actually reset after an outage

Inovelli switches store most configuration parameters in non-volatile memory (NVM) — they survive power outages. Parameters like LED color, dimming speed, min/max dim levels, and Smart Bulb Mode are stored in NVM and should persist. However, the current dim level (the brightness the light was at before the outage) depends on the Power Restore parameter, not NVM. If the switch appears to 'lose configuration' after an outage: it may be that only the dim level or on/off state changed, while the actual parameters are intact.

2

Check the Power Restore parameter

The Power Restore parameter controls what the switch does when power returns after an outage. Blue Series VZM31-SN: Parameter 256 — values: 0 = off, 1 = on at full brightness, 2 = restore previous state. Red Series LZW31-SN: Parameter 11 — check Inovelli docs for exact values per firmware. If set to 0 (off): the light stays off after an outage, which may feel like the dimmer 'lost' its configuration when really it is just set to restore to off. Set to 2 (previous state) for the most intuitive post-outage behavior.

3

Re-read parameters after an outage to verify

After a power outage and restoration: check the actual parameter values in your hub. In Z-Wave JS: go to the switch device > Configure tab. Click 'Refresh' on each parameter to read the current value from the switch. If all parameters match your settings: the configuration was not lost — only the power restore behavior changed the apparent state. If parameters actually show different values than what you set: the switch's NVM may have corrupted during the outage (see next step).

4

Update firmware to fix NVM retention bugs

Early Blue Series firmware (pre-2.11) had a bug where certain parameters could reset to defaults if the switch experienced a rapid power cycle (power flickers during a storm, rather than a clean outage). Firmware 2.11+ improved NVM write handling to prevent corruption during power transitions. Update your firmware via OTA in Zigbee2MQTT or ZHA. After updating, reconfigure all parameters and test by flipping the breaker off and on.

5

Save your parameter configuration externally

As a safeguard: document all your parameter settings in a spreadsheet or text file. If a future outage does corrupt NVM, you can restore everything quickly. In Home Assistant, you can also create a script that sets all parameters automatically — run it once after an outage to restore all settings in seconds. For Zigbee2MQTT users: export the device state from the device page (the YAML shows all configured parameters) and save it as a backup.

Quick Solutions

Confirm parameters actually persist (stored on the device)
Set the power-restore state so behavior looks consistent
Re-sync the hub if it lost the state
Re-apply any parameter that didn't persist
Update firmware
Set the correct power-on default
Ensure parameters were written before the outage
Protect against brownouts (surge/UPS)

Still having issues? This is usually the deeper cause below.

If drain continues after replacing batteries, check the event history — a stuck-open sensor or rapid polling loop burns through batteries in days.

Pro Tip

Maintain a baseline parameter export for each switch model.

Real-World Insight

Battery-related failures are almost always flagged too late — the device degrades silently for days before the app catches up to what's actually happening.

What Usually Goes Wrong
  • Perceived loss (config persists in NVM) — actually state/LED
  • Power-restore state making it look reset
  • Hub lost sync, not the device
  • A parameter that didn't persist
  • Firmware issue

Official Manufacturer Manual

Inovelli provides official product documentation through their online manual rather than downloadable PDF. Access setup guides, troubleshooting steps, and product specifications for your Inovelli Post-Outage Recovery.

View Inovelli Post-Outage Recovery Online Manual

Source: help.inovelli.com

Need More Help? Inovelli Support

Note: The contact information below connects you directly to Inovelli's official customer support team, not Trunetto. They can help with warranty claims, device replacements, and advanced technical issues.