# SmartStart with a custom Z-Wave driver — SmartStart option missing from driver pairing flow

**URL:** <https://community.homey.app/t/smartstart-with-a-custom-z-wave-driver-smartstart-option-missing-from-driver-pairing-flow/160261>\
**Category:** Developers\
**Tags:** z-wave, homey-pro, homey-pro-2023\
**Created:** [October 1, 2026, 10:45pm UTC](https://community.homey.app/t/smartstart-with-a-custom-z-wave-driver-smartstart-option-missing-from-driver-pairing-flow/160261 "2026-10-01T22:45:25Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![J\_Reeves](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/j_reeves/32/79349_2.png) [@J\_Reeves](https://community.homey.app/u/J_Reeves)\
**Post date:** [October 1, 2026, 10:45pm UTC](https://community.homey.app/t/smartstart-with-a-custom-z-wave-driver-smartstart-option-missing-from-driver-pairing-flow/160261/1 "2026-10-01T22:45:25Z")

</div>

I’m working on a custom Apps SDK v3 Z-Wave driver for a Yale YRD430-F-ZW3 lock and have run into an interesting SmartStart issue on Homey Pro.

Setup:

- Homey Pro Early 2023
- Homey OS 13.5.0
- Yale YRD430-F-ZW3
- Z-Wave firmware 2.40
- S2 Access

The lock’s actual Z-Wave fingerprint, verified from a successfully paired identical Yale lock, is:

- Manufacturer ID: 297 / 0x0129
- Product Type ID: 33031 / 0x8107
- Product ID: 18899 / 0x49D3

My custom driver’s manifest uses those exact IDs and requireSecure: true.

Here is the behavior I am seeing.

CUSTOM DRIVER:

If I choose my custom Yale driver and press Connect, Homey opens the normal Z-Wave inclusion screen and tells me to put the lock into learn mode.

However, the SmartStart link is NOT present on this version of the pairing screen.

Classic inclusion does not successfully pair the lock.

GENERIC Z-WAVE:

If I instead go to:

Devices \> Add Device \> Z-Wave

I get essentially the same Homey Z-Wave pairing screen, except this version includes:

“If your device supports it, you can also connect using Z-Wave SmartStart.”

If I select SmartStart and manually enter the DSK from the lock’s Z-Wave module, the lock pairs successfully.

However, Homey then creates it as a Generic/Default Z-Wave lock rather than assigning it to my installed custom driver.

So the situation appears to be:

Custom driver  
 → Homey Z-Wave pairing  
 → no SmartStart option  
 → classic inclusion fails

Generic Z-Wave  
 → Homey Z-Wave pairing  
 → SmartStart option available  
 → SmartStart succeeds  
 → device becomes Generic Z-Wave

The physical device fingerprint exactly matches the custom driver.

Has anyone successfully used SmartStart with a custom Homey Apps SDK Z-Wave driver?

Specifically:

1. Is there an undocumented or newer manifest/SDK option for enabling SmartStart in a custom driver’s Z-Wave pairing screen?

2. Should a SmartStart device added through Homey’s generic Z-Wave screen automatically be matched to an installed custom driver after inclusion if all three Z-Wave IDs match?

3. Is SmartStart currently restricted to Homey’s Generic/Default Z-Wave pairing path?

4. If so, what is the recommended way for a custom driver to support an S2 Access lock that reliably joins through SmartStart?

I have screenshots showing the two nearly identical Homey pairing screens side by side — one without SmartStart when launched from the custom driver and one with SmartStart when launched from generic Z-Wave.

I’m deliberately not posting the DSK or any Z-Wave security information.

Any insight from someone who has worked with the newer Homey SmartStart implementation would be greatly appreciated.