New Jasco Z-Wave is "Unknown"

I bought one of the new Jasco z-wave switches that’s lower profile than the older ones, however HA doesn’t recognize it probably because its device ID isn’t in the XML file yet. I presume the functionality is the same as the older model and it’s a copy and paste job.

How does that get updated? It comes up as Unknown: type=4944, id=3235, which means of course it’s missing all of the node settings/options although it does work for on/off/dimming. Is this a bug for Homeassistant or for openzwave?

You can update the device config by editing device config files in your HA installation. HA uses OpenZWave 1.4, and updates are not being accepted for that version, so you are on your own. If this is a new version of the 14294, you could just duplicate this line with the new Product ID and you’ll get all the same config options (assuming they are the same).

Is this a bug for Homeassistant or for openzwave?

It’s not a bug, but device updates belong with the OpenZWave project. New configs are contributed by the community. If you want to create a new config for 1.6, your contribution will be welcome. Hopefully, HA can move to 1.6 in the near future (work in progress).

Note that the XML format is different between 1.4 and 1.6, I linked instructions for both.

Thanks. Looks like the hard part is going to be finding where that file exists on the Pi I have it running on.

1 Like

What is your installation type? The files reside within the python modules path. A simple find . -name manufacturer_specific.xml from some root directory can find it.

The alternative is to download the config files somewhere, and set the config_path option in the zwave config. If you’re using docker, you’ll have to do it this way because the container contents will revert after an upgrade.

More than a year later, I’m also running into this with the same Jasco Z-Wave smart dimmer as the OP.

I’m running HassOS 4.17 on a Raspberry Pi 3 with the Z-Wave integration; not the OpenZWave (beta).

It looks like the Z-Wave Integration is still based on the older OpenZwave 1.4 according to what’s logged in OZW_Log.txt:

2020-12-02 21:19:01.948 Always, OpenZwave Version 1.4.3469 Starting Up

The instructions in previous posts (2, 4) to update the device config files is not straight forward on my system running on the Raspberry Pi. I don’t see any of the files such as manufacturer_specific.xml even when searching the entire Pi. The following produces no results:
sudo find / -name manufacturer_specific.xml -print

Would I be better off upgrading to the newer OpenZwave Beta that’s based on OpenZwave 1.6 in order to get this newer device working?

Thanks for any insight.