What do you mean, add capabilities? Which device are you using (brand and model)?
That device is supported in the official ST Driver “Zigbee Humidity Sensor”
So, you can enroll in the official channel (here) and install that driver.
I think that what Mariano was referring to is that he cannot add them to his drivers that have a custom presentation.
The team is already working on fixing that issue.
1 Like
Ok thank you. I’m not up on all the lingo.
@nayelyz Can we have thread where we can request device profile to he added to official driver?
I have Z-wave sensor that works perfect with official driver, however it shows all capabilities as is recognized as generic z-wave sensor. All device’s capabilities are working correctly.
Users will need to provide device’s details.
This is driver where I added profile to the same driver
@Mariano_Colmenarejo has created ZigBee Thing MC driver that shows manufacturer and device model details, necessary for adding fingerprint
If we have another one like that for Z-wave, than users can load device, test it, and make requests for fingerprints to be added
Added to this driver version:
┌─────────────┬──────────────────────────────────────┐
│ Name │ Zigbee Switch Power Mc │
│ Version │ 2022-05-11T11:03:32.118064 │
└─────────────┴──────────────────────────────────────┘
- id: "_TZ3000_9vo5icau/TS011F"
deviceLabel: TS011F Plug
manufacturer: _TZ3000_9vo5icau
model: TS011F
deviceProfileName: switch-power-energy-plug
Ok, If I understand correctly, you want to be able to connect a device (that might not be compatible with a driver) so you can see its fingerprints to add them in a custom driver?
Could please add driver to zigbee HUE Philips Light
Hi Mario
It only has switch and level, right?
This driver has a custom presentation vid and until smartthings fixes the problem with these drivers I can’t add anything as packaging the new version of the driver breaks it for all current users.
As soon as they fix it I’ll add it and let you know
Hi @milandjurovic71,
I have made a Z-Wave Thing Mc driver that shows the necessary fingerprints data for pairing with edge driver:
- manufacturerId
- productType
- productId
As with the Zigbee Thing driver, the device must first be paired with an edge driver, by generic or specific fingerprint, since for now until groovy disappears, DTHs have priority for devices that do not have fingerprints in edge drivers and they have them in a DTH.
You can also use these drivers to make a driver change in any Zwave or Zigbee device, see its fingerprints data and reinstall it with its original driver without losing any routine or setting
This fingerprints data can also be viewed in the pairing logs with the CLI with all drivers.
2022-05-11T13:46:58.240588488+00:00 TRACE Z-Wave Thing Mc Z-Wave Device: e062ff99-4cfc-47c2-be7f-91881fdc3a8c
Manufacturer: 0x010F Product Type: 0x0402 Product ID: 0x1002
[0]: MULTI_CHANNEL, SWITCH_BINARY, MANUFACTURER_SPECIFIC, VERSION, CONFIGURATION, ASSOCIATION, MULTI_CHANNEL_ASSOCIATION, MULTI_CHANNEL, SWITCH_BINARY, SWITCH_ALL, FIRMWARE_UPDATE_MD, POWERLEVEL [1]: MULTI_CHANNEL, SWITCH_BINARY, MANUFACTURER_SPECIFIC, VERSION, CONFIGURATION, ASSOCIATION, MULTI_CHANNEL_ASSOCIATION, MULTI_CHANNEL, SWITCH_BINARY, SWITCH_ALL, FIRMWARE_UPDATE_MD, POWERLEVEL
Zigbee and Z-Wave drivers versions
┌─────────────┬──────────────────────────────────────┐
│ Driver Id │ d692640b-402a-4d91-9151-d643ad4771f0 │
│ Name │ Zigbee Thing Mc │
│ Version │ 2022-05-11T13:47:02.276811 │
└─────────────┴──────────────────────────────────────┘
┌─────────────┬──────────────────────────────────────┐
│ Driver Id │ 5197249e-95aa-4a27-a08f-2232d193e13b │
│ Name │ Z-Wave Thing Mc │
│ Version │ 2022-05-11T13:46:07.574005 │
└─────────────┴──────────────────────────────────────┘
2 Likes
Hi @Mariano_Colmenarejo
Once again the switch went offline
I used automation routine to wake it up again, the switch in smartthings become online again but only in app, i mean the switch doesnt really switch the physical light ON/OFF but i see the icon in app change from ON to OFF and OFF to ON
logs
Summary
2022-05-11T23:58:10.473878002+00:00 TRACE Zigbee Multi Switch Mc Received event with handler capability
2022-05-11T23:58:10.506028002+00:00 INFO Zigbee Multi Switch Mc <ZigbeeDevice: 75e707bc-12a3-4ea8-9813-9f025a028d0a [0x102C] (TS0012 Switch)> received command: {"args":{},"capability":"switch","command":"on","component":"main","positional_args":{}}
2022-05-11T23:58:10.513668335+00:00 TRACE Zigbee Multi Switch Mc Found CapabilityCommandDispatcher handler in Zigbee_Multi_Switch
2022-05-11T23:58:10.522605668+00:00 INFO Zigbee Multi Switch Mc <ZigbeeDevice: 75e707bc-12a3-4ea8-9813-9f025a028d0a [0x102C] (TS0012 Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x102C, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x01, seqno: 0x00, ZCLCommandId: 0x01 >, < On || > > >
2022-05-11T23:58:10.549354668+00:00 INFO Zigbee Multi Switch Mc <ZigbeeDevice: 75e707bc-12a3-4ea8-9813-9f025a028d0a [0x102C] (TS0012 Switch)> emitting event: {"attribute_id":"switch","capability_id":"switch","component_id":"main","state":{"value":"on"}}
2022-05-11T23:58:10.585770002+00:00 DEBUG Zigbee Multi Switch Mc TS0012 Switch device thread event handled
2022-05-11T23:58:10.595088002+00:00 DEBUG Zigbee Multi Switch Mc TS0012 Switch device thread event handled
2022-05-11T23:58:12.590190003+00:00 PRINT Zigbee Multi Switch Mc all_switches_status >>>>>
2022-05-11T23:58:12.597641669+00:00 INFO Zigbee Multi Switch Mc <ZigbeeDevice: 75e707bc-12a3-4ea8-9813-9f025a028d0a [0x102C] (TS0012 Switch)> emitting event: {"attribute_id":"switchAllOnOff","capability_id":"legendabsolute60149.switchAllOnOff1","component_id":"main","state":{"value":"S1:On "}}
2022-05-11T23:58:12.616740336+00:00 DEBUG Zigbee Multi Switch Mc TS0012 Switch device thread event handled
2022-05-11T23:58:20.004174340+00:00 TRACE Zigbee Multi Switch Mc Received event with handler capability
2022-05-11T23:58:20.053137340+00:00 INFO Zigbee Multi Switch Mc <ZigbeeDevice: 75e707bc-12a3-4ea8-9813-9f025a028d0a [0x102C] (TS0012 Switch)> received command: {"args":{},"capability":"switch","command":"off","component":"main","positional_args":{}}
2022-05-11T23:58:20.063080340+00:00 TRACE Zigbee Multi Switch Mc Found CapabilityCommandDispatcher handler in Zigbee_Multi_Switch
2022-05-11T23:58:20.094053006+00:00 INFO Zigbee Multi Switch Mc <ZigbeeDevice: 75e707bc-12a3-4ea8-9813-9f025a028d0a [0x102C] (TS0012 Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x102C, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x01, seqno: 0x00, ZCLCommandId: 0x00 >, < Off || > > >
2022-05-11T23:58:20.106530006+00:00 INFO Zigbee Multi Switch Mc <ZigbeeDevice: 75e707bc-12a3-4ea8-9813-9f025a028d0a [0x102C] (TS0012 Switch)> emitting event: {"attribute_id":"switch","capability_id":"switch","component_id":"main","state":{"value":"off"}}
2022-05-11T23:58:20.159028340+00:00 DEBUG Zigbee Multi Switch Mc TS0012 Switch device thread event handled
2022-05-11T23:58:20.173287673+00:00 DEBUG Zigbee Multi Switch Mc TS0012 Switch device thread event handled
2022-05-11T23:58:21.908501674+00:00 DEBUG Zigbee Multi Switch Mc driver device thread event handled
2022-05-11T23:58:22.170723007+00:00 PRINT Zigbee Multi Switch Mc all_switches_status >>>>>
2022-05-11T23:58:22.178027007+00:00 INFO Zigbee Multi Switch Mc <ZigbeeDevice: 75e707bc-12a3-4ea8-9813-9f025a028d0a [0x102C] (TS0012 Switch)> emitting event: {"attribute_id":"switchAllOnOff","capability_id":"legendabsolute60149.switchAllOnOff1","component_id":"main","state":{"value":"All Off"}}
2022-05-11T23:58:22.196667007+00:00 DEBUG Zigbee Multi Switch Mc TS0012 Switch device thread event handled
2022-05-11T23:58:28.913867344+00:00 TRACE Zigbee Multi Switch Mc Received event with handler capability
2022-05-11T23:58:28.947708677+00:00 INFO Zigbee Multi Switch Mc <ZigbeeDevice: 75e707bc-12a3-4ea8-9813-9f025a028d0a [0x102C] (TS0012 Switch)> received command: {"args":{"value":"All On"},"capability":"legendabsolute60149.switchAllOnOff1","command":"setSwitchAllOnOff","component":"main","positional_args":["All On"]}
2022-05-11T23:58:28.954166344+00:00 TRACE Zigbee Multi Switch Mc Found CapabilityCommandDispatcher handler in Zigbee_Multi_Switch
2022-05-11T23:58:28.959534010+00:00 PRINT Zigbee Multi Switch Mc command.args.value >>>>> All On
2022-05-11T23:58:28.966938011+00:00 INFO Zigbee Multi Switch Mc <ZigbeeDevice: 75e707bc-12a3-4ea8-9813-9f025a028d0a [0x102C] (TS0012 Switch)> emitting event: {"attribute_id":"switchAllOnOff","capability_id":"legendabsolute60149.switchAllOnOff1","component_id":"main","state":{"value":"All On"}}
2022-05-11T23:58:28.986940011+00:00 INFO Zigbee Multi Switch Mc <ZigbeeDevice: 75e707bc-12a3-4ea8-9813-9f025a028d0a [0x102C] (TS0012 Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x102C, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x01, seqno: 0x00, ZCLCommandId: 0x01 >, < On || > > >
2022-05-11T23:58:29.003011677+00:00 INFO Zigbee Multi Switch Mc <ZigbeeDevice: 75e707bc-12a3-4ea8-9813-9f025a028d0a [0x102C] (TS0012 Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x102C, dest_endpoint: 0x02, profile: 0x0104, cluster: OnOff >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x01, seqno: 0x00, ZCLCommandId: 0x01 >, < On || > > >
2022-05-11T23:58:29.023873677+00:00 DEBUG Zigbee Multi Switch Mc TS0012 Switch device thread event handled
2022-05-11T23:58:51.913889021+00:00 INFO Zigbee Multi Switch Mc Doing health check read for [102C]:0006:0000
2022-05-11T23:58:51.924243021+00:00 INFO Zigbee Multi Switch Mc <ZigbeeDevice: 75e707bc-12a3-4ea8-9813-9f025a028d0a [0x102C] (TS0012 Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x102C, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x00 >, < ReadAttribute || AttributeId: 0x0000 > > >
2022-05-11T23:58:51.947253688+00:00 DEBUG Zigbee Multi Switch Mc driver device thread event handled
2022-05-11T23:59:06.083852695+00:00 TRACE Zigbee Multi Switch Mc Received event with handler capability
2022-05-11T23:59:06.103702362+00:00 INFO Zigbee Multi Switch Mc <ZigbeeDevice: 75e707bc-12a3-4ea8-9813-9f025a028d0a [0x102C] (TS0012 Switch)> received command: {"args":{"value":"All Off"},"capability":"legendabsolute60149.switchAllOnOff1","command":"setSwitchAllOnOff","component":"main","positional_args":["All Off"]}
2022-05-11T23:59:06.111518028+00:00 TRACE Zigbee Multi Switch Mc Found CapabilityCommandDispatcher handler in Zigbee_Multi_Switch
2022-05-11T23:59:06.117381028+00:00 PRINT Zigbee Multi Switch Mc command.args.value >>>>> All Off
2022-05-11T23:59:06.123847362+00:00 INFO Zigbee Multi Switch Mc <ZigbeeDevice: 75e707bc-12a3-4ea8-9813-9f025a028d0a [0x102C] (TS0012 Switch)> emitting event: {"attribute_id":"switchAllOnOff","capability_id":"legendabsolute60149.switchAllOnOff1","component_id":"main","state":{"value":"All Off"}}
2022-05-11T23:59:06.144561695+00:00 INFO Zigbee Multi Switch Mc <ZigbeeDevice: 75e707bc-12a3-4ea8-9813-9f025a028d0a [0x102C] (TS0012 Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x102C, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x01, seqno: 0x00, ZCLCommandId: 0x00 >, < Off || > > >
2022-05-11T23:59:06.160316695+00:00 INFO Zigbee Multi Switch Mc <ZigbeeDevice: 75e707bc-12a3-4ea8-9813-9f025a028d0a [0x102C] (TS0012 Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x102C, dest_endpoint: 0x02, profile: 0x0104, cluster: OnOff >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x01, seqno: 0x00, ZCLCommandId: 0x00 >, < Off || > > >
2022-05-11T23:59:06.178874362+00:00 DEBUG Zigbee Multi Switch Mc TS0012 Switch device thread event handled
2022-05-11T23:59:09.483985030+00:00 TRACE Zigbee Multi Switch Mc Received event with handler capability
2022-05-11T23:59:09.544882363+00:00 INFO Zigbee Multi Switch Mc <ZigbeeDevice: 75e707bc-12a3-4ea8-9813-9f025a028d0a [0x102C] (TS0012 Switch)> received command: {"args":{"value":"All On"},"capability":"legendabsolute60149.switchAllOnOff1","command":"setSwitchAllOnOff","component":"main","positional_args":["All On"]}
2022-05-11T23:59:09.578915030+00:00 TRACE Zigbee Multi Switch Mc Found CapabilityCommandDispatcher handler in Zigbee_Multi_Switch
2022-05-11T23:59:09.623642363+00:00 PRINT Zigbee Multi Switch Mc command.args.value >>>>> All On
2022-05-11T23:59:09.644091030+00:00 INFO Zigbee Multi Switch Mc <ZigbeeDevice: 75e707bc-12a3-4ea8-9813-9f025a028d0a [0x102C] (TS0012 Switch)> emitting event: {"attribute_id":"switchAllOnOff","capability_id":"legendabsolute60149.switchAllOnOff1","component_id":"main","state":{"value":"All On"}}
2022-05-11T23:59:09.763760697+00:00 INFO Zigbee Multi Switch Mc <ZigbeeDevice: 75e707bc-12a3-4ea8-9813-9f025a028d0a [0x102C] (TS0012 Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x102C, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x01, seqno: 0x00, ZCLCommandId: 0x01 >, < On || > > >
2022-05-11T23:59:09.847081363+00:00 INFO Zigbee Multi Switch Mc <ZigbeeDevice: 75e707bc-12a3-4ea8-9813-9f025a028d0a [0x102C] (TS0012 Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x102C, dest_endpoint: 0x02, profile: 0x0104, cluster: OnOff >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x01, seqno: 0x00, ZCLCommandId: 0x01 >, < On || > > >
2022-05-11T23:59:09.927720697+00:00 DEBUG Zigbee Multi Switch Mc TS0012 Switch device thread event handled
Even now i tried to get it back online by turning the physical swith ON, but doesnt reflect any action in app!!
@nayelyz with @Mariano_Colmenarejo drivers I can add any Zigbee or Z-wave device and provide details for fingerprints. For example I have Ring Contact sensor that is fully functional with SmartThings stock driver, however stock driver doesn’t have fingerprint and correct profile for it, and as result it shows all capabilities including unsupported.
I have added fingerprint to Smartthing stock z-wave sensor driver, published and tested it. I can confirm that it works. Now SmartThings team needs to add fingerprint to their driver and make it available for everyone.
This is the same device with 3 different drivers:
SmartThings Stock Z-Wave Sensor driver
Mariano’s Z-wave Thing MC
Stock Z-Wave Sensor driver where I have added fingerprint above and correct profile.
@nayelyz Where can we create requests for SmartThings’ team to update stock drivers with new fingerprints and profiles for tested/verified devices?
I am ok with “my driver”, however this should be available for everyone in stock SmartThings driver
3 Likes
The drivers only contain the fingerprints of devices that have been certified by device manufacturers. If you want to see a fingerprint (in the ST drivers) that falls in the category of “not certified”, you need to contact the manufacturer’s support and let them know you’re interested in an integration with SmartThings. Then, they will decide if they want to pursue that path.
If you find a problem in the driver using an already supported device, then you can report it normally to us (SmartThings Developer Support team, @nayelyz, @andresg)
About the option to provide the fingerprints, I see there’s a driver called Zigbee-thing. It allows the installation of Zigbee devices not supported by the other official ones.
It doesn’t have a profile to show the data in the app but you can see the device’s fingerprint and the supported clusters in the driver logs (smartthings edge:drivers:logcat).
For example, right after the “driver introduction”, you’ll see something similar to:
2022-05-04T21:44:33.627570843+00:00 TRACE Z-Wave Aeotec Tri Z-Wave Device: cf0b1845-b55d-4288-b2ce-480576a8dc70
Manufacturer: 0x0371 Product Type: 0x0102 Product ID: 0x0005
[0]: VERSION, POWERLEVEL, ASSOCIATION, MULTI_CHANNEL_ASSOCIATION, ASSOCIATION_GRP_INFO, MANUFACTURER_SPECIFIC, DEVICE_RESET_LOCALLY, BATTERY, WAKE_UP, SENSOR_BINARY, NOTIFICATION, SENSOR_MULTILEVEL, CONFIGURATION, FIRMWARE_UPDATE_MD, ZWAVEPLUS_INFO, SECURITY, SECURITY_2, TRANSPORT_SERVICE, SUPERVISION
Note: Make sure you’re updating the version of the CLI accordingly
I’ll mention your comments about showing at least the fingerprints in the profile and ask if there will be a “Z-Wave thing” driver.
Update:
The Z-Wave driver that allows the installation of non recognized devices is “Z-Wave Switch”, this is the corresponding fingerprint:
Sorry, I’m pretty busy with other non-intelligent things and I haven’t been able to analyze it.
In the last logs that you send me, I do not see any messages received from the device, so it seems that it is really offline.
In a previous log, I see that the signal of the device is quite weak, rssi=-71 and lqi=74. I don’t know if it reaches the hub directly or through a repeater, that information is not shown on edge.
It seems that it can lose the connection due to bad signal and that is why it stays offline.
Try to see if the hub has the secure mode disabled to allow an automatic rejoint of the device when the signal improves.
You can check if the device is doing a rejoint, if you notice that it changes its network address (dni) frequently, every time it does a rejoint it changes the network address of the device.
I’m looking for osram motion sensor
could mariano insert in edge??
Hello,
I need the fingerprints: manufacturer, model and if it has any capability besides movement and battery, it seems that it also shows temperature, according to Amazon
I think it reaches the hub directly, this what i remember while i was using DHT before edge from device info in IDE and uder route
Is there a way to see this for edge?
Unsecure Rejoin is enabled
How to see this? from IDE or CLI?
This is weird
I have to switches next to each other, this one reports rssi=-75
the other one next to it reports rssi=-60
maybe they have interferenace?
do you think if i change Zigbee channel in hub will improve?
UPDATE: I just removed the device and pait it again and rssi has improved to -60
In IDE it is not seen with edge
In the cli logs you can see it after the device id:
2022-05-08T19:41:00.010220881+00:00 INFO Zigbee Multi Switch Mc <ZigbeeDevice: 1d30914e-938a-40eb-97e6-20a3e70e7aa2 [ 0x10DF ] (TS0012 Switch)>