(EDGE Driver-Mc) Zigbee switch MC, Zigbee switch power MC, Zigbee multi switch and child MC

Devices & Integrations Community Created Device Types
,
1006

Yup, the SPLZB-131/Develco Products.

Clearing the app cache on my Samsung phone makes no difference. Using a different SPLZB-131 plug (factory reset and then paired) and the CLI the following log may give the answer to the “temperature issue”? 2 other device&driver combos yield identical logs.

What is strange though is that in a previous version of the driver (or the corresponding TEST driver?) the temp field in the app showed up but the temp was stuck at the temp at pairing)

1007

Have two Smartthings outlets (Au latest versions)
Running the Zigbee Switch Power Mc driver.
Both were working now for some months then in last day or so It fails with following message:
“A network or server error occured. Try again later.”
This has been the same for several hours.
If I switch back to the Zigbee Switch driver all is ok (except I lose the aditional features).

1008

2023-06-01T20:48:16.956250633+00:00 INFO Zigbee Switch Power Mc <ZigbeeDevice: a19a34f6-0b12-4596-af04-6aab26ab3b47 [0x7503] (Xxxx SPLZB-131 Plug)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x7503, src_endpoint: 0x02, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: DeviceTemperatureConfiguration >, lqi: 0xD2, rssi: -79, body_length: 0x0009, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x17, ZCLCommandId: 0x01 >, < ReadAttributeResponse || < AttributeRecord || AttributeId: 0x0000, ZclStatus: SUCCESS, DataType: Int16, CurrentTemperature: 35 > > > >
2023-06-01T20:48:17.009736300+00:00 TRACE Zigbee Switch Power Mc Found ZigbeeMessageDispatcher handler in Zigbee_Switch_power → Device Temperature
2023-06-01T20:48:17.036159966+00:00 INFO Zigbee Switch Power Mc Executing ZclClusterAttributeValueHandler: cluster: DeviceTemperatureConfiguration, attribute: CurrentTemperature
2023-06-01T20:48:17.039691633+00:00 PRINT Zigbee Switch Power Mc <<<< value.value = 35
2023-06-01T20:48:17.047719633+00:00 WARN Zigbee Switch Power Mc Attempted to generate event for a19a34f6-0b12-4596-af04-6aab26ab3b47.main but it does not support capability Temperature Measurement

Good morning @S.F.B

In the log it is seen that now the temperature is being received from the device and the value 35° is being processed in the subdriver.
Sure enough, it tries to emit the event but says that the profile, component main does not have the temperature capability.

Very strange, the profile has the temperature capability and as you said in previous versions it appeared correctly in the app.

I understand less and less some things that happen, I’ll look at it and tell you something

1009

This is a problem with the stock driver. When you change to other driver, the divisor that is stored in permanent memory is deleted and when you return to the stock driver, the doConfigure lifecycle is not executed, which is where the key divisor is read and stored in permanent memory.

If you remove the device and pair it directly with the stock driver, it should work fine again.

If this is confirmed, then the device use the same divisor for power and energy, since it only have cluster 0702.

In my driver if you put “Custom Simple Metering Divisor” to value 10 in preferences it must work fine.

With log I could see if device only send simpleMetering cluster messages.

This is the tutorial to instal CLI and send logs

1010

Hi @Geoffs

1011

Hi @S.F.B

try with this driver version.
The problem seems to be in the preference to change the icon with a profile change, which this profile shouldn’t have. I have deleted the preference and the profile temperature capability already appears.

───────────────────────────────────────────────────
 Name         Zigbee Switch Power Mc
 Version      2023-06-02T09:24:46.016396567        
───────────────────────────────────────────────────
1012

I’ll try. I guess there is no way to pull a new version?

(Meaning all devices using a particular driver where a new version is available need to be switched to using a temporary driver, the current driver deleted and reinstalled, the temporary driver swapped with the new one one device at a time…? Or, wait for maybe 12 hours…)

1013

Hi @S.F.B

You can install driver with CLI command driver: install

1014

Hi @S.F.B

In my hub it has already been updated automatically, 6 hours after publication

1015

Very good!
I’ve been using the latest version (2023-06-02…) of Zigbee Switch Power MC for a number of Develco SPLZB-131 at location for a couple of days and they all work Great!

Thank you very very much!

1 Like
1016

Hi again, @Mariano_Colmenarejo
I have Zigbee plug Innr SP220 working with Zigbee switch edge driver and cant change to Zigbee switch power mc driver… I suppose because SP220 is not in fingerprint file.
If so, is it possible to add it?
Thanks in advance for your support

id: “Innr SP 220”
deviceLabel: innr Plug
manufacturer: innr
model: SP 220
deviceProfileName: switch-power-energy-plug

1017

All my socket

Screenshot_20230606-180126
Screenshot_20230606-1801261440×3120 301 KB

Not work from 24 May.
I use this drive
Zigbee Switch Power Mc version 2.06.23
And i have firmware 48.3 (i think from 24 May because I’m in beta , but I’m not sure about the date of 48.3 arrive in my hub)

I try to change drive, reboot hub, bit not change

1018

Hi @Diegocampy

Some users had problems with updating old version of the driver.
Reinstalling driver solves the problem. I think so!!, since when some users have a problem they ask desperately, get a possible solution and then they don’t say anything about whether it is solved or not. I don’t care, but it would make it useful for other users to know if that is the solution to the problem

2 Likes
1019

Hi @Bernfp
This device in the stock zigbee switch driver has basic-switch profile and does not measure power and energy.

 - id: "innr/SP 220"
    deviceLabel: Innr Outlet
    manufacturer: innr
    model: "SP 220"
    deviceProfileName: basic-switch

I can’t put it in the zigbee switch power Mc driver if they don’t have the necessary clusters.
I could add it to the Switch Mc zigbee driver

1020

Hi @Mariano_Colmenarejo
Understood. I’ll continue with Zigbee Switch Mc driver.
Kind regards

1021

I understand your frustration and it seems to me the least for what you do. I’ll do this test and then I’ll tell you

1022

Sorry about delay in response.
The 2 failed devices were showing the latest driver.
But when I removed and readded they now work.

1 Like
1023

Yes, after test I can confirm it.
I remove the drive from all my device, deleted the drive, and reinstall it, now work fine, thank you.

1 Like
1024

Hi there. I request to add a driver for my Tuya door sensor ZD08 model.

It is as follows

Debug
Actual _TZ3000_7d8vme6f
Expected _TZE200_pay2byax
Profile normal-contactSensor-v2
Mode Similarity
Preferences Modified
Exposes EF00 No
Default DP Yes

Device Information:

Manufacturer:_TZ3000__7d8vme6f
Model: TS0203
FingerPrinted_EndPoint. Id: O
App Version: Unknown
ZCL Version: Unknown
Network ID: OxC7D8
Zigbee EUl: A4C1381C31090
Device ID: 4afeb093-bd25-4c89de03541df

Server Cluster:Ep: 0x01={ 0001,0003,0500

Client Clusters:Ep: 0x01={0003,0004,0005,0006,000000A }

Signal Metrics:

Thank you.

1025

Hi @INHO_KIM

Added to this driver version

───────────────────────────────────────────────────
 Name         Zigbee Contact Mc
 Version      2023-06-07T11:11:49.177136508        
───────────────────────────────────────────────────
- id: "_TZ3000__7d8vme6f/Contact Sensor"
    deviceLabel: TS0203 Contact Sensor
    manufacturer: _TZ3000__7d8vme6f
    model: TS0203
    deviceProfileName: contact-battery-profile