Lutron RA3 - LEAP
charlesw
Posts: 11
Has anyone got the Lutron LEAP RA3 module to work? I am using latest RA3 firmware but when calling REINIT get;
(0001174206) LutronRadioRA3::CommManager handleErrorEvent: socket failed to connect
I am using the demo module wrapper from AMX site, changed IP to verified IP of RA3 processor.
Suggestions anyone?
0
Comments
Have you completed the pairing process after the initial boot? Once your controller has entered pairing mode, you will press the only button on the Ra3 controller. From that point, it takes roughly 10 mins for the AMX controller to generate the ~4000bit key. This is a one time action required at the point of commissioning, but is straight forward after that on subsequent reboots.
more info:
(0000042369) [BundleStart #18] INFO org.eclipse.jetty.server.handler.ContextHandler - Started HttpServiceContext{httpContext=com.amx.duet.httpservlets.RootServlet$1@6366a3}
(0000042388) MasterServlets org.knopflerfish.framework.BundleContextImpl@137fc1e installServlets() newInstance(RootServlet 1.0.0)
(0000043788) JSONFileLoader /opt/amx/javalib/jars/master/nxmaster/master.json loaded new definitions
(0000045779) [BundleStart #18] INFO org.eclipse.jetty.server.handler.ContextHandler - Started HttpServiceContext{httpContext=com.amx.duet.httpservlets.MasterServlet$1@a2eb5}
(0000045819) MasterServlets org.knopflerfish.framework.BundleContextImpl@137fc1e installServlets() newInstance(MasterServlet 0.0.2)
(0000045899) JSONFileLoader /opt/amx/javalib/jars/master/nxmaster/login.json loaded new definitions
(0000046266) [BundleStart #18] INFO org.eclipse.jetty.server.handler.ContextHandler - Started HttpServiceContext{httpContext=com.amx.duet.httpservlets.LoginServlet$1@1f1e75a}
(0000046271) MasterServlets org.knopflerfish.framework.BundleContextImpl@137fc1e installServlets() newInstance(LoginServlet 0.0.2)
(0000046359) [BundleStart #18] INFO org.eclipse.jetty.server.handler.ContextHandler - Started HttpServiceContext{httpContext=com.amx.duet.httpservlets.DateTimeServlet$1@8e2f39}
(0000046364) MasterServlets org.knopflerfish.framework.BundleContextImpl@137fc1e installServlets() newInstance(DateTimeServlet 0.0.2)
(0000046366) MasterServlets org.knopflerfish.framework.BundleContextImpl@137fc1e installServlets() com.amx.core.master.SystemConfig.jvmStartupComplete();
(0000046912) Framework launched
(0000047468) GetString - Error 1 Tk=0x0001
(0000047468) CopyString (Reference) - Error 1 S=0x0000 D=0x1011
(0000057356) [DA_DeviceAccess] INFO org.ops4j.pax.web.service.internal.HttpServiceFactoryImpl - Binding bundle: [BundleImpl[id=32]] to http service
(0000060271) 07:14:17:084 -->-->-->-->--> ITGLogger getModuleVirtualNetLinxDevice() called... [41001:1:0]
(0000061354) SNAPIRouter: KeypadSystemComponent loaded
(0000061397) SNAPIRouter: HVACComponent loaded
(0000061422) SNAPIRouter: LightSystemComponent loaded
(0000061439) SNAPIRouter: ModuleComponent loaded
(0000061754) ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~
(0000061755) Lutron_RadioRA3_Comm_dr1_0_0 Device: 41001:1:0 is using ITGCommon v1.0.35 compiled: May 34, 2020 00:35 GMT
(0000061756) ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~
(0000066349)
(0000066350) -+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--
(0000066350) -+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--
(0000066351)
(0000066352) Lutron_RadioRA3_Comm_dr1_0_0 Version: 1.0.1 Compiled: September 13, 2022 21:31
(0000066353)
(0000066353) -+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--
(0000066354) -+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--
(0000066354)
(0000067144) + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
(0000067145) initPropManager
(0000067146) ---- Properties for 41001 ----
(0000067146)
(0000067147) Address-Format-Example [Processor:Link:Keypad:Button]
(0000067147) Device-Channels 360
(0000067148) Device-Interface com.amx.duet.impl.lutron.common.dr1_0_0.interfaces.ILutronLeap
(0000067149) Device-Levels 35
(0000067149) Duet-Device 41001:1:0
(0000067150) Has-Keypad-Control true
(0000067150) Has-Light-Level true
(0000067151) Has-Light-Level-Ramp true
(0000067164) Has-Notes false
(0000067165) IGNORE-UNKNOWN-NETLINX-COMMAND true
(0000067166) IP_Address 172.31.200.229
(0000067167) Poll_Time 10000
(0000067169) Port 8083
(0000067170) Queue_Interval_MS 200
(0000067172) Reconnect_Time 15000
(0000067173) Timeout_Count 3
(0000067174)
(0000067508) + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
(0000068195) LutronRadioRA3::CommManager handleErrorEvent: socket failed to connect
(0000098229) LutronRadioRA3::CommManager handleErrorEvent: socket failed to connect
Chris, thank you for your comment.
Looking at the module document under Authentication and Pairing (page 9), I see the a,b,c,d description where step c describes the need to push the button, but I see no evidence that steps a and b ever happened (please see trace above). I tried the reset but still nothing seems to result from it. I took the supplied stock module code with only the the IP address being changed. RA3 processor verified working ok. Simple bench test network being used.
My suggestion would be to contact your AMX tech support team to help runthrough connectivity potentials and capture debug-4 logs. The module was validated against Ra3 hardware prior to release. Support may be able to assist in finding the configuration issue or the logs could point to something that would require a module revision.
just in case you didn't get anywhere with this, you need latest firmware to make it work. This is because of the changes for TLS connections
I'm using QSX, and I basically used the pairing component and part of the keypad component, plus the main module. I binned the rest and rolled my own code t make it work how I wanted.
The QSX module seems overly complicated for what it is.
Duncan, thanks for the feedback. LEAP is quite an extensive protocol and covers almost all of the Lutron product lines at the moment. The module supports full functionality of their protocol which we understand is not going to be used in every project. Most programmers only want button press emulation and keypad LED feedback, but LEAP allows for far more.
I got the Homeworks QSX one to work - which is pretty much the same. Its all a bit overkill for what it is, creating certificates etc.. for a lighting systems thats on internal networks.
Also, now, every button and every LED has its own address and, from looking in the module code from the website, if you have a lot of buttons, there are quite a few alterations to do.
In the end, I programmed up the lutron as normal then effectively made one list of keys & led in the AMX file.
I changed the startup procedure, as the exitsing code just kept firing all of the addresses at the module to subscribe and its just locked up. So I implemented a timeline to send them at a reasonable rate and also changed the feedback, as that was also a bit questionable, especially for a chunk of buttons - I had over 500 buttons to consider.
You also need to make sure you have the correct firmware as the newer firmware implements a different version of TLS for the connection.
Thank you for the info. I checked my firmware versions (master 1.6.179, device 1.1.48) which appears up to date.
I am still unable to get the RA3 module to pair. I had a tech support session with AMX who were unable to resolve the issue, further they seemed to have trouble following the module documentation (as I did). Being a programmer for a non US dealer we do not have a "field engineer" as I was advised by AMX to contact.
This makes me dead in the water with Lutron RA3.
This issue made me look more closely at TLS programming with AMX in general, as I did my AMX certifications in 200
AMX Canada resolved my issue and I have been working with the module for the last few weeks. It has worked well and I have extended the functionality to suit my requirements.
I did notice that the lighting level ramp commands fail to get a status response from the Ra3 processor, but this appears to be a Lutron issue as their own app also goes out of sync (status). Lutron asked me to try the lastest RA3 version (22.8) which .... has broken the pairing process. So I am back at square one again :-(
So if anyone is using the module stay at 22.7.x
Charles, I apologize that you encountered difficulty with the module after upgrading to Lutron's most recent firmware. We are in contact with Lutron to learn more about their changes and will update the module(s) once additional info is obtained. AMX and Lutron have a great working relationship and ITG has hardware on hand to troubleshoot against.
Charles, it would appear additional testing is needed to understand your situation. Here is what I did today:
CONCLUSION: Unable to recreate.
Test Environment: AMX NX1200 running firmware v1.6.205
RadioRa3 initially running 21.5 and through testing upgraded to 22.08.16f000
Lutron Protocol LEAP VERSION 3.211 was upgraded to 3.229
Methodology:
1) Issued command clean disk-f on the AMX NX1200 controller to wipe out all stored files
2) updated AMX firmware to 1.6.205
3) Updated sample project file from AMX InConcert Ra3 download and changed code to point it at our Ra3 hardware IP, and ensure the proper device ID info was included for our Ra3 hardware devices (buttons and LED integration IDs)
4) Transferred and waited for the huge key to generate on first launch
5) Once telnet messages from the controller indicated I was to press the pairing button, we pushed it
6) DEVICE STATUS 41001:1 reported that SNAPI channels 251,252 were ON which suggest we are properly connected and communicating with end device
7) Tested device control and there were no issues
8) Using Lutron software Lutron Designer 22.8.0.9916, I sent a file transfer and during the transfer it asked to update firmware on Lutron hardware from 21.5 to the latest 22.08.16f000
9) AFTER firmware transferred, I checked the module and we were still communicating and controlling attached Lutron devices.
As an additional test, I set up a second clean system to attempt pairing for the first time against the updated Lutron firmware.
1) Clean disk -f controller to wipe out any prior files, and reboot
2) Upgraded NX1200 to 1.6.205
3) Transferred AMX workspace and waited for key to generate
4) Once messages to press pairing button showed in diagnostics - I pressed the pair button on Lutron
5) Module showed SNAPI channels 251 and 252 ON suggesting good communications between AMX and Lutron
6) A test of device control was not working. Assuming that two controllers polling the Lutron device may be an issue, I clean disk-f the original test controller and rebooted it.
7) I then rebooted the second paired controller and upon reboot, device control was established.
Hi Chris, thank you for your response.
I had been working for a couple of weeks without issue. After the Lutron upgrade was performed, the AMX module entered the pairing stage, output an error (400 Bad Request - Operation not supported) and, (after some time) prompted for the pairing button press which did nothing, the module would keep prompting for the button push. I performed a clean disk command and tried again, same result. I will review your procedure above step by step and report back. Thank you for taking the time in both testing and for the quality write up.
Hi Chris,
Please review my comments below - I have added my comments below your steps. I also added trace at the end along with timestamps for a sense of timing.
1) Issued command clean disk-f on the AMX NX1200 controller to wipe out all stored files
[Charlesw: this is the only difference I could see between your procedure and what I had done. I had done clean disk but without the -f flag which we will now do.]
2) updated AMX firmware to 1.6.205
[Charlesw: My NX-1200 had the same version.]
3) Updated sample project file from AMX InConcert Ra3 download and changed code to point it at our Ra3 hardware IP, and ensure the proper device ID info was included for our Ra3 hardware devices (buttons and LED integration IDs)
[Charlesw: I have used the sample project file included in the module package downloaded from the AMX website. I modified only line 136 (source main) to reflect the RA3 IP.]
4) Transferred and waited for the huge key to generate on first launch
[Charlesw: Uploaded and waited]
5) Once telnet messages from the controller indicated I was to press the pairing button, we pushed it
[Charlesw: I received the request to push button message along with an error at the same time. Pushing the button does nothing at this point. The error came before the push not as a result of it.]
The only other difference I note is my Lutron version is a few revisions ahead at 22.8.0.10728.
Ideas?
Many thanks.
30.01.2023 17:55:05.241 - (0000071662) MasterServlets org.knopflerfish.framework.BundleContextImpl@7bfd66 installServlets() com.amx.core.master.SystemConfig.jvmStartupComplete();
30.01.2023 17:55:05.874 - (0000072278) Framework launched
30.01.2023 17:55:13.166 - (0000079610) [DA_DeviceAccess] INFO org.ops4j.pax.web.service.internal.HttpServiceFactoryImpl - Binding bundle: [BundleImpl[id=32]] to http service
30.01.2023 17:55:15.996 - (0000082388) 17:55:57:182 -->-->-->-->--> ITGLogger getModuleVirtualNetLinxDevice() called... [41001:1:0]
30.01.2023 17:55:18.276 - (0000084761) SNAPIRouter: KeypadSystemComponent loaded
30.01.2023 17:55:18.384 - (0000084803) SNAPIRouter: HVACComponent loaded
30.01.2023 17:55:18.384 - (0000084829) SNAPIRouter: LightSystemComponent loaded
30.01.2023 17:55:18.389 - (0000084847) SNAPIRouter: ModuleComponent loaded
30.01.2023 17:55:18.495 - (0000084873) (Reader=749343824 writer=743969872)- CMessagePipe::Max = 25
30.01.2023 17:55:18.713 - (0000085157) ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~
30.01.2023 17:55:18.718 - (0000085158) Lutron_RadioRA3_Comm_dr1_0_0 Device: 41001:1:0 is using ITGCommon v1.0.35 compiled: May 34, 2020 00:35 GMT
30.01.2023 17:55:18.723 - (0000085158) ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~
30.01.2023 17:55:21.978 - (0000088449)
30.01.2023 17:55:22.086 - (0000088450) -+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--
30.01.2023 17:55:22.088 - (0000088451) -+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--
30.01.2023 17:55:22.093 - (0000088451)
30.01.2023 17:55:22.093 - (0000088452) Lutron_RadioRA3_Comm_dr1_0_0 Version: 1.0.2 Compiled: October 08, 2022 09:44
30.01.2023 17:55:22.106 - (0000088452)
30.01.2023 17:55:22.106 - (0000088453) -+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--
30.01.2023 17:55:22.113 - (0000088453) -+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--
30.01.2023 17:55:22.123 - (0000088454)
30.01.2023 17:55:22.850 - (0000089257) + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
30.01.2023 17:55:22.853 - (0000089258) initPropManager
30.01.2023 17:55:22.858 - (0000089259) ---- Properties for 41001 ----
30.01.2023 17:55:22.862 - (0000089260)
30.01.2023 17:55:22.862 - (0000089260) Address-Format-Example [Processor:Link:Keypad:Button]
30.01.2023 17:55:22.868 - (0000089260) Device-Channels 360
30.01.2023 17:55:22.874 - (0000089261) Device-Interface com.amx.duet.impl.lutron.common.dr1_0_0.interfaces.ILutronLeap
30.01.2023 17:55:22.882 - (0000089261) Device-Levels 35
30.01.2023 17:55:22.888 - (0000089262) Duet-Device 41001:1:0
30.01.2023 17:55:22.888 - (0000089262) Has-Keypad-Control true
30.01.2023 17:55:22.894 - (0000089263) Has-Light-Level true
30.01.2023 17:55:22.897 - (0000089263) Has-Light-Level-Ramp true
30.01.2023 17:55:22.902 - (0000089279) Has-Notes false
30.01.2023 17:55:22.907 - (0000089279) IGNORE-UNKNOWN-NETLINX-COMMAND true
30.01.2023 17:55:22.907 - (0000089280) IP_Address 172.31.200.229
30.01.2023 17:55:22.910 - (0000089282) Poll_Time 10000
30.01.2023 17:55:22.913 - (0000089283) Port 8083
30.01.2023 17:55:22.916 - (0000089284) Queue_Interval_MS 200
30.01.2023 17:55:22.923 - (0000089285) Reconnect_Time 15000
30.01.2023 17:55:22.923 - (0000089286) Timeout_Count 3
30.01.2023 17:55:23.174 - (0000089620)
30.01.2023 17:55:23.283 - (0000089621) + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
30.01.2023 17:55:28.508 - (0000094903) + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
30.01.2023 17:55:28.510 - (0000094904) Generating keys (this can take 10-15 minutes)...
30.01.2023 17:55:28.514 - (0000094905) + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
30.01.2023 17:55:28.833 - (0000095257) (Reader=973177936 writer=743969872)- CMessagePipe::Max = 25
30.01.2023 18:00:32.862 - (0000399295) + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
30.01.2023 18:00:32.867 - (0000399296) Press physical button to proceed with pairing...
30.01.2023 18:00:32.869 - (0000399296) + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
30.01.2023 18:00:32.870 - (0000399302) LutronRadioRA3::LutronRadioRA3Response Unable to process response [{"Header":{"StatusCode":"400 Bad Request","ContentType":"exception;plurality=single"},"Body":{"Exception":{"Message":"This request is not supported"}}}]
I am looking for the differences between what your procedure suggests works and what I have.
The Lutron version has a very minor difference. Hard to see this is the cause.
Our AMX test code is different despite being based on the same core module.
I took the base code supplied with the module and removed all the lighting HVAC, shades etc from it leaving only the core modules.
Now I get the trace you see below with the error "LutronRadioRA3::LutronRadioRA3Response Url [/zone/status] ErrorCode [405 MethodNotAllowed]". This error also seems unrelated to the actual button press which still does nothing.
It might be noted that the Savant RA3 implementation is still working after the button press, so I know the RA3 processor is ok.
I am very open to allowing the module developers to screen share on the machine used in this testing as I am out of ideas.