I know this seems too simple to actually be the cause, but in the Lutron module's I've opened up, they use "login:" (all lower-case) to trigger sending the password. If you're actually receiving "LOGIN:" (all caps) it won't work. However, the module could easily be modified to fix that.
Which exact version of the Lutron module are you using?
toggle quoted message
Show quoted text
--- On Thursday, April 9, 2020 at 11:13 PM, AVMaster wrote:
Ok...so let me attempt to be more specific cause this is really weird.
Everything seems to be connecting just fine, if you view the TX$ and RX$ to and
from the TCP client in debugger you can see the module connect and the Lutron
processor responds with ¡®LOGIN:¡¯...it would be at that point I would expect the
TX$ from the module to respond with the username entered in the core module but
nothing happens...it just times out and responds with something like ¡®failed to
receive expected response¡¯ or something along those lines. I¡¯ve done this a
dozen times before but obviously something is wrong...
The real bummer about all this nonsense is that I only need to control just a
few loads in a theater and a golf simulator, not even doing any extensive
integration.
