mattludwigs

mattludwigs OP

v0.6.4

Added better validation in the UserCode.Set command to ensure that we are keeping to the Z-Wave specification. When you send in invalid user code params the Z-Wave spec is to ignore the command, which can lead to unexpected behavior.

0
Post #11
mattludwigs

mattludwigs OP

v0.6.5

  • Enhancements
    • Support GetDSK command
    • Support FailedNodeRemove command
    • Allow zipgateway_path configuration
    • Generate the zipgateway.cfg to allow device specific
      information to be passed into the zipgateway runtime.
1
Post #12
mattludwigs

mattludwigs OP

v0.6.6

  • Fixes
    • Application start failure when providing the correct
      data structure to the zipgateway_cfg configuration
      field
2
Post #13
mattludwigs

mattludwigs OP

v0.7.0

Introduces SmartStart support!

SmartStart will allow you to pair a device to a Z-Wave controller without
turning the device on. Devices that support SmartStart will have a device
specific key (DSK) that you can provide to the controller prior to turning on
the device.

iex> Grizzly.send_command(Grizzly.Controller, Grizzly.CommandClass.NodeProvisioning.Set, dsk: dsk)
:ok

After running the above command you can plug in your SmartStart device and the
controller will try to join the Z-Wave network automatically.

As a note, your controller might not have the necessary firmware to have SmartStart.

To verify this you can use RingLogger to read zipgateway logs which at the start
will log if the controller supports SmartStart.

Breaking Changes

Breaking change to the return value of sending Grizzly.CommandClass.ZipNd.InvNodeSolicitation.

When using that function send_command would return
{:ok, {:node_ip, node_id, ip_address}} but now it returns
{:ok, %{ip_address: ip_address, node_id: node_id, home_id: home_id}}.

  • Enhancements
    • SmartStart support through the NodeProvisioning command class
    • Added home_id field to Grizzly.Node.t()
    • Support fetching home_id of the Z-Wave nodes when fetching
      Z-Wave information about the node
1
Post #14
mattludwigs

mattludwigs OP

v0.8.0!

Adds support for handling SmartStart meta extension fields.

These fields give more information about the current status, inclusion methods,
and product information for the SmartStart device.

There are two breaking changes:

  1. All SmartStart meta extensions were moved from Grizzly.CommandClass.NodeProvisioning
    namespace into the Grizzly.SmartStart.MetaExtension namespace.
  2. Upon finalizing the meta extension behaviour and API we made changes to how
    previously supported meta extensions worked. Namely, we added a new/1
    callback that does parameter validation, and returns {:ok, MetaExtension.t()}.
    This breaks the previous behaviour of to_binary/1 functions in previously
    implemented meta extensions.
  • Enhancements
    • Full support for SmartStart meta extensions
    • Add meta_extensions field to Grizzly.CommandClass.NodeProvisioning
      commands that can handle meta extensions
    • Update Grizzly.Conn.Server.Config docs
  • Fixes
    • Invalid keep alive (heart beat) interval
    • Set correct constraints on Time command offset values

Thank you to those who contributed to this release:

  • Jean-Francois Cloutier
  • Ryan Winchester
4
Post #15
mattludwigs

mattludwigs OP

v0.8.1!

  • Enhancements
    • Update docs and resources
  • Fixes
    • An issue when the unsolicited message server would cause a
      no match error that propagated up the supervision tree

Thank you to those who contributed to this release:

  • Ryan Winchester
4
Post #16
mattludwigs

mattludwigs OP

v0.8.2

  • Enhancements
    • Support SWITCH_BINARY_REPORT version 2
1
Post #17
mattludwigs

mattludwigs OP

v0.8.3

  • Enhancements
    • Support Wake Up v2 and Multi Channel Association v3
3
Post #18
mattludwigs

mattludwigs OP

v0.8.4

  • Fixes
    • Handle when there are no nodes in the node provisioning list when
      requesting all the DSKs.
1
Post #19
mattludwigs

mattludwigs OP

v0.8.5

  • Fixes
    • various spelling and documentation fixes
    • Dialyzer fixes
3
Post #20