This is applicable for devices using IAS zone cluster and do not comply with the IAS enrollment process.
If the enrollment process is disrespected and therefore not needed, the current implementation is way to penetrant to enforce enrollment. It is always assumed a device not being enrolled yet needs to be, which is perfectly fine for spec compliant devices. However, devices not requiring it will never report back a proper IAS zone state resulting in worst case devices being hammered with write and read requests. This can especially be troublesome for battery powered light sleepers and potentially negatively impacting battery life.
In future, it would be appreciated if the enrollment item would be configurable in the DDFs. Its default value should be 0 to initiate the enrollment process. On the other hand, there should be the possibility to statically set it to 1 for devices not following/requiring the enrollment.
This is applicable for devices using IAS zone cluster and do not comply with the IAS enrollment process.
If the enrollment process is disrespected and therefore not needed, the current implementation is way to penetrant to enforce enrollment. It is always assumed a device not being enrolled yet needs to be, which is perfectly fine for spec compliant devices. However, devices not requiring it will never report back a proper IAS zone state resulting in worst case devices being hammered with write and read requests. This can especially be troublesome for battery powered light sleepers and potentially negatively impacting battery life.
In future, it would be appreciated if the
enrollmentitem would be configurable in the DDFs. Its default value should be0to initiate the enrollment process. On the other hand, there should be the possibility to statically set it to1for devices not following/requiring the enrollment.