Release 2.1.5 Available

Hubitat Elevation Platform update 2.1.5 is now available

Please note, the process takes about a minute to download (depending on your Internet connection) and extract the hub update, and 1-2 minutes to perform the update after you click 'Update Hub'. We recommend that you periodically download a backup of your setup from the Settings page, Backup and Restore.

Changes from 2.1.4:

Platform Additions / Changes

  • Retired SMS functionality.
  • Added method to set hub date/time from apps and drivers.

Drivers and Devices

  • New drivers:
  • New tested devices:
    • Samsung Zigbee Outlet (IM6001-OTP01) using Generic Zigbee Outlet
    • Added bedside lamp 2 support to Yeelight integration.
    • Nue HGZB-44 quad switch using Nue Zigbee Switch
    • Zemismart 2 Gang Switch using Nue Zigbee Switch
  • New driver features:
    • Added “White” as a color to RGB and RGBW drivers
    • Added ASAP timeout option to virtual motion sensor.
    • Added default test lock code to virtual lock driver on initial install.
    • Added lastCodeName attribute to lock drivers.

New App Features

  • Motion Lighting: Now allows contact sensors to turn on the lights.
  • Rule 4.0:
    • Allow rule to pause itself.
    • Allow multiple button devices.
    • Allow volume, player level, shade position, repeat seconds, and repeat number of times to be set from a variable.
  • Dashboard UI has been tweaked and add CSS tags for all tile templates and states.
  • Dashboard Menu has a new look.

Retired App Features

  • Rule Machine: Retired Rule 3.0. Existing instances of Rule 3.0 will continue to work and be editable.
  • Button Controllers: Retired Button Controller 3.0 (use a Rule with ‘Button device’ trigger). Existing instances of Button Controller 3.0 will continue to work and be editable.
  • SMS functionality has been retired from all built-in apps.

Bug Fixes

  • Rule Machine:
    • Fixed Boolean variable connectors.
    • Fixed Wait for Event with Variable.
    • Fixed sorting of list of Variables for Variable Math.
    • Fixed issue preventing Device Attribute device selection for setting Variables with spaces in their names.
    • Fixed bug that prevented ‘Rule paused’ selected rules from being displayed.
    • Fixed bug with Physical Switch triggers not honoring the selected state with bad subscription.
    • Fixed bug with using variable for delay or timeout.
    • Fixed bug with music player toggles.
    • Fixed issues with lock/keypad code conditions.
    • Fixed bug with Boolean logic in setting Boolean variable.
    • Fixed bug with redundant multiple Scenes in list.
    • Fixed UI issue with ‘Button’ trigger creation.
  • Button Controller 3.0: Fixed bug with music player toggles.
  • Motion Lighting:
    • FIxed an issue where Motion Lighting was unaware of the lights being turned off outside the app, and not turning them on thinking they were already on.
    • Fixed a bug that extended off-delay in mode where lights not turned on
  • Groups and Scenes: Fixed bug with redundant multiple Scenes in lists.
  • Scene 1.2: Fixed bug with adjusting switch state.
  • Keen Vent driver: Fixed error on initial install.
  • Sengled drivers: Fixed not retaining correct level when turning off with short report interval settings.
  • Fixed exception with device.updateSetting() when setting is missing, will now create a new setting.
  • Generic Zigbee Outlet: Fixed power reporting.
  • Generic Z-Wave Contact Sensor and Generic Z-Wave Motion Sensor: Fixed double events.
15 Likes

Release 2.1.5.120 Available

This hot fix release corrects the reported issues:

  • Dashboard tile and history problems have been corrected.
  • Conditions based on Mode in RM have been fixed.
  • A bug in Motion Lighting with 'Don't tun off is already on' has been fixed.

There are some additional outstanding issues with Motion Lighting, These will be resolved in a further release.

2 Likes

Release 2.1.5.121 Available

This hot fix release corrects the reported issues:

  • Dashboard tiles fixed for showing device name.
  • Motion Lighting issues with not turning on or off as it should fixed.
4 Likes

Release 2.1.5.123 Available

This hot fix release includes the following fixes and features:

  • Fixed issue with keypad codes in Rule Machine causing error.
  • Added lastCodeName attribute to Centralite and Iris keypad drivers.
  • Added ability to extract token from string variable (see this post).
  • Added ability to convert string variable numeric string to number or decimal.
2 Likes

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