Ledvance zigbee EM EU plug by LQ107 · Pull Request #3009 · SmartThingsCommunity/SmartThingsEdgeDrivers

LQ107 · 2026-06-01T02:27:03Z

Check all that apply

Type of Change

WWST Certification Request
- If this is your first time contributing code:
  - I have reviewed the README.md file
  - I have reviewed the CODE_OF_CONDUCT.md file
  - I have signed the CLA
- I plan on entering a WWST Certification Request or have entered a request through the WWST Certification console at developer.smartthings.com
Bug fix
New feature
Refactor

Checklist

I have performed a self-review of my code
I have commented my code in hard-to-understand areas
I have verified my changes by testing with a device or have communicated a plan for testing
I am adding new behavior, such as adding a sub-driver, and have added and run new unit tests to cover the new behavior

Description of Change

Summary of Completed Tests

…dd driver registration processing

…lict

…/SmartThingsEdgeDrivers into ledvance_zigbee_meter_plug

…ter_handler issue

…/SmartThingsEdgeDrivers into ledvance_zigbee_meter_plug

…ation of the test file

…/SmartThingsEdgeDrivers into ledvance_zigbee_meter_plug

LQ107

I have add the min_api_version opt value for each test , please help review again ,thank you very much .

cjswedes · 2026-06-02T15:27:01Z

Does the device report SimpleMetering.Divisor or the SimpleMetering.Multiplier attributes? The defaults will query these and set them if the device reports them.

If that is the case, this could be a fingerprint only change.

yes , the device report SimpleMetering.Divisor or the SimpleMetering.Multiplier attributes

Since this is being reported by the device, the subdriver is not necessary. Please make this a fingerprint only change or explain why overriding the reported value on device init is necessary for the integration.

Since the values of SimpleMetering.Divisor or SimpleMetering.Multiplier used by the device are different from those of the Smarthings standard driver, a custom sub driver needs to be used

I see now our defaults arent actually issuing a read or configuring those attributes. So I see why the subdriver is needed, and there is some precedence of just setting these values based on device model.

There is some precedence of setting these values (i.e. aurora-relay subdriver), but that should not be needed. The doConfigure handler for the zigbee switch driver issues reads for these values and the default handlers set the fields:

SmartThingsEdgeDrivers/drivers/SmartThings/zigbee-switch/src/lifecycle_handlers/do_configure.lua

Lines 13 to 19 in 917bdad

-- Additional one time configuration

if device:supports_capability(capabilities.energyMeter) or device:supports_capability(capabilities.powerMeter) then

local clusters = require "st.zigbee.zcl.clusters"

-- Divisor and multipler for EnergyMeter

device:send(clusters.SimpleMetering.attributes.Divisor:read(device))

device:send(clusters.SimpleMetering.attributes.Multiplier:read(device))

end

Only a fingerprint change is necessary

Thanks for answer ,If only a fingerprint is added to the main driver, the plug cannot display the correct energy meter value.
The PLUG COMPACT EU EM T has passed SmartThings Certification. Previously, when I verified this model by adding only a fingerprint, the displayed energy meter value was 100 times the actual value. Therefore, a sub-driver needs to be added for this model.
Since the PLUG EU EM T is the same as the PLUG COMPACT EU EM T, I have added the sub-driver fingerprint for the PLUG EU EM T as well.

LQ107

Dear reviewers, I have added the min_api_version. Could you please help review again? Thank you very much.

cjswedes · 2026-06-04T14:11:01Z

The changes here are looking pretty good, but this subdriver should be a subdriver of the zigbee-switch-power subdriver. The aurora-relay subdriver exists for essentially the same reason; just to set the SIMPLE_METERING scaling fields.

Edit: I see that we do read the SimpleMetering.Divisor and SimpleMetering.Multiplier attributes in the zigbee switch default configure, so I dont think this subdriver is needed; those reads will trigger the default handlers when the device is joined which persist that value.

This should be a fingerprint only driver. Please test adding just the fingerprint.

LQ107 · 2026-06-09T02:12:31Z

The changes here are looking pretty good, but this subdriver should be a subdriver of the zigbee-switch-power subdriver. The aurora-relay subdriver exists for essentially the same reason; just to set the SIMPLE_METERING scaling fields.

Edit: I see that we do read the SimpleMetering.Divisor and SimpleMetering.Multiplier attributes in the zigbee switch default configure, so I dont think this subdriver is needed; those reads will trigger the default handlers when the device is joined which persist that value.

This should be a fingerprint only driver. Please test adding just the fingerprint.

I only add a fingerprint only driver, but show energy is incorrect , the displayed energy meter value was 100 times the actual value , I judge the values of SimpleMetering.Divisor or SimpleMetering.Multiplier used by the device are different from those of the Smarthings standard driver ,how can I solve this issue?

LQ107 · 2026-06-09T03:25:51Z

The changes here are looking pretty good, but this subdriver should be a subdriver of the zigbee-switch-power subdriver. The aurora-relay subdriver exists for essentially the same reason; just to set the SIMPLE_METERING scaling fields.
Edit: I see that we do read the SimpleMetering.Divisor and SimpleMetering.Multiplier attributes in the zigbee switch default configure, so I dont think this subdriver is needed; those reads will trigger the default handlers when the device is joined which persist that value.
This should be a fingerprint only driver. Please test adding just the fingerprint.

I only add a fingerprint only driver, but show energy is incorrect , the displayed energy meter value was 100 times the actual value , I judge the values of SimpleMetering.Divisor or SimpleMetering.Multiplier used by the device are different from those of the Smarthings standard driver ,how can I solve this issue?

I reset the PLUG and add the PLUG to the Smartthings HUB again ,the Plug add a fingerprint only driver，the Plug can show the correct Energy meter ，thank you very much ,I will submit the driver again .

LQ107

Dear reviewers, thank you for your comments. I have updated the 'PLUG EU EM T' driver by adding the missing device fingerprints only. No other logic has been changed. Please help review it again. Thanks.

cjswedes

I am not convinced this subdriver is needed. I would expect the attributes to be read by the default do_configure handler of the zigbee switch driver:

SmartThingsEdgeDrivers/drivers/SmartThings/zigbee-switch/src/lifecycle_handlers/do_configure.lua

Lines 13 to 19 in 42a6a23

    
           -- Additional one time configuration 
        
           if device:supports_capability(capabilities.energyMeter) or device:supports_capability(capabilities.powerMeter) then 
        
             local clusters = require "st.zigbee.zcl.clusters" 
        
             -- Divisor and multipler for EnergyMeter 
        
             device:send(clusters.SimpleMetering.attributes.Divisor:read(device)) 
        
             device:send(clusters.SimpleMetering.attributes.Multiplier:read(device)) 
        
           end

And then since the zigbee-switch driver registers for default handlers for powerMeter and energyMeter, I would expect responses from the device to end up setting the field.

I was able to remove the ledvance-metering-plug subdriver from the top level subdrivers file, meaning it is not loaded at all. I then wrote a test validating that this is the behavior when only adding the fingerprint to the driver:

local mock_device = test.mock_device.build_test_zigbee_device(
  {
    profile = t_utils.get_profile_definition("switch-power-energy.yml"),
    zigbee_endpoints = {
      [1] = {
        id = 1,
        manufacturer = "LEDVANCE",
        model = "PLUG COMPACT EU EM T",
        server_clusters = { 0x0006, 0x0702 }
      }
    }
  }
)

test.register_coroutine_test(
        "configure should set the fields if the device response to the read requests",
        function()
            test.socket.zigbee:__set_channel_ordering("relaxed")
            assert(mock_device:get_field(zigbee_constants.SIMPLE_METERING_MULTIPLIER_KEY) == nil)
            assert(mock_device:get_field(zigbee_constants.SIMPLE_METERING_DIVISOR_KEY) == nil)

            --- Do configure by default issues the reads for the device.
            test.socket.device_lifecycle:__queue_receive({ mock_device.id, "doConfigure" })
            test.socket.zigbee:__expect_send({
                mock_device.id,
                SimpleMetering.attributes.Divisor:read(mock_device)
            })
            test.socket.zigbee:__expect_send({
                mock_device.id,
                SimpleMetering.attributes.Multiplier:read(mock_device)
            })
            test.socket.zigbee:__expect_send({
                mock_device.id,
                SimpleMetering.attributes.CurrentSummationDelivered:read(mock_device)
            })
            test.socket.zigbee:__expect_send({
                mock_device.id,
                SimpleMetering.attributes.InstantaneousDemand:read(mock_device)
            })
            test.socket.zigbee:__expect_send({
                mock_device.id,
                OnOff.attributes.OnOff:read(mock_device)
            })
            test.socket.zigbee:__expect_send({
                mock_device.id,
                zigbee_test_utils.build_bind_request(
                    mock_device,
                    zigbee_test_utils.mock_hub_eui,
                    SimpleMetering.ID
                )
            })
            test.socket.zigbee:__expect_send({
                mock_device.id,
                zigbee_test_utils.build_bind_request(
                    mock_device,
                    zigbee_test_utils.mock_hub_eui,
                    OnOff.ID
                )
            })
            test.socket.zigbee:__expect_send({
                mock_device.id,
                SimpleMetering.attributes.InstantaneousDemand:configure_reporting(
                    mock_device, 5, 3600, 5
                )
            })
            test.socket.zigbee:__expect_send({
                mock_device.id,
                SimpleMetering.attributes.CurrentSummationDelivered:configure_reporting(
                        mock_device, 5, 3600, 1
                )
            })
            test.socket.zigbee:__expect_send({
                mock_device.id,
                OnOff.attributes.OnOff:configure_reporting(
                        mock_device, 0, 0x12C
                )
            })
            mock_device:expect_metadata_update({ provisioning_state = "PROVISIONED" })
            assert(mock_device:get_field(zigbee_constants.SIMPLE_METERING_MULTIPLIER_KEY) == nil)
            assert(mock_device:get_field(zigbee_constants.SIMPLE_METERING_DIVISOR_KEY) == nil)

            -- If the device responds to the reads, the driver will save the new values,
            test.socket.zigbee:__queue_receive({ mock_device.id, SimpleMetering.attributes.Divisor:build_test_attr_report(mock_device, 100) })
            test.socket.zigbee:__queue_receive({ mock_device.id, SimpleMetering.attributes.Multiplier:build_test_attr_report(mock_device, 1) })
            test.wait_for_events()
            assert(mock_device:get_field(zigbee_constants.SIMPLE_METERING_MULTIPLIER_KEY) == 1)
            assert(mock_device:get_field(zigbee_constants.SIMPLE_METERING_DIVISOR_KEY) == 100)
        end
)

I packaged the driver here (https://bestow-regional.api.smartthings.com/invite/OzMgLmVWRD29). Please test with the real device.

I would prefer that this PR removes the ledvance-metering-plug subdriver and just adds the fingerprints for the devices. The only thing preventing that is if the devices do not respond to the read requests the driver issues for the multiplier and divisor.

LQ107 · 2026-06-10T02:22:55Z

I am not convinced this subdriver is needed. I would expect the attributes to be read by the default do_configure handler of the zigbee switch driver:

SmartThingsEdgeDrivers/drivers/SmartThings/zigbee-switch/src/lifecycle_handlers/do_configure.lua

Lines 13 to 19 in 42a6a23

    
           -- Additional one time configuration 
        
           if device:supports_capability(capabilities.energyMeter) or device:supports_capability(capabilities.powerMeter) then 
        
             local clusters = require "st.zigbee.zcl.clusters" 
        
             -- Divisor and multipler for EnergyMeter 
        
             device:send(clusters.SimpleMetering.attributes.Divisor:read(device)) 
        
             device:send(clusters.SimpleMetering.attributes.Multiplier:read(device)) 
        
           end

And then since the zigbee-switch driver registers for default handlers for powerMeter and energyMeter, I would expect responses from the device to end up setting the field.
I was able to remove the ledvance-metering-plug subdriver from the top level subdrivers file, meaning it is not loaded at all. I then wrote a test validating that this is the behavior when only adding the fingerprint to the driver:

local mock_device = test.mock_device.build_test_zigbee_device(
  {
    profile = t_utils.get_profile_definition("switch-power-energy.yml"),
    zigbee_endpoints = {
      [1] = {
        id = 1,
        manufacturer = "LEDVANCE",
        model = "PLUG COMPACT EU EM T",
        server_clusters = { 0x0006, 0x0702 }
      }
    }
  }
)

test.register_coroutine_test(
        "configure should set the fields if the device response to the read requests",
        function()
            test.socket.zigbee:__set_channel_ordering("relaxed")
            assert(mock_device:get_field(zigbee_constants.SIMPLE_METERING_MULTIPLIER_KEY) == nil)
            assert(mock_device:get_field(zigbee_constants.SIMPLE_METERING_DIVISOR_KEY) == nil)

            --- Do configure by default issues the reads for the device.
            test.socket.device_lifecycle:__queue_receive({ mock_device.id, "doConfigure" })
            test.socket.zigbee:__expect_send({
                mock_device.id,
                SimpleMetering.attributes.Divisor:read(mock_device)
            })
            test.socket.zigbee:__expect_send({
                mock_device.id,
                SimpleMetering.attributes.Multiplier:read(mock_device)
            })
            test.socket.zigbee:__expect_send({
                mock_device.id,
                SimpleMetering.attributes.CurrentSummationDelivered:read(mock_device)
            })
            test.socket.zigbee:__expect_send({
                mock_device.id,
                SimpleMetering.attributes.InstantaneousDemand:read(mock_device)
            })
            test.socket.zigbee:__expect_send({
                mock_device.id,
                OnOff.attributes.OnOff:read(mock_device)
            })
            test.socket.zigbee:__expect_send({
                mock_device.id,
                zigbee_test_utils.build_bind_request(
                    mock_device,
                    zigbee_test_utils.mock_hub_eui,
                    SimpleMetering.ID
                )
            })
            test.socket.zigbee:__expect_send({
                mock_device.id,
                zigbee_test_utils.build_bind_request(
                    mock_device,
                    zigbee_test_utils.mock_hub_eui,
                    OnOff.ID
                )
            })
            test.socket.zigbee:__expect_send({
                mock_device.id,
                SimpleMetering.attributes.InstantaneousDemand:configure_reporting(
                    mock_device, 5, 3600, 5
                )
            })
            test.socket.zigbee:__expect_send({
                mock_device.id,
                SimpleMetering.attributes.CurrentSummationDelivered:configure_reporting(
                        mock_device, 5, 3600, 1
                )
            })
            test.socket.zigbee:__expect_send({
                mock_device.id,
                OnOff.attributes.OnOff:configure_reporting(
                        mock_device, 0, 0x12C
                )
            })
            mock_device:expect_metadata_update({ provisioning_state = "PROVISIONED" })
            assert(mock_device:get_field(zigbee_constants.SIMPLE_METERING_MULTIPLIER_KEY) == nil)
            assert(mock_device:get_field(zigbee_constants.SIMPLE_METERING_DIVISOR_KEY) == nil)

            -- If the device responds to the reads, the driver will save the new values,
            test.socket.zigbee:__queue_receive({ mock_device.id, SimpleMetering.attributes.Divisor:build_test_attr_report(mock_device, 100) })
            test.socket.zigbee:__queue_receive({ mock_device.id, SimpleMetering.attributes.Multiplier:build_test_attr_report(mock_device, 1) })
            test.wait_for_events()
            assert(mock_device:get_field(zigbee_constants.SIMPLE_METERING_MULTIPLIER_KEY) == 1)
            assert(mock_device:get_field(zigbee_constants.SIMPLE_METERING_DIVISOR_KEY) == 100)
        end
)

I packaged the driver here (https://bestow-regional.api.smartthings.com/invite/OzMgLmVWRD29). Please test with the real device.
I would prefer that this PR removes the ledvance-metering-plug subdriver and just adds the fingerprints for the devices. The only thing preventing that is if the devices do not respond to the read requests the driver issues for the multiplier and divisor.

Thanks for your feedback ,I use the driver that you packaged ,I found a issue ,that the Energy meter value displayed is incorrect ,the above screenshot show the energy meter is 7.0kWh, but the actual energy meter is 70.0Wh , and I change the driver to the sub driver and the Energy is displayed correct ,the energy meter value is 70.0Wh , and the following screenshot is the Plug change driver to sub driver . I think the PLUG COMPACT EU EM T can keep the current sub driver ,thank you very much .

cjswedes · 2026-06-10T14:32:14Z

Thank you for your prompt tests and responses. Lets keep the subdriver, I am not sure why its not working as expected.

Since there are other subdrivers that do similar things in the zigbee-switch-power subdriver (i.e. vimar, aurora-relay), please move this subdriver to be nested under zigbee-switch-power.

LQ107 · 2026-06-11T07:24:13Z

Thank you for your prompt tests and responses. Lets keep the subdriver, I am not sure why its not working as expected.

Since there are other subdrivers that do similar things in the zigbee-switch-power subdriver (i.e. vimar, aurora-relay), please move this subdriver to be nested under zigbee-switch-power.

Thanks for your feedback ,I will move sub driver to zigbee-switch-power

LQ107

Dear Reviewers,
Thank you for your comments. I have moved the sub-driver to the zigbee-switch-power directory and removed the old sub-driver load path. Please review it again. Thank you very much for your time.

cjswedes

This is very close to merging. Conflicts need to be resolved.

LQ107 · 2026-06-12T02:26:01Z

This is very close to merging. Conflicts need to be resolved.

Thanks for you comment , whether the min_api_versio=17 is correct?

github-actions · 2026-06-12T02:49:53Z

Invitation URL:
https://bestow-regional.api.smartthings.com/invite/qyMZppnN4Nlm

github-actions · 2026-06-12T02:53:18Z

Test Results

73 files ±0 515 suites ±0 0s ⏱️ ±0s
2 906 tests +2 2 904 ✅ +1 0 💤 ±0 0 ❌ - 1 2 🔥 +2
4 802 runs +2 4 800 ✅ +1 0 💤 ±0 0 ❌ - 1 2 🔥 +2

For more details on these errors, see this check.

Results for commit 73632d4. ± Comparison against base commit 42a6a23.

♻️ This comment has been updated with latest results.

github-actions · 2026-06-12T02:53:19Z

File	Coverage
All files	`96%`	✅
/home/runner/work/SmartThingsEdgeDrivers/SmartThingsEdgeDrivers/drivers/SmartThings/zigbee-switch/src/inovelli/init.lua	`98%`	✅
/home/runner/work/SmartThingsEdgeDrivers/SmartThingsEdgeDrivers/drivers/SmartThings/zigbee-switch/src/aqara/version/init.lua	`94%`	✅
/home/runner/work/SmartThingsEdgeDrivers/SmartThingsEdgeDrivers/drivers/SmartThings/zigbee-switch/src/color_temp_range_handlers/init.lua	`71%`	❌
/home/runner/work/SmartThingsEdgeDrivers/SmartThingsEdgeDrivers/drivers/SmartThings/zigbee-switch/src/inovelli/vzm32-sn/init.lua	`95%`	✅
/home/runner/work/SmartThingsEdgeDrivers/SmartThingsEdgeDrivers/drivers/SmartThings/zigbee-switch/src/lazy_load_subdriver.lua	`57%`	❌
/home/runner/work/SmartThingsEdgeDrivers/SmartThingsEdgeDrivers/drivers/SmartThings/zigbee-switch/src/init.lua	`92%`	✅
/home/runner/work/SmartThingsEdgeDrivers/SmartThingsEdgeDrivers/drivers/SmartThings/zigbee-switch/src/preferences.lua	`97%`	✅
/home/runner/work/SmartThingsEdgeDrivers/SmartThingsEdgeDrivers/drivers/SmartThings/zigbee-switch/src/frient-IO/init.lua	`88%`	❌
/home/runner/work/SmartThingsEdgeDrivers/SmartThingsEdgeDrivers/drivers/SmartThings/zigbee-switch/src/frient-IO/unbind_request.lua	`71%`	❌
/home/runner/work/SmartThingsEdgeDrivers/SmartThingsEdgeDrivers/drivers/SmartThings/zigbee-switch/src/configurations/init.lua	`98%`	✅
/home/runner/work/SmartThingsEdgeDrivers/SmartThingsEdgeDrivers/drivers/SmartThings/zigbee-switch/src/frient/init.lua	`94%`	✅
/home/runner/work/SmartThingsEdgeDrivers/SmartThingsEdgeDrivers/drivers/SmartThings/zigbee-switch/src/aqara/init.lua	`94%`	✅
/home/runner/work/SmartThingsEdgeDrivers/SmartThingsEdgeDrivers/drivers/SmartThings/zigbee-switch/src/laisiao/init.lua	`96%`	✅
/home/runner/work/SmartThingsEdgeDrivers/SmartThingsEdgeDrivers/drivers/SmartThings/zigbee-switch/src/tuya-multi/can_handle.lua	`90%`	✅
/home/runner/work/SmartThingsEdgeDrivers/SmartThingsEdgeDrivers/drivers/SmartThings/zigbee-switch/src/aqara-light/init.lua	`92%`	✅
/home/runner/work/SmartThingsEdgeDrivers/SmartThingsEdgeDrivers/drivers/SmartThings/zigbee-switch/src/zll-polling/init.lua	`81%`	❌
/home/runner/work/SmartThingsEdgeDrivers/SmartThingsEdgeDrivers/drivers/SmartThings/zigbee-switch/src/zigbee-switch-power/ledvance-metering-plug/can_handle.lua	`66%`	❌
/home/runner/work/SmartThingsEdgeDrivers/SmartThingsEdgeDrivers/drivers/SmartThings/zigbee-switch/src/inovelli/vzm30-sn/init.lua	`95%`	✅

Minimum allowed coverage is 90%

Generated by 🐒 cobertura-action against 73632d4

LQ107 · 2026-06-12T05:31:56Z

Dear Reviewers,
Thank you for your comments. I have update the sub-driver and removed the old sub-driver load path. Please review it again. Thank you very much for your time.

LQ107

Dear Reviewers, I have updated the sub-driver. Could you please review it again? Thank you very much.

cjswedes

LGTM once tests are passing

cjswedes · 2026-06-15T16:36:09Z

 zigbee_test_utils.prepare_zigbee_env_info()

 local function test_init()
-  test.disable_startup_messages()


This is one reason tests are failing (the startup messages should be disabled, otherwise init runs automatically). The other reason is because since this is now nested under the zigbee-switch-power subdriver, you need to add the ledvance fingerprints to that list of fingerprints also https://github.com/SmartThingsCommunity/SmartThingsEdgeDrivers/blob/main/drivers/SmartThings/zigbee-switch/src/zigbee-switch-power/fingerprints.lua

LQ107 added 30 commits January 26, 2026 17:55

ledvance zigbee meter plug driver pull

c8278e8

add the handle file

316276d

add driver fingerprints

c01a9d0

modify the ledvance zigbee meter plug device Label

5e5a387

add driver for PLUG EU EM T

98aafe1

delete the PLUG EU EM T driver

6a76283

Update the PLUG COMPACT EU EM T device driver

14de7ba

set the multiplier and divisor fields in the initial handler

99ce6ea

disable the rely on the defaults to read the multiplier/divisor and A…

22bc75b

…dd driver registration processing

fixing the init.lua multiplier/divisor handle ,fixing the commit conf…

b81fa6b

…lict

update sub driver init.lua files

328797c

Merge branch 'main' into ledvance_zigbee_meter_plug

8f598e7

Remove unnecessary files

5004c95

Merge branch 'main' into ledvance_zigbee_meter_plug

09b89b7

Remove redundant code

3a46f9d

Merge branch 'ledvance_zigbee_meter_plug' of https://github.com/LQ107…

b7eb6b6

…/SmartThingsEdgeDrivers into ledvance_zigbee_meter_plug

Merge branch 'main' into ledvance_zigbee_meter_plug

6b409cb

Merge branch 'main' into ledvance_zigbee_meter_plug

41d31e7

1.add the test unit 2. add sub driver register 3.fixing the energy_me…

28e7783

…ter_handler issue

revert the gitgnore file to the default

875c75f

Merge branch 'ledvance_zigbee_meter_plug' of https://github.com/LQ107…

4011278

…/SmartThingsEdgeDrivers into ledvance_zigbee_meter_plug

Merge branch 'main' into ledvance_zigbee_meter_plug

3347541

Merge branch 'main' into ledvance_zigbee_meter_plug

6063c89

Merge branch 'main' into ledvance_zigbee_meter_plug

9424f57

Merge branch 'main' into ledvance_zigbee_meter_plug

2f5fe4b

1.fixing the energy meter value redundant processing 2.change the loc…

d02ef90

…ation of the test file

Merge branch 'ledvance_zigbee_meter_plug' of https://github.com/LQ107…

c6d53e8

…/SmartThingsEdgeDrivers into ledvance_zigbee_meter_plug

Merge branch 'main' into ledvance_zigbee_meter_plug

6ee58b2

Merge branch 'main' into ledvance_zigbee_meter_plug

2c5a233

Merge branch 'main' into ledvance_zigbee_meter_plug

420f963

LQ107 commented Jun 2, 2026

View reviewed changes

LQ107 requested a review from aleclorimer June 2, 2026 06:01

cjswedes reviewed Jun 2, 2026

View reviewed changes

add Min api version

126d24a

LQ107 commented Jun 3, 2026

View reviewed changes

PLUG EU EM T only add fingerprints

107f072

LQ107 commented Jun 9, 2026

View reviewed changes

cjswedes reviewed Jun 9, 2026

View reviewed changes

LQ107 added 2 commits June 11, 2026 14:49

move sub driver path to zigbee-switch-power

93d250f

remove the old citations of the PLUG COMPACT EU EM T

aa8103b

LQ107 commented Jun 11, 2026

View reviewed changes

cjswedes reviewed Jun 11, 2026

View reviewed changes

Comment thread ...rs/SmartThings/zigbee-switch/src/zigbee-switch-power/ledvance-metering-plug/fingerprints.lua Outdated

PLUG EU EM T add sub driver model

70b6187

Merge branch 'main' into Ledvance_Zigbee_EM_EU_PLUG

d1d7e2e

LQ107 added 2 commits June 12, 2026 13:06

remove old sub driver files

f62199f

remove old sub driver load

73632d4

LQ107 requested a review from cjswedes June 12, 2026 05:32

LQ107 commented Jun 12, 2026

View reviewed changes

cjswedes approved these changes Jun 15, 2026

View reviewed changes

	-- Additional one time configuration
	if device:supports_capability(capabilities.energyMeter) or device:supports_capability(capabilities.powerMeter) then
	local clusters = require "st.zigbee.zcl.clusters"
	-- Divisor and multipler for EnergyMeter
	device:send(clusters.SimpleMetering.attributes.Divisor:read(device))
	device:send(clusters.SimpleMetering.attributes.Multiplier:read(device))
	end

Conversation

LQ107 commented Jun 1, 2026

Type of Change

Checklist

Description of Change

Summary of Completed Tests

Uh oh!

LQ107 left a comment

Choose a reason for hiding this comment

Uh oh!

cjswedes Jun 2, 2026

Choose a reason for hiding this comment

Uh oh!

LQ107 Jun 3, 2026

Choose a reason for hiding this comment

Uh oh!

cjswedes Jun 3, 2026

Choose a reason for hiding this comment

Uh oh!

LQ107 Jun 4, 2026

Choose a reason for hiding this comment

Uh oh!

cjswedes Jun 4, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

LQ107 Jun 8, 2026

Choose a reason for hiding this comment

Uh oh!

LQ107 left a comment

Choose a reason for hiding this comment

Uh oh!

cjswedes commented Jun 4, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

LQ107 commented Jun 9, 2026

Uh oh!

LQ107 commented Jun 9, 2026

Uh oh!

LQ107 left a comment

Choose a reason for hiding this comment

Uh oh!

cjswedes left a comment

Choose a reason for hiding this comment

Uh oh!

LQ107 commented Jun 10, 2026

Uh oh!

cjswedes commented Jun 10, 2026

Uh oh!

LQ107 commented Jun 11, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

LQ107 left a comment

Choose a reason for hiding this comment

Uh oh!

cjswedes left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

LQ107 commented Jun 12, 2026

Uh oh!

github-actions Bot commented Jun 12, 2026

Uh oh!

github-actions Bot commented Jun 12, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Test Results

Uh oh!

github-actions Bot commented Jun 12, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

LQ107 commented Jun 12, 2026

Uh oh!

LQ107 left a comment

Choose a reason for hiding this comment

Uh oh!

cjswedes left a comment

Choose a reason for hiding this comment

Uh oh!

cjswedes Jun 15, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

cjswedes Jun 4, 2026 •

edited

Loading

cjswedes commented Jun 4, 2026 •

edited

Loading

LQ107 commented Jun 11, 2026 •

edited

Loading

github-actions Bot commented Jun 12, 2026 •

edited

Loading

github-actions Bot commented Jun 12, 2026 •

edited

Loading

cjswedes Jun 15, 2026 •

edited

Loading