Hallo,
Der Xiaomi Zigbee-Knopf WXKG01LM bietet mehr Aktionen an, als Gladys derzeit unterstützt.
Zigbee2MQTT erkennt die folgenden Zustände: single, double, triple, quadruple, hold, release, many
Gladys kennt nur die Werte: 1 (Klick), 2 (Doppelklick), 5 (Langdruck)
Könnten diese neuen Möglichkeiten bitte hinzugefügt werden?
Danke
Ich habe die Idee, dass die folgenden Dateien geändert werden müssten, bin mir aber nicht sicher:
server/services/zigbee2mqtt/exposes/enumType.js
addMapping('action', BUTTON_STATUS.CLICK, 'single');
addMapping('action', BUTTON_STATUS.DOUBLE_CLICK, 'double');
addMapping('action', BUTTON_STATUS.TRIPLE_CLICK, 'triple');
addMapping('action', BUTTON_STATUS.QUADRUPLE_CLICK, 'quadruple');
addMapping('action', BUTTON_STATUS.MANY_CLICK, 'many');
addMapping('action', BUTTON_STATUS.HOLD_CLICK, 'hold');
addMapping('action', BUTTON_STATUS.LONG_CLICK, 'long');
et die Datei server/test/services/zigbee2mqtt/exposes/actionEnumType.test.js
const { assert } = require('chai');
const enumType = require('../../../../services/zigbee2mqtt/exposes/enumType');
const { BUTTON_STATUS } = require('../../../../utils/constants');
describe('zigbee2mqtt action enumType', () => {
const expose = {
name: 'action',
values: ['single', 'long', 'short', 'double', 'triple', 'quadruple', 'many', 'hold'],
};
[
{ enumValue: 'single', intValue: BUTTON_STATUS.CLICK },
{ enumValue: 'double', intValue: BUTTON_STATUS.DOUBLE_CLICK },
{ enumValue: 'triple', intValue: BUTTON_STATUS.TRIPLE_CLICK },
{ enumValue: 'quadruple', intValue: BUTTON_STATUS.QUADRUPLE_CLICK },
{ enumValue: 'many', intValue: BUTTON_STATUS.MANY_CLICK },
{ enumValue: 'hold', intValue: BUTTON_STATUS.HOLD_CLICK },
{ enumValue: 'long', intValue: BUTTON_STATUS.LONG_CLICK },
].forEach((mapping) => {
const { enumValue, intValue } = mapping;
it(`should write ${enumValue} value as ${intValue} value`, () => {
const result = enumType.writeValue(expose, intValue);
assert.equal(result, enumValue);
});
it(`should read ${intValue} value as ${enumValue}`, () => {
const result = enumType.readValue(expose, enumValue);
assert.equal(result, intValue);
});
});
it('should write undefined value on missing enum', () => {
const missingEnumExpose = {
values: ['single', 'short', 'double', 'triple', 'quadruple', 'many'],
};
const result = enumType.writeValue(missingEnumExpose, BUTTON_STATUS.LONG_CLICK);
assert.equal(result, undefined);
});
it('should write undefined value', () => {
const result = enumType.writeValue(expose, 7);
assert.equal(result, undefined);
});
it('should read enum value', () => {
const result = enumType.readValue(expose, 'unknown');
assert.equal(result, undefined);
});
it('should have multiple indexes', () => {
const result = enumType.getFeatureIndexes(['1_single', '1_double', '2_single']);
assert.deepEqual(result, [1, 2]);
});
it('should have no indexes', () => {
const result = enumType.getFeatureIndexes(['single', 'double']);
assert.deepEqual(result, []);
});
});
Muss man auch enumType.getFeatureIndexes([‹ single ›, ‹ double ›]); anpassen?
