# Problem adding Sunricher SRP-ZV9105-75CC (Z-Wave Dimmable LED Driver)

**URL:** <https://community.homey.app/t/problem-adding-sunricher-srp-zv9105-75cc-z-wave-dimmable-led-driver/144417>\
**Category:** Devices\
**Tags:** z-wave\
**Created:** [October 22, 2025, 6:45pm UTC](https://community.homey.app/t/problem-adding-sunricher-srp-zv9105-75cc-z-wave-dimmable-led-driver/144417 "2025-10-22T18:45:57Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![yuriestevan](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/yuriestevan/32/123647_2.png) [@yuriestevan](https://community.homey.app/u/yuriestevan)\
**Post date:** [October 22, 2025, 6:45pm UTC](https://community.homey.app/t/problem-adding-sunricher-srp-zv9105-75cc-z-wave-dimmable-led-driver/144417/1 "2025-10-22T18:45:57Z")

</div>

Hi everyone,

I’m trying to add a **Sunricher SRP-ZV9105-75CC Z-Wave Dimmable LED Driver** to my Homey (EU frequency, 868.42 MHz), but I always get the same error:

> “Unable to connect — Something went wrong while adding the device.”

I’ve tried multiple approaches:

- Using the **Sunricher app** , **ROBB Smarrt app** , **easylighting app** and **Generic Z-Wave device**

- Factory reset of the device before each attempt

- Adding both **secure** (S0 / S2) and **non-secure**

- Creating my own **custom app** using the correct manufacturer and product IDs

- Even forcing `"secure": []` to disable security completely

In every case, Homey shows _“Unable to connect”_ (sometimes _request\_timeout_) and the app log shows no activity — meaning the pairing never actually starts communication.

* * *

What I’ve verified

Using **Silicon Labs PC Controller** (Simplicity Studio):

- The device includes successfully and responds to commands normally.

- Here’s the information from the Z-Wave log:

```auto
Manufacturer ID: 0x0330 (816)
Product Type ID: 0x0200 (512)
Product ID: 0xD002 (53250)
Z-Wave Plus Version: 2
Role Type: Always On Slave (AOS)
Node Type: Z-Wave Plus Node

```

So my `driver.compose.json` looks like this:

```auto
"zwave": {
  "manufacturerId": [816],
  "productTypeId": [512],
  "productId": [53250],
  "secure": ["S0", "S2_UNAUTHENTICATED"]
}

```

Still, Homey always fails with a timeout before reaching the `onMeshInit()` in the device driver.

* * *

### My suspicion

It looks like Homey can’t complete the secure inclusion (S2 negotiation), or the product ID is not matching internally.  
Interestingly, the same device includes and works fine through the **Z-Wave PC Controller** , so the hardware itself is okay.

* * *

### What I’m asking

Has anyone managed to include **Sunricher SRP-ZV9105-75CC** or a similar Z-Wave dimmable driver with Homey?  
Is there any known issue with S2\_UNAUTHENTICATED negotiation or Z-Wave inclusion timing on these devices?  
Would forcing Homey to include _non-secure only_ be possible through the app manifest?

* * *

Thanks in advance for any help — I’ve spent quite a few hours debugging this one and would really appreciate any insight.

— Yuri