Hello! I want to request add device fingerprint to zigbee-temp-humidity-sensor.
Thank you for your commitment to community.

• Tuya Zigbee Temperature Humidity Sensor With Backlight https://www.aliexpress.com/item/1005003980647546.html

Mfg Code | _TZE200_whkgqxse
Model | TS0601

Below is one added to Hubitat.

https://github.com/kkossev/Hubitat/blob/main/Drivers/Tuya%20Temperature%20Humidity%20Illuminance%20LCD%20Display%20with%20a%20Clock/Tuya_Temperature_Humidity_Illuminance_LCD_Display_with_a_Clock.groovy#L182

Hello! I want to request add device fingerprint to Zigbee Motion Sensor Mc (I think, I´m new to all this world).
Thank you for your commitment to community.

Tuya PIR motion sensor https://aliexpress.com/item/1005004845802129.html
Mfg Code | _TZ3000_6ygjfyll
Model | TS0202

Thanks in advance for all your help.

Hi,

can you please add the following to Edge Driver Zigbee Light Multifunction Mc

• Manufacturer: IKEA of Sweden
• Model: TRADFRI bulb E27 WS opal 1000lm

I think this is the correct profile: level-colortemp-2200-4000

Thanks

Hi Mario, Visonics MCT-350 SMA temperature reading not working. Request fix please.
Thanks

You driver was working brilliantly for me, with 4 external temperature probes connected. However, sometime before 20 April 04:00 CET, the reading for the first probe in the "virtual" device had been replaced with the word "Connected". The settings avaiable for this device are thre same as those for the actual physical device rather than the virtual device settings shown for the other 3 probres.

Hi Mariano,

could you please check for Nice gate motor opener (IBT4ZWAVE) will fit to any of zwave drivers?
The one I'm using at my home is: https://products.z-wavealliance.org/products/3837?selectedFrequencyId=1

I tested it with stock DTH Z-Wave Window Shade, stock DTH Z-Wave Basic Window Shade and it's working flawlessly. Also, I remember it was working with Fibaro FGR-223 DTH without issues.

MSR: 0441-2400-1000
manufacturer: null
networkSecurityLevel: ZWAVE_S2_FAILED

zw:L type:1100 mfr:0441 prod:2400 model:1000 ver:7.00 zwv:7.13 lib:03 cc:5E,26,85,8E,59,5A,7A,87,72,73,98,9F,6C,55,86,71,22,75,70

Thank you a lot,
Toma

Hello Mariano,

I did select a 2 gang switch as Multi-Title and later back to Single-Title, but the icon in the app still as Multi-Title.
Even when I selected another driver (Zigbee Thing Mc) the button still with Multi-Title appearance, but without switch button.
Is this something in my app or a know issue? Thanks!

Imagem to Single-Title and Thing drivers:

Hi Mariano,

can you please add this fingerprint to your multi-switch driver. It doesn't appear to report a manufacturer id.

zigbeeManufacturer:
  - id: "TERNCY-SM01-D3"
    deviceLabel: TERNCY-SM01-D3
    model: TERNCY-SM01-D3
    deviceProfileName: three-switch

Thanks
Ian

Hello Mariano,

Can you please add the following fingerprint for the Philio PAN11-1B. The switch works but the metering doesn't.

Id: 24420aaa-9708-451c-a3ba-9946a67ab465
DNI: 0x3D
Manufacturer: 0x013C
Product Type: 0x0001
Product ID: 0x0011

Please add a fingerprint for Sengled Element Color Plus Bulb - E12-N1EW https://www.amazon.com/gp/product/B092D8B6FT/ref=ppx_yo_dt_b_search_asin_title?ie=UTF8&th=1

Data from my IDE for one of these bulbs. They're RGBW bulbs. Please let me know if any other data/info is needed on these.

Data
zigbeeNodeType: NON_SLEEPY_END_DEVICE
firmwareManufacturerCode: 4448
firmwareFullVersion: 0000001E
application: 1E
endpointId: 01
firmwareImageType: 1016
manufacturer: sengled
model: E12-N1E

Raw Description |
01 0104 0102 00 0C 0000 0003 0004 0005 0006 0008 0300 0702 0B05 FC03 FC04 FC13 01 0019

Hello,
Can you please add the Thermostat Evolveo fingeprint as follow?

Manufacturer: _TZE200_8whxpsiw
Model: TS0601
Server Cluster: Ep: 01={ 0000,0004,0005,EF00 }
Client Clusters: Ep: 01={ 0019,000A }

Thank you.
Ondrej

Hello Mariano,

Please include the Philips Hue Smart Button into the edge driver st-zigbee-button. This button does not measure temperature and I believe it only supports 1 click actions.

Manufacturer: Signify Netherlands B.V.
Model: ROM001
FingerPrinted_EndPoint.Id: 0x01
App Version: 0x02
ZCL Version: 0x02
Network ID: 0x3CF9
Zigbee EUI: 001788010803E748
Device ID: ab26634f-b55b-4fbf-8f5c-227ebe60dc48
Server Cluster: Ep: 0x01={ 0000,0001,0003,FC00,1000 }
Client Clusters: Ep: 0x01={ 0019,0000,0003,0004,0006,0008,0005,1000 }

Thanks in advance.

After installation, turn off all switches and turn them on, after a few seconds the power is momentarily turned off and instantly restored. After that, it has been on for a long time without any problems, but if I turn off all the switches without using it and turn them on again, the problem occurs again. I'm using a 3gang _TZ3000_wyhuocal switch. What's the matter?

Hi,

can you please update the fingerprint. This device is a single Zigbee 3.0 plug with power metering:

manufacturer: _TZ3000_typdpbpg
model: TS011F

Thanks

Hello Mariano,

Can you please add the following fingerprint for the greenwave powernode 6 NP310-F:

Id: 7472db29-706f-45a1-a12f- 5d089c6acf30
DNI: 0×3B
Manufacturer: 0x0099
Product Type: 0x0003
Product ID: 0x0004

It's a 6 port powerstrip which should have metering capabilities on every one of the ports, however the device handlers have always been problematic so I'd be surprised if metering actually works now.

If just the switches work I'd be happy enough.

-id: “IKEA/TRADFRIbulbGU10WS345lm”
  deviceLabel: IKEA GU10 Bulb
  manufacturer: IKEA of Sweden
  model: TRADFRIbulbGU10WS345lm
  deviceProfileName: level-colortemp-2700-6000

https://zigbee.blakadder.com/Ikea_LED1923R5.html

- id: "TS011F/_TZ3000_gvn91tmx"
  deviceLabel: Aubess Plug
  manufacturer: _TZ3000_gvn91tmx
  model: TS011F
  deviceProfileName: single-switch-plug

https://aliexpress.com/item/1005005122047276.html
https://www.zigbee2mqtt.io/devices/TS011F_plug_1.html

There are default names to switch-2, switch-3 ..., and there is no way to rename them.
Also allow an option to make the "All-On-All-off" toggle the primary action instead of it being the switch-1

Hello. I'd like to request an additional fingerprint.

1gang zemismart switch
manufacturer: _TZ3000_ilauzyjm
model: TS0011

2gang zemismart switch
manufacturer: _TZ3000_rbl8c85w
model: TS0012

3gang zemismart switch
manufacturer: _TZ3000_lrgccsxm
model: TS0013

I am having a happy daily life with your knowledge.
I hope your daily life is happy, too.

Zigbee swich mc edge add fingerprint please.

2gang moes inner module

TS011F
TZ3000_pmz6mjyu

Hello,

I just purchased a MoesGo ZigBee Smart Switch - 3 gang. I already have two of these devices, with model number ZS-EUB (ID _TZ3000_qewo8dlz) but the new one appears to be ZTS-EUB and has a identifier _TZE200_tz32mtza .

If it is likely it will work with this driver, can you please add the following fingerprint:

  - id: "Moes/_TZE200_tz32mtza"
    deviceLabel: Moes TZE200 Switch
    manufacturer: _TZE200_tz32mtza
    model: TZE200
    deviceProfileName: three-switch

I will then happily test and let you know if all works as expected. Thank you.

Marc

Capability not working on app. When using edge:create it complains about missing "name".

Hi Mariano,

hope you are well.

Can you please add the following:

• manufacturer: IKEA of Sweden
• model: TRADFRIbulbB22WSglobeopal1055lm
• zigbeeNodeType: ROUTER

Note: The model doesn't follow IKEA's usual format.

It is a dimmable white bulb with changeable temperature.

Thanks
Ian

Hello Mariano, please add a fingerprint for Jinvoo smart socket (multiswitch).

https://www.amazon.com/Jinvoo-Individual-switches-SmartThings-Certified/dp/B0B4W76NX6/ref=sr_1_2?crid=5BMT2S4SUOSP&keywords=jinvoo+smart+zigbee&qid=1668537607&sprefix=jinvoo+smart+zigbe%2Caps%2C261&sr=8-2

In this device the 3 ports are controllable, 2 outlets and the USB port. They work just fine in HomeAssistant but I'd rather have them configured in Smartthings.

Device data taken from IDE:

application: 43
endpointId: 01
manufacturer: _TZ3000_wc2uoeah
model: TS011F
zigbeeNodeType: ROUTER

Raw Description 01 0104 010A 01 07 0000 0003 0004 0005 0006 E000 E001 02 0019 000A

Please let me know if any further information is required.

Please update the Fingerpint

TS011F
TZ3000_pmz6mjyu

_TZ3000_wyhuocal has the same two-minute issue as _TZ3000_fvh3pjaz, please fix it

I have exchanged couple emails with Eurotronic support, but without any result. The device registers as Dimmer Switch in SmartThings and there seem no suitable driver alternative to make it work.

It's https://eurotronic.org/wp-content/uploads/2023/04/Comet-Z-Wave-EN-2023-04-06.pdf

Thank you for the answer.

Hello Mariano, one more request bro. Pease add this device fingerprint to the Zigbee-Switch driver, there are other fingerprints in the driver but none of them matches this device. Thanks in advance.

Device Information:
Manufacturer: _TZ3000_bmzfjnbp
Model: TS0011
FingerPrinted_EndPoint.Id: 0x01
App Version: 0x44
ZCL Version: 0x03
Network ID: 0xC940
Zigbee EUI: 943469FFFEB7A1BD
Device ID: 2a4e29cd-f697-4827-83de-
9f1ae4ff492c

Server Cluster:
Ep: 0x01={
0000,0003,0004,0005,0006,E000,E001 }

Client Clusters:
Ep: 0x01={0019,000A }
Ep: 0xF2={0021}

Signal Metrics:
LQI: 192.... RSSI: -65 dbm

Device:
https://www.aliexpress.com/item/1005004887397411.html?spm=a2g0o.order_list.order_list_main.17.ea0c180268h9Qc

Mariano... another one. Regards.

"bulbshit": https://pt.aliexpress.com/item/1005004626576014.html?spm=a2g0o.order_list.order_list_main.87.8cb7caa4bo32ro&gatewayAdapt=glo2bra

• id: "eWeLink/Z102LG03-1"
  deviceLabel: eWeLink Z102LG03-1
  manufacturer: eWeLink
  model: Z102LG03-1
  deviceProfileName: rgbw-level-colortemp-2700-6500

There is a problem that _TZ3000_wyhuocal still turns off after 2 minutes. Please check and correct.

Could you add Fingerprints for "Forest Shuttle L Z-Wave" curtain motor? It was working fine with standard Z-Wave Window Shade DTH before edge drivers released.

Screenshot from groovy page and pdf manual from manufacturer attached.
(Device don't have battery. Always knows current curtain position, even if it was changed manually without electric power) - if it's important. Let me know if you need any other info.

download_287_Installing the FOREST SHUTTLE S-M-L Z-wave V1_6EN.pdf

46.0kWh is too high value. It is just one day use.
When I checked with other edge driver, it is displayed as 460Wh.

Hello! New to the world of Smartthing EDGE, we had our devices registered in the previous version in .groovy.
I want to request add device fingerprint to zigbee-multi-switch-v4.5-childs-edge.

Thank you in advance for sharing this with the community.

My information for the 2 fingerprint are:

• id: "NodOn/SIN-4-1-20"
  deviceLabel: "Multifunction Relay Switch"
  manufacturer: NodOn
  model: SIN-4-1-20
  deviceProfileName: NodOn Multifunction Relay Switch

• id: "NodOn/SIN-4-1-20-PRO"
  deviceLabel: "Multifunction Relay Switch PRO"
  manufacturer: NodOn
  model: SIN-4-1-20-PRO
  deviceProfileName: NodOn Multifunction Relay Switch PRO

The both are dual switch (2 endpoints).

https://nodon.fr/en/nodon/zigbee-on-off-lighting-relay-switch/

Thanks in advance for all your help.
Emilie

Hi,

Please add support for D-link motion sensor DCH-B122
https://www.dlink.com/en/products/dch-b122-mydlink-smart-diy-motion-sensor

Data

application: 47
endpointId: 01
manufacturer: D-Link
model: DCH-B122
zigbeeNodeType: SLEEPY_END_DEVICE

Raw Description

01 0104 0402 01 07 0000 0001 0003 0020 0500 0B05 FC81 01 0019

Hi Mariano,
I am complete new to the topic of Edge Driver for SmartThings, so I have to apologize for my question:
Looks that my purchased Innr Color Bulb are not exactly mentioned in your Light Multifunction MC fingerprint, and therefore might not be recorgnized by searching in ST app. You have BY 286 C, but not RB 286 C - which I have - Could that be the issue of not finding? I have copied the data out of SmartthingsHub config which the bulb is connecting to, not using the edge driver.

Data | application: 24
endpointId: 01
manufacturer: innr
model: RB 286 C
zigbeeNodeType: ROUTER

Raw Description | 01 0104 010D 01 0A 0000 0003 0004 0005 0006 0008 0300 1000 FC57 FC82 01 0019

Hope you can help me on this; Great thanks in advance and best regards Ingo

Hi Mariano,

can you please add this Zigbee siren. It is just a basis siren without a switch:

Thanks
Ian

Manufacturer: _TZE204_t1blo2bj
Model: TS0601
FingerPrinted_EndPoint.Id: 0x01
App Version: 0x4A
ZCL Version: 0x03

Server Cluster:
Ep: 0x01={ 0004,0005,EF00,0000 }

Client Clusters:
Ep: 0xF2={ 0021 }
Ep: 0x01={ 0019,000A }

Hello! I want to request add device fingerprint to Zigbee Multi Switch and Child Mc (at least that´s the driver that fits best).
Thank you for your commitment to community.

Aqara H1 Smart Dimmer Switch https://es.aliexpress.com/item/1005005253857998.html
Mfg | Aqara
Model | ZNXNKG02LM

Thanks in advance for all your help.

Hi, first of all, thank you for the effort you put into these drivers!

I am trying to add my Sercomm Open/Closed Sensor (Quirky Tripper) to smartthings but after adding it, the device is unresponsive. When looking at the driver logs, I can see a the follow error which I assume is causing my problem.

2023-03-14T12:27:39.226275629+00:00 PRINT Zigbee Contact Mc subdriver do_configure
2023-03-14T12:27:39.227414296+00:00 ERROR Zigbee Contact Mc Sercomm Open/Closed Sensor thread encountered error: [string "st/dispatcher.lua"]:233: Error encountered while processing event for <ZigbeeDevice: 90412f4f-5b61-473b-b572-cb4d71c10bc0 [0xAFEF] (Sercomm Open/Closed Sensor)>:
arg1: doConfigure
arg2: table: 0x1c5d330
[string "st/dispatcher.lua"]:233: Error encountered while processing event for <ZigbeeDevice: 90412f4f-5b61-473b-b572-cb4d71c10bc0 [0xAFEF] (Sercomm Open/Closed Sensor)>:
arg1: doConfigure
arg2: table: 0x1c5d330
[string "temperature/init.lua"]:39: attempt to perform arithmetic on a nil value (field 'maxTime')
2023-03-14T12:27:39.242849962+00:00 DEBUG Zigbee Contact Mc Sercomm Open/Closed Sensor device thread event handled'

────────────────────────────────────────────────────────────────────────────

Driver Id Name

────────────────────────────────────────────────────────────────────────────
1 cdb5df02-8915-474d-941c-3bc6acd46032 LAN Device Monitor
2 c411db9e-a042-459a-a145-f005c65412ee ST Zigbee Button Mc
3 0fd9a9a4-8863-4a83-97a7-5a288ff0f5a6 Virtual Devices V2
4 0ec75098-cf62-47c5-a23c-5bf7fb1f2dd6 Z-Wave Bulb Mc
5 7ca45ba9-7cfe-4547-b752-fe41a0efb848 Z-Wave Device Config Mc
────────────────────────────────────────────────────────────────────────────
6 e7947a05-947d-4bb5-92c4-2aafaff6d69c Z-Wave Fan
7 d58d8432-ea22-4d38-8300-2bd75fdf1358 Z-Wave Sensor
8 ea748a00-7990-4c87-8275-e15d45d9b40c Z-Wave Siren Mc
9 2cbf55e3-dbc2-48a2-8be5-4c3ce756b692 Z-Wave Switch
10 17c05c19-f008-42e2-aa12-f12f1aae5612 Z-Wave Switch and Child Mc
────────────────────────────────────────────────────────────────────────────
11 5197249e-95aa-4a27-a08f-2232d193e13b Z-Wave Thing Mc
12 3fb97b6c-f481-441b-a14e-f270d738764e Zigbee Button
13 408981c2-91d4-4dfc-bbfb-84ca0205d993 Zigbee Contact
14 b1504ded-efa4-4ef0-acd5-ae24e7a92e6e Zigbee Contact Mc
15 bb1b3fd4-dcba-4d55-8d85-58ed7f1979fb Zigbee Light Multifunction Mc
────────────────────────────────────────────────────────────────────────────
16 12e71b3b-184d-4b78-a0e4-679c02ca43dd Zigbee Moisture Sensor Mc
17 1eef4c45-5c94-4442-a771-0edfe41c8f4a Zigbee Multi Sensor Mc
18 e9bfd289-1d51-499e-8c64-d564d1868ad2 Zigbee Multi Switch and Child Mc
19 f2e891c6-00cc-446c-9192-8ebda63d9898 Zigbee Switch
20 bc53adfe-d18f-4ea4-9610-6aade6696b7a Zigbee Switch Mc
────────────────────────────────────────────────────────────────────────────
21 7fee6e41-26cc-49ef-b1f4-b30a43e02fe6 Zigbee Switch Power Mc
22 d692640b-402a-4d91-9151-d643ad4771f0 Zigbee Thing Mc
23 f82dec82-e5fa-487f-8f0f-22c3e4a8bd89 Zigbee Water Leak Sensor
────────────────────────────────────────────────────────────────────────────
? Select a driver. 14
connecting... connected
2023-03-14T12:01:09.833128495+00:00 DEBUG Zigbee Contact Mc driver device thread event handled
2023-03-14T12:01:39.834241509+00:00 DEBUG Zigbee Contact Mc driver device thread event handled
2023-03-14T12:02:09.852803017+00:00 DEBUG Zigbee Contact Mc driver device thread event handled
2023-03-14T12:02:39.843141031+00:00 DEBUG Zigbee Contact Mc driver device thread event handled
2023-03-14T12:03:10.023282712+00:00 DEBUG Zigbee Contact Mc driver device thread event handled
2023-03-14T12:03:39.853909060+00:00 DEBUG Zigbee Contact Mc driver device thread event handled
2023-03-14T12:04:09.854718074+00:00 DEBUG Zigbee Contact Mc driver device thread event handled
2023-03-14T12:04:39.907220755+00:00 DEBUG Zigbee Contact Mc driver device thread event handled
2023-03-14T12:05:09.868278769+00:00 DEBUG Zigbee Contact Mc driver device thread event handled
2023-03-14T12:05:39.864763450+00:00 DEBUG Zigbee Contact Mc driver device thread event handled
2023-03-14T12:06:09.915834287+00:00 INFO Zigbee Contact Mc Doing health check read for [EA63]:0500:0002
2023-03-14T12:06:09.927651859+00:00 INFO Zigbee Contact Mc <ZigbeeDevice: b2243242-efbb-4d2d-8582-25d0fe847949 [0xEA63] (Fridge Door Sensor)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0xEA63, dest_endpoint: 0x01, profile: 0x0104, cluster: IASZone >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x00 >, < ReadAttribute || AttributeId: 0x0002 > > >
2023-03-14T12:06:09.932937834+00:00 DEBUG Zigbee Contact Mc driver device thread event handled
2023-03-14T12:06:39.884770636+00:00 DEBUG Zigbee Contact Mc driver device thread event handled
2023-03-14T12:07:09.893165317+00:00 DEBUG Zigbee Contact Mc driver device thread event handled
2023-03-14T12:07:39.894797331+00:00 DEBUG Zigbee Contact Mc driver device thread event handled
2023-03-14T12:08:09.905132679+00:00 DEBUG Zigbee Contact Mc driver device thread event handled
2023-03-14T12:08:39.915103359+00:00 DEBUG Zigbee Contact Mc driver device thread event handled
2023-03-14T12:09:09.924741374+00:00 DEBUG Zigbee Contact Mc driver device thread event handled
2023-03-14T12:09:39.914732388+00:00 DEBUG Zigbee Contact Mc driver device thread event handled
2023-03-14T12:10:09.925337534+00:00 DEBUG Zigbee Contact Mc driver device thread event handled
2023-03-14T12:10:39.925054538+00:00 DEBUG Zigbee Contact Mc driver device thread event handled
2023-03-14T12:11:09.949339875+00:00 DEBUG Zigbee Contact Mc driver device thread event handled
2023-03-14T12:11:39.952383878+00:00 DEBUG Zigbee Contact Mc driver device thread event handled
2023-03-14T12:12:09.954747215+00:00 DEBUG Zigbee Contact Mc driver device thread event handled
2023-03-14T12:12:39.961497552+00:00 DEBUG Zigbee Contact Mc driver device thread event handled
2023-03-14T12:13:09.973365889+00:00 DEBUG Zigbee Contact Mc driver device thread event handled
2023-03-14T12:13:39.995422226+00:00 DEBUG Zigbee Contact Mc driver device thread event handled
2023-03-14T12:14:10.008721983+00:00 INFO Zigbee Contact Mc Doing health check read for [EA63]:0500:0002
2023-03-14T12:14:10.010562880+00:00 INFO Zigbee Contact Mc <ZigbeeDevice: b2243242-efbb-4d2d-8582-25d0fe847949 [0xEA63] (Fridge Door Sensor)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0xEA63, dest_endpoint: 0x01, profile: 0x0104, cluster: IASZone >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x00 >, < ReadAttribute || AttributeId: 0x0002 > > >
2023-03-14T12:14:10.034707522+00:00 DEBUG Zigbee Contact Mc driver device thread event handled
2023-03-14T12:14:40.002211778+00:00 DEBUG Zigbee Contact Mc driver device thread event handled
2023-03-14T12:15:09.994763459+00:00 DEBUG Zigbee Contact Mc driver device thread event handled
2023-03-14T12:15:40.009293473+00:00 DEBUG Zigbee Contact Mc driver device thread event handled
2023-03-14T12:16:10.084268487+00:00 DEBUG Zigbee Contact Mc driver device thread event handled
2023-03-14T12:16:40.025633168+00:00 DEBUG Zigbee Contact Mc driver device thread event handled
2023-03-14T12:17:10.024734182+00:00 DEBUG Zigbee Contact Mc driver device thread event handled
2023-03-14T12:17:40.064896863+00:00 DEBUG Zigbee Contact Mc driver device thread event handled
2023-03-14T12:18:10.044759865+00:00 DEBUG Zigbee Contact Mc driver device thread event handled
2023-03-14T12:18:40.224761552+00:00 DEBUG Zigbee Contact Mc driver device thread event handled
2023-03-14T12:19:10.154781889+00:00 DEBUG Zigbee Contact Mc driver device thread event handled
2023-03-14T12:19:40.195426226+00:00 DEBUG Zigbee Contact Mc driver device thread event handled
2023-03-14T12:20:01.717301895+00:00 TRACE Zigbee Contact Mc Received event with handler device_lifecycle
2023-03-14T12:20:01.718504895+00:00 INFO Zigbee Contact Mc <ZigbeeDevice: b2243242-efbb-4d2d-8582-25d0fe847949 [0xEA63] (Fridge Door Sensor)> received lifecycle event: removed
2023-03-14T12:20:01.720317895+00:00 TRACE Zigbee Contact Mc Received event with handler driver_lifecycle
2023-03-14T12:20:01.721511895+00:00 TRACE Zigbee Contact Mc <ZigbeeDevice: b2243242-efbb-4d2d-8582-25d0fe847949 [0xEA63] (Fridge Door Sensor)> received unhandled lifecycle event: removed
2023-03-14T12:20:01.722882229+00:00 DEBUG Zigbee Contact Mc Fridge Door Sensor device thread event handled
2023-03-14T12:20:01.754755562+00:00 DEBUG Zigbee Contact Mc Fridge Door Sensor device thread event handled
2023-03-14T12:27:38.945631962+00:00 TRACE Zigbee Contact Mc Setup driver zigbee_contact with lifecycle handlers:
DeviceLifecycleDispatcher: zigbee_contact
default_handlers:
doConfigure:
infoChanged:
driverSwitched:
init:
child_dispatchers:
DeviceLifecycleDispatcher: zigbee_contact -> Cell battery 2.1v
default_handlers:
init:
child_dispatchers:
DeviceLifecycleDispatcher: zigbee_contact -> Battery Voltage
default_handlers:
child_dispatchers:
DeviceLifecycleDispatcher: zigbee_contact -> Temp-Sensor
default_handlers:
doConfigure:
child_dispatchers:
DeviceLifecycleDispatcher: zigbee_contact -> Multiporpuse
default_handlers:
added:
child_dispatchers:
DeviceLifecycleDispatcher: zigbee_contact -> Multiporpuse -> SmartThings multi sensor
default_handlers:
child_dispatchers:

2023-03-14T12:27:38.947147295+00:00 TRACE Zigbee Contact Mc Setup driver zigbee_contact with Capability handlers:
CapabilityCommandDispatcher: zigbee_contact
default_handlers:
refresh:
refresh
child_dispatchers:
CapabilityCommandDispatcher: zigbee_contact -> Cell battery 2.1v
default_handlers:
child_dispatchers:
CapabilityCommandDispatcher: zigbee_contact -> Battery Voltage
default_handlers:
child_dispatchers:
CapabilityCommandDispatcher: zigbee_contact -> Temp-Sensor
default_handlers:
child_dispatchers:
CapabilityCommandDispatcher: zigbee_contact -> Multiporpuse
default_handlers:
child_dispatchers:
CapabilityCommandDispatcher: zigbee_contact -> Multiporpuse -> SmartThings multi sensor
default_handlers:
child_dispatchers:

2023-03-14T12:27:38.948559962+00:00 TRACE Zigbee Contact Mc Setup driver zigbee_contact with Zigbee handlers:
ZigbeeMessageDispatcher: zigbee_contact
default_handlers:
attr:
ZclClusterAttributeValueHandler: cluster: PowerConfiguration, attribute: BatteryVoltage
ZclClusterAttributeValueHandler: cluster: PowerConfiguration, attribute: BatteryPercentageRemaining
ZclClusterAttributeValueHandler: cluster: IASZone, attribute: ZoneStatus
global:
cluster:
ZclClusterCommandHandler: cluster: IASZone, command: ZoneEnrollResponse
zdo:
child_dispatchers:
ZigbeeMessageDispatcher: zigbee_contact -> Cell battery 2.1v
default_handlers:
attr:
global:
cluster:
zdo:
child_dispatchers:
ZigbeeMessageDispatcher: zigbee_contact -> Battery Voltage
default_handlers:
attr:
ZclClusterAttributeValueHandler: cluster: PowerConfiguration, attribute: BatteryVoltage
global:
cluster:
zdo:
child_dispatchers:
ZigbeeMessageDispatcher: zigbee_contact -> Temp-Sensor
default_handlers:
attr:
ZclClusterAttributeValueHandler: cluster: TemperatureMeasurement, attribute: MeasuredValue
global:
cluster:
zdo:
child_dispatchers:
ZigbeeMessageDispatcher: zigbee_contact -> Multiporpuse
default_handlers:
attr:
ZclClusterAttributeValueHandler: cluster: 0xFC02, attribute: 0x0014
ZclClusterAttributeValueHandler: cluster: 0xFC02, attribute: 0x0010
ZclClusterAttributeValueHandler: cluster: 0xFC02, attribute: 0x0012
ZclClusterAttributeValueHandler: cluster: 0xFC02, attribute: 0x0013
ZclClusterAttributeValueHandler: cluster: IASZone, attribute: ZoneStatus
global:
cluster:
ZclClusterCommandHandler: cluster: IASZone, command: ZoneEnrollResponse
zdo:
child_dispatchers:
ZigbeeMessageDispatcher: zigbee_contact -> Multiporpuse -> SmartThings multi sensor
default_handlers:
attr:
ZclClusterAttributeValueHandler: cluster: 0xFC02, attribute: 0x0010
ZclClusterAttributeValueHandler: cluster: 0xFC02, attribute: 0x0014
ZclClusterAttributeValueHandler: cluster: 0xFC02, attribute: 0x0012
ZclClusterAttributeValueHandler: cluster: 0xFC02, attribute: 0x0013
global:
cluster:
zdo:
child_dispatchers:

2023-03-14T12:27:39.105805295+00:00 TRACE Zigbee Contact Mc Zigbee Device: 90412f4f-5b61-473b-b572-cb4d71c10bc0
Manufacturer: Sercomm Corp. Model: Tripper
[1]: Basic, PowerConfiguration, Identify, IASZone, PollControl, Diagnostics
2023-03-14T12:27:39.106914295+00:00 DEBUG Zigbee Contact Mc driver device thread event handled
2023-03-14T12:27:39.108184962+00:00 TRACE Zigbee Contact Mc Received event with handler _resync
2023-03-14T12:27:39.109315629+00:00 TRACE Zigbee Contact Mc Received event with handler environment_info
2023-03-14T12:27:39.131537629+00:00 TRACE Zigbee Contact Mc Found DeviceLifecycleDispatcher handler in zigbee_contact
2023-03-14T12:27:39.132714962+00:00 INFO Zigbee Contact Mc <ZigbeeDevice: 90412f4f-5b61-473b-b572-cb4d71c10bc0 [0xAFEF] (Sercomm Open/Closed Sensor)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0xAFEF, dest_endpoint: 0x01, profile: 0x0104, cluster: PowerConfiguration >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x00 >, < ReadAttribute || AttributeId: 0x0020 > > >
2023-03-14T12:27:39.145446962+00:00 INFO Zigbee Contact Mc <ZigbeeDevice: 90412f4f-5b61-473b-b572-cb4d71c10bc0 [0xAFEF] (Sercomm Open/Closed Sensor)> emitting event: {"attribute_id":"signalMetrics","capability_id":"legendabsolute60149.signalMetrics","component_id":"main","state":{"value":"Waiting Zigbee Message"},"visibility":{"displayed":false}}
2023-03-14T12:27:39.175224296+00:00 DEBUG Zigbee Contact Mc Sercomm Open/Closed Sensor device thread event handled
2023-03-14T12:27:39.176427629+00:00 TRACE Zigbee Contact Mc Received event with handler environment_info
2023-03-14T12:27:39.207456962+00:00 DEBUG Zigbee Contact Mc Z-Wave hub node ID environment changed.
2023-03-14T12:27:39.208319629+00:00 TRACE Zigbee Contact Mc Received event with handler device_lifecycle
2023-03-14T12:27:39.209456962+00:00 INFO Zigbee Contact Mc <ZigbeeDevice: 90412f4f-5b61-473b-b572-cb4d71c10bc0 [0xAFEF] (Sercomm Open/Closed Sensor)> received lifecycle event: added
2023-03-14T12:27:39.211098296+00:00 TRACE Zigbee Contact Mc <ZigbeeDevice: 90412f4f-5b61-473b-b572-cb4d71c10bc0 [0xAFEF] (Sercomm Open/Closed Sensor)> received unhandled lifecycle event: added
2023-03-14T12:27:39.212285296+00:00 DEBUG Zigbee Contact Mc Sercomm Open/Closed Sensor device thread event handled
2023-03-14T12:27:39.213422629+00:00 TRACE Zigbee Contact Mc Received event with handler device_lifecycle
2023-03-14T12:27:39.214836962+00:00 INFO Zigbee Contact Mc <ZigbeeDevice: 90412f4f-5b61-473b-b572-cb4d71c10bc0 [0xAFEF] (Sercomm Open/Closed Sensor)> received lifecycle event: doConfigure
2023-03-14T12:27:39.225444962+00:00 TRACE Zigbee Contact Mc Found DeviceLifecycleDispatcher handler in zigbee_contact -> Temp-Sensor
2023-03-14T12:27:39.226275629+00:00 PRINT Zigbee Contact Mc subdriver do_configure
2023-03-14T12:27:39.227414296+00:00 ERROR Zigbee Contact Mc Sercomm Open/Closed Sensor thread encountered error: [string "st/dispatcher.lua"]:233: Error encountered while processing event for <ZigbeeDevice: 90412f4f-5b61-473b-b572-cb4d71c10bc0 [0xAFEF] (Sercomm Open/Closed Sensor)>:
arg1: doConfigure
arg2: table: 0x1c5d330
[string "st/dispatcher.lua"]:233: Error encountered while processing event for <ZigbeeDevice: 90412f4f-5b61-473b-b572-cb4d71c10bc0 [0xAFEF] (Sercomm Open/Closed Sensor)>:
arg1: doConfigure
arg2: table: 0x1c5d330
[string "temperature/init.lua"]:39: attempt to perform arithmetic on a nil value (field 'maxTime')
2023-03-14T12:27:39.242849962+00:00 DEBUG Zigbee Contact Mc Sercomm Open/Closed Sensor device thread event handled
2023-03-14T12:27:39.497131296+00:00 TRACE Zigbee Contact Mc Received event with handler device_lifecycle
2023-03-14T12:27:39.498098629+00:00 INFO Zigbee Contact Mc <ZigbeeDevice: 90412f4f-5b61-473b-b572-cb4d71c10bc0 [0xAFEF] (Sercomm Open/Closed Sensor)> received lifecycle event: infoChanged
2023-03-14T12:27:39.525467962+00:00 TRACE Zigbee Contact Mc Found DeviceLifecycleDispatcher handler in zigbee_contact
2023-03-14T12:27:39.526317629+00:00 PRINT Zigbee Contact Mc ***** infoChanged *********
2023-03-14T12:27:39.527463629+00:00 PRINT Zigbee Contact Mc device.preferences[infoChanged]= No preferences: signalMetricsVisibles
2023-03-14T12:27:39.528593296+00:00 PRINT Zigbee Contact Mc << Preference changed name: signalMetricsVisibles old value: nil new value: No
2023-03-14T12:27:39.529719296+00:00 PRINT Zigbee Contact Mc device.preferences[infoChanged]= preferences: version
2023-03-14T12:27:39.531182629+00:00 PRINT Zigbee Contact Mc << Preference changed name: version old value: nil new value:
2023-03-14T12:27:39.532687296+00:00 PRINT Zigbee Contact Mc Device ID <ZigbeeDevice: 90412f4f-5b61-473b-b572-cb4d71c10bc0 [0xAFEF] (Sercomm Open/Closed Sensor)>
2023-03-14T12:27:39.535867962+00:00 PRINT Zigbee Contact Mc Manufacturer >>> Sercomm Corp. Manufacturer_Len >>> 13
2023-03-14T12:27:39.537950629+00:00 PRINT Zigbee Contact Mc Model >>> Tripper Model_len >>> 7
2023-03-14T12:27:39.540028962+00:00 PRINT Zigbee Contact Mc Memory >>>>>>> 1072.5146484375 Kbytes
2023-03-14T12:27:39.542328962+00:00 PRINT Zigbee Contact Mc <<<<< Firmware Version >>>>> Unknown
2023-03-14T12:27:39.544536962+00:00 DEBUG Zigbee Contact Mc Sercomm Open/Closed Sensor device thread event handled
2023-03-14T12:27:39.779414629+00:00 TRACE Zigbee Contact Mc Received event with handler zigbee
2023-03-14T12:27:39.780387962+00:00 INFO Zigbee Contact Mc <ZigbeeDevice: 90412f4f-5b61-473b-b572-cb4d71c10bc0 [0xAFEF] (Sercomm Open/Closed Sensor)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0xAFEF, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: PowerConfiguration >, lqi: 0xC8, rssi: -66, body_length: 0x0008, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x7B, ZCLCommandId: 0x01 >, < ReadAttributeResponse || < AttributeRecord || AttributeId: 0x0020, ZclStatus: SUCCESS, DataType: Uint8, BatteryVoltage: 0x1B > > > >
2023-03-14T12:27:39.806115962+00:00 TRACE Zigbee Contact Mc Found ZigbeeMessageDispatcher handler in zigbee_contact -> Battery Voltage
2023-03-14T12:27:39.806968962+00:00 INFO Zigbee Contact Mc Executing ZclClusterAttributeValueHandler: cluster: PowerConfiguration, attribute: BatteryVoltage
2023-03-14T12:27:39.809776296+00:00 INFO Zigbee Contact Mc <ZigbeeDevice: 90412f4f-5b61-473b-b572-cb4d71c10bc0 [0xAFEF] (Sercomm Open/Closed Sensor)> emitting event: {"attribute_id":"signalMetrics","capability_id":"legendabsolute60149.signalMetrics","component_id":"main","state":{"value":"<em table style='font-size:70%';'font-weight: bold'GMT: 2023/03/14 Time: 12:27
DNI: 0xAFEF LQI: 200 RSSI: -66dbm
"},"visibility":{"displayed":false}}
2023-03-14T12:27:39.831717629+00:00 INFO Zigbee Contact Mc <ZigbeeDevice: 90412f4f-5b61-473b-b572-cb4d71c10bc0 [0xAFEF] (Sercomm Open/Closed Sensor)> emitting event: {"attribute_id":"battery","capability_id":"battery","component_id":"main","state":{"value":100}}
2023-03-14T12:27:39.833062629+00:00 DEBUG Zigbee Contact Mc Sercomm Open/Closed Sensor device thread event handled
2023-03-14T12:28:06.325127642+00:00 TRACE Zigbee Contact Mc Received event with handler zigbee
2023-03-14T12:28:06.326317642+00:00 INFO Zigbee Contact Mc <ZigbeeDevice: 90412f4f-5b61-473b-b572-cb4d71c10bc0 [0xAFEF] (Sercomm Open/Closed Sensor)> received Zigbee message: < ZigbeeMessageRx || type: 0x02, < AddressHeader || src_addr: 0xAFEF, src_endpoint: 0x00, dest_addr: 0x0000, dest_endpoint: 0x00, profile: 0x0000, cluster: OnOff >, lqi: 0xD0, rssi: -68, body_length: 0x0009, < ZDOMessageBody || < ZDOHeader || seqno: 0x02 >, GenericBody: FD FF 04 01 00 01 00 05 > >
2023-03-14T12:28:06.330070308+00:00 DEBUG Zigbee Contact Mc Sercomm Open/Closed Sensor device thread event handled
2023-03-14T12:28:08.949855310+00:00 DEBUG Zigbee Contact Mc driver device thread event handled
2023-03-14T12:28:38.957911324+00:00 DEBUG Zigbee Contact Mc driver device thread event handled
2023-03-14T12:29:08.961589338+00:00 DEBUG Zigbee Contact Mc driver device thread event handled
2023-03-14T12:29:38.971983686+00:00 DEBUG Zigbee Contact Mc driver device thread event handled
2023-03-14T12:30:08.981083700+00:00 DEBUG Zigbee Contact Mc driver device thread event handled
2023-03-14T12:30:38.991191444+00:00 DEBUG Zigbee Contact Mc driver device thread event handled
2023-03-14T12:31:09.014890459+00:00 DEBUG Zigbee Contact Mc driver device thread event handled
2023-03-14T12:31:39.022638473+00:00 INFO Zigbee Contact Mc Doing health check read for [AFEF]:0500:0002
2023-03-14T12:31:39.031358806+00:00 INFO Zigbee Contact Mc <ZigbeeDevice: 90412f4f-5b61-473b-b572-cb4d71c10bc0 [0xAFEF] (Sercomm Open/Closed Sensor)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0xAFEF, dest_endpoint: 0x01, profile: 0x0104, cluster: IASZone >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x00 >, < ReadAttribute || AttributeId: 0x0002 > > >
2023-03-14T12:31:39.036932473+00:00 DEBUG Zigbee Contact Mc driver device thread event handled
2023-03-14T12:32:09.017119821+00:00 DEBUG Zigbee Contact Mc driver device thread event handled
2023-03-14T12:32:39.104747835+00:00 DEBUG Zigbee Contact Mc driver device thread event handled
2023-03-14T12:33:09.014010516+00:00 DEBUG Zigbee Contact Mc driver device thread event handled
2023-03-14T12:33:39.021347864+00:00 DEBUG Zigbee Contact Mc driver device thread event handled
2023-03-14T12:34:09.023513878+00:00 DEBUG Zigbee Contact Mc driver device thread event handled
2023-03-14T12:34:39.031154402+00:00 DEBUG Zigbee Contact Mc driver device thread event handled
2023-03-14T12:35:09.033682417+00:00 DEBUG Zigbee Contact Mc driver device thread event handled
2023-03-14T12:35:39.041277098+00:00 DEBUG Zigbee Contact Mc driver device thread event handled

Hello Mariano,
Could you try 2 devices?

Window

• id: "_TZE200_cf1sl3tj/ZM85EL-2Z"
  deviceLabel: _TZE200_cf1sl3tj
  manufacturer: _TZE200_cf1sl3tj
  model: TS0601

Roller

• id: "_TZE200_7eue9vhc/ZM25RZ01"
  deviceLabel: _TZE200_7eue9vhc
  manufacturer: _TZE200_7eue9vhc
  model: TS0601

Hi Mariano,

I have several Enerwave ZWN-RSM2-PLUS devices throughout my home, and they all exhibit the same behavior after switching to your beta edge drivers.

Here's what works:
-Control both main and child switch from SmartThings app. Switch state is properly updated.
-Switch state updates for the main switch when manually toggled.

What doesn't work:
-Switch state does not update for the child switch when manually toggled.

I have one Monoprice dual relay installed as well, and it does properly update switch states when manually toggled. I am more than happy to provide logs or do any troubleshooting as necessary. Thank you so much for all the work that you do for this.

Chris

Hi Mariano,

Could you take a quick look if there is something wrong that could be making all my devices turn off randomly?
This one in the following log was ON, and just turn OFF with any interaction.

2022-10-25T17:10:33.256594005+00:00 TRACE Zigbee Tomadas WPlaza - MC Received event with handler zigbee

2022-10-25T17:10:33.270970818+00:00 INFO Zigbee Tomadas WPlaza - MC <ZigbeeDevice: 7bbc2c8f-e87c-4357-a05e-77fa6bb4cfae [0x14F3] (Sala Tomada James)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x14F3, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0x68, rssi: -74, body_length: 0x0007, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x08, seqno: 0xD1, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0000, DataType: Boolean, OnOff: false > > > >

2022-10-25T17:10:33.343094276+00:00 TRACE Zigbee Tomadas WPlaza - MC Found ZigbeeMessageDispatcher handler in Zigbee_Switch

2022-10-25T17:10:33.352434693+00:00 INFO Zigbee Tomadas WPlaza - MC Executing ZclClusterAttributeValueHandler: cluster: OnOff, attribute: OnOff

2022-10-25T17:10:33.365325609+00:00 INFO Zigbee Tomadas WPlaza - MC <ZigbeeDevice: 7bbc2c8f-e87c-4357-a05e-77fa6bb4cfae [0x14F3] (Sala Tomada James)> emitting event: {"attribute_id":"signalMetrics","capability_id":"legendabsolute60149.signalMetrics","component_id":"main","state":{"value":"LQI: 104 ... RSSI: -74 dBm"},"visibility":{"displayed":false}}

2022-10-25T17:10:33.476719068+00:00 INFO Zigbee Tomadas WPlaza - MC <ZigbeeDevice: 7bbc2c8f-e87c-4357-a05e-77fa6bb4cfae [0x14F3] (Sala Tomada James)> emitting event: {"attribute_id":"switch","capability_id":"switch","component_id":"main","state":{"value":"off"}}

2022-10-25T17:10:33.591623109+00:00 DEBUG Zigbee Tomadas WPlaza - MC Sala Tomada James device thread event handled

2022-10-25T17:10:33.604483172+00:00 TRACE Zigbee Tomadas WPlaza - MC Received event with handler zigbee

2022-10-25T17:10:33.620764463+00:00 INFO Zigbee Tomadas WPlaza - MC <ZigbeeDevice: 7bbc2c8f-e87c-4357-a05e-77fa6bb4cfae [0x14F3] (Sala Tomada James)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x14F3, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0x68, rssi: -74, body_length: 0x0007, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0xD3, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0000, DataType: Boolean, OnOff: false > > > >

2022-10-25T17:10:33.669589109+00:00 TRACE Zigbee Tomadas WPlaza - MC Received event with handler zigbee

2022-10-25T17:10:33.685278172+00:00 INFO Zigbee Tomadas WPlaza - MC <ZigbeeDevice: 7bbc2c8f-e87c-4357-a05e-77fa6bb4cfae [0x14F3] (Sala Tomada James)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x14F3, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: 0xE001 >, lqi: 0x64, rssi: -75, body_length: 0x000A, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x08, seqno: 0xD2, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0xD001, DataType: Bitmap32, Bitmap32: 0x00000004 > > > >

2022-10-25T17:10:33.737237630+00:00 TRACE Zigbee Tomadas WPlaza - MC Found ZigbeeMessageDispatcher handler in Zigbee_Switch

2022-10-25T17:10:33.747268547+00:00 INFO Zigbee Tomadas WPlaza - MC Executing ZclClusterAttributeValueHandler: cluster: OnOff, attribute: OnOff

2022-10-25T17:10:33.761006401+00:00 INFO Zigbee Tomadas WPlaza - MC <ZigbeeDevice: 7bbc2c8f-e87c-4357-a05e-77fa6bb4cfae [0x14F3] (Sala Tomada James)> emitting event: {"attribute_id":"signalMetrics","capability_id":"legendabsolute60149.signalMetrics","component_id":"main","state":{"value":"LQI: 104 ... RSSI: -74 dBm"},"visibility":{"displayed":false}}

2022-10-25T17:10:33.871136192+00:00 INFO Zigbee Tomadas WPlaza - MC <ZigbeeDevice: 7bbc2c8f-e87c-4357-a05e-77fa6bb4cfae [0x14F3] (Sala Tomada James)> emitting event: {"attribute_id":"switch","capability_id":"switch","component_id":"main","state":{"value":"off"}}

2022-10-25T17:10:33.907851859+00:00 DEBUG Zigbee Tomadas WPlaza - MC Sala Tomada James device thread event handled

2022-10-25T17:10:33.921946213+00:00 DEBUG Zigbee Tomadas WPlaza - MC Sala Tomada James device thread event handled

Hi,

Please add support for termostat from Tuya / Connecte.

I belive I found some information about the thermostat in another case: Koenkk/zigbee2mqtt#11895 :

zigbeeModel: ['hbx5cvx'],
fingerprint: [
{
modelID: 'TS0601',
manufacturerName: '_TZE200_4hbx5cvx'

In the routine, there is no separate selection menu to turn on/off the main switch and other switches, and there is a problem that the main switch is unconditionally turned on. Each switch needs a separate menu to turn it on and off.

Hi,

this device is a powerboard with 4 switchable plugs and 1 group of switchable USB ports (1 switch for 4 USB).

Currently when I add it, it is recognised by your Zigbee Mult Switch Mc driver, but only 4 switches in total are added (main+3).

Can you please update the fingerprint to make this a 5 switch plug.

Manufacturer

• _TZ3000_cfnprab5
  Model:
• TS011F

Thanks
Ian

Hello,
can you please add Lidl switch button as follow?

Manufacturer: _TZ3000_rco1yzb1
Model: TS004F
Server Cluster: Ep: 01={ 0000,0001,0003,0004,0006,1000,E001 }
Client Clusters: Ep: 01={ 0019,000A,0003,0004,0005,0006,0008, 1000 }

Thank you.
Ondrej

Hi dear,
How are you?
This is Sky from zemismart.com
Would u like to help us to write edge driver?
We will provide free samples.
Best regards,
Sky

Hi Mariano,

can you please add this fingerprint for irrigation valve:

Product page: https://wooxhome.com/products-c10/other-c4/woox-r7060-smart-garden-irrigation-control-p61

application: 45
endpointId: 01
firmwareFullVersion: 00000045
firmwareImageType: 5634
firmwareManufacturerCode: 4098
manufacturer: _TZ3210_eymunffl
model: TS0101
zigbeeNodeType: SLEEPY_END_DEVICE

I suppose bolded part is fingerprint.

Thanks,
Tomislav

Hi,

can you please add this device:

Thanks

Device Zooz ZEN31

When trying to change settings in Smartthings (build on:off etc), it may register the change 1-2 times then strlart receiving the following error in Smartthings:

"A neteork or server error occured. Please try again later."

Please Make Edge Driver of Zemismart LED Strip

TZ3210_k1pe6ibm(Manufacturer)_TS0505B(Model)

thank you