Hello --
My RA2 Plugin has worked perfectly for about a year until about 3 weeks ago, when very simple events involving RA2 stopped working. An example of a "simple" event I am trying to get to work is "when RA2 light is turned on, also turn on a Hue Light" (see event image below). This has worked flawlessly for about a year. I'm sure my problem is user-error, but I just can't figure out what I did to cause this.
After some trial and error, I've discovered that my events work as expected when I control the RA2 devices from the HS3 web interface, but they do not work when I push the physical button on the wall keypads. Moreover, when I push the physical button, nothing is ever recorded in the log, even when I uncheck "Do not log commands from this device," nothing shows up in the log.
When I enable RA2 plugin debug logging and push a physical button, I get:
I do not get any log entry of the associated event triggering. (But, again, if I turn on the light from the HS3 web interface, I get a log of the event running, and the event runs correctly.)
I have tried restarting the plugin, restarting the server, deleting and rewriting the event, and deleting the device the pressing "systems create all new devices that don 't exist" to recreate the device (and then updating the event). Nothing seems to work. My next move will be to recreate ALL of the RA2 devices, but I hesitate because that means I'll have to update all of my 25+ events!
Interestingly, the LED status on the HS3 web page updates correctly when I physically toggle the wall controller button on and off, thus there is some communication happening...
Any ideas on what I should try next? Restart the repeaters (I have restarted them main repeater which controls this specific device, but not the other 3 secondary repeaters, could that matter?). Any ideas on what checkbox I may have inadvertently clicked? Help???
Thanks in advance for any assistance you can provide.
cagold

Current Date/Time: 9/1/2019 5:26:27 PM
HomeSeer Version: HS3 Pro Edition 3.0.0.548
Operating System: Microsoft Windows 10 Home - Work Station
System Uptime: 14 Days 23 Hours 34 Minutes 56 Seconds
IP Address: 192.168.1.200
Number of Devices: 847
Number of Events: 47
Available Threads: 200
HSTouch Enabled: True
Event Threads: 0
Event Trigger Eval Queue: 0
Event Trigger Priority Eval Queue: 0
Device Exec Queue: 0
HSTouch Event Queue: 0
Email Send Queue: 0
Anti Virus Installed: Windows Defender
In Virtual Machine: No MFG: shuttle inc.
Enabled Plug-Ins
2.0.61.0: BLBackup
0.0.0.24: DoorBird
0.0.0.24: DoorBird
3.0.0.65: EasyTrigger
3.0.0.33: Ecobee
3.0.0.40: EnvisaLink
2.0.3.3: JowiHue
3.0.0.114: LutronRA2
1.2.2.0: SceneMaster
3.0.1.252: Z-Wave
My RA2 Plugin has worked perfectly for about a year until about 3 weeks ago, when very simple events involving RA2 stopped working. An example of a "simple" event I am trying to get to work is "when RA2 light is turned on, also turn on a Hue Light" (see event image below). This has worked flawlessly for about a year. I'm sure my problem is user-error, but I just can't figure out what I did to cause this.
After some trial and error, I've discovered that my events work as expected when I control the RA2 devices from the HS3 web interface, but they do not work when I push the physical button on the wall keypads. Moreover, when I push the physical button, nothing is ever recorded in the log, even when I uncheck "Do not log commands from this device," nothing shows up in the log.
When I enable RA2 plugin debug logging and push a physical button, I get:
Sep-01 5:06:15 PM | LutronRA2 Debug | Receive<2: ~ERROR,1 |
Sep-01 5:06:15 PM | LutronRA2 Debug | ~ERROR,1 |
Sep-01 5:06:15 PM | LutronRA2 Debug | Receive<2: ~ |
Sep-01 5:06:15 PM | LutronRA2 Debug | ~ |
Sep-01 5:06:14 PM | LutronRA2 Debug | Receive: ~DEVICE,19,84,9,0 |
Sep-01 5:06:14 PM | LutronRA2 Debug | ~DEVICE,19,84,9,0 |
Sep-01 5:06:14 PM | LutronRA2 Debug | Receive<2: ~ |
Sep-01 5:06:14 PM | LutronRA2 Debug | ~ |
Sep-01 5:06:14 PM | LutronRA2 Debug | Send: ?DEVICE,19,84,9 |
Sep-01 5:06:14 PM | LutronRA2 Debug | Receive: ~DEVICE,19,4,3 |
Sep-01 5:06:14 PM | LutronRA2 Debug | ~DEVICE,19,4,3 |
Sep-01 5:06:14 PM | LutronRA2 Debug | Receive<2: ~ |
Sep-01 5:06:14 PM | LutronRA2 Debug | ~ |
I have tried restarting the plugin, restarting the server, deleting and rewriting the event, and deleting the device the pressing "systems create all new devices that don 't exist" to recreate the device (and then updating the event). Nothing seems to work. My next move will be to recreate ALL of the RA2 devices, but I hesitate because that means I'll have to update all of my 25+ events!
Interestingly, the LED status on the HS3 web page updates correctly when I physically toggle the wall controller button on and off, thus there is some communication happening...
Any ideas on what I should try next? Restart the repeaters (I have restarted them main repeater which controls this specific device, but not the other 3 secondary repeaters, could that matter?). Any ideas on what checkbox I may have inadvertently clicked? Help???
Thanks in advance for any assistance you can provide.
cagold
Current Date/Time: 9/1/2019 5:26:27 PM
HomeSeer Version: HS3 Pro Edition 3.0.0.548
Operating System: Microsoft Windows 10 Home - Work Station
System Uptime: 14 Days 23 Hours 34 Minutes 56 Seconds
IP Address: 192.168.1.200
Number of Devices: 847
Number of Events: 47
Available Threads: 200
HSTouch Enabled: True
Event Threads: 0
Event Trigger Eval Queue: 0
Event Trigger Priority Eval Queue: 0
Device Exec Queue: 0
HSTouch Event Queue: 0
Email Send Queue: 0
Anti Virus Installed: Windows Defender
In Virtual Machine: No MFG: shuttle inc.
Enabled Plug-Ins
2.0.61.0: BLBackup
0.0.0.24: DoorBird
0.0.0.24: DoorBird
3.0.0.65: EasyTrigger
3.0.0.33: Ecobee
3.0.0.40: EnvisaLink
2.0.3.3: JowiHue
3.0.0.114: LutronRA2
1.2.2.0: SceneMaster
3.0.1.252: Z-Wave
Comment