I’ve configured my z-wave devices to use z-wave js because it was the recommended approach. I see “firmware updates” on the roadmap:
WS API Ready, awaiting frontend changes
Refresh Node (re-interview, refresh values, refresh CC values)
Replace Failed Node
Show node metadata on the device page (exclusion, inclusion, reset, wakeup, manual, device database URL)
Node Firmware Updates
opened 02:55PM - 21 Jan 21 UTC
Roadmap for the Z-Wave JS integration.
Note: for a list of all that is already … supported see [here](https://www.home-assistant.io/integrations/zwave_js/).
**Remaining platform support/features**
**Service calls**
**Z-Wave control panel within Home Assistant (UI) for managing the Z-Wave nodes/network.**
- **WS API Ready, awaiting frontend changes**
- [ ] Refresh Node (re-interview, refresh values, refresh CC values)
- [ ] Replace Failed Node
- [ ] Show node metadata on the device page (exclusion, inclusion, reset, wakeup, manual, device database URL)
- [ ] Node Firmware Updates
- [ ] Check for and install device config file updates
- [ ] Node tx/rx statistics [[PR](https://github.com/home-assistant/frontend/pull/12794)]
- [ ] UI for managing node associations
- [ ] Add support for changing wakeup time to config panel (separate CC from normal configuration)
- **Lib ready, WS API support missing**
- [ ] Node diagnostics (checking route health, testing power level, etc.)
- [ ] Record events and commands, see options (in either case we can have a stop button to stop recording because we can see whether recording is enabled or not):
- reload config entry after setting a parameter that tells the config entry to start recording when initializing the client during setup
- Update the parameter live, downside is we miss past events
- **Z-Wave JS ready, lib support missing**
- **zwave-js support missing**
- [ ] S2 multicast support
- **Unclear yet on what's needed**
- [ ] Some form of network health check, make it easier to point out dead nodes or nodes that are slow to respond or having communication failures.
- [ ] Network visualization of the mesh (like ZHA)
Note: Full configuration of the options are already available in the zwavejs2mqtt control panel.
**Other**
- [ ] Better documentation! (this will likely never be checked off unless and until the zwave-js project stops maturing)
- [ ] Improve the Core config flow for add-on config options. Provide a list of USB devices to select device, and validate that security keys have the correct format.
**Finished**
- **Services**
- [x] Set configuration parameter service.
- [X] Poll node/value service.
- [x] Bulk set partial configuration parameter service.
- [x] Multicast support
- [x] Reset meters
- **UI**
- [x] UI for updating node configuration settings
- [x] Adjust logging level of zwave-js server from UI
- [x] Subscribe to logs in the frontend
- [x] Node specific page
- [x] Log config update handling
- [x] Heal network
- [x] Show parameter number on node config page (most device manuals refer to parameter numbers instead of descriptions)
- [x] Heal node
- [x] Remove failed node
- [x] metadata comments (e.g. known issues with the device)
- **General**
- [x] Add sensor for node status (awake/asleep/dead/etc)
- [x] SoundSwitch (siren) support [2021.8]
- [x] Support setting default tone and volume [2021.9]
- [x] Device conditions (config parameter state, any value state, node status) [2021.8]
- [x] Device triggers for value notifications, notifications, and node status [2021.8]
- [x] Protection Command Class (`select` entity?) [[2021.9](https://github.com/home-assistant/core/pull/54717)]
- [x] Automation triggers (non-device) for any value update [[2021.9](https://github.com/home-assistant/core/pull/54897)]
- [x] Device triggers for any value update [[2021.9](https://github.com/home-assistant/core/pull/54958)]
- [x] Device actions [[2021.10](https://github.com/home-assistant/core/pull/53038)]
- [x] Migration wizard from (deprecated) `zwave` integration [[2021.10](https://github.com/home-assistant/core/pull/56159)]
- [x] S2 support [2021.10]
- [x] QR code (SmartStart) inclusion [[2021.12](https://github.com/home-assistant/core/pull/59037)]
- [ ] Controller statistics [[2022.6](https://github.com/home-assistant/frontend/pull/12668)]
- **HA support missing but supported by the library**
**Obsolete**
- [ ] ~~Some sort of UI for configuring complex device settings, like notifications for Inovelli switches: https://nathanfiscus.github.io/inovelli-notification-calc/ or aeotec energy monitor reporting configs.~~ (solved by partial parameter service)
- [ ] ~Migration wizard from `ozw` integration~ (based on current analytics and the low usage of the `ozw` component, we feel a migration wizard is significantly more effort than its worth)
Does anyone know if there is a way to do the update via command line/some other trick without needing to switch to zwavejs2mqtt or find a Windows computer to update hardware?
freshcoast
(Z-Wave AI Bot)
June 3, 2022, 10:51pm
2
1 Like
Switching to zwavejs2mqtt isn’t actually a big deal - I did it a week or so ago and haven’t looked back. The MQTT component is optional, and it’s actually off by default so don’t let that put you off. It’s almost the same feature wise, but exposes the Z-Wave JS GUI, which is far far superior to anything available in the native integration - and has menu options for OTA upgrades, so probably ticks that box for you.
Thanks for recommendation
I was nervous I would have to re-setup my z-wave devices and configure my zooz usb stick all over again. Is it easier than that? (Best case = just add the add-on, and I can use the front end without changing anything )
freshcoast
(Z-Wave AI Bot)
June 14, 2022, 3:53pm
5
It was recently announced that firmware update support is planned for next release.
7 Likes
sota
(Pat Rooney)
June 18, 2022, 6:51am
7
No,w if only you could get Fibaro to do the same. Currently you either have to use their controller to update their devices or else return them to the factory.
3 Likes
HVR88
June 21, 2022, 2:12pm
8
Still better than Homeseer.