Firmware Release
LAMP-ZW2 Firmware 8.10.0
LAMP-ZW2 firmware 8.10.0 rebuilds the Z-Wave 800 Series Long Range plug-in dimmer on Silicon Labs Z-Wave SDK 7.24.1, replacing the SDK 7.19.3 build that shipped as firmware 8.0.0. No feature, configuration parameter, load rating, or Z-Wave command class changes. What changes is radio and stack behavior.
This update is optional. A LAMP-ZW2 that pairs, dims, and reports correctly on firmware 8.0.0 needs no action. The signed .gbl file below is published for installers who want the newer Z-Wave 800 Series radio behavior, and it is applied over the air from a hub with a Z-Wave firmware update tool: Home Assistant, Z-Wave JS UI, Hubitat, or HomeSeer.
↓ Download the firmware (.gbl)
What is in firmware 8.10.0
One thing changed: the Silicon Labs Z-Wave SDK the firmware is compiled against. Everything an installer or homeowner touches carries over unchanged from 8.0.0.
| Item | Firmware 8.0.0 | Firmware 8.10.0 |
|---|---|---|
| Silicon Labs Z-Wave SDK | 7.19.3 (3 May 2023) | 7.24.1 (21 July 2025) |
| Hardware revision | hw1 | hw1 - unchanged |
| Region | US-LR, 908.42 MHz | US-LR, 908.42 MHz |
| Configuration parameters | 20 parameters, numbered 1-21 | Identical, same defaults |
| Button control | 1x, 2x, 3x, 5x, 8x, 10x, press-and-hold, factory reset | Identical |
| Load ratings | 200W incandescent / 100W LED | Identical |
| Build date | n/a | 15 January 2026 |
| File | n/a | Signed Gecko Bootloader image (.gbl), 148,920 bytes |
Why Versa moved the SDK
Silicon Labs maintains the Z-Wave 800 Series in its Simplicity SDK release stream. The SDK 7.21.7 release notes direct 800 Series work there explicitly: 800 Series developments "must migrate to the Simplicity SDK Z-Wave SDK releases (7.22.x and newer)." SDK 7.19.3 dates to 3 May 2023 and predates that stream, so the 800 Series radio and stack work Silicon Labs shipped over the following two years lands in releases a 7.19.3 build never sees.
Firmware 8.10.0 puts the LAMP-ZW2 on the maintained branch. That is the whole reason for a release with no visible feature changes: two years of accumulated 800 Series fixes arrive in one step. For background on what separates the two chip generations, see Z-Wave 800 vs 700: what installers need to know.
What SDK 7.24.1 improves for an 800 Series dimmer
These are the items across SDK 7.20.0 through 7.24.1 that matter to a mains-powered, always-on Z-Wave 800 Long Range node. Each is quoted from the Silicon Labs release notes for the SDK version that introduced it.
| SDK | What Silicon Labs changed | What it means on a LAMP-ZW2 |
|---|---|---|
| 7.24.1 | "Improved the Series 800 radio reception capability in environments crowded by wake-up beams." | More reliable command reception on a mesh that also carries FLiRS and battery devices, which fill the air with wake-up beams. |
| 7.24.0 | "Improved Clear Channel Assessment (CCA) reliability. Previously, only the latest measured RSSI value was used instead of the highest value in the RX window." | The dimmer weighs the whole receive window before deciding the channel is free, so it transmits into other traffic less often. |
| 7.24.0 | "Fixed an issue where the radio layer would stop receiving packet until the next TX radio event (1409388)." | Removes a failure mode where a node ignores commands until it happens to transmit something itself. |
| 7.23.1 | "After a firmware update over-the-air process, an end device would need to be reincluded in the network. The issue is fixed, and the inclusion step is no longer necessary." | Removes the blanket re-inclusion step that used to follow every over-the-air update on an end device. |
| 7.22.1 | Fixed an end device soft reset in crowded RF environments (1325746). | Fewer spontaneous resets on dense sites - apartment buildings, commercial installs, anywhere the 900 MHz band is busy. |
| 7.20.0 | Fixed occasional long wake-up beams, up to 9 seconds, on Z-Wave Long Range devices (1112625). | Shorter beams on a Long Range node mean quicker, more predictable responses. |
| 7.24.0 | "The Z-Wave stack and associated binary resources are compiled with the Link Time Optimization (LTO) option enabled." | A smaller stack image on the 800 Series chip. No user-visible effect. |
Why 8.10.0 targets SDK 7.24.1 and not 7.24.0
Silicon Labs shipped SDK 7.24.0 on 16 June 2025 and labeled it in its own release notes: "The 7.24.0 Z-Wave SDK is a Pre-certified version and is not recommended for Production use." The reason is known issue 1468819, described there as follows: "This issue prevents Over-the-Air firmware update after an initial update has been performed successfully." An end device that reached 7.24.0 by over-the-air update could not be updated again, and Silicon Labs published no workaround.
SDK 7.24.1, released five weeks later on 21 July 2025, closes it: "Fixed an issue preventing existing Z-Wave end devices updated to SDK version 7.24.0 via Over-the-Air firmware update to upgrade beyond this version." That makes 7.24.1 the first 7.24.x SDK safe to distribute as an over-the-air image, which is why LAMP-ZW2 firmware 8.10.0 is built on it and why no Versa firmware was ever published on 7.24.0.
Before you update
Home Assistant states it plainly in its own Z-Wave documentation: "A firmware update can damage your Z-Wave device." If a transfer is interrupted, the dimmer can be left unusable, and there is no over-the-air recovery path. Because firmware 8.10.0 is optional and adds no capability, do not update a dimmer that is doing a job you cannot afford to lose.
1. Match the file to the device. This image is for the LAMP-ZW2, hardware revision 1, US region. The hardware revision and region are both encoded in the file name; a controller will refuse an image whose hardware version does not match.
2. Back up your controller first. Export your hub's Z-Wave network backup before you start. It is the one step that makes a bad outcome recoverable.
3. Unplug the lamp load and leave the dimmer powered. The output state during a transfer is not defined, so take the fixture off it. The dimmer itself must stay in the outlet for the whole transfer. Home Assistant: "Once you have started the update process, you must not interrupt the update process but let it complete."
4. Keep the radio link short. Hubitat notes that "Factors such as network conditions, the number of hops from the hub to the device, and distance will all have an influence on the amount of time required to complete the firmware update." If the dimmer sits at the edge of the mesh, move it near the controller for the update and put it back afterward. Expect several minutes, and longer with S2 security enabled.
How to update LAMP-ZW2 firmware over the air
The LAMP-ZW2 accepts over-the-air firmware updates through the Z-Wave Firmware Update Meta Data command class, which is the mechanism every hub-based updater uses. You need a controller with a firmware update tool that accepts a .gbl file. Z-Wave JS UI and Hubitat both ask you to pick a firmware target: it is target 0, the Z-Wave chip itself. Home Assistant does not ask.
Home Assistant (Z-Wave JS integration)
Download the .gbl file to your computer
Save the LAMP-ZW2 firmware file from the button above. Home Assistant uploads it from your local machine, so it has to be downloaded first rather than linked.
Open the device page
Go to Settings → Z-Wave, open Devices, and select the LAMP-ZW2. You need administrator rights on the Home Assistant instance.
Choose Update from the device menu
Under Device info, open the three-dot menu and select Update. Select the firmware file you downloaded in step 1.
Begin the update and let it finish
Select Begin firmware update and leave it alone until it completes. Home Assistant reports progress, then tells you the device is being re-interviewed.
Z-Wave JS UI
Expand the node and check the version
In Control Panel, click the LAMP-ZW2's row in the Nodes table to expand it. The row carries the installed firmware in the FW column. If it already reads 8.10.0, you are done - there is nothing to install.
Advanced, then Firmware update, then Begin
Click the Advanced button, choose Firmware update, then Begin. The confirmation dialog lists the node's manufacturer, product, current firmware and current SDK version, which is a useful check that you have the right node selected.
Select the file and target 0
In the File field choose the LAMP-ZW2 .gbl. Leave Target at Target 0. Confirm with Ok.
Watch the progress bar
The Nodes table shows a percentage as fragments transfer, and Z-Wave JS UI reports the outcome in a dialog when the transfer ends. The same Advanced menu carries an Abort action if you have to stop before the transfer begins in earnest.
Hubitat
Hubitat ships a built-in Device Firmware Updater app, and its documentation confirms the format: "This app supports devices joined with or without security and supports firmware file types HEX, OTZ, BIN, and GBL." Add it from Apps → Add Built-In App → Device Firmware Updater, upload the file in Firmware File Manager, then choose Update Z-Wave Firmware, pick the LAMP-ZW2 and firmware target 0, and select Start Firmware Update. Hubitat's own instruction is worth following exactly: do not power cycle the device until the updater app reports that it is complete.
HomeSeer
In HomeSeer, go to Plugins → Z-Wave Plus → Update Firmware. Select the LAMP-ZW2 and click CONTINUE, upload the .gbl file and click CONTINUE again, then click START. HomeSeer notes the transfer "may take several minutes to complete." Click FINISH when it reports success.
How to check which firmware version is installed
Every Z-Wave controller reads the installed version from the device's Version command class, so you never have to guess. In Z-Wave JS UI, the Nodes table carries an FW column, and the firmware update dialog shows both Current Firmware and Current SDK. In Hubitat's Device Firmware Updater, the current version appears next to each firmware target as you pick the device. Units on the older build report 8.0.0; updated units report 8.10.0.
What happens when the update finishes
Your hub re-interviews the node once the transfer completes. That is the controller re-reading the device's capabilities and version information, and it is expected. Wait for the interview to finish before sending commands. If your hub asks you to power-cycle the dimmer, unplug it for a few seconds and plug it back in.
You do not re-pair the dimmer as a matter of course. Silicon Labs removed the blanket requirement to re-include an end device after an over-the-air update in SDK 7.23.1: "After a firmware update over-the-air process, an end device would need to be reincluded in the network. The issue is fixed, and the inclusion step is no longer necessary." Confirm your parameter values and association groups read back correctly once the interview finishes, and restore them from your controller backup if anything did not carry across.
Z-Wave 800 Long Range plug-in dimmer, officially Alarm.com approved.
LAMP-ZW2 firmware download
Firmware 8.10.0 for the LAMP-ZW2, hardware revision 1, US-LR region, as a signed Gecko Bootloader image of 148,920 bytes. The file name encodes the SKU, firmware version, hardware revision and region, so you can confirm you have the right image before you upload it.
↓ Download the firmware (.gbl)
For mounting, pairing, LED behavior and the full parameter reference, see the LAMP-ZW2 installation manual. For what the 20 configuration parameters do, see Z-Wave configuration parameters explained. For Long Range pairing and SmartStart, see the LAMP-ZW2 setup guide and Z-Wave 800 Long Range explained.
Frequently asked questions
What changed in LAMP-ZW2 firmware 8.10.0?
Only the Silicon Labs Z-Wave SDK the firmware is compiled against: 7.19.3 in firmware 8.0.0 becomes 7.24.1 in firmware 8.10.0. No feature, configuration parameter, button pattern, load rating, or command class changes. What you gain is two years of Z-Wave 800 Series radio and stack work, including improved Clear Channel Assessment and better reception in networks crowded by wake-up beams.
Do I need to update my LAMP-ZW2 to firmware 8.10.0?
No. Firmware 8.10.0 is a maintenance release that adds no capability, so a LAMP-ZW2 running 8.0.0 that pairs and dims correctly needs no action. Install it if you are commissioning a dense or RF-congested site and want every node on the maintained 800 Series stack, or if you are chasing reception symptoms on a specific dimmer.
How do I update LAMP-ZW2 firmware?
Download the signed .gbl file, then push it over the air from a hub with a Z-Wave firmware update tool. In Home Assistant, open Settings then Z-Wave, select the device, choose Update from the three-dot menu under Device info, pick the file, and select Begin firmware update. In Z-Wave JS UI, expand the node, click Advanced, choose Firmware update then Begin, and select the file with Target 0. Back up your controller and unplug the lamp load before you start.
Which hubs can perform a LAMP-ZW2 firmware update?
Any controller with a Z-Wave firmware update tool that accepts a .gbl file. Home Assistant with the Z-Wave JS integration, Z-Wave JS UI, Hubitat's built-in Device Firmware Updater app, and the HomeSeer Z-Wave Plus plug-in all publish documented procedures and all four accept .gbl images. Firmware 8.10.0 is optional, so no controller is required to install it.
What is a .gbl file, and why is LAMP-ZW2 firmware distributed in that format?
A .gbl is a Gecko Bootloader image, the upgrade file format Silicon Labs defines for its wireless chips. It is the format the Z-Wave over-the-air bootloader on 700 and 800 Series devices consumes, and Silicon Labs requires the image to be cryptographically signed. The file carries a CRC integrity check, so a truncated or corrupted transfer fails verification rather than being applied. The LAMP-ZW2 8.10.0 image is 148,920 bytes.
Will a LAMP-ZW2 firmware update remove the dimmer from my Z-Wave network?
Not as a matter of course. Silicon Labs removed the blanket re-inclusion requirement in SDK 7.23.1: after an over-the-air firmware update, the inclusion step is no longer necessary. Your hub re-interviews the node when the transfer completes, which is expected. Export a controller backup before you start, then confirm your parameter values and association groups read back correctly afterward.
How do I check which firmware version my LAMP-ZW2 is running?
Your controller reads it from the device's Version command class. In Z-Wave JS UI the Nodes table has an FW column, and the firmware update dialog shows Current Firmware and Current SDK. In Hubitat's Device Firmware Updater the current version appears next to each firmware target. Units on the older build report 8.0.0; updated units report 8.10.0.
LAMP-ZW2 firmware 8.10.0, built 15 January 2026 on Silicon Labs Z-Wave SDK 7.24.1, for LAMP-ZW2 hardware revision 1, US region (908.42 MHz). Distributed as a signed Gecko Bootloader (.gbl) image, 148,920 bytes. SDK release information quoted from the Silicon Labs Z-Wave SDK release notes for versions 7.20.0, 7.21.7, 7.22.1, 7.23.1, 7.24.0 and 7.24.1. FCC ID: 2AD9XLAMP-ZW2. ETL Listed by Intertek to UL 60730-1:2016. Z-Wave Plus certified (Z-Wave Alliance cert # ZC14-24040421). versawireless.com
