ParMan wrote:I presume the plugin is mimicking how other luton clients accesses the gateway?
Not necessarily. The plugin uses the published Integration protocol,
https://www.lutron.com/TechnicalDocumen ... 040249.pdf. Lutron's own clients might use something else. I know that for RRa2 the current iOS app requires a connect bridge which (I think) implements their LEAP protocol. I think HWQS MDU might be the same, based on this diagram:
https://www.lutron.com/TechnicalDocumen ... ecture.pdfParMan wrote:If this is correct, are there different access levels available in the gateway, and I could have been given a client login that does not have access to what the client needs? I have access to the system via the iOS app - with another id and password. Is the app accessing via a different route?
I have not used a telnet client for years, but I can try that.
What kind of settings do I need to enter apart from what I have? Comm sped etc is only for serial connects, right?
If I can convince the technician to enter his master login in the plugin, then the plugin should get what it needs, unless it this version of the gateway has not been dumbed down correct?
I know there was a recent change in the RRa2 software such that you could not use the default telnet login for an automation controller. I had to set up a new user for Indigo. I have no idea how this relates to HWQS.
All you need for a telnet client is the IP address and (maybe) the port number. Lutron uses the default Telnet port of 22.