ICP-7369 Fix the ORVIBO smoke sensor status don't changed in ST app after trigger a smoke event

[BYDengS]

@greens @MAblewiczS and @ALamchaS ,please help review this change.And merge it to China IOT Server. Thank you!.

[BYDengS]

Thanks @tpmanley help to solve this problem.

Hi Deng Biaoyi,

The issue is with IAS Zone enrollment. The older sensor sent a ZoneEnrollRequest shortly after it joined (timestamp 15.587418) and the hub responded with a successful ZoneEnrollResponse (timestamp 16.621316). After that point the device is enrolled and able to generate alarm events. The new sensor does not send a ZoneEnrollRequest during joining so it does not get enrolled in an IAS Zone and so it does not generate alarm events.

Most IAS Zone devices work the way this new version of the sensor works, in that they do not send a ZoneEnrollRequest automatically. Instead they rely on the DTH to send a ZoneEnrollResponse (not a ZoneEnrollRequest), and write the CIE Address attribute in the configure method.

Here is how I'd suggest updating the configure method:

def configure() {
log.debug "configure"sendEvent(name: "checkInterval", value:6 * 60 * 60 + 2 * 60, displayed: false, data: [protocol: "zigbee", hubHardwareId: device.hub.hardwareID, offlinePingable: "1"])

return refresh() + zigbee.enrollResponse() + zigbee.configureReporting(zigbee.POWER_CONFIGURATION_CLUSTER, 0x0021, DataType.UINT8, 30, 21600, 0x10)

}

The reason I moved refresh to the beginning is will decrease the amount of time it takes to get the initial status for battery and zoneStatus. The additional call to zigbee.enrollResponse() will take care of writing the CIE address and sending the ZoneEnrollResponse to get the device enrolled in the IAS Zone. Please give this change a try and see if it fixes the problem.

Best regards,
Tom

[tpmanley]

This has been deployed to PROD and STG