I am running Vera3 1.5.408. I am currently and have been running v0.38 of the DSC plug in against my 1832 panel with the 2DS (01.07.90) for a couple months now and until this past weekend it was rock solid. The Vera3 is connected to my network over wired Ethernet (wi-fi is disabled), and it is connected to the same hub as the 2DS.
On Friday I installed a Foscam 8910 on my network (as wi-fi, not wired) and I also installed the 2.4 version of the Foscam plugin, or it actually auto-detected and self-installed. After the usual debugging of the plug-in settings for a few hours and a couple forum posts I reached steady state and the Foscam was basically completely functional.
Shortly after that I started to see Lua Failure messages in red in the UI under the main DSC Alarm Panel device. Upon examining the logs I see this at Lua startup:
50 09/24/12 17:24:09.109 luup_log:48: DSCAlarmPanel: Running Network Attached DSCAlarmPanel using EnvisaLink 2DS 192.168.1.51:4025 Device# 48, id <0x2bafb680>
02 09/24/12 17:24:09.112 IOPort::Run RecvFailed -1 close 11 <0x2e8fb680>
… cutting out other lines from other devices starting up …
02 09/24/12 17:24:14.120 IOPort::Run RecvFailed -1 close 12 LEAK this:385024 start:385024 to 0xf8c000 <0x2e8fb680>
Restarting Lua does not help. When I perused the logs further, I saw that the DSC plug-in then trying to send its usual commands to the 2DS later, also to no avail:
02 09/24/12 17:18:57.157 IOPort::Run RecvFailed -1 close 11 <0x2e339680>
02 09/24/12 17:19:02.164 IOPort::Run RecvFailed -1 close 12 <0x2e339680>
02 09/24/12 17:19:07.172 IOPort::Run RecvFailed -1 close 12 <0x2e339680>
02 09/24/12 17:19:12.179 IOPort::Run RecvFailed -1 close 12 <0x2e339680>
50 09/24/12 17:19:17.049 luup_log:48: DSCAlarmPanel: debug cannot send command: ‘001’ <0x2bd39680>
06 09/24/12 17:19:17.049 Device_Variable::m_szValue_set device: 48 service: urn:micasaverde-com:serviceId:HaDevice1 variable: CommFailure was: 1 now: 1 #hooks: 0 upnp: 0 v:0xb27f38/NONE duplicate:1 <0x2bd39680>
02 09/24/12 17:19:17.182 IOPort::Run RecvFailed -1 close 11 <0x2e339680>
02 09/24/12 17:19:22.190 IOPort::Run RecvFailed -1 close 12 <0x2e339680>
02 09/24/12 17:19:27.198 IOPort::Run RecvFailed -1 close 13 <0x2e339680>
02 09/24/12 17:19:32.206 IOPort::Run RecvFailed -1 close 14 <0x2e339680>
02 09/24/12 17:19:37.212 IOPort::Run RecvFailed -1 close 14 <0x2e339680>
02 09/24/12 17:19:42.219 IOPort::Run RecvFailed -1 close 12 <0x2e339680>
50 09/24/12 17:19:47.102 luup_log:48: DSCAlarmPanel: debug cannot send command: ‘056’ <0x2bd39680>
06 09/24/12 17:19:47.103 Device_Variable::m_szValue_set device: 48 service: urn:micasaverde-com:serviceId:HaDevice1 variable: CommFailure was: 1 now: 1 #hooks: 0 upnp: 0 v:0xb27f38/NONE duplicate:1 <0x2bd39680>
02 09/24/12 17:19:47.227 IOPort::Run RecvFailed -1 close 11 <0x2e339680>
02 09/24/12 17:19:52.234 IOPort::Run RecvFailed -1 close 12 <0x2e339680>
Rebooting the 2DS (or powercycling the DSC) restores functionality, but so does restarting the Vera3 unit. While it would might still appear at first glance that the 2DS is at fault, I would appreciate other suggestions for troubleshooting this further before escalating to whomever. I should also note that 2DS continues to send messages and status to EYEZ-ON and otherwise appears unaffected, and there were no problems prior to the installation of the camera and the plug-in. Also anyone who has the DSC panel, the 2DS and a Foscam camera and either has or has not seen this issue.
I cannot say conclusively which component is at fault yet, and my first troubleshooting step today has been to replace the network hub connecting the two devices (and I need to let the new one run for a few days), however posting this in the Security Forum made the most sense for starters based on the evidence so far.