Leviton joins as a Works with Home Assistant partner

Blog
21

I think the benefit here is mostly that Leviton Zwave products are going to have firmware updates available through HA directly. Right now you have to go hunting for the firmware to do updates or raise support tickets with Leviton to get the firmware package.

From the way this reads updated firmwares will start to ship with HA itself so that end users can apply them without the hassle of sourcing them! To me, this is a big win as hunting down firmware can be a real pain.

1 Like
22

I’m not using zwave, but zigbee. And zigbee2mqtt provides firmware. No hunting. :slight_smile:

23

I just went through every leviton device in z2m’s supported devices. Not one lists firmware updates as a supported feature currently. Which one do you have?

1 Like
24

This is awesome, Leviton is a great company.

25

Good to hear! Glad the partnership program is getting momentum

26

The blog post mentioned a Leviton integration for 2022.8. I just tried and did not find a “Leviton Z-Wave” integration when trying to add. I am on 2022.8.1

More interesting will be if this adds support for older scene controllers and perhaps the Leviton smart breaker panels…

27

It’s supported through zwave js.

1 Like
28

Thanks. The description makes it sound like there is a separate component to be installed.

29

Leviton Z-Wave is in 2022.8 and shows in my integration list

30

And the docs say

The Leviton Z-Wave integration was introduced in Home Assistant 2021.2

31

The integration was as ZwaveJS was introduced then. The Leviton Z-Wave entry in the integrations list was added as of 2022.8

32

Its kinda misleading, and I don’t mean that in a perjorative way. Perhaps confusing is a better word.

33

The rebadging of Z-Wave JS to Z-Wave may confuse some, but lets not detract from the fact this is Leviton, a quite big company, partnering with an Open Source project, Home Assistant, to ensure their range of products will work properly in Home Assistant. This is a huge step forward and will hopefully lead the way for other major companies to jump in. Imagine Tuya doing Works with Home Assistant. That would be huge.

The Z-waveJS rebadge to Z-Wave doesn’t really affect the integration. It was just a naming thing. The Works with Home Assistant thing however, that is a different thing. That gives some guarantee it will continue working with future devices.

3 Likes
34

Tuya, they promised to work with home assistant. But they couldn’t carry through. Please be careful what you wish for.

2 Likes
35

Imagine Tuya (chips) work with esphome :rocket:

…so one can take full control and ownership :muscle:

36

My whole house is leviton z wave decora switches. They’re pretty amazing. 56 switches total, so a pretty substantial zwave network. I haven’t ever had any devices drop out of mesh in over a year since setting them all up.

It’s one of the only z wave switches with companions that all sync, so the indicators for on/off, and the dimmer values all sync in multiway switching. My favorite part is they are center spring switches, so no ‘some up, some down’ as they all rest in the center.

Most zwave switches have the primary attached to load, with dumb switches down stream that don’t look the same or match.

Here’s the models I use

  • Leviton DZ6HD-1BZ Decora Smart Dimmer
  • Leviton DD00R-DLZ Decora Companion Dimmer
  • Leviton DZ15S Decora Smart Switch
  • Leviton DD0SR-DLZ Decora Companion Switch
  • Leviton ZW4SF-1BW Decora Smart 4 Speed Fan Controller

I know people like lutron and such, but you can’t get more intuitive than simple up down paddles matching everywhere with no batteries to ever replace.

2 Likes
38

Do you get the scene buttons too? I just added one in via the HK integration and all I get is the relay button, none of the scenes.

39

Any news on “Work with Home Assistant” for Leviton’s Zigbee devices and zigpy OTA provider for ZHA?

Leviton only joined “Works with Home Assistant” partner program (Nabu Casa device compatibility partnership) with the promise of support for their Z-Wave devices, but not for their Zigbee devices?

Meaning that they now have the right to add “Works with Home Assistant” badges to their devices once they tested and confirmed compatibility for those devices? → https://partner.home-assistant.io/

That is, I missed that while Leviton was the very first company to join the “Works with Home Assistant” partner program, it looks like it then solely partnered with Nabu Casa to get the “Works via Z-Wave with Home Assistant” badge, only agreeing to work with Nabu Casa to make sure that their line of Z-Wave series devices will work with Home Assistant, and not also partnered to get the “Works via Zigbee with Home Assistant” badge as well(?). That is, to also make sure that users of existing and future Leviton branded Zigbee devices, such as Leviton’s Decora Smart family of Zigbee-enabled lighting control products (which are Zigbee Certified), will also have a great experience with their Zigbee devices when using Home Assistant’s ZHA integration.

Leviton Decora Smart family

Leviton Lumina family (which are not only Zigbee devices) and other Zigbee devices from Leviton

At least I understand that the idea with the program is that manufacturers get rewarded with badges if they agree to work with Nabu Casa on making their devices work fully work out-of-the-box as well as get automatic firmware updates via Home Assistant, for a greater user experience.

“There are manufacturers that are creating products that integrate into Home Assistant using standards like Z-Wave, Zigbee, or Matter (soon). In these cases, the integration is maintained by the Home Assistant community and Nabu Casa. These companies can still become a member of the Works with Home Assistant program but are relieved from integration maintenance.” “With Home Assistant we are always working on educating our users about preferring local control and open standards when acquiring new products. This is also reflected in the “Works with Home Assistant” badges.”

https://www.home-assistant.io/blog/2022/07/12/partner-program/

https://partner.home-assistant.io/

image

Thus I would like to suggest this as an open letter question Leviton as a company in the hope that they consider providing public Zigbee OTA firmware update images for their devices?

The Follow-up question to that or rather an feature request is if Leviton as a company is willing to spare development time to add a publicly available OTA (Over-The-Air) Provider Server or Repository where it publishes/hosts Zigbee firmware update image files for its devices as well as contribute some OTA Provider downloader code for the zigpy library which is what Home Assistant’s ZHA integration depends on?

https://www.home-assistant.io/integrations/zha#ota-firmware-updates

https://github.com/zigpy/zigpy/blob/dev/README.md#zigbee-device-ota-updates

As Leviton as a company probably do not know yet, zigpy is the Zigbee framework and hardware radio API/CLI abstraction code library that is used by Home Assistant’s ZHA integration as well as a few other popular home automation software as a dependency in their Zigbee implementations and providing a “Leviton Zigbee OTA provider” and matching downloader code support for Zigbee devices from Leviton in this zigpy library could potentially enable much easier OTA firmware upgrades for end-users of those in the future, and include; for Home Assistant’s ZHA integration today, as well as probably Zigbee plugin for Domoticz (e.i. the Domoticz-Zigbee project) and the official Zigbee Plugin developed by Jeedom SAS (i.e. the Zigbee plugin for Jeedom) in the future.

FYI, puddly is now working on supporting “Generic OTA providers” for zigpy via this new JSON format schema:

https://github.com/zigpy/zigpy/wiki/OTA-Information-for-Manufacturers

https://github.com/zigpy/zigpy/pull/1165

“This allows for new providers to be added to zigpy without extra code. This also allows for manufacturers to distribute test feed URLs to customers without deploying them globally.”

This feature will be introduced via this new pull request that is still a work-in-progress → #1165

If Leviton already provides a publicly available OTA (Over-The-Air) Provider Server or Repository where it publishes/hosts Zigbee firmware update image files then all that should be missing is an OTA provider code with server/repository URL in zigpy.

Please see zigpy’s existing OTA provider code (provider.py) in Python which includes the URL links as source and downloader code for Zigbee OTA firmware image files for direct download:

https://github.com/zigpy/zigpy/blob/b79a072fe19ed4f2adddbb36a7c1a8d901c32fa9/zigpy/ota/provider.py

https://github.com/zigpy/zigpy/tree/dev/zigpy/ota

That is, this zigpy library would need a new “Leviton OTA Firmware provider” section in that OTA provider code (provider.py) to handle image download for Leviton OTA firmware update image files, (please see the “Skeleton OTA Firmware provider” for reference, as well as for referencing also studying provider.py to also look at the other OTA providers that already have different code sections to handle the download of OTA files, such as; IKEA, INOVELLI, ThirdReality (3reality), SONOFF/ITEAD, SALUS/Computime, and LEDVANCE/OSRAM.

https://github.com/zigpy/zigpy/blob/b79a072fe19ed4f2adddbb36a7c1a8d901c32fa9/zigpy/ota/OTA_URLs.md

Hopefully, Leviton management will consider setting up an OTA provider server or creating a dedicated repository for all officially released Zigbee OTA files for Leviton branded Zigbee devices.

That way it will be a single trusted and official primary source of official Zigbee OTA files released by Leviton, and that OTA provider source repository with your Zigbee OTA files could not only be used by zigpy as it could also be reused by other Zigbee implementations independently (both other open-source implementations as well as closed source and proprietary implementations).

FYI, zigpy developers has recently added a new feature to the “zigpy-cli” tool that manufacturers can use to produce a skeleton JSON index from a given set of OTA files, and that way make sure manufacturers OTA files are correctly-structured so that they will be compatible with zigpy out-of-the-box. See the README.md for that “zigpy-cli” tool:

https://github.com/zigpy/zigpy-cli/blob/dev/README.md#ota

Maybe also consider copying concept of index.json with metadata on all files like Koenkk repository has to make scripting easier:

https://github.com/Koenkk/zigbee-OTA/blob/aad94e167391eb95e3aff551374fe4ba0a125221/index.json

zigpy and ZHA does not yet use this or other OTA Index files but Zigbee2MQTT allows users to use it locally as described here:

https://github.com/Koenkk/zigbee2mqtt.io/blob/7a0e49eec80db8292e5e8d4e77586e973ace6cf4/docs/guide/usage/ota_updates.md#local-ota-index-and-firmware-files

and discussion in relation to zigpy implementation here:

#535

And of course README.md file which among other things could contain some basic information on how to update those:

https://github.com/Koenkk/zigbee-OTA/blob/aad94e167391eb95e3aff551374fe4ba0a125221/README.md

Perhaps also as keeping some kind of CHANGELOG.md with changelog release history for each device firmware version:

https://github.com/Koenkk/Z-Stack-firmware/blob/1c3f97ca9ed3fea3112ee9c37012ba1d7907a0ef/coordinator/Z-Stack_3.x.0/CHANGELOG.md

PS: Off-topic but ZHA/Zigbee developers might also be interested to in this related discussion regarding here Koenkk’s zigbee-OTA repository that is used for Zigbee2MQTT and IoBroker → #535

40

This is fantastic news overall - will there be any future interoperability with the Leviton Load Center with the LDATA hub? Having visibility into that data at the breaker panel level through HA would be beyond amazing (and SO appreciated).