homeassistant-zwave_mqtt icon indicating copy to clipboard operation
homeassistant-zwave_mqtt copied to clipboard

Differences between old component and this component

Open cgarwood opened this issue 4 years ago • 1 comments

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)

cgarwood avatar May 08 '20 13:05 cgarwood

The zwave.node_event (AKA Basic Set) event is no longer supported. See #90 and OpenZWave/qt-openzwave/issues/60. (Plus it isn't implemented here)

kpine avatar May 08 '20 15:05 kpine