Releases: smartrent/grizzly
Releases · smartrent/grizzly
v8.8.0
Changed
- Use strictly seconds or :default as duration when setting a binary or multilevel switch (#1061)
- The meaning of a duration would vary from seconds to converted minutes when exceeding 127 (128 meant one minute, 129 meant 2 minutes etc., and 255 meant manufacturer default)
v8.7.1
Fixed
- Increase timeout for
Grizzly.Network.reset_controller/1
to 60 seconds to allow enough time
for the Default Set command to complete (#1058)
v8.6.10
Fixed
- Increase timeout for
Grizzly.Network.reset_controller/1
to 60 seconds to allow enough time
for the Default Set command to complete (#1058)
v8.7.0
Changed
- Remove the
listening?
node info property (#1050)
- See the PR for more details, but tl;dr this flag was long ago misinterpreted and does not
actually indicate whether a node is listening
v8.6.9
Added
- Require MuonTrap v1.6.0 for logging improvements (#1045)
Fixed
- Fix module name typos in
Grizzly.ZWave.Decoder
(#1046)
- Enforce command names match module names and handler specs (#1047)
v8.6.7
Added
- Implement Configuration Default Reset from Config v4 (#1040)
- Elixir 1.18 compatibility (#1041)
Fixed
- Fix incorrect command IDs for Config Info Get/Report (#1039)
v8.6.6
Added
- Handle incoming Multi Channel Association commands for endpoint associations (#1029)
v8.6.4
Added
- Add retry logic to unsolicited server listen call (#1021)
- Provide the possible scales for a given sensor type (#1019)
- Support alarm reports for Alarm CC v1 (#1017)
- Unknown alarm types and events will be the raw value
Fixed
- Fix the decoding of
alarm_type_supported_report
when version 1 of alarm types and events are also supported by the device (#1024)
v8.6.3
Fixed
- Inclusion Server handles Extended Node Add Status (#1015)