- Code: Select all
2023-12-27 08:35:01.509 | [0000000100000000----],030,[f700000f1030000008020000000000],"FAULT 30 "
That type of message above is a "Keypad Message" or KPM message. These are the message types the plugin reads and processes to change the state of the device, in your case Zone 30.
I'll recap that we're dealing with 5 log files: The Indigo Event Log, two different plugin.log files for each of your two instances, and two different panelMessage. log files for each of the instances. The next step in getting to the bottom of this is to see how the plugin processed the message above by looking at the plugin.log file for the appropriate instance that contains the Garage Door Zone 30.
Hopefully, you have verbose logging turned on for the plugin.log per the attached image for the instance of the plugin that has this Zone 30. If not, turn it on and fault the Garage Zone 30 again. Because you have two instances, you'll have two plugin.log files in their respective directories. Based on what you've sent me so far, I think the instance with the Zone 30 Garage is named "AD2USB Alarm Interface LH". So we want to look at that instance's plugin.log file. It will be located "/Library/Application Support/Perceptive Automation/Indigo 2023.1/Logs/YOUR_ID_OF_THE_LH_INSTANCE/plugin.log". I don't know the ID of your LH instance so hopefully that is clear and you'll know how to find it.
The relevant sections are described below and this is similiar as the post I made yesterday.
Once you find the correct plugin.log it's often easiest to make a copy the file and open the copy in TextEdit or a similar editor and simply remove the unwanted lines. To find the first line of the log that we are interested in you can look for three things. The first is the log entry string "Plugin.panelReadWrapper: read from AlarmDecoder (Python 3) bytes". This is the beginning of the code that starts to process a fault message on the keypad (e.g. AlarmDecoder). The second thing is the date/time. Take note of the time you opened your garage door and then look for that start time in the log and that string (approximately 2023-12-27 08:35:01 per the Panel Message log) . The third part is the keypad message string from above: 2023-12-27 08:35:01.509 | [0000000100000000----],030,[f700000f1030000008020000000000],"FAULT 30 "
The last line of the relevant log entries is easier to find. It will be the first line after the FAULT Keypad message line you just found that contains the text: "Plugin.panelMsgRead: completed". An example is below:
- Code: Select all
2023-12-25 19:12:46.343 DEBUG 123145428803584 Plugin.panelMsgRead: completed
Attach or post the relevant log entries and we can see how that instance is processing that KPM message and get to the bottom of this.