Z-Wave 800 vs 700 series: does it matter which controller stick I buy?

The controller is the one device where the series shows#

Every node in a Z-Wave network talks to one controller, directly or through repeaters, so the controller's receiver is the one radio that has to hear everything. A better end device improves one link. A better controller improves every link that ends at it. The other difference is firmware: 700 and 800 controllers have different "good" firmware ranges. So "700 or 800?" for a stick is two questions, which receiver and which firmware. For the switches and sensors around it, the series matters far less.

The figures, gathered in one place#

No single vendor page puts the spec sheet, the field guidance and the firmware advice side by side. As of October 2026:

For reference, the 500 series that many people are upgrading from sits at 128 kB flash, 16 kB RAM, "600 meters" and "up to 1.5 years" in HomeSeer's table, and around -90 dBm in Z-Wave JS's guidance.

The rows that change what you buy are the receiver and firmware rows. The range and battery rows are the ones quoted in forum threads, and they settle much less.

The confusion, settled: range and battery#

One claim says an 800 series stick reaches much further and makes batteries last much longer. The other says the series makes no difference. Neither is right for a controller. The first persists because spec tables print chip figures without conditions, and they get repeated as if they described a mesh in a house.

Range. HomeSeer lists "1.0 miles" for 700 and "1.5+ miles" for 800, with no conditions attached. No classic Z-Wave mesh link inside a house behaves like that: our Z-Wave explainer gives roughly 200 m line of sight outdoors and 50 m indoors per hop. The mile-scale numbers are chip-level, open-air figures, and on this site the 1.5 mile figure belongs to Z-Wave Long Range with line of sight, not to the mesh.

The one product figure with its conditions written down is from Zooz: the ZSE42 800LR water sensor reaches a hub "at a distance of 1300 feet (only with a hub/controller that provides Long Range support)." A large figure, on Long Range, from a controller that supports it. On a classic mesh, range per hop is decided by walls, placement and the receiver's noise floor.

Battery. HomeSeer's own table gives both series "up to 10 years." A controller stick is USB powered, so battery life is not a property of the stick at all. It belongs to each end device, and the device is more than its chip: moving the ZSE42 from 700 to 800LR, Zooz also moved from a CR2032 to a CR2450, a physically larger coin cell, and added an IP66 rating.

The difference that is real: the receiver#

Z-Wave JS's troubleshooting guide tells you to check the controller's background RSSI and says it "should be as close as possible to the sensitivity limit of your radio": around -100 dBm for 700 series, around -110 dBm for 800 series.

A 10 dB difference is a factor of ten in power: an 800 series controller in a quiet spot can hear a transmission ten times weaker than the faintest a 700 series controller can. That helps the marginal links, such as a lock behind a metal door frame or an acknowledgment that otherwise gets lost and forces a retry.

The catch: that advantage only exists if the stick is in a quiet place. Z-Wave JS says sticks are "prone to interference by USB ports, especially by USB3 ports," and Home Assistant's first troubleshooting step for any Z-Wave problem is: "All users are encouraged to use a USB extension cable to prevent such interference." A stick in a noisy spot performs like its noise floor, whatever its series. The same mechanism hits Zigbee coordinators, as 2.4 GHz interference and channel planning explains.

The difference that is real: firmware#

Z-Wave JS describes the "jammed" or unresponsive 700/800 controller as "a series of firmware issues" that "can only be resolved by a firmware update," adding that "there is no known firmware version that is completely fixed." If devices keep dropping to unavailable for no visible reason, rule this out alongside the causes in a device shows as unresponsive. Three rules follow:

• Check the SDK version, not the firmware number. Both documents say "the SDK version does not have to match the firmware version." If a maker's release notes do not name the SDK, ask the maker.
• Upgrade carefully, because you cannot go back. Z-Wave JS warns that controllers "generally do not allow downgrading the firmware," and to "avoid the _v255 upgrades available from Silicon Labs," which "can not be upgraded either."
• Prefer the newer guidance where the two disagree. For 800 series, Z-Wave JS's common issues page still prefers 7.22.x, while Home Assistant's adapter page prefers 7.23.x and newer and recommends at least 7.23.2. For 700 series, Home Assistant extends the avoid range to 7.21.5 and adds 7.21.6 and newer as preferred.

Home Assistant still lists six 700 series USB adapters as working "if using the SDK and firmware versions mentioned above." But a 700 stick from old stock may sit on firmware in the avoid range, and fixing that is a flash you would not need with a current 800 stick.

Long Range is a controller question#

Long Range is the feature most people want from an 800 series stick, and the controller decides it. The Z-Wave Alliance describes Long Range as "maintaining Z-Wave backward compatibility and interoperability," and Home Assistant says that with a Long Range region selected "you can still add devices that don't support Long Range." The mesh keeps working; Long Range devices are added beside it.

The chip alone does not deliver it. Zooz's 1,300 ft figure applies "only with a hub/controller that provides Long Range support," and as the Z-Wave explainer warns, the controller firmware and the software above it both have to support Long Range inclusion. Look for Long Range in the specification, not just "800." The adapters Home Assistant lists as 800 series are the Connect ZWA-2, the HomeSeer SmartStick G8 and the Zooz ZST39 LR. The ZWA-2 runs the classic mesh and Long Range simultaneously, costs $69, and is one model for every region (the rest of a Home Assistant radio setup is on its platform page). On 700 and 800 adapters the region can be changed, but "the frequency of end devices cannot." A stick can follow you abroad; your switches cannot.

If you are choosing a whole hub rather than a stick, the series is fixed by the box. Hubitat ships an 800 series radio with Long Range, Homey Pro ships 700 series, and the hub comparison lists the rest side by side.

Where the chip series stops mattering#

End devices in a mixed mesh. Z-Wave JS notes that all routes should run at the highest speed your devices support, "which will be 100 kbps, except for some very old ones (before 500 series)." So 500, 700 and 800 series switches share the same top rate on one mesh, and replacing working switches to "upgrade the network" buys little.

When the problem is too much traffic. Z-Wave JS warns that "too much RF traffic can be the death of a Z-Wave network," naming multisensors and power meters as the worst offenders. A new stick does not cure a flood of reports.

When your hub is closed. On a hub such as SmartThings, you get whatever radio and firmware the vendor ships.

Upgrading from a 700 or 500 stick#

You do not have to re-pair to change sticks if your software can move the network. Home Assistant's Migrate adapter wizard backs up the old adapter's non-volatile memory (NVM), "which contains your network information including paired devices," and restores it onto the new one. The prerequisites differ by what you are leaving:

• From a 500 series adapter: update it to SDK 6.61 or later first.
• From a Nortek HUSBZB-1: "There is no easy way to update that device. You need to set up a new network."
• From a 700 series adapter: no extra prerequisite is listed.

Unplug the old stick when the wizard tells you to: Home Assistant warns it "might interfere with the new one" even if no error appears. The Zigbee equivalent is Zigbee coordinator migration. If you are changing software at the same time, that is a platform move, and switching platforms sets out the order.

The rule to apply#

Z-Wave stays the right radio for the jobs it was already right for: locks, outbuildings and masonry, as Zigbee vs Z-Wave and which radio for which job set out. The stick decides how well your controller hears that network, not which devices belong on it.