(EDGE Driver-Mc): Zigbee Drivers for Motion, Open/Close, Moisture, Smoke-Co Sensors and others Devices

amin300 · January 22, 2022, 6:17pm

Thank you @Mariano_Colmenarejo for your quick reply
Tested and still light goes OFF after 2 mins
I checked and device picked the new driver

Markusjonsson · January 23, 2022, 6:39am

Thank you works great !

Markus

Markusjonsson · January 23, 2022, 6:55am

Hallo again !

Is it possible to do a edge driver to this aqara vibration / tilt sensor

application: 08
endpointId: 01
manufacturer: LUMI
model: lumi.vibration.aq1
zigbeeNodeType: SLEEPY_END_DEVICE
Raw Description 01 0104 000A 01 04 0000 0003 0019 0101 06 0000 0004 0003 0005 0019 0101

Markus

Mariano_Colmenarejo · January 23, 2022, 5:46pm

Because of the clusters it has, I don’t think it will work with any of the drivers I have.
I don’t handle LUMI devices well, there are developers @veonua or @ygerlovin who have drivers for this manufacturer, I don’t know if they can help you with this

Mariano_Colmenarejo · January 23, 2022, 6:08pm

Test with this version.
I wrote 0X0000 in cluster 0x0006, atribute 0x04001 (onTime)

┌─────────────┬──────────────────────────────────────┐
│ Name        │ Zigbee Multi Switch Zemismart Mc     │
│ Version     │ 2022-01-23T18:07:24.327887           │
└─────────────┴──────────────────────────────────────┘

JDRoberts · January 23, 2022, 6:17pm

That is a Tuya-made switch and the turning itself off after two minutes is a known issue for that model with many different brands of hubs, not just smartthings. It only seems to work well out of the box with a tuya-made Gateway.

For example, here’s a discussion over at openhab

The Zigbee standard allows companies to use some custom clusters, and Tuya does so. And they are not required to document those custom clusters. So it can be challenging to get those devices to work with other hubs.

Specifically, some of their switch models have a built in timer and it appears that that is being activated when the device joins the network unless you are using a tuya gateway.

I suggest you start a new thread with the model number in the topic title and hopefully if anybody else has it working with ST they will let you know how.

If you find someone who has it working with a Groovy DTH than that information might be helpful to those who are trying to write edge Drivers.

Markusjonsson · January 23, 2022, 6:33pm

Okey thanks anyway

amin300 · January 23, 2022, 6:36pm

Thanks @JDRoberts for your reply.

This issue is solved in DTH as explened in below post link:

Do you think is something useful to use and modify the driver for this device?

Thanks
Amin

amin300 · January 23, 2022, 7:01pm

This is the DTH which I am using and in line 271 I have changed to my device

github.com

SmartThingsCommunity/SmartThingsPublic/blob/master/devicetypes/smartthings/zigbee-multi-switch.src/zigbee-multi-switch.groovy

/*
 *  Copyright 2018 SmartThings
 *
 *  Licensed under the Apache License, Version 2.0 (the "License"); you may not
 *  use this file except in compliance with the License. You may obtain a copy
 *  of the License at:
 *
 *		http://www.apache.org/licenses/LICENSE-2.0
 *
 *  Unless required by applicable law or agreed to in writing, software
 *  distributed under the License is distributed on an "AS IS" BASIS, WITHOUT
 *  WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the
 *  License for the specific language governing permissions and limitations
 *  under the License.
 *  Author : Fen Mei / f.mei@samsung.com
 *  Date : 2018-08-29
 */

metadata {
	definition(name: "ZigBee Multi Switch", namespace: "smartthings", author: "SmartThings", ocfDeviceType: "oic.d.switch", mnmn: "SmartThings", vid: "generic-switch") {

This file has been truncated. show original

Mariano_Colmenarejo · January 23, 2022, 7:18pm

This is done by DTH:

	if (isOrvibo()) {
		//the orvibo switch will send out device anounce message at ervery 2 mins as heart beat,setting 0x0099 to 1 will disable it.
		def cmds = zigbee.writeAttribute(zigbee.BASIC_CLUSTER, 0x0099, 0x20, 0x01, [mfgCode: 0x0000])
		cmds += refresh()
		return cmds

This done by driver published yesterday, I publish now again:

local function do_configure(self,device)
  if device:get_manufacturer() == "_TZ3000_fvh3pjaz" then
    --- Configure basic cluster, attributte 0x0099 to 1
    local data_value = {value = 0x01, ID = 0x20}
    local cluster_id = {value = 0x0000}
    local attr_id = 0x0099
    write_attribute_function(device, cluster_id, attr_id, data_value)
  end
   device:configure()
end

┌─────────────┬──────────────────────────────────────┐
│ Name        │ Zigbee Multi Switch Zemismart Mc     │
│ Version     │ 2022-01-23T19:15:03.670094           │
└─────────────┴──────────────────────────────────────┘

For it to works, you have to uninstall the device and re-pair it with this new driver to configure it correctly.

If you install it and send me the pairing CLI log, to see if the writing of the attribute is accepted, I will be able to analyze something, if it just tells me it doesn’t work, I can’t do anything.

amin300 · January 23, 2022, 7:43pm

Thanks @Mariano_Colmenarejo
I have Uninstalled the device and re-paired it again but it didnt pick the new driver
2022-01-23T19:15:03.670094
Still picking the version:
2022-01-22T17:23:29.327658
I tried 3 times
Are you sure it is puplished or I am doing something wrong?

amin300 · January 23, 2022, 7:56pm

BTW @Mariano_Colmenarejo , how I can send you the pairing CLI Log?

Mariano_Colmenarejo · January 23, 2022, 8:19pm

The automatic driver update can take up to 12 hours.

So you only have that device installed with the driver:

Uninstall the device
Remove the driver from your Hub
Enter the channel and reinstall the driver, that will be the latest version. You can check it by clicking on the driver and see the date.
Re-pair the device

amin300 · January 24, 2022, 5:21pm

Hi again @Mariano_Colmenarejo

I still can’t see the latest driver of 2022-01-23T19:15:03.670094
Still picking the version:
2022-01-22T17:23:29.327658

Even when device is paired and i go to select another driver, still can’t see latest one

Any other suggestion please?

amin300 · January 24, 2022, 6:17pm

Now i can see it, i had to remove old driver from hub and install again
Tested and issue still there

I tried to capture logs by going to IDE logs tab but i can’t see my device although it is installed!!

Can you please guide me to capture CLI logs please?

joinwind · January 24, 2022, 7:05pm

@Mariano_Colmenarejo can you try to modify the driver : zigbee-window-treatment from samsung and add this info in fingerprint :

application: 01
endpointId: 0A
manufacturer: Vimar
model: Window_Cov_v1.0
zigbeeNodeType: ROUTER

Thanks if you can publish !

Mariano_Colmenarejo · January 24, 2022, 7:10pm

It seems a bit complicated at first, but most of us get it done.

You have to download from this link release 34 of the compressed file smartthings-win.zip, if you use windows or the one necessary for your operating system
In that link you also have installation help, use and all the commands you can use
Unzip it and move the smartthings.exe file to a folder on your computer from where it will be used. for example to a new folder in documents/CLI
You have to open the windows powerShell terminal window and you have to go to the directory (folder) where the smarttings.exe file is.
Use the DOS commands “cd…” to move down directory and “cd directory name” to move to that directory. This is an example of my folder for CLI

the first time you type a CLI command it will take you to the smartthing page to authorize your account.
type .\smartthings edge:drivers:logcat
enter the IP of your HUB, you can see it in IDE
It will show you the list of drivers installed on your HUB
type the number corresponding to the driver you want to see
It will show you the activity of the device connected to that driver.

To capture the pairing log:

Uninstall the device with the app
Open the terminal window with the CLI ready to see the log of the driver to which the device is going to be paired
In the app, add new device and search nearby
When paired in the app you will see information appear in the CLI window
When it finishes pairing, select the data in the window, copy and paste it in the post
Similar to this example:

? Select a driver. 23
2022-01-24T17:54:45.422836623+00:00 TRACE Zigbee Switch Power Mc Setup driver Zigbee_Switch with lifecycle handlers:
DeviceLifecycleDispatcher: Zigbee_Switch
default_handlers:
init:
infoChanged:
doConfigure:
driverSwitched:
removed:
child_dispatchers:

2022-01-24T17:54:45.433937838+00:00 TRACE Zigbee Switch Power Mc Setup driver Zigbee_Switch with Capability handlers:
CapabilityCommandDispatcher: Zigbee_Switch
default_handlers:
switchLevel:
setLevel
energyMeter:
resetEnergyMeter
switch:
on
off
legendabsolute60149.randomOnOff1:
setRandomOnOff
refresh:
refresh
child_dispatchers:

2022-01-24T17:54:45.443345539+00:00 TRACE Zigbee Switch Power Mc Setup driver Zigbee_Switch with Zigbee handlers:
ZigbeeMessageDispatcher: Zigbee_Switch
default_handlers:
attr:
ZclClusterAttributeValueHandler: cluster: ElectricalMeasurement, attribute: ACPowerMultiplier
ZclClusterAttributeValueHandler: cluster: ElectricalMeasurement, attribute: ACPowerDivisor
ZclClusterAttributeValueHandler: cluster: ElectricalMeasurement, attribute: ActivePower
ZclClusterAttributeValueHandler: cluster: OnOff, attribute: OnOff
ZclClusterAttributeValueHandler: cluster: SimpleMetering, attribute: InstantaneousDemand
ZclClusterAttributeValueHandler: cluster: SimpleMetering, attribute: Multiplier
ZclClusterAttributeValueHandler: cluster: SimpleMetering, attribute: Divisor
ZclClusterAttributeValueHandler: cluster: SimpleMetering, attribute: CurrentSummationDelivered
ZclClusterAttributeValueHandler: cluster: Level, attribute: CurrentLevel
global:
ZclGlobalCommandHandler: cluster: OnOff, command: DefaultResponse
cluster:
zdo:
child_dispatchers:

2022-01-24T17:54:45.511152092+00:00 TRACE Zigbee Switch Power Mc Received event with handler _resync
2022-01-24T17:54:45.516996346+00:00 TRACE Zigbee Switch Power Mc Received event with handler environment_info
2022-01-24T17:54:45.532995675+00:00 TRACE Zigbee Switch Power Mc Found DeviceLifecycleDispatcher handler in Zigbee_Switch
2022-01-24T17:54:45.538784902+00:00 PRINT Zigbee Switch Power Mc <<<< random_state >>>> Inactive
2022-01-24T17:54:45.545711363+00:00 INFO Zigbee Switch Power Mc <ZigbeeDevice: 92d80935-27ff-4d7f-ba4d-70ac7c0db9e7 [0xCCC5] (Caldera)> emitting event: {“attribute_id”:“randomOnOff”,“capability_id”:“legendabsolute60149.randomOnOff1”,“component_id”:“main”,“state”:{“value”:“Inactive”}}
2022-01-24T17:54:45.565924465+00:00 INFO Zigbee Switch Power Mc <ZigbeeDevice: 92d80935-27ff-4d7f-ba4d-70ac7c0db9e7 [0xCCC5] (Caldera)> emitting event: {“attribute_id”:“randomNext”,“capability_id”:“legendabsolute60149.randomNextStep”,“component_id”:“main”,“state”:{“value”:“Inactive”}}
2022-01-24T17:54:45.588026844+00:00 PRINT Zigbee Switch Power Mc device_running[id]= <ZigbeeDevice: 92d80935-27ff-4d7f-ba4d-70ac7c0db9e7 [0xCCC5] (Caldera)>
2022-01-24T17:54:45.594267629+00:00 PRINT Zigbee Switch Power Mc device_running, random_Step= <ZigbeeDevice: 92d80935-27ff-4d7f-ba4d-70ac7c0db9e7 [0xCCC5] (Caldera)> 1
2022-01-24T17:54:45.602485736+00:00 PRINT Zigbee Switch Power Mc device_running, random_totalStep= <ZigbeeDevice: 92d80935-27ff-4d7f-ba4d-70ac7c0db9e7 [0xCCC5] (Caldera)> 2
2022-01-24T17:54:45.608596790+00:00 PRINT Zigbee Switch Power Mc device_running, random_timer= <ZigbeeDevice: 92d80935-27ff-4d7f-ba4d-70ac7c0db9e7 [0xCCC5] (Caldera)> 18
2022-01-24T17:54:45.614712513+00:00 PRINT Zigbee Switch Power Mc random_state >>>>> Inactive
2022-01-24T17:54:45.621036007+00:00 DEBUG Zigbee Switch Power Mc Caldera device thread event handled
2022-01-24T17:54:45.628412360+00:00 TRACE Zigbee Switch Power Mc Received event with handler _resync
2022-01-24T17:54:45.634823897+00:00 TRACE Zigbee Switch Power Mc Received event with handler environment_info
2022-01-24T17:54:45.640548091+00:00 DEBUG Zigbee Switch Power Mc Z-Wave hub node ID environment changed.
2022-01-24T17:54:45.655721674+00:00 TRACE Zigbee Switch Power Mc Received event with handler environment_info
2022-01-24T17:54:45.664314302+00:00 TRACE Zigbee Switch Power Mc Received event with handler environment_info
2022-01-24T17:54:45.672036494+00:00 TRACE Zigbee Switch Power Mc Received event with handler device_lifecycle
2022-01-24T17:54:45.677818717+00:00 INFO Zigbee Switch Power Mc <ZigbeeDevice: 92d80935-27ff-4d7f-ba4d-70ac7c0db9e7 [0xCCC5] (Caldera)> received lifecycle event: added
2022-01-24T17:54:45.686320633+00:00 TRACE Zigbee Switch Power Mc <ZigbeeDevice: 92d80935-27ff-4d7f-ba4d-70ac7c0db9e7 [0xCCC5] (Caldera)> received unhandled lifecycle event: added
2022-01-24T17:54:45.691853731+00:00 DEBUG Zigbee Switch Power Mc Caldera device thread event handled
2022-01-24T17:54:45.697675641+00:00 TRACE Zigbee Switch Power Mc Received event with handler device_lifecycle
2022-01-24T17:54:45.703458197+00:00 INFO Zigbee Switch Power Mc <ZigbeeDevice: 92d80935-27ff-4d7f-ba4d-70ac7c0db9e7 [0xCCC5] (Caldera)> received lifecycle event: driverSwitched
2022-01-24T17:54:45.712275270+00:00 TRACE Zigbee Switch Power Mc Found DeviceLifecycleDispatcher handler in Zigbee_Switch
2022-01-24T17:54:45.722751839+00:00 DEBUG Zigbee Switch Power Mc Caldera device thread event handled
2022-01-24T17:54:45.730693808+00:00 DEBUG Zigbee Switch Power Mc Caldera device thread event handled
2022-01-24T17:54:50.750604509+00:00 INFO Zigbee Switch Power Mc <ZigbeeDevice: 92d80935-27ff-4d7f-ba4d-70ac7c0db9e7 [0xCCC5] (Caldera)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0xCCC5, dest_endpoint: 0x01, profile: 0x0104, cluster: ElectricalMeasurement >, < ZCLMessageBody ||
< ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x00 >, < ReadAttribute || AttributeId: 0x050B > > >
2022-01-24T17:54:50.773669036+00:00 INFO Zigbee Switch Power Mc <ZigbeeDevice: 92d80935-27ff-4d7f-ba4d-70ac7c0db9e7 [0xCCC5] (Caldera)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0xCCC5, dest_endpoint: 0x01, profile: 0x0104, cluster: SimpleMetering >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x00 >, < ReadAttribute || AttributeId: 0x0000 > > >

Don’t be in a hurry, take it patiently, it was hard for all of us the first time and if you have any problem, say so.

Helder_Rodrigues · January 24, 2022, 10:16pm

Hello @Mariano_Colmenarejo

can you create for this device?
Data * zigbeeNodeType: ROUTER

firmwareManufacturerCode: 4417
firmwareFullVersion: 00000043
application: 43
endpointId: 01
firmwareImageType: 54179
manufacturer: _TZ3000_tqlv4ug4
model: TS0001
Raw Description 01 0104 0100 01 07 0003 0004 0005 0006 E000 E001 0000 02 0019 000A

Mariano_Colmenarejo · January 25, 2022, 12:29pm

Hello @joinwind,

I am not going to modify the official beta drivers to include fingerprints in them, since it would be impossible to serve it correctly.
There are more and more drivers and it would be impossible

I will continue to maintain the drivers that I have created or modified with different functions to official drivers.

I can help you to modify them, it is not very difficult, 3 months ago I did not know anything about CLI or lua.

In this link I explained it to another user who wants to do the same

Setting Up Edge Development Environment Support

@Jake_Mohl, I don’t know exactly where you are, but I’ll try to explain how I did it How to edit the LUA and yml code of the Edge drivers I’m going to explain the steps I did, that I’m not a developer and I started from scratch, without knowing the CLI or Lua. First I read the Edge Drivers tutorials and CLI in the community https://community.smartthings.com/t/tutorial-creating-drivers-for-zigbee-devices-with-smartthings-edge/229502 https://community.smartthings.com/t/creating-drivers-for-z-wave-devices-with-smartthings-edge/229503 Download a multilanguage code editor, I opted for Visual Studio since they recommended it in some thread of the tutorials. https://visualstudio.microsoft.com/es/ Once installed, the Windows version in my case, this window appears [Visual studio] Clic…

Mariano_Colmenarejo · January 25, 2022, 1:01pm

Added to this driver version

┌─────────────┬──────────────────────────────────────┐
│ Name        │ Zigbee Switch Mc                     │
│ Version     │ 2022-01-25T12:57:40.013495           │
└─────────────┴──────────────────────────────────────┘

  - id: "_TZ3000_tqlv4ug4/Switch"
    deviceLabel: TUYATEC Switch
    manufacturer: _TZ3000_tqlv4ug4
    model: TS0001
    deviceProfileName: single-switch

Topic		Replies	Views
(EDGE Driver-Mc): Zigbee Light Multifunction Mc Community Created Device Types edge_lighting	1364	51535	December 15, 2024
What is Mariano Shared Beta Driver? Community Created Device Types	115	6707	March 24, 2024
Https://community.smartthings.com/t/beta-zigbee-edge-driver-compatible-with-lidl-ecosmart-osram-smartthings-others/231689/30 Community Created Device Types	0	330	October 20, 2021
Edge Driver for Third Reality Zigbee Devices? Devices & Integrations	6	3142	June 13, 2023
[ST Edge] Lidl Bulb Zigbee Driver Community Created Device Types edge-device , edge_lighting	44	8181	September 28, 2021

(EDGE Driver-Mc): Zigbee Drivers for Motion, Open/Close, Moisture, Smoke-Co Sensors and others Devices

Related topics