Skip to content

Releases: Tom-Hirschberger/MMM-GPIO-Notifications

Release 0.2.7

06 Sep 16:21
b1470b1
Compare
Choose a tag to compare

This is release 0.2.7 with the following changes:

  • Introducing the new option forceInfoFileUsage. If this option is set to true the build in device information will be skipped the usage of the gpioinfo.json is forced.

Release 0.2.6

21 Apr 06:33
677687c
Compare
Choose a tag to compare

This is release 0.2.6 with the following changes:

  • fixed a issue which caused the converter script to not be called correctly by the preinstall script in some container setups
  • fixed bloated output introduced with version 0.2.5

Release 0.2.4

06 Apr 08:16
695bb4f
Compare
Choose a tag to compare

This is release 0.2.4 with the following changes:

  • fixed another issue in the stop function which de-registers all pins during shutdown

Release 0.2.3

05 Apr 18:53
65696c1
Compare
Choose a tag to compare

This is release 0.2.3 with the following changes:

  • fixed a bug which caused the stop function of node_helper.js to throw an error

Release 0.2.2

02 Apr 19:15
f6d8a09
Compare
Choose a tag to compare

This is release 0.2.2 with the following changes:

  • As the new version of the opengpio library contains the GPIO information of most of the Raspberry devices now, the module tries to use the information of the library in a first manner. Only if no information is available for the used board the information generated during installation in gpioinfo.json is used.
  • added exception handling. Now console messages are printed instead of killing the whole application if a pin is already used or no information about the chip and lane to use are available.
  • the module releases all registered pins during shutdown now.

Release 0.2.1

24 Mar 17:34
3e9833b
Compare
Choose a tag to compare

This is release 0.2.1 with the following changes:

  • Now not only GPIOs which are named "GPIOX" (where X is the number of the GPIO) in the output of gpioinfo can be used but also named GPIOs.
  • added more output to log to show if a GPIO could be registered or not.

Release 0.2.0

22 Mar 13:30
e291ab6
Compare
Choose a tag to compare

This is release 0.2.0 with the following changes:

  • changed the "under the hood" library from onoff to opengpio to make it possible to use GPIO with kernels >= 6.6
  • totally rewrite of the GPIO handling
  • totally rewrite of the installation process
    • the required library gets installed with apt
    • the required toolset gets installed with apt
    • a python script automatically creates a configuration file with your GPIO info inside. The file will be used by the module to determine which GPIO chipset and GPIO line needs to be used for a specific GPIO number
    • removed the test scripts in the example folder and added some new one to either monitor GPIO ports or test a rotary encoder

BREAKING CHANGES

  • dropped "gpio_debounce" option as the new library does not support debounce (at the moment). Please use delays as an alternative.

Release 0.1.0

18 Jun 14:49
a78c975
Compare
Choose a tag to compare

This is release 0.1.0 with the following changes:

  • it is possible to use rotary encoders with this module now
  • added a hint about how to use the module in a container setup to the readme

Release 0.0.9

22 Jan 12:28
2e623ca
Compare
Choose a tag to compare

This is release 0.0.9 with the following changes:

  • it is possible to set different delays for high and low state now
  • the default value of gpio_debounce is now set to 0
  • the old syntax using gpio_state and notifications options is deprecated now. Use notifications_low and notifications_high instead.
  • add examples and a own section about the difference between gpio_debounce and the options delay, delay_low and delay_high to the README

Release 0.0.8

17 Jan 19:44
c2c0458
Compare
Choose a tag to compare

This is release 0.0.8 with the following changes:

  • It is possible to send notifications for both states of a watched pin now