Author Topic: Child Device/Interface communications via Zwave  (Read 994 times)

PeteK

  • Guru
  • ****
  • Posts: 408
    • View Profile
Child Device/Interface communications via Zwave
« on: September 23, 2007, 09:00:51 am »
Hi--

I sent this question to the Pluto ZWave developer because it's a Z-wave question, but it might be generic enough that someone else here can answer:

Thank you for your help with this.  I've been moving forward with
creating the Insteon interface.  One issue that I am unclear about is
the mechanism for a lighting device (i.e a #38 Dimmable Switch) to
create, say a Zwave job, when it receives a message from DCERouter.

For example, on the lights page of the control html page, It has 'ON'
'OFF' and '50%'.   If i understand correctly, these send a DCE Message
to the light device.  How does the light device then trigger the
creation of a Zwave Job?

Thank you for your help

bulek

  • Administrator
  • wants to work for LinuxMCE
  • *****
  • Posts: 886
  • Living with LMCE
    • View Profile
Re: Child Device/Interface communications via Zwave
« Reply #1 on: September 23, 2007, 11:00:34 am »
Hi--

I sent this question to the Pluto ZWave developer because it's a Z-wave question, but it might be generic enough that someone else here can answer:

Thank you for your help with this.  I've been moving forward with
creating the Insteon interface.  One issue that I am unclear about is
the mechanism for a lighting device (i.e a #38 Dimmable Switch) to
create, say a Zwave job, when it receives a message from DCERouter.

For example, on the lights page of the control html page, It has 'ON'
'OFF' and '50%'.   If i understand correctly, these send a DCE Message
to the light device.  How does the light device then trigger the
creation of a Zwave Job?

Thank you for your help
Not sure how this is implemented in Zwave wrapper, but do know how it goes :
- light device  is usually child device of parent that is usually driver for some automation system. But all these child devices don't have that tick "implements DCE" , that means that all messages for child devices will be actually send to its parent and then driver activates proper job - so actually message never comes to child device....

HTH,

regards,

Rob.
Thanks in advance,

regards,

Bulek.

PeteK

  • Guru
  • ****
  • Posts: 408
    • View Profile
Re: Child Device/Interface communications via Zwave
« Reply #2 on: September 23, 2007, 05:21:18 pm »
Thanks for the info!  It wasn't clear from the code how this happened.