-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
LEDVANCE Smart+ Outdoor Plug (AC26940) not propagating its state back to Z2M #10403
Comments
Can you provide the data/database.db entry of this device? |
Of course, this is the corresponding line from
|
Can you check with the following external converter? const fz = require('zigbee-herdsman-converters/converters/fromZigbee');
const tz = require('zigbee-herdsman-converters/converters/toZigbee');
const exposes = require('zigbee-herdsman-converters/lib/exposes');
const reporting = require('zigbee-herdsman-converters/lib/reporting');
const extend = require('zigbee-herdsman-converters/lib/extend');
const e = exposes.presets;
const ea = exposes.access;
const definition = {
zigbeeModel: ['Outdoor Plug', 'Plug Value'],
model: 'AC26940/AC31266',
vendor: 'LEDVANCE',
description: 'Smart Zigbee outdoor plug EXTERNAL CONVERTER',
extend: extend.switch(),
ota: ota.ledvance,
configure: async (device, coordinatorEndpoint, logger) => {
const endpoint = device.getEndpoint(1);
await reporting.bind(endpoint, coordinatorEndpoint, ['genOnOff']);
await reporting.onOff(endpoint);
},
};
module.exports = definition; See https://www.zigbee2mqtt.io/advanced/support-new-devices/01_support_new_devices.html#_2-adding-your-device how to add the external converter, to make sure it is loaded the description in the frontend should contain EXTERNAL CONVERTER |
Great, added the fix. Changes will be available in the dev branch in a few hours from now. (https://www.zigbee2mqtt.io/advanced/more/switch-to-dev-branch.html) |
Great, thank you very much! |
What happened?
I am not sure whether this is common behavior of these LEDVANCE plugs, but when I manually press their power button to toggle its state, it changes the state (on/off) of that plug, but that state isn't propagated back to the Z2M and Z2M still thinks that plug is in previous state.
What did you expect to happen?
I would expect that the plug's state would be synced properly in Z2M, e. g. when I turn the plug on, it would show in Z2M that plug is turned on.
Is this common behavior of these LEDVANCE plugs? I tried to upgrade firmware via available OTA to the latest available
00203045
, but it still behaves in the same way. For example, Xiaomi plugs that I also have, are reporting state back immediately after a power button is pressed.As a workaround I am currently periodically sending
zigbee2mqtt/ledvance-plug/get {"state": ""}
message to refresh the state, but it depends on active polling of the device, so if there would be a way to avoid this it would be better.How to reproduce it (minimal and precise)
Change the plug's state using physical button.
Zigbee2MQTT version
1.22.1
Adapter firmware version
20210708
Adapter
zzh!
Debug log
When I press the plug's button nothing appears in debug log at all.
The text was updated successfully, but these errors were encountered: