Command response from Baronet 100 not fully recognized/understood
James Sentman
james at sentman.com
Sun Oct 18 10:14:04 EDT 2015
The address thing is a red herring. When the command error has no idea how to interpret a command to create an error message it falls back to trying to turn the address into an X10 style address which the barix doesn’t use so those fields are just empty, thus A1. I see that in a few other places in Xtension that are on my list to clean up like if you try to send a command to an interface that is turned off it will tell you that the command for A1 was not sent. It’s confusing and I’ll get it cleaned up eventually ;)
The other is interesting though, it’s sending me back some extra data there. It may be something related to the expansion modules connected. Michael is still recovering from his recent trip but should be back up to speed and able to dig into that code soon ;)
> On Oct 17, 2015, at 10:15 PM, Brian Williams <brwill at me.com> wrote:
>
> I recently noticed (but that does not mean a recently new situation) that when I send a command to turn off or turn on a digital output or a relay on a Barionet 100, Xtension receives more response to the command than it expects, and records: ack: Extended Data for A1 from BCB.
>
> There is no address A1 in the Barionet 100. This appears to be the case when commanding any and all B100 output points (and controlled modules such as the IO12 and R6). All works well, but there is this data string that is not well interpreted (and may be useful if interpreted correctly.) Regardless of what point is addressed, the Extended Data is always for A1.
Thanks,
James
James Sentman http://sentman.com http://MacHomeAutomation.com
More information about the XTensionList
mailing list