Out of curiosity I searched for the error message I got about invalid device class in the source and found that in the ZWaveDeviceClass, there is no definition for SPECIFIC_TYPE_SOUND_SWITCH under GENERIC_TYPE_AV_CONTROL_POINT.
I’m guessing this mapping needs to be added before it will work at all. Not sure what else needs to be added besides an entry in this enum, but I might give it a try if I can figure out how to build and install a custom version of the Z-Wave add-on for now.
The manufacturer number is the same as the Aeotec TriSensor’s attribute page (which also says, “Unknown Manufacturer”). But that was identified with the right product name.
Thanks again for all your help, Bruce!
I am still looking into building and using the Z-Wave binding from source so that I can experiment with adding the device classes to the allowable device classes enums (managed to build it, but am having trouble getting all the dependencies loaded when putting it into the /usr/share/openhab2/addons directory).
OK, that is a ZW164 and it is not in our database. Our newer database versions recognize that manufacturer ID.
If you have an xml file that may help us further. I will start building our the device as I find time.
A pdf copy of the user manual may be useful too.
Unfortunately, an XML file for the device doesn’t get generated though
I’m wondering if it’s because the data coming back from the device about its available device classes is being rejected by the Z-Wave binding (the “invalid device class” error I constantly get when the device is included).
Well I downloaded the manual and there is a lot of work to get all the configuration & other parameters entered. I have already started on it though.\I was hoping an xml file would help.
@chris or @sihui would updating from 2.4 to a snapshot binding perhaps help us get an xml file for this?
It looks like the device is using a new device class that needs to be added to the binding before the device can work. I will look into this tonight if jetlag doesn’t get the better of me!
Are you trying to create the database entry by hand? If so, I would really not recommend this and we should delete the endpoints that you’ve added. Generating this by hand will be very error prone - it is highly recommended to create the endpoints directly from the XML.
If you wanted to add the config parameters and associations, that’s fine, but leave the endpoints until the XML is available.
OK. I was going through the manual.
Would moving to a snapshot binding affect creating the xml file? It looks like 2.4 does not recognize the manufacturer ID.
The first 22 configuration parameters will be a real challenge to figure out how to present well.
I’ve deleted the endpoints now so you should be good to go. You must upload the XML to the same database entry that you’ve created. If there’s any issues I’ll take a look later - I have to go out shortly to meet up with work colleagues.