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.
mattludwigs
0
mattludwigs
v0.6.5
- Enhancements
- Support
GetDSKcommand - Support
FailedNodeRemovecommand - Allow
zipgateway_pathconfiguration - Generate the
zipgateway.cfgto allow device specific
information to be passed into thezipgatewayruntime.
- Support
1
mattludwigs
v0.6.6
- Fixes
- Application start failure when providing the correct
data structure to the zipgateway_cfg configuration
field
- Application start failure when providing the correct
2
mattludwigs
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
NodeProvisioningcommand class - Added
home_idfield toGrizzly.Node.t() - Support fetching
home_idof the Z-Wave nodes when fetching
Z-Wave information about the node
- SmartStart support through the
1
mattludwigs
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:
- All SmartStart meta extensions were moved from
Grizzly.CommandClass.NodeProvisioning
namespace into theGrizzly.SmartStart.MetaExtensionnamespace. - Upon finalizing the meta extension behaviour and API we made changes to how
previously supported meta extensions worked. Namely, we added anew/1
callback that does parameter validation, and returns{:ok, MetaExtension.t()}.
This breaks the previous behaviour ofto_binary/1functions in previously
implemented meta extensions.
- Enhancements
- Full support for SmartStart meta extensions
- Add
meta_extensionsfield toGrizzly.CommandClass.NodeProvisioning
commands that can handle meta extensions - Update
Grizzly.Conn.Server.Configdocs
- Fixes
- Invalid keep alive (heart beat) interval
- Set correct constraints on
Timecommand offset values
Thank you to those who contributed to this release:
- Jean-Francois Cloutier
- Ryan Winchester
4