Throw me a BONE!!!

[ddamron]

I'm SOOOOOO close...
1.  Can't get this damn PnP working right..
2.  need to send STATE info to devices (lights)
Suggestions?? Stab in the dark??

[PeteK]

What portion exactly are you trying to implement?

[ddamron]

Part 1.
Trying to get the PnP wizard to run properly...

I can get it to run on the core, but it doesn't 'blink' the light either, and it doesn't save some information it's supposed to...
namely, the [12] info...

[totallymaxed]

Part 1.
Trying to get the PnP wizard to run properly...

I can get it to run on the core, but it doesn't 'blink' the light either, and it doesn't save some information it's supposed to...
namely, the [12] info...

Dan... I don't think the current Lighting Wizard will just 'work' with your driver. My understanding is that there are currently some specific dependencies related to the current z-wave implimentation.

[tschak909]

okay, I guess that means I need to start digging through the wizard to figure out how to generalise it, to help out.

-Thom

[ddamron]

Ok, I MIGHT have enough info for the lighting wizard...

The real problem is reporting back the state info..

[ddamron]

State information has been figured out! YAY
It took me a couple hours of trial and error to find a work around...
The Orbiters don't do anything special, they just send a command to the device.
When DCE routes the command, it internally sets the State information inside the device.
So, I said to myself, Self, What are they doing that you're not... Sending a command to self!

gotta love axioms...  when one object A is the same as object B, then Object B can be considered the same as object A...
(remember that in Math class??? except it was when Line A is the same as Line B...) lol

So, the solution was to say: Self, Cmd184, setlevel=x. 

<never had to send myself a useless command before... guess there's a use for everything...>

Dan

[Matthew]

State information has been figured out! YAY
It took me a couple hours of trial and error to find a work around...
The Orbiters don't do anything special, they just send a command to the device.
When DCE routes the command, it internally sets the State information inside the device.
So, I said to myself, Self, What are they doing that you're not... Sending a command to self!

(...)

<never had to send myself a useless command before... guess there's a use for everything...>

That is actually the precisely correct OOP approach. "Self.setParam(val)" is called "sending a message to the object itself". LMCE distributes the objects around the network more or less transparently, but it's still objects sending messages around, even more clearly so than when a C++ program is running on a local stack and VM.