I left the house for a couple of weeks and when I came back I found the following on my HS3 machine:
Caddx Alarm Plugin for Homeseer 3.4 has stopped working
Problem signature:
Problem Event Name: CLR20r3
Problem Signature 01: hspi_caddx.exe
Problem Signature 02: 3.4.1.0
Problem Signature 03: 581a2279
Problem Signature 04: mscorlib
Problem Signature 05: 4.0.0.0
Problem Signature 06: 4ba1da6f
Problem Signature 07: 4f6b
Problem Signature 08: 13
Problem Signature 09: System.NullReferenceException
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 1033
Additional Information 1: 0a9e
Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
Additional Information 3: 0a9e
Additional Information 4: 0a9e372d3b4ad19135b953a78882e789
I am running HS3 3.0.0.298 and Caddx plug-in 3.4.1
I looked at all of my Caddx events and don't see any problems, but I'm not sure what to look for. I only use the plug-in to report zone faults and user codes. I use the Caddx aux outputs to provide partition status info through Stargate.
A few days after I left the house the alarm siren apparently turned on. I sense the voltage to it with my Stargate system and trigger events when the siren turns on. There was no break-in. There were no zone faults in the log. This has never happened before this. A few weeks before I left the house, I upgraded the plug-in to 3.4.1. I suspect this was the cause but have no way to verify that.
Anyone else have similar problems or a clue as to what may have caused this strange behavior?
Caddx Alarm Plugin for Homeseer 3.4 has stopped working
Problem signature:
Problem Event Name: CLR20r3
Problem Signature 01: hspi_caddx.exe
Problem Signature 02: 3.4.1.0
Problem Signature 03: 581a2279
Problem Signature 04: mscorlib
Problem Signature 05: 4.0.0.0
Problem Signature 06: 4ba1da6f
Problem Signature 07: 4f6b
Problem Signature 08: 13
Problem Signature 09: System.NullReferenceException
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 1033
Additional Information 1: 0a9e
Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
Additional Information 3: 0a9e
Additional Information 4: 0a9e372d3b4ad19135b953a78882e789
I am running HS3 3.0.0.298 and Caddx plug-in 3.4.1
I looked at all of my Caddx events and don't see any problems, but I'm not sure what to look for. I only use the plug-in to report zone faults and user codes. I use the Caddx aux outputs to provide partition status info through Stargate.
A few days after I left the house the alarm siren apparently turned on. I sense the voltage to it with my Stargate system and trigger events when the siren turns on. There was no break-in. There were no zone faults in the log. This has never happened before this. A few weeks before I left the house, I upgraded the plug-in to 3.4.1. I suspect this was the cause but have no way to verify that.
Anyone else have similar problems or a clue as to what may have caused this strange behavior?