I donβt know what model your device is.
Mine is a samjin, (aeotec) and the three profiles work well, Multipurpose, Temperature and vibration
If you were using the old smartthings Multipurpose Sensor Mc and have switched to the Zigbee Contact Mc you may need to pair it directly with this driver for it to configure correctly.
The changes that have been made to the flow of life cycles in driverSwitched may not work correctly with this function.
Good morning @Mariano_Colmenarejo
This morning I produced a video for Wesley M ( @w35l3y ) with the smatthins-cli prompt ouput window for the fingerbot plus zigbee. If youβre interested, Iβll leave you the link to the produced files.
Bye
PS obviously the files are available to all developers who know what they are.
For what you want to do, you donβt need to modify any drivers.
You just have to do a routine on each device:
If switch is On then turn Off after 2 sec.
Thanks - I deleted the ST Multipurpose Sensor Mc and switched to the Zigbee Contact Mc. Itβs now reflecting the temperature, but the tile is showing this weirdness which is why I was switching from the ST Multipurpose Sensor to begin with:
Hi @Mariano_Colmenarejo
Yes, you are absolutely right, in fact I had used your driver and created a routine which after 2 seconds would turn off the object. (from ON to OFF)
The only drawback is that the servo, in this way, makes two commutations
(UP to DOWN to UP - wait 2seconds - UP to DOWN to UP)
As far as Iβm concerned I could easily use it like this, butβ¦ why not improve
Interestingly deleting and re-pairing only worked with one of the two identical devices. I canβt get the other to show anything but the contact sensor on the main tile. It is using the Zigbee Contact Mc by default when it pairs. Ugh. This system gets more frustrating every day.
Iβve been having issues with my Centralite temperature/humidity sensors as well. A couple just will not pair correctly, even when switched to stock drivers. They always default to custom drivers. I believe there is something with the custom drivers that is causing them to not pair correctly, or not do an initial sync correctly, and then they fail to work when switched to the desired drivers.
Hello @Mariano_Colmenarejo, my Fingerbot Plus seems to have the following manifacturer code: _TZ3210_j4pdtz9v (model TS0001) instead of the one that you mapped (_TZ3210_dse8ogfy).
βββββββββββββββββββββββββββββββββββββββββββββββββββ
Name Zigbee Switch Mc
Version 2023-09-04T12:26:07.568365363
βββββββββββββββββββββββββββββββββββββββββββββββββββ
- id: "_TZ3210_j4pdtz9v/Fingerboot"
deviceLabel: Fingerboot Plus
manufacturer: _TZ3210_j4pdtz9v
model: TS0001
deviceProfileName: switch-battery
Hi @Mariano_Colmenarejo
Sorry to bother you again for this object (Fingerbot PLUS zigbee) but it seems that for now your βZigbee Switch MCβ driver is the best performing one (Wesley is still working on it).
As you said, the routine also resolves the issue of the OFF - ON - OFF state.
The problem remains that the battery level is not displayed⦠Do you think there is anything you can do?
Thank you for your job.
@Mariano_Colmenarejo - Hi, do you know if the Halo RL56 Zigbee lights are compatible with your driver? If not, what do you need to add them? I see other posts providing screenshots of the light details, but can seem to find that in my ST app for my Halo lights. Below is a link to their website.