fix: Prevent IKEA PARASOLL and BADRING being stuck on a previously reported state after it rapidly changes back and forth.

[marazmarci]

Credit goes to @legsim for discovering that configuring reporting for the ssIasZone cluster's zoneStatus attribute with minimumReportInterval: 0 fixes a common problem with the PARASOLL and BADRING sensors where their state can become stuck on a previously reported state after it rapidly changes back and forth.

[marazmarci]

@Koenkk, please add the hacktoberfest-accepted label to the PR. 🙏

[sjorge]

This can probably extracted into a modernExtend quirk and added for these 2 devices.

e.g.

zigbee-herdsman-converters/src/lib/modernExtend.ts

Lines 2350 to 2359 in 7e8a807

	export function quirkCheckinInterval(timeout: number | keyof typeof timeLookup): ModernExtend {
	const configure: Configure[] = [
	async (device, coordinatorEndpoint, definition) => {
	device.checkinInterval = typeof timeout == 'number' ? timeout : timeLookup[timeout];
	device.save();
	},
	];
	return {configure, isModernExtend: true};
	}

is quirk that also adds an addition configure step.

[Koenkk]

I think it would be better to add this to the already existing iasZoneAlarm, @marazmarci is this something you could change?

[marazmarci]

@Koenkk, I implemented the changes you requested. I'm no TypeScript dev, but I hope it is good and it works.

I didn't yet have time to actually test it, so I'm marking the PR as a draft in the meantime.

[Koenkk]

Made some small updates, let me know if this work!

[marazmarci]

I tested it, and it worked both for PARASOLL and BADRING! I saw the zoneStatus attribute with the correct endpoint on the Reporting tab.

[Koenkk]

thanks!