Releases: smartrent/grizzly
v0.8.8
- Enhancements
- Make Z-Wave versions standard version formatting
- Fixes
- Parsing the FirmwareMD report for version 5
- Fix spec for queued commands
v0.8.7
- Enhancements
- Support
FIRMWARE_UPDATE_MD
meta data report command v5
- Support
v0.8.6
- Fixes
- duplicate fields on the
Grizzly.Node
struct
- duplicate fields on the
v0.8.5
- Fixes
- various spelling and documentation fixes
- dialyzer fixes
v0.8.4
- Fixes
- Handle when there are no nodes in the node provisioning list when
requesting all the DSKs.
- Handle when there are no nodes in the node provisioning list when
v0.8.3
- Enhancements
- Support Wake Up v2 and Multi Channel Association v3
v0.8.2
- Enhancements
- Support SWITCH_BINARY_REPORT version 2
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
- An issue when the unsolicited message server would cause a
Thank you to those who contributed to this release:
- Ryan Winchester
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:
- All SmartStart meta extensions were moved from
Grizzly.CommandClass.NodeProvisioning
namespace into theGrizzly.SmartStart.MetaExtension
namespace. - 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/1
functions in previously
implemented meta extensions.
- Enhancements
- Full support for SmartStart meta extensions
- Add
meta_extensions
field toGrizzly.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
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 toGrizzly.Node.t()
- Support fetching
home_id
of the Z-Wave nodes when fetching
Z-Wave information about the node
- SmartStart support through the