Re: [mh] Object dilema

[David N. <dno...@ya...>]

> One thing I have noticed with my Insteon devices is that I can manually
> turn on an appliance attached to an Insteon module and it returns the
> X10 address with the state (E1EOn for instance). How can I associate
> the E1 state to the Insteon objects state?

Does the device send a X10 message or an Insteon message or both?  You add 
"on" states for both Z015507J and E1EJ, but I don't see why you need to 
support X10 in your Insteon object.  Is your object a derivative of X10?

> BTW, I figured out how to set and Insteon device to On within MH and
> it now reaches my driver as Z015507J. I used Z because X10 supports
> I as a house code. This was the missing step I needed. I'll also
> have to figure out a few other things like what happens to the
> string once the driver passes it up to MH. That will allow me to
> send and receive Insteon commands. So far it looks like I'll be
> able to send real Insteon commands soon.

You're using J for on?  Yuck!  Insteon supports 256 commands and 256 sub 
commands.  You are going to run out of letters quick.  Why not use the 
actual two digit Insteon command and optionally the same for sub command?

Also, the Z is reserved for sending and receiving X10 extended data, but 
that only applies to Serial_Item strings that start with X.  I think you 
should separate your code from the X10 stuff.  There is no reason Insteon 
commands should start with an X and look like X10 commands.

David