Figured it would be good to write down the differences between the two components so we have it in one place that can be referenced in HA release notes/blog posts/etc.
Notable Differences
COMMAND_CLASS_NOTIFICATION automatically generates binary_sensors for supported notification types. In the old component you'd have a sensor.motion_sensor_burglar entity that toggled between 0/8 on motion, now that is automatically converted to a binary_sensor. The original sensor.motion_sensor_burglar entity is still created for backwards compatibility, but will be disabled by default in the entity registry.
The zwave.door_sensor_node style entities have been removed
"Central Scene" commands are natively supported
Multiple qt-openzwave instances are supported, so you could have multiple devices with Z-Wave sticks running qt-openzwave (for example, a second stick in a detached garage)
Device classes are automatically assigned for temperature/humidity/power/etc sensors.
Current Limitations
A direct migration path for devices/entities has not been created yet
RGB light support is not yet implemented
Lock platform is not yet implemented
Events for Central Scenes are not yet published as device triggers (so they easily be used in device automations)
Figured it would be good to write down the differences between the two components so we have it in one place that can be referenced in HA release notes/blog posts/etc.
Notable Differences
binary_sensor
s for supported notification types. In the old component you'd have asensor.motion_sensor_burglar
entity that toggled between 0/8 on motion, now that is automatically converted to a binary_sensor. The originalsensor.motion_sensor_burglar
entity is still created for backwards compatibility, but will be disabled by default in the entity registry.zwave.door_sensor_node
style entities have been removedCurrent Limitations