Author
Topic: ZWave API (Read 60084 times)

I've just bought some zwave kit(AEON labs USB and HomePro socket) and am keen to see what drivers and libraries are out there. I see there is kernel driver but I'm not sure that is required for this stick as it may present itself as a serial device with the USB serial driver? Also I see there is a mention by Hari of a standalone library being worked, is there any more information on this?

I'm running dcerouter, mysql and a few DCE devices like Z-Wave "standalone" on fedora and openembedded. Not much hassle, but you need to understand some of the core components. Jump into #linuxmce-devel if you need more info.

Hi, I'm having difficulties in the installation of door/window sensor sm103 and hope to get some advice. Wiki is quite limited atm.

I included the sensor in the network with ACT HomePro ZTH200 remote. The response was 'only added to network 7'. OK. LMCE sees now the sensor (once the settings were downloaded from the remote), but sensor status is missing.

The Seluxit Multisensor e.g. has distinct groups for all sensor inputs.

Could somebody give me more info how to do that and where, please? I expected that for each subsensor will be created a child device under the Multisensor. Similar to GC100 interface. But it seems I was wrong.

The Seluxit Multisensor e.g. has distinct groups for all sensor inputs.

Could somebody give me more info how to do that and where, please? I expected that for each subsensor will be created a child device under the Multisensor. Similar to GC100 interface. But it seems I was wrong.

Thanks in advance.

There are no child devices yet, sambuca is working on the multi instance features. But you can use the seluxit now, just associate the dongle into those groups. The Z-Wave driver will send DCE events when it receives new values from the sensors.

The multi-instance support is mostly finished. What could still be improved is the detection of devices. But that is another story, as it would require mapping each device to the correct multi instance device templates. I.e. the EZMotion sensor should be added as one motion detector and two multilevel sensors, but as the device reports itself as a multilevel sensor with three instances, it is currently added as three multilevel sensors.But they are not added as child devices, but as three devices on the same level. This is because one device can contain sensors that are of different types, like the EZMotion, it has two climate sensors, that needs to be added below the climate interface, and one motion sensor, which needs to be added below the security interface.

I haven't figured out the proper way to do it, but it should be along the lines of the already existing device template system in LMCE. I'm not actively working on this, so anyone should feel free to take it on