- Fixed an edge case scenario where DNS resolution to SmartThings cloud would fail indefinitely until a hard reboot
LAN Improvements
- Increased SSDP buffer size to support longer search terms
- Fixed bug where incorrect MAC address would occasionally be sent to the cloud for a LAN connected device
- Fixed a race condition where several concurrent LAN connections would cause the hub to reboot
ZigBee Improvements
- Reworked the ZigBee joining process on the hub to improve success rate of joining new devices and prevent devices joining as “Thing”
- The new joining process will be documented here on Thursday 4/21/16
- These changes were made to improve the reliability of the device join and identification process. As an example, some devices will actually join the network, leave almost immediately, and then join again. This would sometimes result in devices showing up as a “Thing” because some of the discovery messages were not responded to. With this new method the hub will automatically retry any messages that are not responded to and restart the entire discovery process if a device rejoins while the discovery is still in progress.
- Key take aways for developers and users
- When you want to write a device type handler for a new device first join it, then go look at the zbjoin message for all the information you need for the fingerprint.
- ZigBee devices known by the platform should no longer occasionally join as Things (if they do, please report it to support so we can figure out what’s going on)
- This only changes the initial device discovery process and does not affect the fingerprinting process or the way the DTH interacts with the device.
- The first endpoint in the list is used for fingerprinting. Multiple endpoint support is not included in this release.
- Added ability to view if unsecure join is disabled
- This is available in Graph in the Hub Utilities page
- Added ability to view presence timeout for HubV2
- This is available in Graph in the Hub Utilities page
- Improved reporting on ZigBee network state changes to the cloud
- ZigBee devices are removed from the network when deleted from the platform
- When a device is deleted it will be sent the ZigBee Mgmt_Leave_req. If the device supports this optional command it will leave the network.
AppEngine Improvements
- Fix bug where duplicate sunset and sunrise events could be generated
- Fix bug where large numbers of devices selected in SmartApps could lead to execution failure