PUSH FAIL/RES MOD 1 and log weirdness

[lucascosti]

Thanks for this integration!

Since I've been using it, I've noticed a few things:

• Not sure if it's just coincidence, but since I've started using the integration, I've been getting notifications on RSC+ like PUSH FAIL MOD 1 and sometime later PUSH RES. MOD 1. I can't reliably reproduce what causes it. We normally arm/disarm from the panel, and it happens about 25% of the time for an arm/disarm cycle.

• I've noticed that the log in Home Assistant sometimes doesn't update reliably. For example, here is the current state of the log compared to what's shown in RSC+. At the moment, anything after the PUSH FAIL isn't shown in the HA log; could the PUSH FAIL be failing to push to Home Assistant?

  HA log: https://github.com/user-attachments/assets/6753da62-276a-4b47-8631-372200ee188c RSC+ log: https://github.com/user-attachments/assets/3bf4616c-9980-42e6-9749-ea18213ca2e7

• I've also noticed that the HA log shows things like Quick Area0 AWAY Arm and Quick Area2 Disarm where Area<number> is actually supposed to be the user number.

Edit, forgot to post my details:

• Bosch Solution 3000, version 2.1.3,
• B426-M, firmware 03.13.0208

[sanjay900]

I have certainly seen the PUSH FAIL MOD 1 myself, and i haven't armed my panel in a while, so not actually sure what causes that

I have also seen the logs not updating reliably but don't really know what causes that, I have to assume the panel sometimes just isn't sending us a log update message

I did all the log messages by hand so I've probably just got the string for that one wrong, i can fix that one.

[lucascosti]

I did all the log messages by hand so I've probably just got the string for that one wrong, i can fix that one.

Awesome, thanks heaps! 🙇‍♂️

I have certainly seen the PUSH FAIL MOD 1 myself, and i haven't armed my panel in a while, so not actually sure what causes that

Thanks for confirming! I'll try to keep a closer eye on it to see if I can pinpoint some reproducible scenarios.

[sanjay900]

I have updated the log messages, so that should be fixed now