Charmed Quark Systems, Ltd. - Support Forums and Community

Dean,

What Z-Wave devices do you already have definitions for in the driver?  Specifically door/window sensors aka contact sensors. 

As you know currently I'm running a mostly Insteon setup with ISY (any chance of getting a few updates???) and all of my current motion and contact sensors are Insteon.  This works great but as I transition to RadioRA 2 that leaves with less dual-band Insteon devices for the open/close sensors to work with.  Also once this migration is complete I won't have any Insteon devices left but I will have Z-Wave thermostat's left.  So I need to know what the options are for contact sensors.

Ultimate goal is to install an ELK panel and use that for contact sensors (wireless) for interior doors used with automations.  I'm looking for a middle-ground in-between solution and as I already have Z-Wave devices that are not being replaced anytime soon I can use Z-Wave.

I figured it best to find out what sensors the driver already supports and I could buy those versus buying sensors and sending you information and hoping you have time to add them to an update.

If you look in [CQC]\CQCData\Local\ZWInfo there's a ZWDevInfoIndex.xml file. This is a file that is compiled from the individual XML device info files and is used by the driver to know what is available. Don't modify it or the driver will stop working, but it has all of the devices in it.

Keep in mind that single sensors are pretty trivial to add. Unless they are stupidly designed they will fall with in a standard pattern that we already handle and it's just a matter of whipping up a device info file for it, which can usually be done by eye for simple devices like that. Multi-sensors are a huge PITA. Even though there's some standards for dealing with them, almost no one ever adopts that standard (multi-channel.) Instead they all do some stupid ad hoc thing that requires special knowledge in many cases. But single sensors that just report one thing like motion, open/close, etc... those are easy to deal with.

(02-01-2020, 07:20 AM)Dean Roddey Wrote: [ -> ]If you look in [CQC]\CQCData\Local\ZWInfo there's a ZWDevInfoIndex.xml file. This is a file that is compiled from the individual XML device info files and is used by the driver to know what is available. Don't modify it or the driver will stop working, but it has all of the devices in it.

Keep in mind that single sensors are pretty trivial to add. Unless they are stupidly designed they will fall with in a standard pattern that we already handle and it's just a matter of whipping up a device info file for it, which can usually be done by eye for simple devices like that. Multi-sensors are a huge PITA. Even though there's some standards for dealing with them, almost no one ever adopts that standard (multi-channel.) Instead they all do some stupid ad hoc thing that requires special knowledge in many cases. But single sensors that just report one thing like motion, open/close, etc... those are easy to deal with.

Cool I'll go check what's in that file and pick some sensors from what's already there.

Yeah multi-sensors are a PITA.... looking at Fibaro.... Details I've received from Z-Wave alliance is they are going to actually start enforcing sensors to be certified.  This is part of the new changes happening around opening spec, allowing 3rd party manufacturers.  We'll see if this improves things or not....