# Force On/Off Z-wave device to work even though there is no driver

**URL:** <https://community.homey.app/t/force-on-off-z-wave-device-to-work-even-though-there-is-no-driver/102857>\
**Category:** Questions & Help\
**Created:** [January 31, 2024, 6:42pm UTC](https://community.homey.app/t/force-on-off-z-wave-device-to-work-even-though-there-is-no-driver/102857 "2024-01-31T18:42:51Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![surf123](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/surf123/32/71094_2.png) [@surf123](https://community.homey.app/u/surf123)\
**Post date:** [January 31, 2024, 6:42pm UTC](https://community.homey.app/t/force-on-off-z-wave-device-to-work-even-though-there-is-no-driver/102857/1 "2024-01-31T18:42:51Z")

</div>

I have Leviton On/Off switches that are in the Z-wave node list as unknown and even have working routes. I can test and switch them on/off perfectly from the node list. Is They even have a last working route. I have removed and added them multiple times and always get the same error. Is there a way to force a device to be identified as a Basic Z-wave device. If not can this be added.

---

<div class="post-metadata">

**Author:** ![Peter\_Kawa](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/peter_kawa/32/173848_2.png) [@Peter\_Kawa](https://community.homey.app/u/Peter_Kawa)\
**Post date:** [January 31, 2024, 6:54pm UTC](https://community.homey.app/t/force-on-off-z-wave-device-to-work-even-though-there-is-no-driver/102857/2 "2024-01-31T18:54:30Z")

</div>

> [@surf123](#):
>
> are in the Z-wave node list as unknown and even have working routes. I can test and switch them on/off perfectly from the node list. Is They even have a last working route

I don’t get it, what is the issue here? It seems to be working fine. “Unknown zwave device” means nothing more than “Homey could not find a matching app for this device, so it is now added as a generic Homey zwave device”  
Of course Homey recognizes it as a OnOff switch, or doesn’t it? Does Homey think it’s a thermostat, or speaker?

> [@surf123](#):
>
> always get the same error

It probably would help, when you are willing to reveil the error message as well… ?

---

<div class="post-metadata">

**Author:** ![surf123](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/surf123/32/71094_2.png) [@surf123](https://community.homey.app/u/surf123)\
**Post date:** [January 31, 2024, 10:13pm UTC](https://community.homey.app/t/force-on-off-z-wave-device-to-work-even-though-there-is-no-driver/102857/3 "2024-01-31T22:13:36Z")

</div>

It works fine from the Tools-\>Devices page on the developer site (on/off/test/test frame) and has a direct route from the Homey. It does not show in Wireless-\>Z-Wave or on the App. My wording was incorrect and should have been “unknown node”.

---

<div class="post-metadata">

**Author:** ![JPe4619](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jpe4619/32/9017_2.png) [@JPe4619](https://community.homey.app/u/JPe4619)\
**Post date:** [February 1, 2024, 11:14am UTC](https://community.homey.app/t/force-on-off-z-wave-device-to-work-even-though-there-is-no-driver/102857/4 "2024-02-01T11:14:21Z")

</div>

> [@surf123](#):
>
> identified as a Basic Z-wave device.

Unknown device = Basic device

---

<div class="post-metadata">

**Author:** ![Peter\_Kawa](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/peter_kawa/32/173848_2.png) [@Peter\_Kawa](https://community.homey.app/u/Peter_Kawa)\
**Post date:** [February 1, 2024, 11:25am UTC](https://community.homey.app/t/force-on-off-z-wave-device-to-work-even-though-there-is-no-driver/102857/5 "2024-02-01T11:25:15Z")

</div>

Additionally, when you want to use it in flows, you can’t use the ‘apps’ section (while it uses no app), but you’ll need to look up the device per ‘Zones’ and navigate to the zone it resides in.  
Or just use the search bar.

 ![Screenshot_20240201-124707_Firefox](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/c/4/c4b3c5e7167e905ccda892c775c10fbc6586c2f5.jpeg)

---

<div class="post-metadata">

**Author:** ![surf123](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/surf123/32/71094_2.png) [@surf123](https://community.homey.app/u/surf123)\
**Post date:** [February 3, 2024, 11:19pm UTC](https://community.homey.app/t/force-on-off-z-wave-device-to-work-even-though-there-is-no-driver/102857/6 "2024-02-03T23:19:51Z")

</div>

![Screenshot 2024-02-03 at 6.15.08 PM](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/1/0/1026fda378bd085f5ad9b06742896b03ab9742bd.png)

#27: Leviton On/Off Switch (no routes but can turn on/off from this screen  
#32: Leviton Dimmer (routes and can turn on/off from this screen

Neither are accessible from the App. I do not care about the dimming capability, but just want on/off which I know work.

---

<div class="post-metadata">

**Author:** ![Peter\_Kawa](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/peter_kawa/32/173848_2.png) [@Peter\_Kawa](https://community.homey.app/u/Peter_Kawa)\
**Post date:** [February 4, 2024, 1:34pm UTC](https://community.homey.app/t/force-on-off-z-wave-device-to-work-even-though-there-is-no-driver/102857/7 "2024-02-04T13:34:42Z")

</div>

Hmmm, unknown nodes probably don’t have flowcards indeed.  
Isn’t it possible to repair those? Or re-pair without removing them prior to that?  
I’m not a zwave expert btw.

 ![Screenshot_20240204-143341_Chrome](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/6/0/600bb7207af479ee0e108d60f306fa3735e35277.jpeg)

---

<div class="post-metadata">

**Author:** ![surf123](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/surf123/32/71094_2.png) [@surf123](https://community.homey.app/u/surf123)\
**Post date:** [February 4, 2024, 9:29pm UTC](https://community.homey.app/t/force-on-off-z-wave-device-to-work-even-though-there-is-no-driver/102857/8 "2024-02-04T21:29:13Z")

</div>

No flow cards as you guessed. Repair does not offer any devices up to repair. Message is “No devices that can be repaired are available.”

I have unpaired and paired multiple times with the same results. It is unfortunate because these are Leviton switches that were expensive and match with the other Leviton switches in my home. It just seems weird that I can send on/off, test, send frame and all are good results. It would be nice if I could change it to be a generic Z-wave device.

---

<div class="post-metadata">

**Author:** ![surf123](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/surf123/32/71094_2.png) [@surf123](https://community.homey.app/u/surf123)\
**Post date:** [February 5, 2024, 2:21pm UTC](https://community.homey.app/t/force-on-off-z-wave-device-to-work-even-though-there-is-no-driver/102857/9 "2024-02-05T14:21:04Z")

</div>

Hoping one of the developers of Homey could step in and provide some insight as to how to work around this.

---

<div class="post-metadata">

**Author:** ![Peter\_Kawa](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/peter_kawa/32/173848_2.png) [@Peter\_Kawa](https://community.homey.app/u/Peter_Kawa)\
**Post date:** [February 5, 2024, 2:43pm UTC](https://community.homey.app/t/force-on-off-z-wave-device-to-work-even-though-there-is-no-driver/102857/10 "2024-02-05T14:43:23Z")

</div>

Hoping doesn’t work, reporting your issue to [support](https://homey.app/support) could work better 😉  
Officially this is a users only forum…
