Vesternet VES-ZB-REM-013 multiple commands for on and off action

[lukasjakobi]

I noticed that the Vesternet VES-ZB-REM-013 outputs 4 separate action states (f.e."on_1", "on_2", "on_3", "on_4") when pressing the top on and off buttons. This causes Home Assistant to sometimes output a WARNING log with message Already running and thus dropping the action.

I think a better solution can be to add the two actions as separate actions, "on" and "off".

Can this be fixed with a change to the converter definition or is this a firmware problem?

Converter Definition

zigbee-herdsman-converters/src/devices/vesternet.ts

Lines 58 to 81 in cc15841

	{
	fingerprint: [{modelID: 'ZGRC-KEY-013', softwareBuildID: '2.5.3_r20'}, {modelID: 'ZGRC-KEY-013', softwareBuildID: '2.7.6_r25'}],
	model: 'VES-ZB-REM-013',
	vendor: 'Vesternet',
	description: 'Zigbee remote control - 12 button',
	fromZigbee: [fz.command_on, fz.command_off, fz.command_move, fz.command_stop, fz.command_recall, fz.battery, fz.ignore_genOta],
	exposes: [e.battery(), e.action([
	'on_1', 'off_1', 'stop_1', 'brightness_move_up_1', 'brightness_move_down_1', 'brightness_stop_1',
	'on_2', 'off_2', 'stop_2', 'brightness_move_up_2', 'brightness_move_down_2', 'brightness_stop_2',
	'on_3', 'off_3', 'stop_3', 'brightness_move_up_3', 'brightness_move_down_3', 'brightness_stop_3',
	'on_4', 'off_4', 'stop_4', 'brightness_move_up_4', 'brightness_move_down_4', 'brightness_stop_4',
	'recall_1_1', 'recall_1_2', 'recall_1_3', 'recall_1_4',
	'recall_2_1', 'recall_2_2', 'recall_2_3', 'recall_2_4'])],
	toZigbee: [],
	meta: {multiEndpoint: true, battery: {dontDividePercentage: true}, publishDuplicateTransaction: true},
	whiteLabel: [{vendor: 'Sunricher', model: 'SR-ZG9001K12-DIM-Z4'}],
	configure: async (device, coordinatorEndpoint) => {
	await reporting.bind(device.getEndpoint(1), coordinatorEndpoint, ['genOnOff', 'genLevelCtrl', 'genScenes', 'genPowerCfg']);
	await reporting.bind(device.getEndpoint(2), coordinatorEndpoint, ['genOnOff', 'genLevelCtrl', 'genScenes']);
	await reporting.bind(device.getEndpoint(3), coordinatorEndpoint, ['genOnOff', 'genLevelCtrl', 'genScenes']);
	await reporting.bind(device.getEndpoint(4), coordinatorEndpoint, ['genOnOff', 'genLevelCtrl', 'genScenes']);
	await reporting.batteryPercentageRemaining(device.getEndpoint(1));
	},
	},

[lukasjakobi]

Also for this device the buttons labeled "S1" and "S2" are also sending 4 events each. They follow the pattern of "recall_{1-2}_{1-4}". For using this device with Home Assistant this is not very useful. On the other hand i know that this behavior is expected when paring the remote to Zigbee bulbs directly.

[github-actions]

This issue is stale because it has been open 180 days with no activity. Remove stale label or comment or this will be closed in 30 days