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

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.

Following up on my October 1 question: is there a supported SDK3 route for SmartStart enrollment into a custom driver, or for using the required notification while the device remains Generic-owned?

For clarity, the observed test setup and results were:

  • Homey Pro (Early 2023), Homey OS 13.5.0 at the time of testing.
  • Yale YRD430-F-ZW3, Z-Wave firmware 2.40; S2 Access observed on a working paired Yale.
  • Non-secret fingerprint verified from a working paired Yale: manufacturer 297 (0x0129), productType 33031 (0x8107), productId 18899 (0x49D3). All three match the custom HA-002 v1.5.4 Apps SDK3 driver’s manifest, which sets requireSecure: true.
  • Classic inclusion failed through both the custom-driver and Generic Z-Wave paths.
  • Controller-level SmartStart through Devices > Add Device > Z-Wave paired successfully, but assigned the device to Generic/Default Z-Wave rather than HA-002.
  • The inclusion UI launched from the custom driver’s Connect button did not offer SmartStart.

I would appreciate clarification on four points:

  1. SmartStart and driver ownership: What is the supported enrollment/provisioning workflow for an SDK3 custom Z-Wave driver? Should controller-level SmartStart match an installed custom driver by fingerprint? Are additional manifest settings, publication/distribution requirements, or other documented conditions involved?
  2. Generic-to-custom reassignment: Is there a supported way to transfer an already-included device from Generic to the matching custom driver while preserving its inclusion/security relationship? If this is unsupported, please confirm the supported alternative and its limitations.
  3. Generic-owned notifications: Can an SDK3 app subscribe through a supported API to Notification CC Access Control (type 0x06), Event 6 (Keypad Unlock Operation), from a device owned by Generic? Alternatively, does Generic expose documented event/source metadata that distinguishes keypad unlock from manual/thumbturn or RF unlock? Ordinary Unlocked state alone is insufficient for this project; runtime source metadata has not been validated.
  4. Comparable Classic-inclusion report: In this Yale Assure Lock 2 report, Dustysa4 describes learn-mode inclusion through Generic Z-Wave followed by a DSK prompt, explicitly without SmartStart. The preceding post identifies Assure Lock 2 Touch with AYR-MOD-ZW3-USA firmware v2.40.0. This is comparable hardware, not proof of identical hardware or fingerprint. Are there documented model/module, inclusion-sequencing, Homey-version, or security-negotiation differences that could explain why that Classic path works while ours failed? Has later Homey support changed either path?

Links to official documentation, a minimal supported example, or a clear statement of unsupported behavior would help us choose the next step. No further pairing or driver changes are being performed while this is unresolved. Please keep replies free of PINs, DSK values, network/security keys, or other credentials.

Thank you!