Re: x10 connector and state unknown!

["Edward Pearson" <edward.mailgroup@xxxxxxxxxxxxxxxx>]

James is correct - until an X10 command for the device has been
observed the current state cannot be determined. On the 'to-do' list
for the connector is to have the ability either for the connector to
make an assumption for each X10 device about its state at startup
(optionally persisted between connector sessions) - useful for
rarely changed devices or for the connector to ensure a particular
state for a device by sending a command.


--- In xap_automation@xxxxxxx, James <james@...> wrote:
>
> aiui, you will get an unknown state until a device is controlled (
by
> xAP or x10).  The trouble is that the connector cannot query the
current
> state of a x10 device at startup and as it doesn't know the state
it
> reports state as unknown.  As soon as it sends an x10 command to
the
> unit, or hears an x10 command sent to the unit, the connector
would now
> know the state and you should find the sate becoming Onoff in the
xAP
> messages
>
> hth
>
> James
>
>
> lasses nilsson wrote:
> > Hi
> > I was wondering if anybody knows why I get state unknown all the
> > time in the hub from the X10 connector. I want to use the state
in
> > another application, but all I get is unknown. Is this fixable?
> > I got the X10 connector from here.
> > http://www.xapautomation.org/wiki/index.php/xAP_X10_Connector
> >
> > xap-header
> > {
> >     v=12
> >     hop=1
> >     uid=FF102001
> >     class=xAPBSC.info
> >     source=ERSP.X10.dreambox:BioRum.Slang
> > }
> > output.state
> > {
> >     state=?
> >     displaytext=Info: BioRum.Slang state unknown
> > }
> >
> > regards
> >
> > Lasse
> >
> >
> >
> >
> >
> >
> >
> > Yahoo! Groups Links
> >
> >
> >
> >
> >
> >
> >
>