I'm going on hearsay here but I was told Lutron recently pushed from the cloud an update to their QSX processors. I didn't know this was a thing but apparently it is. Coincidentally, around the same time a system we have stopped being able to control shades. This is using the Simpl module "Lutron HomeWorks QSX Command Processor v1.3" which is in the Crestron module store, but I know it's written by Control Concepts.?
?
Has anyone heard of this or has systems that have stopped working? if I turn on the debug option I get a lot of?
?
CP4>[FAh][E0h][01h]LutronLeapCommLib1[ Reconnect!!! ]
[FBh][FAh][E0h][01h]LutronLeapCommLib1[ Connecting to: 192.168.1.112 ]
[FBh][FAh][E0h][01h]LutronLeapCommLib1[ SocketStatusChange: SOCKET_STATUS_NO_CONNECT ]
[FBh][FAh][E0h][01h]LutronLeapCommLib1[ Reconnect!!! ]
[FBh][FAh][E0h][01h]LutronLeapCommLib1[ Connecting to: 192.168.1.112 ]
[FBh][FAh][E0h][01h]LutronLeapCommLib1[ SocketStatusChange: SOCKET_STATUS_NO_CONNECT ]
[FBh][FAh][E0h][01h]LutronLeapCommLib1[ Reconnect!!! ]
[FBh][FAh][E0h][01h]LutronLeapCommLib1[ Connecting to: 192.168.1.112 ]
?
The QSX processor is absolutely at the correct address and pingable from my processor. So we're curious if something they did broke this module's ability to communicate, or something with their authentication, or maybe it's some unrelated issue unique to this site. Rebooting both ends etc all tried.?
?
TIA
OP
