Thanks Jeff1 for the steps and hope my slight modification helps anyone with an older Gen Schlage lock

I will defenitely play with all the options!

Huib_o:

What am I doing wrong? I installed your driver . but I do not get the “three times:” button

The dual button does not support triple press natively, only double press.

The driver implements a hack to give you a triple press option but you have to enable it in the settings and, as explained in the first post, it’s not 100% reliable given the button does not actually report the third press.

Regarding the Toggled Up, it is indeed the release of the long press.

Currently, I have tried following -

Reset the Hub (tried multiple times - holding reset button, connect power, wait until solid yellow light and leave reset button). This goes through the process of flashing blue light for about 5-7 seconds, solid blue for 5 seconds and then red/green flashing. At this point, I scanned QR code, followed Ethernet/WiFi options, and in the hub detection screen → ST app shows “Something went wrong error 33-303”

I tried manual method by selecting v3 hub option, at one step it asks for serial number, but it would not proceed to next even though S/N entered is correct. Looks the handshake between cloud and hub or the app is not happening.

What am I doing wrong? I installed your driver . but I do not get the “three times:” button.

The “toggled up” is in fact a long hold and release? Works nice.

Thanks anyway.

I live on more locations and only on the TP-link (No settings changed) it started working.

I already had to throw one away because I really bricked it. pfff. Anyway. I am strtaing those new V4 ones and they are great but no Z-wave

Believe me: i tried everything. cost me days….

Is there a better process to get a new hub added to my smartthings environment?

I also love how things in general gain momentum. Every other week Google Home adds long missing features (Cameras! Window sensors! Heating!), and even Alexa has had some noticeable under-the-hood improvements (like response time from a Thread button to my ancient BLE mesh light bulbs all of a sudden is fast).

Also to note maybe that my IKEA devices (those that connect to the ST hub) did come back on their own after the last couple of beta ST hub firmware updates. Yes some of them did take their sweet time.

Hopefully a button firmware update will fix it, I guess they’ll add support for Matter 1.4 next time they update them, right now they are Matter 1.3 where Long Idle Time (LIT) was even provisional so might have bugs. I tried to switch to Short Idle Time to test but doesn’t seem like I can change it and, after a reset, SmartThings defaults to LIT.

Dear hardware and firmware developers: Watchdog Timers are a thing. Use them.

This is not rocket science.

There has been a big improvement generally but it’s all still a bit flaky. Waiting for the IKEA plugs to see if I can improve my mesh before
making any decisions.

I’ve rebooted both hubs and attempted again to add the device and that hasn’t helped.

I’d greatly appreciate any troubleshooting help.

Figured the serial number on back of the battery plate: SN 3010081647 not able to activate it

While users could theoretically use SmartThings’ built-in automation, we aim to handle these complex configurations on our own cloud to simplify the experience for users who may find manual setup difficult.

Specifically, we need to subscribe to real-time events from external devices integrated with SmartThings and utilize that data for our service, rather than relying on the inefficient polling method.

I am using the SmartThings CLI on Windows to manage my SmartThings apps. After running `smartthings login`, my browser opens and redirects me to a localhost URL like:

http://localhost:61973/finish?code=2RoZxx

However, after that, when I try to list my apps:

smartthings apps

I get the following error:

TypeError: Invalid URL
Code: ERR_INVALID_URL

Environment details:

• OS: Windows 10/11
• Node.js version: (please insert your version)
• SmartThings CLI version: (please insert your version)

Steps I have tried:

1. Logging out and back in
2. Updating CLI to the latest version
3. Restarting the terminal

Could you please help me understand why this error occurs and how to fix it?

Thank you.
Dyaa Kassoma

v2026-03-10 - Version: 2026-03-10T11:46:42.497344974

• Cleaned up onboarding to hopefully prevent command initialization issues
• Added support for button 6 when using momentary as 3-way switch
• Added support for ZEN35 parameters 42, 43 for fw 1.10 and higher

UPDATE: Zooz Plugs v2026-03-15

Sorry I have to keep moving things around, this is again due to the SmartThings limit on each driver package to 512Kb. With the support for multiple firmwares and adding full descriptions the profiles keep growing in size. The switch package got too large for upcoming updates so I had to move something out of it.

For continued full feature support on these plugs please change to this new driver.

Supported Models:

ZEN04, ZEN05, ZEN06, ZEN15

v2026-03-15 - Version: 2026-03-15T18:50:45.459370036

• Split Plugs into separate driver due to SmartThings driver package size limits.
• Removed unnecessary custom capabilities and device-configs

UPDATE: Zooz Switch v2026-03-15

v2026-03-15 - Version: 2026-03-16T01:10:19.276878272

• Removed fingerprints for ZEN04, ZEN05, ZEN06, ZEN15 - use new Zooz Plugs package
• ZEN53 - added param 19, 20 for fw 1.40
• ZEN54 - added param 15-19 for fw 1.30 and fw 1.40 changes
• Removed some unnecessary custom capabilities (firmware, associations, networkID)

UPDATE: Zooz Relay v2026-03-15

Moving ZEN51 and ZEN52 to the relay package so they can eventually share some of the same code with the ZEN57/58 for the separated inputs and child devices. Eventually the fingerprints will be removed from the other packages they are included in.

NOTE: If you have issues with the ZEN52 and unexpected state changes on Relay 2 or the separated inputs, you may need to update to a patched 1.90 firmware from Zooz.

v2026-03-15 - Version: 2026-03-16T02:29:08.403975796

• Added support for ZEN51 and ZEN52 with all settings for current firmware
  • Support to disable input trigger to separate inputs from relays
  • Does not have option to create child devices at this time

The_Halo_Bros:

is there a reason that the internal hubs lag behind the standalone ones?

I’ve always assumed it is because the V1/V2/V3/V4 are SmartThings in-house hubs, albeit no longer with an in-house sales channel, and all the others are third-party products, albeit with that third-party being Samsung.

I was unable to connect any of my devices. I have managed to find a couple of channels to force a download of nonstandard drivers. (Like Sonoff). I even found aa official Smarthings channel, but they claim they are only beta drivers.

Is the a way to force the standard drivers to download, or is there a Channel I can register with to download the standard, non-beta drivers?

I tried to create a new location and connected to a different router/ blocked NTP port 123 in access control - neither of it worked.

Let me try with other suggestions, while waiting for the Smartthings staff to review the logs that I had shared.

There was a time when if the mobile app was being used to set a Location it seemed to be able to correctly find a location by address, then did a reverse lookup using the correct latitude and longitude and picked up an incorrect address to display, and then bizarrely used that incorrect address to look up the incorrect latitude and longitude and saved that. It stopped being so ridiculous and generally an incorrect address, or no address at all, is only a display issue in the app.

You started by saying all your geolocation routines were failing. That could be, and perhaps is likely to be, a coincidence. I have had to disable and reenable location on all the household phones this year as they all started misbehaving. There was a time when I had to do this every time the mobile app updated but that hasn’t been an issue for years and there hasn’t been an update this year.

I would also suggest looking to see what Google Maps is up to as the Google Location Services are being used and they can be eccentric and indeed hopelessly and stupidly incorrect. In particular, I find it useful to make sure my home is explicitly marked on the map in the correct place and that a completely different property isn’t. I also occasionally check where Google believes the centre of my post code is as I don’t think it has grown out of its habit of moving it to completely the wrong place to accommodate incorrect user input.