That looks like it should work.
Unfortunately not. It turns the coffee machine on, and one minute later turns it off again. Im trying to get the espresso maker to stay on, but the fingerbot somehow revert back to “off” without physically pushing the button again.. or else it be able to give the “on” command even if it’s turned off (I think that could work)
I think I see the problem. You may not need this automation. The FingerBot probably automatically resets after each activation. That is how my SwitchBot works.
EDIT: In you automation utilizing the FingerBot you my need to use Turn On or Off (toggle) instead of Turn On. Then the state of the switch in ST does not matter.
In my automation I am not seeing a toggle option. I only have 3 options- turn on, turn off, and turn on and off which will turn the device on and after a specified amount of time later it’ll turn off again
I believe the OP talks about what I’m trying to accomplish further up in the post, but I’m having a hard time understanding and implementing it
It’s Turn on or turn off, which is a toggle. If you don’t care about the state use that as action as suggested.
Regarding reverting the state of the device, you can’t given the explanations by Mariano.
Ah I see that option now when I build a new routine. I was looking at the generic ones that are already listed when you go into the routine page.
That’ll have to suffice, thanks for all your help!
@Mariano_Colmenarejo I hope you feel good 
My friend @Niro_Gabriel just installed that device and all the additions for setting the FingerBot are not present. Here is what he got:
The FingerBot is working and perform clicks when ON and when OFF, but calibration is misiing and switch type as well. Seems like all the costume capability that you created is not there…. Can you please check what happened ?
Hi,
It will have been paired as a generic TS001 because the manufacturer will not be in the fingerprints.
This is @Niro_Gabriel FingerPrint:
Model Name: TS0001
Manufacturer Name: _TZ3210_a04acm9s
And There are also that I find:
Manufacturer Name: _TZ3210_7vgttna6
Manufacturer Name: _TZ3210_cm9mbpr1
Please add them all
Added two fingerprints in this driver version
───────────────────────────────────────────────────
Driver Id bc53adfe-d18f-4ea4-9610-6aade6696b7a
Name Zigbee Switch Mc
Package Key Zigbee_Switch_v6.5
Version 2025-12-18T16:46:29.761614002
───────────────────────────────────────────────────
#added dec-25
- id: "_TZ3210_a04acm9s/Fingerboot"
deviceLabel: Hej Fingerbot Plus
manufacturer: _TZ3210_a04acm9s
model: TS0001
deviceProfileName: switch-battery
-id: "_TZ3210_7vgttna6/Fingerboot"
deviceLabel: Hej Fingerbot Plus
manufacturer: _TZ3210_7vgttna6
model: TS0001
deviceProfileName: switch-battery
Hi! I have two fingerboards both using the MC switch v6.5. I am using click mode as I want the bot to go down and then back up. With each motion change state from on to off. One of them is working great. The other reverts to OFF exactly 1min after it is invoked and switches state to ON. When it resets to OFF the finger not is not moving, the state is just changing. This is happening on just one of my two identical setups. Is there a way to force a reset of the configuration? It seems to be stuck in Program or Random mode or something maybe?
Have you tried deleting the device, resetting and pair with smartthings again?
See if this driver works with your device:
Thanks, I will try it. After multiple changes to the Mariano driver settings it eventually started to work properly. The random or program mode must have been stuck on. Personally I don’t understand the use of these random options I see in edge drivers. Seems silly to me to make something do whatever.
See for yourself why it is like it is…
It uses something like a catch-all profile that is used for many other devices, where it theoretically makes sense. That’s why I prefer dedicated drivers for very similar models over “everything but the kitchen sink” drivers.
What I believe is that in the rush, little time is dedicated to thinking about the potential uses of the various custom functions of an edge driver.
In case the AI misleads, I’ll tell you firsthand, without any training…
These functions are the result of many hours of effort from many users over the last 5 years, thinking about the different functions that could improve the operation of their devices, and the many hours dedicated to implementing these functions without slowing down or degrading the driver’s functionality. The functions are available when needed, without requiring dozens of different drivers to be installed or having to search for them in the community.
That’s why SmartThings designed and perfected subdrivers, providing more efficient use of the hub than using multiple repetitive drivers, especially for users with many devices. Also included are user preference settings, which allow for customized functionality.
The only complication is for whoever has to write and test the driver with subdrivers and preferences. For users, there are many advantages: a single driver for hundreds of different and customizable devices. There’s also a minor complication: an interface with more capabilities that requires a bit more thought, but our brain will thank you in the long run.
A Fingerbot, like a switch, can be used to control a light, a fan, a humidifier, and many other simple things.
The random function is useful for simulating lights turning on and off when you’re away from home, for example.
The scheduled function is useful for maintaining controlled humidity, using a simple exhaust fan, for example.
The virtual power meter is useful for monitoring the energy consumption of the simple devices connected to the Fingerbot, for example.
The native Zigbee group assignment allows you to use the device in native Zigbee groups without needing a hub, for example.
This, along with many other custom features of the various edge drivers, adds value to the platform and improves device usability. These features, such as circadian rhythm support, gradual power-on, etc., were not available with the stock drivers some time ago, or are still unavailable today or need cloud exection
I hope you enjoy functions when you need them, or that your imagination comes up with an unexpected or new use for them. And if you don’t need them, don’t worry; you won’t lose any efficiency or performance on your device, driver, or hub.
Regards