Would appreciate some clearer guidance on how health check works and the impact of this change. Does this mean that health check is disabled for battery operated devices which use default configurations ? Does this apply all default configurations (battery, IASZone, Temperature etc)!
Sorry for the confusion Rboy, this release note is not clear. The only change related to the zigbee attribute health monitoring (which we automatically do by default based on monitored/configured attributes in the driver) is that if the driver opts out of this monitoring, it actually gets the latency and memory savings from opting out. The hub is tracking device health for all hub connected devices in some way, including battery devices. The monitoring functionality provided by the Lua libs will only stop if your driver opts out of it.
For context, this change was made because we will be making ST drivers opt out of this monitoring to get the small memory/latency improvement. The functionality itself has been there since edge drivers were first released, and its purpose is to be a defensive mechanism to try to keep devices online, but the hub has its own algorithm for determining device health based on protocol, capabilities, and device configuration. The attribute monitoring mechanism in the zigbee lua libraries is not something that directly affects the health of a zigbee device, and the only way it would affect it is if it causes a device to send a message to the hub; it is not involved in determining the length of time without communication it takes for a device to be marked offline.