HomeSeer HS-WD200+ Channels

Tutorials & Examples
1

Version: 2.5.0-SNAPSHOT (#1652)
openhab> bundle:list | grep -i zwave
217 x Active x 80 x 2.5.0.201908041243 x openHAB Add-ons :: Bundles :: ZWave Binding

I have a dozen HS-WD200+ things with firmware v5.9 and they work perfectly. I recently bought two new one’s with firmware v5.13 and v5.14 and they are missing all the config channels. Any ideas on how I can fix this?

OLD Things
{channel=“zwave:device:834762c1:node52:switch_dimmer”}
{channel=“zwave:device:834762c1:node52:scene_number”}
{channel=“zwave:device:834762c1:node52:config_decimal_param13”}
{channel=“zwave:device:834762c1:node52:config_decimal_param14”}
{channel=“zwave:device:834762c1:node52:config_decimal_param21”}
{channel=“zwave:device:834762c1:node52:config_decimal_param22”}
{channel=“zwave:device:834762c1:node52:config_decimal_param23”}
{channel=“zwave:device:834762c1:node52:config_decimal_param24”}
{channel=“zwave:device:834762c1:node52:config_decimal_param25”}
{channel=“zwave:device:834762c1:node52:config_decimal_param26”}
{channel=“zwave:device:834762c1:node52:config_decimal_param27”}
{channel=“zwave:device:834762c1:node52:config_decimal_param30”}
{channel=“zwave:device:834762c1:node52:config_decimal_param31”}

New Things
{channel=“zwave:device:834762c1:node53:switch_dimmer”}
{channel=“zwave:device:834762c1:node53:scene_number”}

2

There are two different devices in the database:
https://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/806
https://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/1040
The older version below firmware version 5.9 do not have the channels configured.
You need to add them please:
https://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-database-guide

1 Like
3

I download the Openhab2 XML files for both things and used WinMerge to do a diff… I then edited the 1040 file to include the missing channels as they were presented in 806. When I upload the new XML file I get the following error (Error ERR: XML file format is not known, or has incomplete information. You must use openHAB 1.8 or newer.). Any guidance on what I’m doing wrong would be helpful?

HS-WD200 New Firmware Version XML.txt
|attachment (23.3 KB)

4

You can’t upload a newer xml if the command classes are already available.
You need to manually add the missing config parameters (check the other device on how to do it)

5

Does anyone know the time table for updating the z-wave device setting merged from the online database? It seems the snapshot is immediate but testing hasn’t been updated and it’s been a few weeks.

I don’t want to run a snapshot version. Is there a way to only upgrade the z-wave database?

Thanks

6

You can update just the zwave binding which includes the updated database. The database is part of the binding.

1 Like
7

Thanks Bruce…

I’ve been searching the forums and can’t seem to find clear instructions on how to upgrade only the zwave binding to a snapshot. I downloaded org.openhab.binding.zwave-2.5.0-SNAPSHOT.jar from Jackson but have no idea what to do with it. Can you please point me in the correct direction?

8

I know this script works well if you re running 2.4 or 2.5M1. I am not sure it has been tested onn 2.5M2. @5iver would know.

9

I tested the script on snapshots before 2.5M2, but manual installs of both zwave and zigbee stopped working after they were migrated to bnd. Although, I kind of remember zwave started working again after some serial changes in core. I’m running S1674 in production. For me, the snapshots have only gotten better since 2.5M2.

1 Like
10

:frowning: The script ends with:

!!! It has taken more than two minutes to install the Z-Wave binding, so exiting !!!
[14:13:29] openhabian@openhab:/usr/share/openhab2/addons$

11

You are running OpenHAB 2.5M2, I presume?

12

Yes

13

Everything might have completed, but for some reason the REST API wasn’t returning the code to inform the script that the binding was installed. The manual steps are all listed in the readme.