Yay! I can’t wait to try it out! Big thanks to @mattludwigs and the entire SmartRent team!

30%20AM660×362 114 KB

I can’t wait to try it out!

This is really really cool. I have been using Hypriot OS with elixir on docker containers to do home network stuff and was thinking about how to use z-wave with pi and elixir. I can’t wait to get this working.

By the way, if you want to get more people involved, I think you should announce Grizzly here: https://www.reddit.com/r/homeautomation/ Some people there would love this project.

Thank you! If you run into any issues getting setup feel free to ask a question.

Thanks for the suggestion, I will look into announcing it there too soon!

New release v0.4.3

• Enhancements
  • Support Powerlevel command class
  • Doc clean up
  • Grizzly.send_command/2 and Grizzly.send_command/3
    can be passed a node id instead of a node.

New release v0.5.0

TLDR; Provides better error handling when trying to encode command arguments. Improves robustness of Grizzly.

Introduces Grizzly.Command.EncodeError exception and updates encoding and
decoding functions to return tagged tuples. We now use these things when trying
to send a command via Grizzly.send_command/3 so if you have invalid command
arguments we can provide useful error handling with
{:error, Grizzly.Command.EncodeError.t()}. The EncodeError.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 the {:error, EncodeError.t()}
to improve the usability of and robustness your command. The new
Grizzly.Command.Encoding module provides some useful functionality for
validating specs for command arguments.

• Enhancements
  • Provide command argument validation and error handling via
    Grizzly.Command.EncodeError.()
  • Update all the command arg encoder/decoder to use tagged
    tuples for better handling of invalid command arguments
  • Introduces new Grizzly.Command.Encoding modules for helping
    validate command argument specifications
• Fixes
  • Crashes when providing invalid command arguments

Big thanks to @jfcloutier for the hard work on this!

New Release: v0.6.0

Changed Grizzly.CommandClass.CommandClassVersion to Grizzly.CommandClass.Version
and changed Grizzly.ComamndClass.CommandClassVersion.Get to
Grizzly.CommandClass.Version.CommandClassGet as these names reflect the Z-Wave
specification better.

If you only have used Grizzly.get_command_class_version/2 and the related function
in Grizzly.Node module this change should not affect 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
  • Renamed Grizzly.CommandClass.CommandClassVersion to Grizzly.CommandClass.Version
  • Renamed Grizzly.CommandClass.CommandClassVersion.Get to
    Grizzly.CommandClass.Version.CommandClassGet

Another shout out to @jfcloutier for adding more support to for commands and command classes!

New Release: v0.6.1

• Enhancements
  • Update commands IntervalGet and ManufacturerSpecificGet to be more
    consistent
  • Better handling of invalid ManufacturerSpecific info received from
    devices

New Release: v0.6.2

• Enhancements
  • Remove the dependence on pidof allowing grizzly to work on any nerves
    device without the need of busybox

New Release: v0.6.3

• Enhancements
  • Supports AssociationGroupInformation Command Class