Tomas,
I reviewed the information you provided with Engineering this morning. We believe we have identified the issue and corrected it in the firmware. We will test to confirm the resolution and publish a firmware update for the panel. Below is an overview of the issue.
The information you referenced in the history pertains to a key fob low battery condition. The system should display the sensor name and details in the history, but due to a bug, this information is getting scrambled and is not relevant. There were recent updates to how sensor information is displayed, but key fobs were overlooked in that process.
To confirm this, can you check the history to see if a user armed or disarmed the system around the time this entry was logged? I assume that is the case. If you see a user entry, please check that user’s fob for a possible low battery.
Regarding the odd behavior from the keypad that you sent me—I greatly appreciate that, as this is not something we have seen before. Can you provide details about the system? We would like to attempt to recreate the issue in our testing. Specifically, I need information on the number of bus devices, power devices, battery type and size, etc.—any details that would help us closely replicate your setup.
If you’re more comfortable providing this information via email, please send it directly to me. I believe you have my contact information.
I’ll update you on the progress of the key fob issue as soon as I have more information.
Thanks,
Mike