Hubitat 2.5.2: ZWave-JS on Older Hubs, Built-In Reolink, and a Cloud Calls Log
Hubitat released platform 2.5.2 on September 29, 2026, and has pushed six more builds since. The latest is 2.5.2.139, posted October 16. The release notes thread lists every build. This post covers the changes that affect a hub running locally next to Home Assistant, Alexa, and Apple Home.
ZWave-JS for C-5, C-7, and C-8 hubs
With 2.5.2, ZWave-JS is available on C-5, C-7, and C-8 hubs. You switch under Settings > Z-Wave Details > Switch to ZWave-JS. Hubitat says existing devices and security keys migrate, so you don’t have to exclude and re-include anything (announcement). C-5 hubs pick up S2 security and SmartStart, which the old stack never offered on that hardware. Older hubs take longer to start up on ZWave-JS.
The switch is optional if you already have Z-Wave devices; build .134 only switches hubs automatically when they have no Z-Wave devices.
A few fixes in later builds are worth reading before you switch:
- .134 fixed a ZWave-JS migration interview that caused some locks to lose their user codes. If you have Z-Wave locks with codes, update to at least .134 first.
- .139 marks sleeping ZWave-JS devices as Not Responding after 48 hours with no messages. Battery sensors that check in rarely may show up there.
- .139 fixed lock keypad and code reporting on some Alfred locks.
Backups
Build .126 added full local backup support. There is also a new Z-Wave backup, restore, and import tool under Settings > Z-Wave Details > Backup and Restore (details). It saves the Z-Wave radio data and security keys to a file you keep, and it can import a backup from Z-Wave JS UI on another platform. That means a Z-Wave network from a Z-Wave JS UI setup, such as Home Assistant’s, could be imported into Hubitat without re-pairing. Restore is blocked if the backup came from a different Z-Wave stack than the one the hub has enabled, and a Z-Wave backup does not replace a full hub database backup.
Two catches. The Z-Wave tool needs a Backup Plus or Hub Protect subscription. And the backup file holds your Z-Wave security keys, so store it like a password.
Build .139 also fixed a bug where failed backups were reported as successful. If you rely on scheduled backups, check that recent ones actually downloaded.
Built-in Reolink integration
Hubitat now ships a Reolink integration, credited in the notes to a community developer. It started at v1.6.3 in .126 and was up to v1.6.11 by .139, so it is changing fast.
Cloud calls tab in the logs
Build .129 redesigned the Logs page and added a Cloud calls tab that tracks cloud usage. For a local-first setup, this is a place to check how much the hub is using the cloud.
Maker API and Home Assistant
Maker API is how Home Assistant reads Hubitat devices in a setup like mine. Build .126 added curl and bearer token examples to Maker API, and the notes say the same bearer token authentication now works for all apps. Maker API also reports Zigbee quality now.
Alexa, Matter, and Lutron
These were smaller changes, but they touch things a lot of Hubitat owners use:
| Area | Change | Build |
|---|---|---|
| Alexa | Hub mode support in the Alexa skill | .126 |
| Alexa | Likely fix for garage doors showing “not responding” when the command worked | .126 |
| Alexa | Likely fix for missed routine triggers when several attributes change at once | .139 |
| Matter | Firmware updates through the driver’s updateFirmware command, if the maker publishes them | .126 |
| Matter | Attestation now checks the CSA’s online device database, aimed at failed pairings | .126 |
| Lutron | RadioRA 3, keypads, fans, and shades in the LEAP integration | .126 |
| Hue | Event stream and scene transition fixes | .139 |
Other changes: Sonos Integrator replaces the old Sonos integration, which is now deprecated. Visual Rule Builder 2 gained repeated actions in .135. Build .139 added an advanced option to turn off the redirect from the hub’s .local name to its IP address, and, also in .139, a likely fix for Zigbee send-queue stalls.
Before updating
- Take a hub backup and confirm it actually downloaded.
- If you have Z-Wave locks with user codes, wait until you’re on .134 or later before switching to ZWave-JS.
- If you use the old Sonos integration, plan for the move to Sonos Integrator.
- If Home Assistant reads the hub through Maker API, check that device states still update afterward.