I hope this is what you need to ensure the Halo Bulbs work correctly with your driver. Thank you so much for all your help. This is learning curve but I’m getting there.
Could I get the following switch added to the zigbee switch driver?
Device Information:
Manufacturer: Jasco Products
Model: 43094
FingerPrinted EndPoint.Id: 0x01
App Version: Ox12
ZCL Version: 0x03
Network ID: 0x277C
Zigbee EUI: EC1BBDFFFEFAF460
Device ID: 6b85c6f6-712e-4aee-b527-49319e4625a4
Server Cluster:
Ep: 0x01={
0000,0003,0004,0005,0006,0B05}
Ep: 0x02-0000,0003,0B05}
Client Clusters:
Ep: 0xF2={0021}
Ep: 0x01={000A,0019}
Ep: 0x02-0003,0006}
Added to this driver version
───────────────────────────────────────────────────
Name Zigbee Light Multifunction Mc
Version 2023-09-06T21:52:01.030445238
───────────────────────────────────────────────────
- id: "Eaton/Halo_RL5601"
deviceLabel: Halo Light
manufacturer: Eaton
model: Halo_RL5601
deviceProfileName: level-colortemp-2700-5000
1 Like
Hi @r_m1
This device is in zigbee switch smartthings driver
- id: "Jasco Products/43094"
deviceLabel: Enbrighten Switch
manufacturer: Jasco Products
model: 43094
deviceProfileName: basic-switch
Hi Mariano,
Can you please add these fingerprints as well? They are almost the same as the one above.
Manufacturer: _TZ3000_cea5xugq (WOOX)
Model: TS0203
Endpoint: 01
App: 43
ZCL: 03
Server Cluster:
Ep: 0x01={ 0000,000A,0001,0500 }
Client Clusters:
Ep: Ox01{ 0019 }
Signal Metrics:
LQI: 202 … RSSI: -75 dbm
Thank you,
Alin
HI Alin
Added to this driver version
───────────────────────────────────────────────────
Name Zigbee Contact Mc
Version 2023-09-08T11:24:29.728785924
───────────────────────────────────────────────────
- id: "_TZ3000_cea5xugq/Woox"
deviceLabel: TS0203 Contact Sensor
manufacturer: _TZ3000_cea5xugq
model: TS0203
deviceProfileName: contact-battery-profile
1 Like
Thank you! Works like a charm 
1 Like
Hi I have a contact sensor, it’s branded as Living Smart, but it has the following details:
Model: SM11
FCC ID: 2ACLPSM11
In the groovy world, I added this as an ORVIBO contact sensor and it worked. After living in edge, I can’t add the device. It doesn’t get picked up when I scan for nearby devices. I’ve installed the contact edge driver from this channel as well. Is there any way to get these sensors to work, I want to avoid buying new contact sensors if I can.
Here’s the specs from ORVIBO: Orvibo Door & Window Sensor SM11 Zigbee compatibility
At the bare minimum it should get picked up as a Zigbee Thing and then you could try changing the driver to a usable driver.
Where are you trying to pair the device? Sometimes you need to pair the device right next to your hub for pairing to occur.
2 Likes
Is it possible to change the driver for the leak sensor so it can report as Present/Away instead of Wet/Dry?
I was going to connect the sensor to a pressure mat.
It could be possible, but you have to make a specific subdriver for this feature and also add code to a optional change the profile so that it can continue to be used as a water leak by other users.
This or making a specific driver, I don’t know if it’s worth so much work
I remember now that you can use a virtual device text fields and with two routines show the text you want for the status of any device
Thanks, I brought the contact sensor to the hub and then was able to pick it up and it worked with OP’s edge driver, yay! No need to buy new sensors!!
1 Like
I am using the zigbee motion sensor MC driver for a Tuya sensor with both luminance and motion (TS0601). Readings always list 1 lux for the sensor. However, the actual lux readings are reported in the history and they can be used in routines. I am thinking I could correct this if I knew the datapoint for the luminance, but I can’t find it.
Hi @dayton45
If you see the lux events in the history, then they need to be seen in the details view as well.
The same command is the one that emits the value for the whole platform. They have to be a problem with the app or the platform.
If you refresh by swiping down in the details view then does it update?
That part of the driver, cluster EF00, was not done by me, it was a collaboration from another user.
The code is on github
Here is how is shows up in the history. The correct value is quickly replaced by a 1. The routines are triggered by the correct value, so it doesn’t seem to be a serious problem.
Sep 10, 2023, 12:10 AM
Presence Sensor basement
normal-presenceSensor-v3
Ralph
main
main
illuminanceMeasurement
illuminance
“1”
Sep 10, 2023, 12:10 AM
Presence Sensor basement
normal-presenceSensor-v3
Ralph
main
main
illuminanceMeasurement
illuminance
“2310”
The driver only emit what the device sends to the driver.
If the driver emits two illuminance values, it means that it has received those values from the device.
With that information I cannot analyze anything else.
If you send me the exact device it is and the CLI logs I could analyze what the device sends to the driver.
It could be that it is sending information through the EF00 Tuya cluster and also through the standard 0x0400 cluster, I would not be surprised
I can see that this device was not paired directly with this driver, it must have been paired with the personal EF00 devices driver, right?
Try uninstalling it and pairing it directly with this driver
The manufacturer code for the device is _TZE200_3towulqd and it is model TS0601. When I remove, reset and pair the device, the Personal Tuya Device driver is automatically installed. I do not know how to restrict it so that it just installs the zigbee mc driver. The Tuya driver does not report anything. When I change the driver back to zigbee mc, it is the same as before.
I am not sure what the CLI file is or where to find it. I am posting the config file after the repair. It is from the API browser
{
“mnmn”: “SmartThingsCommunity”,
“vid”: “e471193b-f7e0-3192-aa92-b42d61917623”,
“version”: “0.0.1”,
“type”: “profile”,
“dashboard”: {
“states”: [
{
“component”: “main”,
“capability”: “motionSensor”,
“version”: 1,
“idx”: 0,
“group”: “main”,
“values”: ,
“composite”: false
}
],
“actions”: ,
“basicPlus”:
},
“detailView”: [
{
“component”: “main”,
“capability”: “motionSensor”,
“version”: 1,
“values”: ,
“patch”:
},
{
“component”: “main”,
“capability”: “illuminanceMeasurement”,
“version”: 1,
“values”: ,
“patch”:
},
{
“component”: “main”,
“capability”: “battery”,
“version”: 1,
“values”: ,
“patch”:
},
{
“component”: “main”,
“capability”: “legendabsolute60149.signalMetrics”,
“version”: 1,
“values”: ,
“patch”:
},
{
“component”: “main”,
“capability”: “refresh”,
“version”: 1,
“values”: ,
“patch”:
},
{
“component”: “main”,
“capability”: “firmwareUpdate”,
“version”: 1,
“values”: ,
“patch”:
}
],
“automation”: {
“conditions”: [
{
“component”: “main”,
“capability”: “motionSensor”,
“version”: 1,
“values”: ,
“patch”: ,
“exclusion”:
},
{
“component”: “main”,
“capability”: “illuminanceMeasurement”,
“version”: 1,
“values”: ,
“patch”: ,
“exclusion”:
},
{
“component”: “main”,
“capability”: “battery”,
“version”: 1,
“values”: ,
“patch”: ,
“exclusion”:
},
{
“component”: “main”,
“capability”: “legendabsolute60149.signalMetrics”,
“version”: 1,
“values”: ,
“patch”: ,
“exclusion”:
},
{
“component”: “main”,
“capability”: “firmwareUpdate”,
“version”: 1,
“values”: ,
“patch”: ,
“exclusion”:
}
],
“actions”: [
{
“component”: “main”,
“capability”: “legendabsolute60149.signalMetrics”,
“version”: 1,
“values”: ,
“patch”: ,
“exclusion”:
},
{
“component”: “main”,
“capability”: “refresh”,
“version”: 1,
“values”: ,
“patch”: ,
“exclusion”:
},
{
“component”: “main”,
“capability”: “firmwareUpdate”,
“version”: 1,
“values”: ,
“patch”: ,
“exclusion”:
}
]
},
“presentationId”: “e471193b-f7e0-3192-aa92-b42d61917623”,
“manufacturerName”: “SmartThingsCommunity”
}
If you are not using that driver with other devices then you can delete it from the hub.
Say you are using it and you can’t delete it so I don’t know what you can do to pair with this driver
1 Like
hello, i just installed a xhs2-ue zigbee contact sensor and using Zigbee Contact Mc as the driver.
just wondering if this is still a valid driver to use ???, or is there any other native support for this Xfinity sensor.
it was quite the chore to be seen by the hub, but followed this instruction and got it working.
1 Like
@Mariano_Colmenarejo hey amistad, anything i can do to “clean up” the code in the history for this switch? thanks
