zigpy 2.4.0, the Zigbee library underneath Home Assistant's ZHA integration, was released on 21 October 2026. Two changes matter for ZHA users: the library now batches its database writes, and it has a working Green Power runtime, the part of the Zigbee standard used by battery-free switches. Neither reaches Home Assistant until ZHA moves to the new zigpy. The latest ZHA library release is 2.3.1 from 9 October.

Fewer database writes

Until now zigpy committed to its SQLite database after almost every event it recorded: attribute reports, state changes, last-seen updates. On a busy network with plugs that report power all the time, that meant a write to the SQLite journal roughly every second.

Version 2.4.0 adds a database_commit_interval setting with a default of 30 seconds. Writes still run in order, but the commit waits for the interval. Events that should not wait are written at once: network backups, pairing and removing devices, network address changes and group changes. Pending changes are also flushed on shutdown, and a value of 0 brings back the old commit-after-every-event behaviour.

The developers are clear about the cost. After a hard crash or a power cut, up to 30 seconds of attribute, last-seen and topology data can be lost. Pairings and backups are not affected because they skip the delay. A follow-up fix in the same release makes sure a device re-interview does not force a commit halfway through another write.

Green Power, six years after the request

Green Power devices are the Zigbee switches that run on the energy of the button press, like the Philips Hue Tap. A request for Green Power in zigpy has been open since March 2020. The parsing layer (frame types and encryption) was merged in July, and 2.4.0 adds the rest of the runtime:

  • a Green Power manager for commissioning, pairing and handling incoming packets;
  • a device model for Green Power devices and a proxy table;
  • interception of Green Power frames on endpoint 242, cluster 0x0021, and a permit_gp call to open the network for them.

Commissioned Green Power devices are stored in the SQLite database (schema v16, a new gp_devices table), so they survive a restart. Their frame counter is saved on every press, not only at pairing, which keeps the protection against replayed packets working.

Quirks for specific Green Power devices are not part of this release, because the quirks system itself is being reworked. There is no word yet on when ZHA will use the new code.

Smaller fixes

  • With a local time zone configured, the Time cluster now answers with daylight saving start, end and shift. Without one, zigpy can't know the DST dates and no longer sets the Master_for_Zone_and_DST flag.
  • The periodic topology scan stops properly when shutdown happens during a scheduled scan.
  • An exception in one event listener no longer breaks the others.