Independent guide for Hubitat owners ยท Last checked
Get your Hubitat ready for Z-Wave JS before Feb 1, 2027
Hubitat ends legacy Z-Wave support on that date. See which devices have reported problems on Z-Wave JS, what fixed them, and what to do before you switch.
- Days left
- 72
- Devices with reported issues
- 20
- Already fixed by an update
- 9
Numbers show reported issues for each kind of device, last checked Nov 21, 2026.
Reported issues
Devices with reported Z-Wave JS problems
20 Z-Wave devices: 1 not fixed yet, 5 open reports, 5 with a workaround and 9 fixed. The Evidence column shows the source for each report. Last checked .
Every battery device: it may not finish setting up after the switch. Wake each device, or wait for its own wake-up. 2.5.3 improves recovery after restarts. Owner feedback thread
Moving to a new hub: one owner could not finish a move from a C-7 to a C-8 with Z-Wave JS on while some devices had not finished setting up. They switched both hubs back to legacy Z-Wave and finished the move. Reported by one owner. Forum thread 167528
These are owner reports about how each device works with Hubitat's Z-Wave JS, not defects in the devices themselves.
Showing 20 of 20
| Device | What owners saw | Seen on | Status and fix | Evidence | Last checked |
|---|---|---|---|---|---|
| GoControl garage door openerGarage | Tamper alarm sounds after the interview or a reboot | Z-Wave JS | Not fixed yetOpen at the last report (Nov 11, 2026). Power cycling the opener helps until the next hub reboot | 2 ownersOwner feedback thread | |
| iBlindsBlindsReported by one owner | Blinds stop responding | Z-Wave JS on 2.5.1.142 | Open reportA window-covering patch shipped in 2.5.1.143, but the reporting owner still had lock-ups at the last post (Aug 8, 2026) | Staff acknowledged; 1 ownerForum thread 165469 | |
| Aeon MinimoteRemoteReported by one owner | Stuck in interview after switching; no communication | Z-Wave JS (reported Oct 26, 2026, after 2.5.2.134) | Open reportNo fix recorded. One owner reverted to legacy Z-Wave, where the remotes worked again | 1 owner (3 remotes)Owner feedback thread | |
| Aeotec Door/Window Sensor 7 and recessed sensorsSensor | Go offline or are lost after an update | Z-Wave JS | Open reportA forum moderator said it seems to be resolved in Z-Wave JS 15.31.2. The reporting owner replaced the sensors and did not confirm. A second owner disputed easy recovery of battery sensors on Nov 21, 2026 | Forum moderator statement, unconfirmed; 2 ownersForum thread 167583 | |
| VeriLock Translator (window and door lock sensors)SensorReported by one owner | Stuck at 'interview in progress'; child sensors stop reporting | Switch to Z-Wave JS on 2.5.2.139, then update to 2.5.3.123 | Open reportOpen at Nov 19, 2026; no reply yet | 1 owner; unconfirmedForum thread 167594 | |
| Qubino Flush 2 RelayPlug or relay | Parent switch does not respond from the device page; a child switch flickers between on and off | Z-Wave JS (reports on 2.5.3 builds) | Open reportNo reply or fix recorded at Nov 3, 2026 | 2 ownersForum thread 167240 | |
| Leviton VRMX1, VRI06, VRS15 and other older Leviton dimmersDimmer | Instant status updates stop | Z-Wave JS on 2.5.1.142 | WorkaroundUpdate the device firmware to 1.22. A device-side adjustment also shipped in Z-Wave JS 15.31.1; whether 2.5.3 alone clears it is not confirmed by an owner | Staff diagnosed; 2 ownersForum thread 165502 | |
| Fibaro FGS-224 (community driver)Plug or relayReported by one owner | State does not update after a hub command | Z-Wave JS | WorkaroundThe owner edited the community driver. No platform fix is recorded | 1 owner; staff discussedForum thread 165650 | |
| GoControl contact sensorsSensor | Drop off or will not stay connected | Z-Wave JS | WorkaroundExclude and pair again | 2 reports, one from a forum moderatorOwner feedback thread | |
| Schlage BE468 and BE469 locksLockReported by one owner | Lock event descriptions changed, so rules that match on words such as how the door was locked stop firing | Switch to Z-Wave JS | WorkaroundEdit the rules to match the new event wording. The lock itself kept working for the reporting owner. Staff said on Oct 20, 2026 that a related fix was going into the next beta build; which fix was not stated | 1 owner; staff engagedForum thread 166772 | |
| Leviton ZW6HD dimmer with the community Universal Z-Wave Dimmer driverDimmerReported by one owner | Light turned on at the wall still shows off in Hubitat until Refresh | Z-Wave JS | WorkaroundA community fork of that driver, published Nov 13, 2026, accepts the reports the original discards. No platform fix recorded | 1 owner (the fork's author)Forum thread 167475 | |
| Zooz ZSE50 sirenSiren | Sound files would not clear after reconfiguring | 2.5.0.143 | FixedFixed in 2.5.0.153 | Named in release notes; 2 ownersForum thread 164206 | |
| Aeotec Smart Switch 6Plug or relay | On/off state does not update | Z-Wave JS (2.5.0.153 onward) | FixedFixed across 2.5.2.134 and 2.5.2.139 | Named in release notes2.5.2 release notes | |
| Fibaro Wall PlugPlug or relay | Shows off right after switching on | Z-Wave JS | FixedFixed in 2.5.2.128 | Named in release notes; staff fixed2.5.2 release notes | |
| Zooz ZSE41 contact sensorSensor | False open report after a battery report | 2.5.1.x | FixedFixed in 2.5.2.126 | Named in release notes; 2 owners2.5.2 release notes | |
| Zooz ZEN55Sensor | Goes offline after Refresh | 2.5.2 | FixedFixed in 2.5.2.134 | Staff fixed; owner confirmedForum thread 166510 | |
| Alfred Z-Wave lockLock | Keypad unlock and code-use reports missing | Z-Wave JS | FixedFixed in 2.5.2.139 | Named in release notes2.5.2 release notes | |
| Zooz ZEN31 RGBW dimmerDimmer | State not reported; child controls wrong | Z-Wave JS | FixedFixed in 2.5.2.139 | Named in release notes; 1 owner2.5.2 release notes | |
| Aeotec / Aeon Labs Key Fob Gen5 (4 button)RemoteReported by one owner | Button presses do not trigger rules | Z-Wave JS | FixedWorking after updating to 2.5.2.134, per the reporting owner. Not named in the release notes | Staff acknowledged; owner confirmedOwner feedback thread | |
| Z-Wave locks (Kwikset Home Connect 620 named)Lock | Lock codes wiped when switching | Switch to Z-Wave JS before 2.5.2.134 | FixedFixed in 2.5.2.134, which stops the switch from wiping codes. Codes already lost must be entered again | Named in release notes; staff confirmed; 4 owners2.5.2 release notes |
No report for that search as of Nov 21, 2026. That is not a guarantee: use the checklist below.
Not listed does not mean tested. This table covers problems found in public reports up to the last-checked date.
By device type
What to check on each kind of device
Locks
- Update to 2.5.2.134 or newer before you switch. Earlier builds could erase lock codes.
- Write down every user code anyway.
- After the switch, test each code at the door.
Battery sensors
- Hubitat says battery devices may need waking after the switch.
- Keep each sensor's wake-up steps handy.
- Open and close each door sensor once afterwards.
Remotes and key fobs
- Press every button once after the switch.
- Check that each automation it drives still runs.
Dimmers and switches
- Turn each one on and off from the wall.
- Check the dashboard updates right away.
Garage door openers
- Watch for a tamper alarm after the hub re-reads the device.
- Test open and close while you are home.
Plugs and relays
- Check on, off and power reporting.
- Community drivers may need an update for Z-Wave JS.
Before Feb 1, 2027
Your switch plan in six steps
Until Feb 1, 2027, Hubitat still supports legacy Z-Wave, so you can choose the day you switch.
Update the hub
Install platform 2.5.3 or newer. It includes Z-Wave JS fixes and a new Troubleshooting Center.
Make a backup
Save a local backup. Hubitat's cloud backup is free and works without Hub Protect.
Write things down
Lock user codes, and which devices run on batteries.
Check your devices
Look each model up in the table above and open the source for details.
Switch on a quiet day
Pick a day you are home. Wake battery devices as Hubitat asks.
Check afterwards
Use the Troubleshooting Center to find devices that need attention, then test locks, remotes and sensors.
Questions
Frequently asked questions
When does Hubitat end legacy Z-Wave support?
On Feb 1, 2027. Hubitat announced on Nov 20, 2026 that Z-Wave JS will then be the only supported Z-Wave implementation.
Will I have to pair all my devices again?
Hubitat says battery devices may need waking and that certain devices may need extra attention. Owners reported re-pairing some GoControl contact sensors. 9 of the 20 problems in our table were fixed by a platform update.
My device is not in the table. Is it safe?
Not necessarily. The table lists problems found in public reports up to the last-checked date. A missing device means we found no public report, not that it was tested.
Does this affect Zigbee devices?
No. The change covers Z-Wave only.
Who runs this page?
Olsen Industries LLC, an independent publisher in New Jersey. It is not affiliated with Hubitat, Inc. Facts are restated in our own words, with links to the public sources.
Sources
Where these facts come from
We read these public pages and restate the facts in our own words. Each device row links to its own report.