Post by rdgerken on Oct 19, 2013 17:42:44 GMT -5
Hey guys... when I was giving the EventGhost plugin an overhaul - I noticed three odd things.
1. When commanding an output to flash - the entire system flashes - not just the one output being commanded. Lutron was able to reproduce this on 6.2.0.
2. When commanding a wall keypad LED to Flash or Rapidflash - the actual LED doesn't do anything, but when viewing the keypad within Home+ it shows as it is supposed to. There is a footnote about the flash and rapidflash functionality in the protocol - but I don't understand what they are trying to say. (I was attempting this with an unprogrammed keypad button)
3. Sometimes when querying the status of an LED for a wall keypad, it returns a value of 255 (which is not a valid parameter for LEDs). It should return a number between 0 and 3. I haven't yet figured out how to reproduce this one all the time, but I think I notice it only the first time after a system is transferred. It seems like once the LED value is set, then it works fine -but the very first time after a download, it will return a 255 when queried unless the value is set first. Additionally, after the value is set, then the next query of the LED will return something like "~DEVICE,62,82,9,1GNET>" - where there should be a CRLF between the 1 and the GNET> and there isn't. Eventually, it seems to snap out of it (perhaps after setting it to On, then back to Off), but again, I'm not sure how to reproduce these exact events, but I think these are the steps to reproduce:
a. Transfer program to repeater - have one keypad button that has no programming on it.
b. Query the status of the LED for unprogrammed button. When I do this, the system returns a 255 for led status. Like: ~DEVICE,62,82,9,255 - which is not valid
c. Set LED value to ON (value of 1) - system returns proper value, but is missing CRLF and shows ~DEVICE,62,82,9,1GNET> where it should show ~DEVICE,62,82,9,1.
d. Set LED value to OFF. Now I think it will behave properly from this point forth. (Until next transfer anyways).
All of this testing was done on 6.2.0 with a Hybrid keypad.
Can one of you guys who work for Lutron or have close contacts there get the low down on this for me? Every time I call into tech support, they act like I'm the biggest idiot on the planet. Even the guy that reproduced these issues on his end had no interest at all in escalating it - and even after I asked him to, I never got any response - so I highly doubt this will go anywhere unless someone else pushes it.
While I'm creating a list, here is another one I noticed:
When executing TIMECLOCK events - The index of the timeclock event command (#) seems to be '1' based, but the response (~) for that event seems to be '0' based. For example, if I send the command #TIMECLOCK,33,5,2 (for setting event number 2) - I get back ~TIMECLOCK,33,5,1
Thanks,
Ryan