Author Topic: ZWave API  (Read 54340 times)

yowl

  • Newbie
  • *
  • Posts: 4
    • View Profile
Re: ZWave API
« Reply #135 on: September 23, 2009, 10:12:10 am »
Hi,

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?

Thanks

Scott

hari

  • Administrator
  • LinuxMCE God
  • *****
  • Posts: 2421
    • View Profile
    • ago control
Re: ZWave API
« Reply #136 on: September 24, 2009, 11:20:30 am »
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.

best regards,
Hari
rock your home - http://www.agocontrol.com home automation

Kooma

  • Veteran
  • ***
  • Posts: 102
    • View Profile
Re: ZWave API
« Reply #137 on: January 17, 2010, 10:43:04 am »
also in the wiki: http://wiki.linuxmce.org/index.php/Everspring_SM103
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.

How can I get the status?

Thank you in advance.

/Kooma

hari

  • Administrator
  • LinuxMCE God
  • *****
  • Posts: 2421
    • View Profile
    • ago control
Re: ZWave API
« Reply #138 on: January 18, 2010, 02:37:34 pm »
you need to do the proper group associations.

br Hari
rock your home - http://www.agocontrol.com home automation

Kooma

  • Veteran
  • ***
  • Posts: 102
    • View Profile
Re: ZWave API
« Reply #139 on: January 18, 2010, 06:46:17 pm »
you need to do the proper group associations.

br Hari

Thank's hari. Feel like a moron to ask where/how the group association can be done?

Previously in this topic it was mentioned that this sensor can only be associated with group one. Noticed that before the installation, yet don't understand (obviously) what it actually means.

/Kooma

nite_man

  • NEEDS to work for LinuxMCE
  • ***
  • Posts: 1019
  • Want to work with LinuxMCE
    • View Profile
    • Smart Home Blog
Re: ZWave API
« Reply #140 on: March 12, 2010, 03:33:14 pm »
Quote
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.
Michael Stepanov,
My setup: http://wiki.linuxmce.org/index.php/User:Nite_man#New_setup
Russian LinuxMCE community: http://linuxmce.ru

hari

  • Administrator
  • LinuxMCE God
  • *****
  • Posts: 2421
    • View Profile
    • ago control
Re: ZWave API
« Reply #141 on: March 13, 2010, 12:30:10 pm »
Quote
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.

best regards,
Hari
rock your home - http://www.agocontrol.com home automation

sambuca

  • Guru
  • ****
  • Posts: 447
    • View Profile
Re: ZWave API
« Reply #142 on: March 13, 2010, 12:41:39 pm »
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  ;)

br,
sambuca

nite_man

  • NEEDS to work for LinuxMCE
  • ***
  • Posts: 1019
  • Want to work with LinuxMCE
    • View Profile
    • Smart Home Blog
Re: ZWave API
« Reply #143 on: March 13, 2010, 07:04:47 pm »
Thanks, guys, for the answers. If I understand correctly to install multi-sensor correctly separate device for each subsensor should be added via admin interface. But what ID should be used for them?
Michael Stepanov,
My setup: http://wiki.linuxmce.org/index.php/User:Nite_man#New_setup
Russian LinuxMCE community: http://linuxmce.ru

sambuca

  • Guru
  • ****
  • Posts: 447
    • View Profile
Re: ZWave API
« Reply #144 on: March 13, 2010, 10:14:38 pm »
You can use the EZMotion wiki article as a guide. Basically, the Port/Channel number device data should be node_id/instance id. But you would have to guess the instance IDs.

When the ZWave driver adds a new device, it should add a lmce device for each instance, so you could re-add your zwave device and see what instance IDs it adds.

br,
sambuca