So, I never really got anywhere with that. Does mh allow for
parsing/acting on X10 dim/bright events?
On Sun, May 17, 2009 at 05:44:02PM -0700, Marc MERLIN wrote:
> I seem to receive:
> 17/05/2009 17:40:02 [Insteon_PLM] Parsing serial data: 0252b580
> 17/05/2009 17:40:02 X10: Unmatched incoming data=XLL
> 17/05/2009 17:40:03 [Insteon_PLM] Parsing serial data: 02520480
> 17/05/2009 17:40:03 [Insteon_PLM] received x10 data: XMM
> 17/05/2009 17:40:03 XL3: mbr_kpl_x10 manual
> 17/05/2009 17:40:09 [Insteon_PLM] Parsing serial data: 0252b480
> 17/05/2009 17:40:09 X10: Unmatched incoming data=XLM
> 17/05/2009 17:40:10 [Insteon_PLM] Parsing serial data: 02520480
> 17/05/2009 17:40:10 [Insteon_PLM] received x10 data: XMM
> 17/05/2009 17:40:10 XL3: mbr_kpl_x10 manual
> but it's not that easy to use as is since it only contains the house code
> and not the item code which is supposed to be remembered from context
> (stupid protocol).
> Does mh have a way to easily get a dim/bright event linked to a device?
> (the idea being of course to gateway X10 dim/bright to insteon dim/bright)
> Yes, I could set the X10 code on the insteon device, I actually used to do
> that, but I've found that it them makes the switch randomly switch every so
> often because its X10 decoding engine seems quite good at turning random
> noise that the PLM doesn't even see, into X10 commands from time to time :-/
"A mouse is a device used to point at the xterm you want to type in" - A.S.R.
Microsoft is to operating systems & security ....
.... what McDonalds is to gourmet cooking
Home page: http://marc.merlins.org/