# Zwave device ist "unknown", but as "known" expected - can't see the reason

**URL:** <https://community.openhab.org/t/zwave-device-ist-unknown-but-as-known-expected-cant-see-the-reason/165954>\
**Category:** Bindings\
**Tags:** zwave\
**Created:** [August 27, 2025, 5:08pm UTC](https://community.openhab.org/t/zwave-device-ist-unknown-but-as-known-expected-cant-see-the-reason/165954 "2025-08-27T17:08:00Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Duke\_Jones](https://community.openhab.org/user_avatar/community.openhab.org/duke_jones/32/91350_2.png) [@Duke\_Jones](https://community.openhab.org/u/Duke_Jones)\
**Post date:** [August 27, 2025, 5:08pm UTC](https://community.openhab.org/t/zwave-device-ist-unknown-but-as-known-expected-cant-see-the-reason/165954/1 "2025-08-27T17:08:00Z")

</div>

Hi everyone 🙂 ,

my system: openhabian 4.3.7/64bit on Raspberry 8 GB

On my OH v4.3.2 I integrated a “Fibaro Rollershutter 4” into my zwave network. Sadly the device was recognized as “unknown” by openHAB (of course, because the first time it was included in the zwave database was on March ‘25 while OH v4.3.2 was released on January’25).

Ok, now I’ve updated my system to v4.3.7 (released in August ’25). Hopefully I deleted the thing from openHAB and started a scan on the zwave binding but the device is still recognized as “unknown.

Do I have wrong expectations or did I something wrong ?

```yaml
2025-08-27 17:04:17.092 [WARN] [wave.discovery.ZWaveDiscoveryService] - NODE 31: Device discovery could not resolve to a thingType! 010F:0304:1000::8.2

```

```yaml
openhab> list | grep -i zwave
303 │ Active │ 80 │ 4.3.7 │ openHAB Add-ons :: Bundles :: ZWave Binding

```

---

<div class="post-metadata">

**Author:** ![rlkoshak](https://community.openhab.org/user_avatar/community.openhab.org/rlkoshak/32/75251_2.png) [@rlkoshak](https://community.openhab.org/u/rlkoshak)\
**Post date:** [August 27, 2025, 5:23pm UTC](https://community.openhab.org/t/zwave-device-ist-unknown-but-as-known-expected-cant-see-the-reason/165954/2 "2025-08-27T17:23:48Z")

</div>

I don’t think the updated Zwave database was pack ported to 4.3.7. There’s no mention in the release notes that anything changes with Zwave. You probably need to upgrade to OH 5 to get this device working with the current set of releases.

---

<div class="post-metadata">

**Author:** ![apella12](https://community.openhab.org/user_avatar/community.openhab.org/apella12/32/117154_2.png) [@apella12](https://community.openhab.org/u/apella12)\
**Post date:** [August 27, 2025, 5:45pm UTC](https://community.openhab.org/t/zwave-device-ist-unknown-but-as-known-expected-cant-see-the-reason/165954/3 "2025-08-27T17:45:28Z")

</div>

True. No Zwave DB updates in 2025 were included in any 4.3.x patch release.

Another option besides upgrading to 5.0 is to modify your 4.3.7 jar with the needed XML file using this tutorial.[Update ZWave binding with new/updated device xml - Tutorials & Examples - openHAB Community](https://community.openhab.org/t/update-zwave-binding-with-new-updated-device-xml/147248)

EDIT: For a head start here is the file;

[fgr224\_0\_0.xml](https://community.openhab.org/uploads/short-url/67CIDQbG9j3ZYmTf1RRRsDmOY6J.xml) (16.9 KB)

---

<div class="post-metadata">

**Author:** ![Duke\_Jones](https://community.openhab.org/user_avatar/community.openhab.org/duke_jones/32/91350_2.png) [@Duke\_Jones](https://community.openhab.org/u/Duke_Jones)\
**Post date:** [August 27, 2025, 5:54pm UTC](https://community.openhab.org/t/zwave-device-ist-unknown-but-as-known-expected-cant-see-the-reason/165954/4 "2025-08-27T17:54:05Z")

</div>

@apella12 ah, thanks. I will try this and report…

EDIT:

It works perfectly. Thank you 🙂