View Source CHANGELOG

Changelog

This project follows Semantic Versioning.

[v6.8.3] - 2023-08-01

Fixed

  • Fix `:ack_request in response to AsyncConnection command (#810) ## [v6.8.2] - 2023-07-31 ### Added - Implement Sound Switch CC v1-2 (#806) - Implement all commands from User Code CC v2 (#697) ### Fixed - Fix async command timeout handling (#808) - Fix decoding of meter type in Meter Reports (#807) ## [v6.8.1] - 2023-07-19 ### Changed - Pass trace options through from Grizzly.Supervisor (#803) - Made network management command arguments more consistent (#804) ## [v6.8.0] - 2023-07-18 ### Added - Add telemetry (#751) - Implement Mailbox Command Class (#777) - Allow DTLSv1.2 for Z/IP Gateway connections (#782) - Add :raw trace format (#784) - Add option to ignore keepalive frames in traces (#785) - Use Z-Wave XML to generate command class mappings (#793) - Add :mode option to Grizzly.send_command/4 (#795) ### Fixed - Use correct command module for Wake Up Interval Set in Grizzly.ZWave.Decoder (#798) - Skip unsupported values when parsing command class lists (#799) - Trace :text format prints command binary (without Z/IP Packet header) exactly as received (#800) ## [v6.7.1] - 2023-06-20 ### Added - Added Grizzly.Network.get_lifeline_association/1 convenience function (#781) ### Fixed - Increased default command timeout to 15 seconds (#776) - Unsolicited server ACKs all messages (#778) - Made opts arg optional in Grizzly.Network.node_neighbor_update_request/2 (#780) ## [v6.7.0] - 2023-06-02 ### Added - Subscribe to all commands from a given node ### Fixed - Replace Logger.warn with Logger.warning - Ignore trailing bytes in MultilevelSwitchReport - Transmission stats use minimum of rssi_hops for rssi_dbm instead of average - Use signed values for Thermostat Setpoint Set (fixes an error when the value is negative) ### Misc - Drop support for OTP 24 ## [v6.6.1] - 2023-05-12 ### Added - Opt-in IEx autocompletion for Grizzly.send_command (#763) ### Fixed - Ignore unexpected trailing bytes in ConfigurationReport (#764) - Reduce log level for closed connections in UnsolicitedServer (#765) - Better logging for DTLS unexpected error messages (#767) ## [v6.6.0] - 2023-05-05 ### Changed / Fixed - Commands are no longer retried by default (#761) - Node Add Status always includes the :command_classes param even when empty (#760) ## [v6.5.1] - 2023-05-01 ### Fixed - Device classes in Node Add Status are now decoded like in Node Info Cached Get (#759) ## [v6.5.0] - 2023-05-01 ### Added - Implement Network Management Basic Node / Node Information Send command (#749) - Add helper functions for some common debugging tasks (#754) - Extract Home ID and network keys from Z/IP Gateway logs (#755) ### Changed / Fixed - Reset tun/tap interface in Z/IP Gateway tunnel script (#750) - Update RSSI to signal bar calculation (#752) - Normalize multilevel switch report for Leviton DZ1KD-1BZ (#753) ## [v6.4.0] - 2023-04-18 ### Added - Support arbitrary extra items in Z/IP Gateway config (#744) - Support signed integer, unsigned integer, enum, and bit field formats in Configuration Set (#745) ## [v6.3.0] - 2023-04-13 ### Added - Add API to restart Z/IP Gateway (#739) - Implement S0/S2 Security Commands Supported Get/Report (#739) - Implement Network Management Inclusion Failed Node Replace (#741) - Optionally dump traces in Erlang external term format (#742) ### Changed/Fixed - Allow all out-of-spec values in RSSIREPORT (#740) - Trace dumps are now formatted in the calling process instead of the trace server process (#742) ## [v6.2.0] - 2023-04-05 NOTE: Dropped support for Elixir 1.11. ### Added - Add support for sending supervised commands (#727) ### Fixed - Set more info flag when ACKing supervision get commands (#735) - Fix trace dump for :no_operation commands (#733) ## [v6.1.1] - 2023-03-29 ### Fixed - Adds simple command name validation to Grizzly.Commands.Table to ensure correct naming in implementation modules - Fixed the command class versions list for the HVAC virtual thermostat ## [v6.1.0] - 2023-03-22 ### Added - Network Management Inclusion CC (#718) - Neighbor Update Request - Neighbor Update Status - Version CC (#718) - Capabilities Get - Capabilities Report - Z-Wave Software Get - Z-Wave Software Report ### Fixed - Fix encoding of RSSI values in RSSI_REPORT (#722) - Rescue errors in Grizzly.Trace.dump/1 (#723) - Fix command name for Wake Up Notification (#725) ## [v6.0.1] - 2023-03-13 ### Fixed - Typespec for ThermostatSetpointReport params now includes all params (#712) - Enabled Dialyzer :extra_return and :missing_return options and fixed some incorrect return values (#714) - Fixed interpretation of :target_value param in SwitchMultilevel{Set,Report} (#715) ## [v6.0.0] - 2022-03-03 ### Fixed - Handle illegal values from Z/IP Gateway in RSSI_REPORT (#705) ### BREAKING CHANGES - Use abbreviations (:f and :c) for temperature scales (#706) ## [v5.4.1] - 2022-02-14 - Improve InclusionServer crash recovery from non-idle status (#699) ## [v5.4.0] - 2022-02-06 ### Added - Support for Master Code Set/Get/Report commands from User Codes command class (#693) ### Fixed - Parse multilevel switch level 0xFF as 100 (instead of 99) (695) ## [v5.3.0] - 2022-12-16 ### Added - Support for getting configuration parameter name (#691) ## [v5.2.8] - 2022-12-09 ### Changed - Attempting to stop add/remove/learn mode while the inclusion server is idle returns :ok (#688) - Types for command classes and device classes are now generated from their mapping tables (#689) ## [v5.2.7] - 2022-11-17 ### Fixed - Fix virtual temperature sensor command handling (#685) ## [v5.2.6] - 2022-10-28 ### Fixed - Format IPv6 addresses in traces using standard port notation (#677) - Record correct node IP for outgoing traces (#679) - Prevent a crash in Grizzly.Trace.dump/1 when an S2 device has recently been included (#680) ## [v5.2.5] - 2022-10-18 ### Fixed - Support unknown weekday in clock command class (@jfcloutier) ## [v5.2.4] - 2022-10-14 ### Added - Implement event parameter decoding for home security idle notifications (#671) ## [v5.2.3] - 2022-09-28 ### Fixed - Fix Elixir 1.14 deprecation warnings (@bjyoungblood) ## [v5.2.2] - 2022-09-27 ### Fixed - Handling timeout of node removing (@jfcloutier) ## [v5.2.1] - 2022-09-26 ### Fixed - Fix typo for celsius (@jwdotjs) - Handle timeout on DSK input during inclusion (@jfcloutier) - Fix inclusion crash leading to invalid in-memory controller state ## [v5.2.0] - 2022-09-15 ### Added - Grizzly.VirtualDevices.Device.set_device_id/2 callback function (@jfcloutier) - Grizzly.VirtualDevices.TemperatureSensor.state() now has a :device_id field (@jfcloutier) - Grizzly.VirtualDevices.TemperatureSensor.set_device_id/2 implementation (@jfcloutier) - Grizzly.VirtualDevices.Thermostat.set_device_id/2 implementation (@jfcloutier) ### Fixed - When a virtual device is started outside of Grizzly, Grizzly would still automatically add them to virtual network (@jfcloutier) ## [v5.1.2] - 2022-08-09 ### Fixed - Handling timeouts during S2 inclusion process ## [v5.1.1] - 2022-08-09 ### Fixed - GenServer calling its self during S2 inclusion ## [v5.1.0] - 2022-08-02 ### Changed - Deprecated Grizzly.Inclusions.stop/0, please use remove_node_stop/0, add_node_stop/0, or learn_mode_stop/0 instead. ### Added - Grizzly.Inclusions.NetworkAdapter behaviour - Grizzly.Inclusions.ZWaveAdapter implementation of the network adapter behaviour (default adapter Grizzly uses). ### Fixed - Issues around canceling the inclusion process ## [v5.0.2] - 2022-07-28 ## Fixed - Passing a configuration set value parameter that is bigger than the supplied size parameter. (@jfcloutier) ## [v5.0.1] - 2022-06-27 ### Fixed - Virtual thermostat reporting fan state command class did not actually support that command class (@jfcloutier) ## [v5.0.0] - 2022-06-24 Refactored the Grizzly.VirtualDevices.Device behaviour. The behavior no longer has an init/1 callback. Moreover, the handle_command/2 callback still exists but second parameter is not Grizzly.VirtualDevices.Device.device_opts() type. Lastly, a new callback device_spec/1 was added. The change to handle_command/2 also changes the return value expected by the behaviour. If you have implemented this behaviour see the documentation for Grizzly.VirtualDevices.Device.handle_command/2 for new return values. The Grizzly.VirtualDevices.Thermostat and Grizzly.VirtualDevices.TemperatureSensor have both been updated to reflect the changes to the virtual device behaviour. In order to use either of these virtual devices you will need to call start_link/1 on them before you're able to send commands to them. This change requires process based device implementations to be supervised outside of the Grizzly supervision tree. This allows the consuming application the ability to control how the virtual devices are started and when and how they should be shut down. ### Changed - Deleted Grizzly.VirtualDevices.init/1 callback - Changed parameters and return values from Grizzly.VirtualDevices.Device.handle_command/2 - Deleted Grizzly.VirtualDevices.handle_info/2 callback - Grizzly.VirtualDevices.Thermostat (see module docs) - Grizzly.VirtualDevices.TemperatureSensor (see module docs) ### Added - Grizzly.VirtualDevices.Device.device_opts() type - Grizzly.VirtualDevices.Device.device_spec/1 callback - Support for empty alarm report event params (@jfcloutier) - Support long range node ids in the smart start meta extension field :network_status (@jfcloutier) - Grizzly.VirtualDevices.whereis/1 ### Fixed - Grizzly.ZWave.Commands.NodeAddStatus.param() value :node_id type now reflects virtual device ids ## [v4.0.1] - 2022-06-13 ### Fixed - Fix ClockReport command :name field (@jfcloutier) - Fix forcing zipgateway cache update when calling Grizzly.Node.get_info/2 ## [v4.0.0] - 2022-05-19 Breaking change in the Grizzly.VirtualDevices.Device behaviour. If you have not implemented a custom virtual device then you can safely upgrade. If you have implemented a custom virtual device the init/0 callback is now init/1. To upgrade change your implementation to: ```elixir @impl Grizzly.VirtualDevice.Device def init() do {:ok, mystate, my_device_class} end `` The change is to add theas the argument to yourinitimplementation. ### Changed -Grizzly.VirtualDevice.Devicesbehaviourinit/0callback is nowinit/1### Added - Support for the sensor multilevel get command for theGrizzly.VirtualDevices.Thermostatvirtual device implementation - Virtual device support forGrizzly.Node.set_lifeline_association/2- Add virtual device support for the battery get command - Add virtual device support for the version get command - Addhandle_info/2callback inGrizzly.VirtualDevices.Devicebehaviour to allow asynchronous events to broadcast Z-Wave reports - Add return value forhandle_command/2callback inGrizzly.VirtualDevices.Devicebehaviour to allow broadcasts Z-Wave reports based off incoming commands -Grizzly.VirtualDevices.add_device/2now allows a tuple{my_device_impl, my_device_opts}has the first argument -Grizzly.VirtualDevices.TemperatureSensorvirtual device ### Fixed - EnsureGrizzly.VirtualDevices.Thermostatdevice implementation returns:noreplyfor unsupported command classes. (@jfcloutier) - Fix to calculating RSSI averages (@jfcloutier) - Crashing the initialization of a new virtual device caused the virtual device network to get in a bad state ## [v3.0.0] - 2022-05-12 Breaking change in these modules: -Grizzly.ZWave.CommandClasses.NetworkManagementInstallationMaintenance-Grizzly.ZWave.Commands.PriorityRouteReportInNetworkManagementInstallationMaintenancecommand class the:speedtype is now a list ofspeed()rather than a single speed. This effects the commandPriorityRouteReportparameter:speed. This parameter is now a list ofspeed()rather than a single value. If you do not use this command you can safely upgrade with no changes. If you do use this command you will need to update code that assumes the:speedparameter is single value. This change was made to better aline with the Z-Wave specification. ### Changed -Grizzly.ZWave.CommandClasses.NetworkManagementInstallationMaintenance.neighbor_param()type's:speedparam returns a list of typespeed(). (@jfcloutier) -Grizzly.ZWave.Commands.PriorityRouteReport.params()'s:speedparam is now a list ofspeed()than than a singlespeed(). (@jfcloutier) ### Added -Grizzly.VirtualDevicesmodule to allow virtual devices -Grizzly.VirtualDevices.Devicebehaviour to allow custom virtual devices to be used with Grizzly -Grizzly.VirtualDevices.Thermostatvirtual device implementation for a basic virtual thermostat device -Grizzly.ZWave.DeviceClassmodule for defining common device class specifications -Grizzly.send_command/4virtual device support, so you can send commands to virtual devices just like you would a regular Z-Wave device -Grizzly.Network.opt()type now allows for a:seq_numberoption -Grizzly.Network.get_all_node_ids/1to get a list of both regular and virtual device ids -Grizzly.Node.get_info/2support for virtual device ### Fixed - Error when the primary route report would try to be handled (@jfcloutier) ## [v2.1.0] - 2022-04-27 ### Added -Grizzly.ZWave.CommandClasses.WindowCovering(@jfcloutier) -Grizzly.ZWave.Commands.WindowCoveringGet(@jfcloutier) -Grizzly.ZWave.Commands.WindowCoveringReport(@jfcloutier) -Grizzly.ZWave.Commands.WindowCoveringSet(@jfcloutier) -Grizzly.ZWave.Commands.WindowCoveringStartLevelChange(@jfcloutier) -Grizzly.ZWave.Commands.WindowCoveringStopLevelChange(@jfcloutier) -Grizzly.ZWave.Commands.WindowCoveringSupportedGet(@jfcloutier) -Grizzly.ZWave.Commands.WindowCoveringSupportedReport(@jfcloutier) ### Fixed - When a lock does not encode anUserCodeReportas an event parameter (@jfcloutier) - When an unknown user code is encoded as a empty string (@jfcloutier) ## [v2.0.0] - 2022-03-21 ### Breaking change For this release we removed theon_readyoption for Grizzly and added theGrizzly.StatusReporterbehaviour. This is a module that the consuming application can implement to get a more specific type of ready status. There are a handful of moving parts to getting Z-Wave and Grizzly up, so this behaviour can be extended over time to handle more ready cases. To use the status reporter: ```elixir defmodule MyApp.StatusReporter do @behaviour Grizzly.StatusReporter @impl Grizzly.StatusReporter def read() do # Grizzly and Z-Wave are set up! :ok end @impl Grizzly.StatusReporter def zwave_firmware_update_status(status) do # Grizzly is trying informing you if it tried to update teh Z-Wave firmware # and what the status of that attempt is :ok end end ``` ### New feature The newest feature is automatic Z-Wave firmware update. This feature is opt-in and will only try to run if configured. This is useful if you need to update the Z-Wave firmware when Grizzly starts. Here's the configuration: ```elixir grizzly_opts = [ # enables the updating the Z-Wave chip update_zwave_firmware: true, # configure which firmwares you might want to flash to the Z-Wave chip. zwave_firmware: [%{chip_type: 7, path: "/path/to/firmware_file", version: "7.16.03"}], # path the Z-Wave programmer program provided by Silicon Labs zw_programmer_path: "/usr/sbin/zw_programmer", # ..other options ] {Grizzly, grizzly_opts} ``` ### Changed - removed:on_readyGrizzly option ### Added - Z-Wave firmware updates on Grizzly start (@jfcloutier) - Ability to get the Z-Wave chip version information (@jfcloutier) - AddGrizzly.StatusReporterbehaviour ## [v1.0.1] - 2022-02-28 ### Fixed - Ignore extra bytes reported in association group list by some devices (@jfcloutier) - Decode0x00..0x063as:onin Basic command class to align with Z-Wave specification (@jfcloutier) ## [v1.0.0] - 2021-12-20 This release bumps Grizzly to v1.0.0. Grizzly has been used for many years now and has helped a product pass Z-Wave certification. Most the work that gone into Grizzly for the last little while has been minor changes and bug fixes, but core API has remained stable. Thank you to everyone who has contributed over the years! ## [v0.22.7] - 2021-12-2 ### Fixed - Unhandled errors when trying to firmware upgrade (@jfcloutier) - Unhandled errors when trying to get failed node list (@jfcloutier) ## [v0.22.6] - 2021-11-29 ### Added -Grizzly.ZWave.CommandClasses.BarrierOperator(@jfcloutier) -Grizzly.ZWave.Commands.BarrierOperatorGet(@jfcloutier) -Grizzly.ZWave.Commands.BarrierOperatorReport(@jfcloutier) -Grizzly.ZWave.Commands.BarrierOperatorSet(@jfcloutier) -Grizzly.ZWave.Commands.BarrierOperatorSignalGet(@jfcloutier) -Grizzly.ZWave.Commands.BarrierOperatorSignalReport(@jfcloutier) -Grizzly.ZWave.Commands.BarrierOperatorSignalSet(@jfcloutier) -Grizzly.ZWave.Commands.BarrierOperatorSignalSupportedGet(@jfcloutier) -Grizzly.ZWave.Commands.BarrierOperatorSignalSupportedReport(@jfcloutier) ## [v0.22.5] - 2021-11-22 ### Added -Grizzly.ZWave.Commands.FailedNodeListGet(@jfcloutier) -Grizzly.Network.report_failed_node_ids/0(@jfcloutier) ## [v0.22.4] - 2021-11-16 ### Added -Grizzly.ZWave.Commands.ThermostatSetpointSupportedGet(@bjyoungblood) -Grizzly.ZWave.Commands.ThermostatSetpointSupportedReport(@bjyoungblood) -Grizzly.ZWave.Commands.ThermostatModeSupportedGet(@bjyoungblood) -Grizzly.ZWave.Commands.ThermostatModeSupportedReport(@bjyoungblood) - Add how to heal Z-Wave network to cookbook ### Fixes - No longer hard crashs on Z/IP Packets that don't follow Z-Wave spec - Fix crash when zipgateway's mailbox queue is full when trying to send command to a sleeping device ## [v0.22.3] - 2021-10-22 ### Fixes - Make CentralSceneSupportedReport more forgiving ## [v0.22.2] - 2021-10-12 ### Fixes - Incorrect parsing of:motiontype from a SensorBinaryReport ## [v0.22.1] - 2021-10-4 ### Added - Support version 3Grizzly.ZWave.Commands.S2ResynchronizationEventcommand (Z-Wave LR) ### Fixes -Grizzly.ZWave.Commands.FailedNodeListReportcommand not able to parse empty extended node id list ## [v0.22.0] - 2021-10-01 This release brings Grizzly up to speed to support command classes that have been updated to support extended node ids. This allows Grizzly to support zipgateway versions that have Z-Wave Long Range support. That is zipgateway>= v7.15. ## Changed - RemovedGrizzly.ZWave.Commands.NodeAddStatus.status()type - Now isGrizzly.ZWave.CommandClasses.NetworkManagementInclusion.node_add_status()- Changed return type ofGrizzly.ZWave.CommandClasses.ThermostatSetpoint.decode_type/1function fromtoGrizzly.ZWave.CommandClasses.ThermostatSetpoint.type()### Added - Support version 4Grizzly.ZWave.Commands.NodeListReportcommand (Z-Wave LR) - Support version 4Grizzly.ZWave.Commands.NodeRemoveStatuscommand (Z-Wave LR) - Support version 4Grizzly.ZWave.Commands.FailedNodeListReportcommand (Z-Wave LR) - Support version 4Grizzly.ZWave.Commands.FailedNodeRemovecommand (Z-Wave LR) - Support version 4Grizzly.ZWave.Commands.FailedNodeRemoveStatuscommand (Z-Wave LR) - Support version 4Grizzly.ZWave.Commands.NodeInfoCachedGetcommand (Z-Wave LR) - Support version 4Grizzly.ZWave.Commands.RssiReportcommand (Z-Wave LR) -Grizzly.ZWave.Commands.ZWaveLongRangeChannelGetcommand -Grizzly.ZWave.Commands.ZWaveLongRangeChannelReportcommand -Grizzly.ZWave.Commands.ZWaveLongRangeChannelSetcommand -Grizzly.ZWave.Commands.ExtendedNodeAddStatuscommand -Grizzly.ZWave.Commands.NetworkManagementMultiChannelEndPointGetcommand -Grizzly.ZWave.Commands.NetworkManagementMultiChannelEndPointReportcommand -Grizzly.ZWave.Commands.NetworkManagementMultiChannelCapabilityGetcommand -Grizzly.ZWave.Commands.NetworkManagementMultiChannelCapabilityReportcommand -Grizzly.Network.add_long_range_device/2function -Grizzly.ZWave.CommandClasses.NetworkManagementInclusion.parse_node_add_status/1function -Grizzly.ZWave.CommandClasses.NetworkManagementInclusion.parse_node_info/1function -Grizzly.ZWave.CommandClasses.NetworkManagementInclusion.node_add_status()type -Grizzly.ZWave.CommandClasses.NetworkManagementInclusion.extended_node_info_report()type -Grizzly.ZWave.CommandClasses.NetworkManagementInclusion.node_info_report()type -Grizzly.ZWave.CommandClasses.NetworkManagementInclusion.tagged_command_classes()type -Grizzly.ZWave.Command.encode_params/2optional callback - Support parsing header new IME report stats from version 5 of ZIP command class - The atom:natoGrizzly.ZWave.CommandClasses.ThermostatSetpoint.type()type ### Fixed - Parsing thermostat setpoint types that are considered NA by the specification - Version report command parsing for zipgateway >= 7.14 ## [v0.21.1] - 2021-9-21 ### Fixed - Transmission stats - Ensure:rssi_4barsand:rssi_dbmaccurately calculate no signal when:rssi_hopsare nil ## [v0.21.0] - 2021-9-20 ### Added - Transmission stats - Added:rssi_4barsand:rssi_dbm### Changed - Transmission stats -:rssiis now:rssi_hopsand has been changed from a tuple to a list -:last_working_routeand:transmission_speedhave been separated -:last_working_routeis now a list -:route_changedis now a boolean ### Fixed - Fix error when sendingGrizzly.ZWave.Commands.StatisticsGet## [v0.20.2] - 2021-8-11 ### Changed - Turn off TLS warning for connecting withzipgatewayserver ## [v0.20.1] - 2021-7-1 ### Added - Support for ScheduleEntryLock command class -Grizzly.ZWave.CommandClasses.ScheduleEntryLock-Grizzly.ZWave.Commands.ScheduleEntryLockDailyRepeatingGet-Grizzly.ZWave.Commands.ScheduleEntryLockDailyRepeatingReport-Grizzly.ZWave.Commands.ScheduleEntryLockDailyRepeatingSet-Grizzly.ZWave.Commands.ScheduleEntryLockEnableAllSet-Grizzly.ZWave.Commands.ScheduleEntryLockEnableSet-Grizzly.ZWave.Commands.ScheduleEntryLockTimeOffsetGet-Grizzly.ZWave.Commands.ScheduleEntryLockTimeOffsetReport-Grizzly.ZWave.Commands.ScheduleEntryLockTimeOffsetSet-Grizzly.ZWave.Commands.ScheduleEntryLockWeekDayGet-Grizzly.ZWave.Commands.ScheduleEntryLockWeekDayReport-Grizzly.ZWave.Commands.ScheduleEntryLockWeekDaySet-Grizzly.ZWave.Commands.ScheduleEntryLockYearDayGet-Grizzly.ZWave.Commands.ScheduleEntryLockYearDayReport-Grizzly.ZWave.Commands.ScheduleEntryLockYearDaySet-Grizzly.ZWave.Commands.ScheduleEntryTypeSupportedGet-Grizzly.ZWave.Commands.ScheduleEntryTypeSupportedReport- Support for elixir 1.12-otp-24 Thank you to those who contributed to this release: - Grace Yanagida ### Fixed - Invalid warnings when calling function inGrizzly.SwitchBinary## [v0.20.0] - 2021-6-14 The release breaks the return value ofGrizzly.ZWave.CommandClasses.NodeProvisioning.optional_dsk_to_binary/1from returningnilto returning a DSK filled will0s if an empty binary string is passed into the function. If you have not called this function directly then it is safe to upgrade tov0.20.0. ### Changed - Allow values greater than99to be passed inGrizzly.ZWave.Commands.SwitchMultilevelSet.encode_target_value/1## [v0.19.1] - 2021-4-23 ### Added - Configuration option for setting the RF region - Configuration option for setting power level settings - Allow passing send command options to functions inGrizzly.SwitchBinarymodule Thank you to djantea for testing out the RF configuration changes! ## [v0.19.0] - 2021-4-19 Breaking change in regards to how meta extensions are passed toGrizzly.Network.set_node_provisioning/3. The meta extension were once structs that need to be built and passed to the function, but now they are a keyword list. Please seeGrizzly.ZWave.SmartStart.MetaExtensionmodule for more details on the keyword keys and their values. ## Added - AddedGrizzly.SwitchBinaryhas a higher level helper module to control - binary switches - Added basic support for including Z-Wave LR devices - Added LR command class support for NetworkManagementInclusion - Support version 2 of User Number Report command - Better handling of RSSI channel reports - Better handling of Association Group Name Report command Thank you to those who contributed to this release: - Jean-Francois Cloutier ## [v0.18.3] - 2021-3-11 ### Added -Grizzly.ZWave.DSK.parse_pin/1-Grizzly.ZWave.DSK.to_pin_string/1### Fixed - Ensure that the DSK binary is 128 bits ## [v0.18.2] - 2021-2-18 ### Added - Use [cerlc](https://github.com/mdsebald/cerlc) library forGrizzly.ZWave.CRC- Clean up inspects from tests - Ensurezipgatewayfiles are usable by system utils forzipgateway## [v0.18.1] - 2021-2-10 ### Fixed - Fix up dialyzer types Thank you to those who contributed to this release: - Jean-Francois Cloutier ## [v0.18.0] - 2021-2-10 This release breaks the DSK API and other supporting APIs. If you have not supported S2 inclusions, smart start, or use the DSK API for any reason then it should be safe to upgrade. The break to DSKs is the newGrizzly.ZWave.DSK.t()struct. All inclusion and node provisioning commands now expect aGrizzly.ZWave.DSK.t(). There are two times you will need to get aDSK.t(): 1. User input of a DSK pin (the nicely formatted representation) 1. The binary (<<>>) representation. For the first case you can useGrizzly.ZWave.DSK.parse/1and for the second case you can useGrizzly.ZWave.DSK.new/1. A common use case for DSKs is using the DSK pin (the first 5 digits in the DSK) to do S2 inclusion. This was done by callingGrizzly.Inclusions.set_input_dsk/1. Where the input DSK was annon_neg_integer(). This API has been changed to take aDSK.t(). ### Example ```elixir dsk_pin = "12345" {:ok, dsk} = Grizzly.ZWave.DSK.parse(dsk_pin) Grizzly.Inclusions.set_input_dsk(dsk) ``` This API is more useful for taking user input (which the DSK pin is), parsing it, and passing the DSK to the inclusion process. Also this pushes validation of DSK to theGrizzly.ZWave.DSK.parse/1function. ```elixir dsk_pin = "123456" {:error, :invalid_dsk} = Grizzly.ZWave.DSK.parse(dsk_pin) ``` TheDSK.t()has theString.Charsprotocol implemented so if you want to a pretty representation of the DSK, say for logging or displaying the DSK to the user, you call theto_string/1function on theDSK.t(). Also, seeGrizzly.ZWave.DSK.to_string/2for more details. If you need to access the raw binary form of the DSK you theDSK.t()exposes the:rawfield, so you can access that viadsk.raw. This release also added support S2/SmartStart QR code generation. See theGrizzly.ZWave.QRCodemodule for more details. ### Changed -Grizzly.Inclusions.set_input_dsk/1use to takenon_neg_integer()type as - an argument, but the type has changed toGrizzly.ZWave.DSK.t()-Grizzly.ZWave.CommandClasses.NodeProvisioning.optional_dsk_to_binary/1use to take a string as the DSK input but now it takesGrizzly.ZWave.DSK.t()-Grizzly.ZWave.CommandClasses.NodeProvisioning.optional_binary_to_dsk/1use to take a string as the DSK input but now it takesGrizzly.ZWave.DSK.t()- The following commands had params that took a string for the DSK and now takeGrizzly.ZWave.DSK.t(): -Grizzly.ZWave.Commands.DSKReport-Grizzly.ZWave.Commands.LearnModeSetStatus-Grizzly.ZWave.Commands.NodeAddDSKReport-Grizzly.ZWave.Commands.NodeAddDSKSet-Grizzly.ZWave.Commands.NodeAddStatus-Grizzly.ZWave.Commands.NodeProvisioningDelete-Grizzly.ZWave.Commands.NodeProvisioningGet-Grizzly.ZWave.Commands.NodeProvisioningListIterationReport-Grizzly.ZWave.Commands.NodeProvisioningReport-Grizzly.ZWave.Commands.NodeProvisioningSet-Grizzly.ZWave.Commands.SmartStartJoinStarted### Added - QR code support via theGrizzly.ZWave.QRCodemodule. ## [v0.17.7] - 2021-2-4 ### Fixed - An issue whenzipgatewaysends an invalidFirmwareMDReportpacket causing invalid hardware version errors during firmware updates. Thank you to those who contributed to this release: - Jean-Francois Cloutier ## [v0.17.6] - 2021-2-3 ### Fixed - Grizzly would throw an exception when callingGrizzly.commands_for_command_class/1- Grizzly would always return an empty list of supported commands for a command class when callingGrizzly.commands_for_command_class/1even though Grizzly supports commands for that command class - Fix S2 DSK pin setting when the pin was <256 Thank you to those who contributed to this release: - Jean-Francois Cloutier ## [v0.17.5] - 2021-1-26 ### Added - Docs on operating indicator light ### Fixed - Crash when indicator handler isnil- Math forMeterReportThank you to those who contributed to this release: - Jean-Francois Cloutier ## [v0.17.4] - 2021-1-21 ### Added - Support for handling indicator events via the:indicator_handleroption to theGrizzly.Supervisor. ## [v0.17.3] - 2021-1-14 ### Added -Grizzly.Tracemodule for logging Z/IP packets that are sent from and received by Grizzly. ### Fixed - No match error when trying to encode a node id list ## [v0.17.2] - 2021-1-13 ### Added - Decoding theNodeInfoCacheGetcommand ### Fixed - Incorrect return value forNodeInfoCacheGetwhen decoding the params - Issues around firmware updates andzipgatewayversions >= 7.14.2 Thank you to those who contributed to this release: - Jean-Francois Cloutier ## [v0.17.1] - 2021-1-12 Added supported for usingzipgatewayversions >= 7.14.2. When upgrading from azipgatewayversion less than 7.14.2 you should provide thezgw_eeprom_to_sqliteutility in your system or firmware. The utility should be located in/usr/bin. Grizzly will try to run the utility if we detected it. You can configure the database file and eeprom file via:database_fileand:eeprom_fileoptions for theGrizzly.Supervisor. These are optional and no changes are necessary for how you start Grizzly if you have already been using Grizzly. ### Added - Support forzipgatewayversions >= 7.14.2 -:eeprom_fileto supervisor args (optional) -:database_fileto supervisor args (optional) Thank you to those who contributed to this release: - Frank Hunleth ## [v0.17.0] - 2021-1-8 Breaking change with how Grizzly reports water alarms. If you are listening for water alarm notifications you will need to update from:waterto:water_alarm. This change was made to align better with the Z-Wave specification. ### Added - Complete support for all notification events - Support for version 2 of the Antitheft command class - Support for SceneActuatorConf command class - Support for SceneActivation command class - More support for Erlang 23.2 DSL messages ### Changed -:wateris not:water_alarmnotification ### Fixed - When receiving the supervision command class with a command encapsulated Grizzly was not actually processing the encapsulated command. Thank you to those who contributed to this release: - Jean-Francois Cloutier ## [v0.16.2] - 2020-12-23 ### Added -:list_modeparam for theGrizzly.ZWave.Commands.AssociationGroupInfoReportcommand. ## [v0.16.1] - 2020-12-22 ### Added -Grizzly.ZWave.Commands.S2ResynchronizationEvent### Fixed - Data structure change in the associations file when deleting all associations - WrongMultiChannelAssociationversion number being reported to devices - Ensure ack responses are sent when extra commands are received - Force bind tofd00::aaaa::2sincezipgatewayforces that all acks come from this address - Crash when receiving errors other than timeouts when trying to establish connections tozipgatewayThank you to those who contributed to this release: - Frank Hunleth ## [v0.16.0] - 2020-12-21 This release introduces a breaking change to the naming of the command class get and command class report modules. If you are using those modules directly, you will need to update to the use the new module names. ### Changed -Grizzly.ZWave.Commands.CommandClassGetis nowGrizzly.ZWave.Commands.VersionCommandClassGet- The:namefield for:command_class_getis now:version_command_class_get-Grizzly.ZWave.Commands.CommandClassReportis nowGrizzly.ZWave.Commands.VersionCommandClassReport- The:namefield for:command_class_reportis now:version_command_class_report### Added - Added support for forcing the Z-Wave cache to update when fetching node information. SeeGrizzly.Node.get_info/2for more information. - Support for OTP 23.2 ### Fixed - In some GenServers an exception would cascade ### Changed - Easier to read stack traces when some GenServers crash ## [v0.15.11] - 2020-12-11 ### Added - Support for DoorLock command class version 4 ### Fixed - Querying command class versions for extra commands on the LAN will return the version report correctly now. Thank you to those who contributed to this release: - Jean-Francois Cloutier ## [v0.15.10] - 2020-12-8 ### Added - Support for querying the gateway about the command class versions it supports when querying extra supported command classes. ### Fixed - Spelling error fix for theWakeUpNoMoreInformationcommand name Thank you to those who contributed to this release: - Jean-Francois Cloutier ## [v0.15.9] - 2020-12-4 ### Added - Sending commands directly to the Z-Wave Gateway by passingGrizzly.send_command/4:gatewayas the node id. - How to get DSK for a device in the cookbook docs ### Fixed - Spelling, whitespace and markdown issues in docs Thank you to those who contributed to this release: - Frank Hunleth ## [v0.15.8] - 2020-12-1 ### Added - Support forZwavePlusInfocommand class ### Fixed - No function clause matching error when a connection closes - Missing support for:undefinedindicator Thank you to those who contributed to this release: - Jean-Francois Cloutier ## [v0.15.7] - 2020-11-30 ### Added - AddGrizzly.send_binary/2### Fixed - Error when handling older Z-Wave devices that use CRC16 checksums over any security schema - Internal typo Thank you to those who contributed to this release: - Jean-Francois Cloutier ## [v0.15.6] - 2020-11-19 ### Added - Add support forNetworkUpdateRequestcommand - AddGrizzly.Network.request_network_update/0### Changed - Drop support for Elixir 1.8 and 1.9 Thank you to those who contributed to this release: - Jean-Francois Cloutier ## [v0.15.5] - 2020-11-12 ### Added - Support multi-channel associations in the unsolicited destination ### Fixed - Add the:aggregated_endpointsparams to theMultiChannelEndpointReportThank you to those who contributed to this release: - Jean-Francois Cloutier ## [v0.15.4] - 2020-11-5 ### Added - Network management installation and maintenance command class - Clock command class - Unsolicited server support for the extra command classes: - Association group command class list - Association group name get - Association group info get - Device reset locally notification ### Changed - When a supervision get command is received in the unsolicited destination we send the supervision report for that command back to the sender. - Dev deps updates - Code clean up Thank you to those who contributed to this release: - Jean-Francois Cloutier ## [v0.15.3] - 2020-10-27 ### Fixed - Documentation fixes - Internal firmware update runner bug ### Changed - Updates in internal association persistence Thank you to those who contributed to this release: - Jean-Francois Cloutier ## [v0.15.2] - 2020-10-23 ### Added - Support for theunknown_eventnotification event for theaccess_controlnotification type ### Fixed - SupportSupervisionGetcommand for notifications. - Tried to send:ack_responsevia unsolicited server which the unsolicited server should not be sending anything directly. - Fix typo in code Thank you to those who contributed to this release: - Jean-Francois Cloutier ## [v0.15.1] - 2020-10-09 ### Added - Support for getting association grouping report via the Z-Wave PAN - Support for setting associations via the Z-Wave PAN - Support for removing associations via the Z-Wave PAN - Support for getting specific associations via the Z-Wave PAN - Added option toGrizzly.Supervisorfor where to store data used by the - unsolicited server for support of extra command classes ### Changed - When getting the associations via the Z-Wave PAN, Grizzly will now look at the stored data and respond accordingly. ### Fixed -Grizzly.ZWave.Commands.SwitchBinaryReportdid not properly encode and decode the version 2 of the switch binary command class ## [v0.15.0] - 2020-10-08 This release does a major overhaul on theGrizzly.Transportbehaviour. If you haven't implemented a custom transport this release should not effect you and you should be able to update with out too many issues, see the "Removed" section of this release to note any other breaking changes. If you have created a custom transport please see the documentation forGrizzly.Transportto see how transports are now implemented. ### Added - How to resetting the controller to the cook book - The:unsolicited_destinationoption to theGrizzly.Supervisor- Support for the association get command via the Z-Wave PAN network - Support proper ack response when a command is delivered through the Z-Wave PAN -Grizzly.Transports.UDP- This is experimental and is subject to change. -Grizzly.ZWave.CommandClasses.CRC16Encap-Grizzly.ZWave.Commands.CRC16Encap-Grizzly.ZWave.CommandClasses.Powerlevel-Grizzly.ZWave.Commands.PowerlevelGet-Grizzly.ZWave.Commands.PowerlevelReport-Grizzly.ZWave.Commands.PowerlevelSet-Grizzly.ZWave.Commands.PowerlevelTestNodeGet-Grizzly.ZWave.Commands.PowerlevelTestNodeReport-Grizzly.ZWave.Commands.PowerlevelTestNodeSet### Changed - Refactored theGrizzly.Transportbehaviour - please see documentation to see how to use the behaviour now. ### Removed -Grizzly.Node.get_node_info/1### Fixed -MultiChannelAssociationGetcommand name fix - Documentation - Command class fixes for theGrizzly.ZWave.CommandClasses.TimeThank you to those who contributed to this release: - Jean-Francois Cloutier - Jon Wood ## [v0.14.8] - 2020-09-29 ### Added - Support for power management notifications ## [v0.14.7] - 2020-09-25 ### Added - AddedGrizzly.ZWave.Commands.FailedNodeListReportcommand Thank you to those who contributed to this release: - Jean-Francois Cloutier ## [v0.14.6] - 2020-09-18 ### Added - Cookbook documentation for common uses of Grizzly ### Changed - Reduced the amount of logging ## [v0.14.5] - 2020-09-02 ### Fixed - Commands with aggregated reports did not aggregate the results as expected - Commands with aggregated reports would crash if that device was also handling another command due to the aggregate handler assuming that only one command was being processed at one time ## [v0.14.4] - 2020-09-01 ### Added - Full support forThermostatFanModemode types Thank you to those who contributed to this release: - Jean-Francois Cloutier ## [v0.14.3] - 2020-08-31 ### Fixed - Fix the start order of the connection supervisor and Z-Wave ready checker to ensure the supervisor process is alive before trying to test the connection ## v0.14.2 Added -Grizzly.ZWave.CRCmodule for CRC functions related to the Z-Wave protocol Removed -crcdependency ## v0.14.1 Enhancements - Supportzipgateway7.14.01 - AddGrizzly.ZWave.CommandClasses.CentralScene- AddGrizzly.ZWave.Commands.CentralSceneConfigurationGet- AddGrizzly.ZWave.Commands.CentralSceneConfigurationSet- AddGrizzly.ZWave.Commands.CentralSceneConfigurationReport- AddGrizzly.ZWave.Commands.CentralSceneNotification- AddGrizzly.ZWave.Commands.CentralSceneSupportedGet- AddGrizzly.ZWave.Commands.CentralSceneSupportedReportThank you to those who contributed to this release: - Jean-Francois Cloutier ## v0.14.0 This breaking change has to do with how Grizzly is started. It is no longer an application. Grizzly exposes theGrizzly.Supervisormodule for a consuming application to add to its supervision tree. All other APIs are backwards capable. See the [upgrade guide](https://gist.github.com/mattludwigs/bb312906b1bf85a021080c45d1562f2b) for more specifics on how to upgrade. Breaking Changes - Grizzly is not an OTP application anymore and will need to be started manually via the newGrizzly.Supervisormodule - All application config/mix config options are not used - Removed theGrizzly.Runtimemodule Enhancements - AddGrizzly.Supervisormodule - AddGrizzly.ZWave.CommandClasses.Indicator- AddGrizzly.ZWave.Commands.IndicatorGet- AddGrizzly.ZWave.Commands.IndicatorSet- AddGrizzly.ZWave.Commands.IndicatorReport- AddGrizzly.ZWave.Commands.IndicatorSupportedGet- AddGrizzly.ZWave.Commands.IndicatorSupportedReport- AddGrizzly.ZWave.CommandClasses.Antitheft- AddGrizzly.ZWave.Commands.AntitheftGet- AddGrizzly.ZWave.Commands.AntitheftReport- AddGrizzly.ZWave.CommandClasses.AntitheftUnlock- AddGrizzly.ZWave.Commands.AntitheftUnlockSet- AddGrizzly.ZWave.Commands.AntitheftUnlockGet- AddGrizzly.ZWave.Commands.AntitheftUnlockReport- AddGrizzly.ZWave.Commands.ConfigurationBulkGet- AddGrizzly.ZWave.Commands.ConfigurationBulkSet- AddGrizzly.ZWave.Commands.ConfigurationBulkReport- AddGrizzly.ZWave.Commands.ConfigurationPropertiesGet- AddGrizzly.ZWave.CommandClasses.ApplicationStatus- AddGrizzly.ZWave.Commands.ApplicationBusy- AddGrizzly.ZWave.Commands.ApplicationRejectedRequestThank you to those who contributed to this release: - Jean-Francois Cloutier ## v0.13.0 This update breaks the mainGrizzly.send_command/4API as Grizzly use to respond with different tuples but now it will return with the newGrizzly.Report.t()data structure. A full guide on the breaking changes and what needs to be updated can be found [here](https://gist.github.com/mattludwigs/323cbdbfc32075745cd3fdae7163c930). This change allows us to gather more information about a response from Grizzly. For example, with this change you can get transmission stats about network properties when sending a command now: ```elixir {:ok, report} = Grizzly.send_command(node_id, command, command_args, transmission_stats: true) report.transmission_stats ``` See theGrizzly.Reportmodule for full details. Enhancements - AddGrizzly.Report- Add getting transmission stats for sent commands - Docs and type spec updates ## v0.12.3 Fixes - Handle multichannel commands that are not appropriately encapsulated Thank you to those who contributed to this release: - Jean-Francois Cloutier ## v0.12.2 Enhancements - AddGrizzly.ZWave.CommandClasses.Hail- AddGrizzly.ZWave.Commands.Hail- Support updated Z-Wave spec command params forGrizzly.ZWave.Commands.DoorLockOperationReport## v0.12.1 Enhancements - AddGrizzly.ZWave.Commands.MultiChannelAggregatedMemberGet- AddGrizzly.ZWave.Commands.MultiChannelAggregatedMemberReport- AddGrizzly.ZWave.Commands.MultiChannelCapabilityGet- AddGrizzly.ZWave.Commands.MultiChannelCommandEncapsulation- AddGrizzly.ZWave.Commands.MultiChannelEndpointFind- AddGrizzly.ZWave.Commands.MultiChannelEndpointFindReport- AddGrizzly.ZWave.CommandClasses.MultiCommand- AddGrizzly.ZWave.Commands.MultiCommandEncapsulation- AddGrizzly.ZWave.CommandClasses.Time- AddGrizzly.ZWave.Commands.DateGet- AddGrizzly.ZWave.Commands.DateReport- AddGrizzly.ZWave.Commands.TimeGet- AddGrizzly.ZWave.Commands.TimeReport- AddGrizzly.ZWave.Commands.TimeOffsetGet- AddGrizzly.ZWave.Commands.TimeOffsetReport- AddGrizzly.ZWave.Commands.TimeOffsetSet- AddGrizzly.ZWave.CommandsClasses.TimeParameters- AddGrizzly.ZWave.Commands.TimeParametersGet- AddGrizzly.ZWave.Commands.TimeParametersReport- AddGrizzly.ZWave.Commands.TimeParametersSet- Documentation updates Fixes - Some devices send alarm reports that do not match the specification in a minor way. So, we allow for parsing of these reports now. - Fixed internal command class name to module implementation mapping issue for:switch_multilevel_setand:switch_multilevel_getcommands. Thank you to those who contributed to this release: - Jean-Francois Cloutier ## v0.12.0 There is a small breaking change that will only effect you if you hard have:water_leak_detected_known_locationand:water_leak_dropped_known_locationhard coded into your application for any reason. These are notifications about water leaks, and so if you have not directly tried to match on or handle logic about water leak notifications then this breaking change should not effect you. From a high level this release provides updates to Z-Wave notifications in terms of command support and package parsing, extra tooling for better introspection, a handful of new commands and command classes, and helpful configuration items. Enhancements - AddGrizzly.ZWave.Commands.ApplicationNodeInfoReport- AddGrizzly.ZWave.CommandClass.NodeNaming- AddGrizzly.ZWave.Commands.NodeLocationGet- AddGrizzly.ZWave.Commands.NodeLocationReport- AddGrizzly.ZWave.Commands.NodeLocationSet- AddGrizzly.ZWave.Commands.NodeNameGet- AddGrizzly.ZWave.Commands.NodeNameReport- AddGrizzly.ZWave.Commands.NodeNameSet- AddGrizzly.ZWave.Commands.AlarmGet- AddGrizzly.ZWave.Commands.AlarmSet- AddGrizzly.ZWave.Commands.AlarmEventSupportedGet- AddGrizzly.ZWave.Commands.AlarmEventSupportedReport- AddGrizzly.ZWave.Commands.AlarmTypeSupportedGet- AddGrizzly.ZWave.Commands.AlarmTypeSupportedReport- AddGrizzly.ZWave.Commands.AssociationGroupingsGet- AddGrizzly.ZWave.Commands.AssociationGroupingsReport- AddGrizzly.ZWave.Commands.AssociationRemove- AddGrizzly.ZWave.Commands.AssociationReport- AddGrizzly.ZWave.Commands.AssociationSpecificGroupingsGet- AddGrizzly.ZWave.Commands.AssociationSpecificGroupingsReport- AddGrizzly.ZWave.CommandClasses.MultiChannelAssociation- AddGrizzly.ZWave.Commands.MultiChannelAssociationGroupingsGet- AddGrizzly.ZWave.Commands.MultiChannelAssociationGroupingsReport- AddGrizzly.ZWave.Commands.MultiChannelAssociationRemove- AddGrizzly.ZWave.Commands.MultiChannelAssociationReport- AddGrizzly.ZWave.Commands.MultiChannelAssociationSet- AddGrizzly.ZWave.CommandClass.DeviceResetLocally- AddGrizzly.ZWave.Commands.DeviceResetLocallyNotification- AddGrizzly.ZWave.Commands.LearnModeSet- AddGrizzly.ZWave.Commands.LearnModeSetStatus- AddGrizzly.Inclusions.learn_mode/1- AddGrizzly.Inclusions.learn_mode_stop/0- Support version 8 of theGrizzly.ZWave.Commands.AlarmReport- Support parsing naming and location parameters from Z-Wave notifications - Addmix zipgateway.cfgto print out the zipgateway config that Grizzly is configured to use. - AddGrizzly.list_commands/0to list all support Z-Wave commands in Grizzly. - AddGrizzly.commands_for_command_class/1for listing the Z-Wave commands support by Grizzly for a particular command class. - Add:handlersto:grizzlyconfiguration options for firmware update and inclusion handlers. - Documentation updates Fixes - Parsing the wrong byte for into the wrong notification type - Invalid type spec forGrizzly.ZWave.Security.failed_type_from_byte/1Thank you to those who contributed to this release: - Jean-Francois Cloutier ## v0.11.0 Grizzly now supports parsing alarm/notification parameters as a keyword list of parameters. This change is breaking because the event parameters use to be the raw binary we received from the Z-Wave network and now it is a keyword list. We only support lock and keypad event parameters currently, but this puts into place the start of being able to support event parameters. Enhancements - Support parsing event parameters for lock and keypad operations Thank you to those who contributed to this release: - Jean-Francois Cloutier ## v0.10.3 Enhancements - Addhandle_timeout/2to theGrizzly.InclusionHandlerbehaviour. This allows for handling when an inclusion process timesout. - AddGrizzly.Inclusions.stop/0force stop any type of inclusion process. - AddGrizzly.FirmwareUpdatesmodule for updating the Z-Wave firmware on Z-Wave hardware Fixes - not parsing command classes correctly onGrizzly.ZWave.Commands.NodeAddStatus- Not stopping an inclusion process correctly when callingGrizzly.Inclusions.add_node_stop/0Thank you to those who contributed to this release: - Jean-Francois Cloutier ## v.0.10.2 Enhancements - AddGrizzly.ZWave.Commands.FailedNodeRemove- AddGrizzly.ZWave.Commands.FailedNodeRemoveStatusFixes - Sensor types returned from the support sensors report - Broken link in docs Thank you to those who contributed to this release: - Jean-Francois Cloutier ## v.0.10.1 Enhancements - AddGrizzly.ZWave.Commands.ConfigurationGet- AddGrizzly.ZWave.Commands.ConfigurationReportThank you to those who contributed to this release: - Jean-Francois Cloutier ## v0.10.0 Removed the parameter:secure_command_classesfromGrizzly.ZWave.Command.NodeInfoCacheReport. Also updated the param:command_classesto be a keyword list of the various command classes that the node can have. The fields in the keyword list are: -:non_secure_supported-:non_secure_controlled-:secure_supported-:secure_controlledIf you are using:secure_command_classesfor checking if the device is securely added you can update like this: ```elixir {:ok, node_info} = Grizzly.Node.get_info(10) Keyword.get(Grizzly.ZWave.Command.param!(node_info, :command_classes), :secure_controlled) ``` Enhancements - AddGrizzly.ZWave.Commands.AssociationGroupCommandListGet- AddGrizzly.ZWave.Commands.AssociationGroupCommandListReport- AddGrizzly.ZWave.Commands.AssociationGroupInfoGet- AddGrizzly.ZWave.Commands.AssociationGroupInfoReport- AddGrizzly.ZWave.Commands.AssociationGroupNameGet- AddGrizzly.ZWave.Commands.AssociationGroupNameReport- AddGrizzly.ZWave.Commands.MultiChannelEndpointGet- AddGrizzly.ZWave.Commands.MultiChannelEndpointReportFixes - Internal command class name discrepancies Thank you to those who contributed to this release: - Jean-Francois Cloutier ## v0.9.0 The officialv0.9.0release! If you trying to upgrade fromv0.8.xplease see [Grizzly v0.8.0 -> v0.9.0](https://gist.github.com/mattludwigs/b172eaae0831f71df5ab53e2d6066081) guide and follow the Changelog from the initialv0.9.0-rc.0release. Changes from the lastrcare: Enhancements - Support Erlang 23.0 with Elixir 1.10 - Dep updates and tooling enhancements Fixes - miss spellings of command names Thank you to those who contributed to this release: - Jean-Francois Cloutier ## v0.9.0-rc.4 Enhancements - AddGrizzly.ZWave.Commands.FirmwareMDGet- AddGrizzly.ZWave.Commands.FirmwareUpdateMDRequestGet- AddGrizzly.ZWave.Commands.FirmwareUpdateMDRequestReport- AddGrizzly.ZWave.Commands.FirmwareUpdateMDStatusReport- AddGrizzly.ZWave.Commands.FirmwareUpdateMDReport- AddGrizzly.ZWave.Commands.FirmwareUpdateActivationSet- AddGrizzly.ZWave.Commands.FirmwareUpdateActivationReport- Remove some dead code Fixes - When resetting the controller we were not closing the connections to the nodes. This caused some error logging inzipgatewayand also left open unused resources. This could cause problems later when reconnecting devices to resources that were already in the system. Thank you to those who contributed to this release: - Jean-Francois Cloutier ## v0.9.0-rc.3 Enhancements - Some Z-Wave devices report the wrong value for the switch multilevel report so we added support for those values. Fixes - When two processes quickly sent the same command to the same device only one process would receive the response Thank you to those who contributed to this release: - Jean-Francois Cloutier ## v0.9.0-rc.2 Deprecated -Grizzly.Node.get_node_info/1- useGrizzly.Node.get_info/1instead Added -Grizzly.Node.get_info/1-Grizzly.ZWave.CommandClasses.Supervision-Grizzly.ZWave.Commands.SupervisionGet-Grizzly.ZWave.Commands.SupervisionReport-Grizzly.ZWave.CommandClasses.SensorBinary-Grizzly.ZWave.Commands.SensorBinaryGet-Grizzly.ZWave.Commands.SensorBinaryReportEnhancements - Support forDoorLockOperationReport>= V3 parsing Fixes - Bad parsing ofNodAddStatus:failedvalue Thank you to those who contributed to this release: - Jean-Francois Cloutier ## v0.9.0-rc.1 Breaking Changes -Grizzly.ZWave.IconTypesremovedicon_typefrom the atom values of the icon name. -Grizzly.ZWave.DeciveTypes.icon_name()->Grizzly.ZWave.DeviceTypes.name()-Grizzly.ZWave.DeciveTypes.icon_integer()->Grizzly.ZWave.DeviceTypes.value()Enhancements - Doc updates - Internal code quality - Deps updates - Better types around DSKs - CI support for elixir versions 1.8, 1.9, and 1.10 - Support all versions of the meter report - Support a low battery report ## v0.9.0-rc.0 For more detailed guide to the breaking changes and how to upgrade please see our [Grizzly v0.8.0 -> v0.9.0](https://gist.github.com/mattludwigs/b172eaae0831f71df5ab53e2d6066081) guide. This release presents a simpler API, faster boot time, more robustness in Z-Wave communication, and resolves all open issues on Grizzly that were reported as bugs. ### Removed APIs -Grizzly.Nodestruct -Grizzly.Connmodule -Grizzly.Notificationsmodule -Grizzly.Packetmodule -Grizzly.close_connection-Grizzly.command_class_versions_known?-Grizzly.update_command_class_versions-Grizzly.start_learn_mode-Grizzly.get_command_class_version-Grizzly.has_command_class-Grizzly.connected?-Grizzly.has_command_class_names-Grizzly.config-Grizzly.Network.busy?-Grizzly.Network.ready?-Grizzly.Network.get_state-Grizzly.Network.set_state-Grizzly.Network.get_node-Grizzly.Node.new-Grizzly.Node.update-Grizzly.Node.put_ip-Grizzly.Node.get_ip-Grizzly.Node.connect-Grizzly.Node.disconnect-Grizzly.Node.make_config-Grizzly.Node.has_command_class?-Grizzly.Node.connected?-Grizzly.Node.command_class_names-Grizzly.Node.update_command_class_versions-Grizzly.Node.get_command_class_version-Grizzly.Node.command_class_version_known?-Grizzly.Node.update_command_class-Grizzly.Node.put_association-Grizzly.Node.get_association_list-Grizzly.Node.configure_association-Grizzly.Node.get_network_information-Grizzly.Node.initialize_command_versions### Moved APIs -Grizzly.reset_controller->Grizzly.Network.reset_controller-Grizzly.get_nodes->Grizzly.Network.get_node_ids-Grizzly.get_node_info->Grizzly.Node.get_node_info-Grizzly.Notifications.subscribe->Grizzly.subscribe_commandandGrizzly.subscribe_commands-Grizzly.Notifications.unsubscribe->Grizzly.unsubscribe-Grizzly.add_node->Grizzly.Inclusions.add_node-Grizzly.remove_node->Grizzly.Inclusions.remove_node-Grizzly.add_node_stop->Grizzly.Inclusions.add_node_stop-Grizzly.remove_node_stop->Grizzly.Inclusions.remove_node_stop-Grizzly.Client->Grizzly.Transport-Grizzly.Security->Grizzly.ZWave.Security-Grizzly.DSK->Grizzly.ZWave.DSK-Grizzly.Node.add_lifeline_group->Grizzly.Node.set_lifeline_associationWe moved all the commands and command classes to be under the theGrizzly.ZWavemodule namespace and refactored the command behaviour. ###Grizzly.send_commandChanges The main API function to Grizzly has changed in that it only takes a node id, command name (atom), command args, and command options. Also it no longer returns a plain map when there is data to report back from a Z-Wave node but it will return}. Please seeGrizzlyandGrizzly.ZWave.Commanddocs for more information. ### Connections Grizzly uses thezipgatewaybinary under the hood. The binary has its own networking stack and provides a DTLS server for us to connect to. Prior to Grizzly v0.9.0 we greatly exposed that implementation detail. However, starting in Grizzly v0.9.0 we have hidden that implementation detail away and all connection functionally is handle by Grizzly internally. This leaves the consumer of Grizzly to just work about sending and receiving commands. If you are using%Grizzly.Conn{}directly this is no longer available and you should upgrade to just using the node id you were sending commands to. ### When Grizzly is Ready We use to send a notification to let the consumer to know when Grizzly is read. Staring in v0.9.0 the consumer needs to configure Grizzly's runtime with theon_readymodule, function, arg callback. ```elixir config :grizzly, runtime: [ on_ready: {MyApp, :some_function, []} ] ``` SeeGrizzly.Runtimefor more details ### Inclusion Handler Behaviour Adding and removing a Z-Wave node can be a very interactive process that involves users being able to talk to the including controller and device. The way Grizzly < v0.9.0 did it wasn't vary useful or robust. By adding the the inclusion handler behaviour we allow the consumer to have full control over the inclusion process, enabling closer to Z-Wave specification inclusion process. SeeGrizzly.InclusionHandlerandGrizzly.Inclusionsfor more information. ### Command Handler Behaviour If you need to handle a Z-Wave command lifecycle differently than the default Grizzly implementation you can make your own handler and pass it intoGrizzly.send_commandas an option: ```elixir Grizzly.send_command(node_id, :switch_binary_set, [value: :on], handler: MyHandler) ``` SeeGrizzly.CommandHandlerfor more information. ### Supporting Commands At the point of therc.0release are not fully 100% supporting the same commands as in < v0.8.8, but we are really close. The commands that we haven't pulled over are not critical to average Z-Wave device control. We will work to get all the commands back into place. Thank you to Jean-Francois Cloutier for contributing so much to this release. ## v0.8.8 - Enhancements - Make Z-Wave versions standard version formatting - Fixes - Paring the FirmwareMD report for version 5 - Fix spec for queued commands ## v0.8.7 - Enhancements - SupportFIRMWARE_UPDATE_MDmeta data report command v5 ## v0.8.6 - Fixes - duplicate fields on theGrizzly.Nodestruct ## v0.8.5 - Fixes - various spelling and documentation fixes - dialzyer fixes ## v0.8.4 - Fixes - Handle when there are no nodes in the node provisioning list when requesting all the DSKs. ## 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 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: 1. All SmartStart meta extensions were moved fromGrizzly.CommandClass.NodeProvisioningnamespace into theGrizzly.SmartStart.MetaExtensionnamespace. 2. Upon finalizing the meta extension behaviour and API we made changes to how previously supported meta extensions worked. Namely, we added anew/1callback that does parameter validation, and returns. This breaks the pervious behaviour ofto_binary/1functions in perviously implemented meta extensions. - Enhancements - Full support for SmartStart meta extensions - Addmeta_extensionsfield toGrizzly.CommandClass.NodeProvisioningcommands that can handle meta extensions - UpdateGrizzly.Conn.Server.Configdocs - Fixes - Invalid keep alive (heart beat) interval - Set correct constraints onTimecommand 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 with out 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. ```elixir 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 useRingLoggerto readzipgatewaylogs which at the start will log if the controller supports SmartStart. ### Breaking Changes Breaking change to the return value of sendingGrizzly.CommandClass.ZipNd.InvNodeSolicitation. When using that functionsend_commandwould return}but now it returns}. - Enhancements - SmartStart support through theNodeProvisioningcommand class - Addedhome_idfield toGrizzly.Node.t()- Support fetchinghome_idof the Z-Wave nodes when fetching Z-Wave information about the node ## v0.6.6 - Fixes - Application start failure when providing the correct data structure to thezipgateway_cfgconfiguration field ## v0.6.5 - Enhancements - SupportGetDSKcommand - SupportFailedNodeRemovecommand - Allowzipgateway_pathconfiguration - Generate thezipgateway.cfgto allow device specific information to be passed into thezipgatewayruntime. ## v0.6.4 - Enhancements - Validation of UserCode arguments to help ensure usage of Grizzly follows the Z-Wave specification ## v0.6.3 - Enhancements - Supports AssociationGroupInformation Command Class ## v0.6.2 - Enhancements - Remove the dependence onpidofallowinggrizzlyto work on any nerves device without the need ofbusybox### v0.6.1 - Enhancements - Update commandsIntervalGetandManufacturerSpecificGetto be more consistent - Better handling of invalidManufacturerSpecificinfo received from devices ### v0.6.0 ChangedGrizzly.CommandClass.CommandClassVersiontoGrizzly.CommandClass.Versionand changedGrizzly.ComamndClass.CommandClassVersion.GettoGrizzly.CommandClass.Version.CommandClassGetas these names reflect the Z-Wave specification better. If you only have usedGrizzly.get_command_class_version/2and the related function inGrizzly.Nodemodule this change should not effect you. - Enhancements - Add support for: - MultiChannelAssociation Command Class - WakeUp Command Class NoMoreInformation command - Complete Association Command Class - ZwaveplusInfo Command Class - Version Get Command - Clean up docs - RenamedGrizzly.CommandClass.CommandClassVersiontoGrizzly.CommandClass.Version- RenamedGrizzly.CommandClass.CommandClassVersion.GettoGrizzly.CommandClass.Version.CommandClassGet### v0.5.0 IntroducesGrizzly.Command.EncodeErrorexception and updates encoding and decoding functions to return tagged tuples. We now use these things when trying to send a command viaGrizzly.send_command/3so if you have invalid command arguments we can provide useful error handling with. TheEncodeError.t()implements Elixir's exception behaviour so you can leverage the standard library to work with the exception. Unless you have implemented custom commands or used one of the many command encoders or decodes explicitly this update should not affect you too much. If you have used the encoder/decoders explicitly please see the documentation for the ones you have used to see the updated API. If you have written a command we encourage you to validate the arguments and return theto improve the usability of and robustness your command. The newGrizzly.Command.Encodingmodule provides some useful functionality for validating specs for command arguments. - Enhancements - Provide command argument validation and error handling viaGrizzly.Command.EncodeError.()- Update all the command arg encoder/decoder to use tagged tuples for better handling of invalid command arguments - Introduces newGrizzly.Command.Encodingmodules for helping validate command arugment specifications - Fixes - Crashes when providing invalid command arguments ### v0.4.3 - Enhancements - Support Powerlevel command class - Doc clean up -Grizzly.send_command/2andGrizzly.send_command/3can be passed a node id instead of a node. ### v0.4.2 - Enhancements - Support NoOperation command class ### v0.4.1 - Enhancements - Add support for Network Management Installation Maintenance - Updates to docs and examples ### v0.4.0 Changed how configuration works. Grizzly now requires the serial port to be configured: ```elixir config :grizzly, serial_port: "/dev/ttyACM0" ``` Also added thepidof_binconfiguration option to allow official Nerves systems to work with some of the Grizzly scripts the call that utility by using the [busybox](https://hex.pm/packages/busybox) package and pointing to the executable ofpidofthat is compiled withbusybox. If you are using a custom system you can add that utility to the busybox config, and not need to use this configuration option. ```elixir config :grizzly, pidof_bin: "/srv/erlang/lib/busybox-0.1.2/priv/bin/pidof" ``` Double check the version of busybox you are using and make sure that version matches the version in thepidof_binpath. Changedrun_grizzly_bintorun_zipgateway_bin. ## v0.3.1 - Enhancements - Implement multilevel sensor command to get supported sensor types ## v0.3.0 The big change here is removing the in memory cache for devices on the network. Most common use cases will be for a consuming application to hold on to the network device information and apply some costume logic to now that is managed. Also, we would have to keep both the external and internal cache in sync, which is really hard and was creating an odd event based system, which also lends itself to complexity. ### Breaking ChangesGrizzly.list_nodes()->Grizzly.get_nodes()This is mostly because before we were listing nodes from a cache, and now we are getting nodes from the Z-Wave network. Also withget_nodeswe don't automatically connect to the nodes. So getting and connecting to all nodes on the Z-Wave network might look something like this: ```elixir def get_and_connect() do case Grizzly.get_nodes() do {:ok, nodes} -> Enum.map(nodes, &Grizzly.Node.connect/1) error -> error end end ```Grizzly.update_command_class_versions/2->Grizzly.update_command_class_versions/1Before we would pass if the update would be async or not after reviewing how this gets used it made sense to always do it sync. Also it returns aNode.t()now with the command classes updated with the version. This is the same change found inGrizzly.Node.update_command_class_versionsGrizzly.command_class_version/3->Grizzly.get_command_class_version/2Removed theuse_cacheparam as there is no longer a cache. Same change found inGrizzly.Node.get_command_class_version- Enhancements - SupportGrizzly.CommandClass.Timecommand class - SupportGrizzly.CommandClass.TimeParametersGET and SET commands - SupportGrizzly.CommandClass.ScheduleEntryLockcommand class -Grizzly.Notifications.subscribe_all/1- subscribe to many notifications at once -Grizzly.CommandClass.name/1- get the name of the command class -Grizzly.CommandClass.version/1- get the version of the command class -Grizzly.Network.get_nodes/0- get the nodes on the network -Grizzly.Network.get_node/1- get a node by node id from the network -Grizzly.Network.get_node_info/1- get node information about a node via node id -Grizzly.Node.get_ip/1- can now take either aNode.t()or a node id - Updates - Docs and type clean up - Fixes - Timeout when getting command class versions ## v0.2.1 - Updates - Support for the time command class - Fixes - Time-boxing of getting a command class version ## v0.2.0 - Fixes - Logging with oldZipGatewaylabel is nowGrizzly- Fix queued API from{ZipGateway, :queued_response, ref, response}to{Grizzly, :queued_response, ref, response}- Fix timeout error when waiting for DTLS server from thezipgateway` side [v6.8.3]: https://github.com/smartrent/grizzly/compare/v6.8.0..v6.8.3 [v6.8.2]: https://github.com/smartrent/grizzly/compare/v6.8.0..v6.8.2 [v6.8.1]: https://github.com/smartrent/grizzly/compare/v6.8.0..v6.8.1 [v6.8.0]: https://github.com/smartrent/grizzly/compare/v6.7.1..v6.8.0 [v6.7.1]: https://github.com/smartrent/grizzly/compare/v6.7.0..v6.7.1 [v6.7.0]: https://github.com/smartrent/grizzly/compare/v6.6.1..v6.7.0 [v6.6.1]: https://github.com/smartrent/grizzly/compare/v6.6.0..v6.6.1 [v6.6.0]: https://github.com/smartrent/grizzly/compare/v6.5.1..v6.6.0 [v6.5.1]: https://github.com/smartrent/grizzly/compare/v6.5.0..v6.5.1 [v6.5.0]: https://github.com/smartrent/grizzly/compare/v6.4.0..v6.5.0 [v6.4.0]: https://github.com/smartrent/grizzly/compare/v6.3.0..v6.4.0 [v6.3.0]: https://github.com/smartrent/grizzly/compare/v6.2.0..v6.3.0 [v6.2.0]: https://github.com/smartrent/grizzly/compare/v6.1.1..v6.2.0 [v6.1.1]: https://github.com/smartrent/grizzly/compare/v6.1.0..v6.1.1 [v6.1.0]: https://github.com/smartrent/grizzly/compare/v6.0.1..v6.1.0 [v6.0.1]: https://github.com/smartrent/grizzly/compare/v6.0.0..v6.0.1 [v6.0.0]: https://github.com/smartrent/grizzly/compare/v5.4.1..v6.0.0 [v5.4.1]: https://github.com/smartrent/grizzly/compare/v5.4.0..v5.4.1 [v5.4.0]: https://github.com/smartrent/grizzly/compare/v5.3.0..v5.4.0 [v5.3.0]: https://github.com/smartrent/grizzly/compare/v5.2.8..v5.3.0 [v5.2.8]: https://github.com/smartrent/grizzly/compare/v5.2.7..v5.2.8 [v5.2.7]: https://github.com/smartrent/grizzly/compare/v5.2.6..v5.2.7 [v5.2.6]: https://github.com/smartrent/grizzly/compare/v5.2.5..v5.2.6 [v5.2.5]: https://github.com/smartrent/grizzly/compare/v5.2.4..v5.2.5 [v5.2.4]: https://github.com/smartrent/grizzly/compare/v5.2.3..v5.2.4 [v5.2.3]: https://github.com/smartrent/grizzly/compare/v5.2.2..v5.2.3 [v5.2.2]: https://github.com/smartrent/grizzly/compare/v5.2.1..v5.2.2 [v5.2.1]: https://github.com/smartrent/grizzly/compare/v5.2.0...v5.2.1 [v5.2.0]: https://github.com/smartrent/grizzly/compare/v5.1.2...v5.2.0 [v5.1.2]: https://github.com/smartrent/grizzly/compare/v5.1.1...v5.1.2 [v5.1.1]: https://github.com/smartrent/grizzly/compare/v5.1.0...v5.1.1 [v5.1.0]: https://github.com/smartrent/grizzly/compare/v5.0.2...v5.1.0 [v5.0.2]: https://github.com/smartrent/grizzly/compare/v5.0.1...v5.0.2 [v5.0.1]: https://github.com/smartrent/grizzly/compare/v5.0.0...v5.0.1 [v5.0.0]: https://github.com/smartrent/grizzly/compare/v4.0.1...v5.0.0 [v4.0.1]: https://github.com/smartrent/grizzly/compare/v4.0.0...v4.0.1 [v4.0.0]: https://github.com/smartrent/grizzly/compare/v3.0.0...v4.0.0 [v3.0.0]: https://github.com/smartrent/grizzly/compare/v2.1.0...v3.0.0 [v2.1.0]: https://github.com/smartrent/grizzly/compare/v2.0.0...v2.1.0 [v2.0.0]: https://github.com/smartrent/grizzly/compare/v1.0.1...v2.0.0 [v1.0.1]: https://github.com/smartrent/grizzly/compare/v1.0.0...v1.0.1 [v1.0.0]: https://github.com/smartrent/grizzly/compare/v0.22.7...v1.0.0 [v0.22.7]: https://github.com/smartrent/grizzly/compare/v0.22.6...v0.22.7 [v0.22.6]: https://github.com/smartrent/grizzly/compare/v0.22.5...v0.22.6 [v0.22.5]: https://github.com/smartrent/grizzly/compare/v0.22.4...v0.22.5 [v0.22.4]: https://github.com/smartrent/grizzly/compare/v0.22.3...v0.22.4 [v0.22.3]: https://github.com/smartrent/grizzly/compare/v0.22.2...v0.22.3 [v0.22.2]: https://github.com/smartrent/grizzly/compare/v0.22.1...v0.22.2 [v0.22.1]: https://github.com/smartrent/grizzly/compare/v0.22.0...v0.22.1 [v0.22.0]: https://github.com/smartrent/grizzly/compare/v0.21.1...v0.22.0 [v0.21.1]: https://github.com/smartrent/grizzly/compare/v0.21.0...v0.21.1 [v0.21.0]: https://github.com/smartrent/grizzly/compare/v0.20.2...v0.21.0 [v0.20.2]: https://github.com/smartrent/grizzly/compare/v0.20.1...v0.20.2 [v0.20.1]: https://github.com/smartrent/grizzly/compare/v0.20.0...v0.20.1 [v0.20.0]: https://github.com/smartrent/grizzly/compare/v0.19.1...v0.20.0 [v0.19.1]: https://github.com/smartrent/grizzly/compare/v0.19.0...v0.19.1 [v0.19.0]: https://github.com/smartrent/grizzly/compare/v0.18.3...v0.19.0 [v0.18.3]: https://github.com/smartrent/grizzly/compare/v0.18.2...v0.18.3 [v0.18.2]: https://github.com/smartrent/grizzly/compare/v0.18.1...v0.18.2 [v0.18.1]: https://github.com/smartrent/grizzly/compare/v0.18.0...v0.18.1 [v0.18.0]: https://github.com/smartrent/grizzly/compare/v0.17.8...v0.18.0 [v0.17.7]: https://github.com/smartrent/grizzly/compare/v0.17.6...v0.17.7 [v0.17.6]: https://github.com/smartrent/grizzly/compare/v0.17.5...v0.17.6 [v0.17.5]: https://github.com/smartrent/grizzly/compare/v0.17.4...v0.17.5 [v0.17.4]: https://github.com/smartrent/grizzly/compare/v0.17.3...v0.17.4 [v0.17.3]: https://github.com/smartrent/grizzly/compare/v0.17.2...v0.17.3 [v0.17.2]: https://github.com/smartrent/grizzly/compare/v0.17.1...v0.17.2 [v0.17.1]: https://github.com/smartrent/grizzly/compare/v0.17.0...v0.17.1 [v0.17.0]: https://github.com/smartrent/grizzly/compare/v0.16.2...v0.17.0 [v0.16.2]: https://github.com/smartrent/grizzly/compare/v0.16.1...v0.16.2 [v0.16.1]: https://github.com/smartrent/grizzly/compare/v0.16.0...v0.16.1 [v0.16.0]: https://github.com/smartrent/grizzly/compare/v0.15.11...v0.16.0 [v0.15.11]: https://github.com/smartrent/grizzly/compare/v0.15.10...v0.15.11 [v0.15.10]: https://github.com/smartrent/grizzly/compare/v0.15.9...v0.15.10 [v0.15.9]: https://github.com/smartrent/grizzly/compare/v0.15.8...v0.15.9 [v0.15.8]: https://github.com/smartrent/grizzly/compare/v0.15.7...v0.15.8 [v0.15.7]: https://github.com/smartrent/grizzly/compare/v0.15.6...v0.15.7 [v0.15.6]: https://github.com/smartrent/grizzly/compare/v0.15.5...v0.15.6 [v0.15.5]: https://github.com/smartrent/grizzly/compare/v0.15.4...v0.15.5 [v0.15.4]: https://github.com/smartrent/grizzly/compare/v0.15.3...v0.15.4 [v0.15.3]: https://github.com/smartrent/grizzly/compare/v0.15.2...v0.15.3 [v0.15.2]: https://github.com/smartrent/grizzly/compare/v0.15.1...v0.15.2 [v0.15.1]: https://github.com/smartrent/grizzly/compare/v0.15.0...v0.15.1 [v0.15.0]: https://github.com/smartrent/grizzly/compare/v0.14.8...v0.15.0 [v0.14.8]: https://github.com/smartrent/grizzly/compare/v0.14.7...v0.14.8 [v0.14.7]: https://github.com/smartrent/grizzly/compare/v0.14.6...v0.14.7 [v0.14.6]: https://github.com/smartrent/grizzly/compare/v0.14.5...v0.14.6 [v0.14.5]: https://github.com/smartrent/grizzly/compare/v0.14.4...v0.14.5 [v0.14.4]: https://github.com/smartrent/grizzly/compare/v0.14.3...v0.14.4 [v0.14.3]: https://github.com/smartrent/grizzly/compare/v0.14.2...v0.14.3