feat: modern extend improvements

[mrskycriper]

TODO

• sort Modern Extends roughly according to ZCL documentation chapters
• update identify extend
  • separate sleepy devices
  • remove compatibility with numeric identify as it will be removed in fix: convert IKEA to modern extend #7220
• add linkquality extend
• add pm25 extend
• add commandsOnOff extend
• add commandsLevelCtrl extend
• add commandsColorCtrl extend
• add commandsWindowCovering extend
• add windowCovering extend
• add deviceTemperature extend
• add flow extend
• add soilMoisture extend
• merge multiple action exposes into one on processing
• add GET converters to battery extend
• fix meta in battery extend
• move identify to inputExtenders
• add ota extend to definition generator

[mrskycriper]

@Koenkk implemented all suggested changes

[Koenkk]

Many thanks for another great refactor 😄

[burmistrzak]

@Koenkk Just realized we have no option to configured reporting for batteryAlarmState, so battery_low probably won't work as expected, i.e. not automatically update?

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

Lines 270 to 290 in f7993f5

	if (msg.data.hasOwnProperty('batteryAlarmState')) {
	const battery1Low = (
	msg.data.batteryAlarmState & 1<<0 ||
	msg.data.batteryAlarmState & 1<<1 ||
	msg.data.batteryAlarmState & 1<<2 ||
	msg.data.batteryAlarmState & 1<<3
	) > 0;
	const battery2Low = (
	msg.data.batteryAlarmState & 1<<10 ||
	msg.data.batteryAlarmState & 1<<11 ||
	msg.data.batteryAlarmState & 1<<12 ||
	msg.data.batteryAlarmState & 1<<13
	) > 0;
	const battery3Low = (
	msg.data.batteryAlarmState & 1<<20 ||
	msg.data.batteryAlarmState & 1<<21 ||
	msg.data.batteryAlarmState & 1<<22 ||
	msg.data.batteryAlarmState & 1<<23
	) > 0;
	if (args.lowStatus) payload.battery_low = battery1Low || battery2Low || battery3Low;
	}

Do some devices report batteryAlarmState on their own, or do we need to fix this? 🤔

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

Lines 318 to 340 in f7993f5

	if (args.percentageReporting || args.voltageReporting) {
	const configure: Configure[] = [];
	if (args.percentageReporting) {
	configure.push(
	setupConfigureForReporting(
	'genPowerCfg',
	'batteryPercentageRemaining',
	args.percentageReportingConfig,
	ea.STATE_GET,
	),
	);
	}
	if (args.voltageReporting) {
	configure.push(
	setupConfigureForReporting(
	'genPowerCfg',
	'batteryVoltage',
	args.voltageReportingConfig,
	ea.STATE_GET,
	),
	);
	}
	result.configure = configure;

[Koenkk]

Some devices might report it on their own, but the question is wether we want to batteryAlarmState to be reported when we already have the battery %

[burmistrzak]

Some devices might report it on their own, but the question is wether we want to batteryAlarmState to be reported when we already have the battery %

Yea, kinda hard to know which devices actually do report it on their own...
It's probably sensible to just remove battery_low, unless we know for sure the attribute is reported by the device in question. It's better having battery_low not exposed than it always being null.