Release 2.1.5 Available

📰 News and Updates Release Notes
5

Release 2.1.5.124 Available

This hot fix release includes the following fixes and features:

  • Fixed an issue with Rule Machine where Global Variable Connectors would break if you changed the Connector device label. Now, the Connector device label can be freely changed. DO NOT change the device name.
  • Added a feature to Motion Lighting to allow a contact sensor to turn off the lights when closed.
  • Added a feature to Group 2.0 to allow the group device to be Off if any of the lights in the group are off. There are now three choices available: (1) The group device on/off state reflects the most recent activity of the group device, and does not reflect anything about the actual state of the group members; (2) The group device will be on if any of the group members are on; and (3) The group device will be off if any of the group members are off.
  • Driver update for the Ecolink motion sensors using the Genereic Z-Wave Motion Sensor driver.
    If you have other brand motion sensors using this driver, you can ignore the remainder of this section.
    If you own any Ecolink motion sensors and are using the Generic Z-Wave Motion Sensor driver, please perform the following steps for each device after the update, failing to do so may result in these devices either not reporting or double reporting.
    If you elect not to apply this update, you will have to perform these steps the next time you update anyway, best to do it now and get it over with.
    • 1: Verify that within the data section of the driver details you have a value in the MSR field, it should be 014A-0001-0001 or 014A-0004-0001
      ** If you don't have an MSR field, then remove the battery cover on the sensor, then click the configure command in the driver page, refresh the page and you should now have an MSR value, if not, repeat until you get an MSR value...
    • 2: Verify that you are seeing one, and only motion event, the easiest way to verify this is to have a live logging session running and look for the info events, be sure that Enable descriptionText logging is enabled in the driver.
      ** If you are receiving no motion events, or you are receiving double motion events, then remove the battery cover on the sensor, then click the configure command on the driver page, trigger a motion event to verify that it's working.

Barring unforeseeable issues, problems and other catastrophes, this should be the final hot fix release for 2.1.5.

8 Likes