HSM status not correctly updating on C5 after 2.5.0.135

HSM status working fine in 2.5.0.135 and lower software versions since it’s been configured years ago. It shows the proper status on webpage, mobile and dashboard when home, away or night mode.

I originally found this issue in the 2.5.0.146 update and reverted back to the 2.5.0.135 to confirm and then updated just now to the 2.5.0.153 build and it still has this issue.

This image below shows 2.5.0.146 shows webpage logged into the hub showing correct status of I’m Home and has a dashboard pulled up to show status as well highlighted with red to show same status.

This image is after the update to 2.5.0.146 and as you can see, when I set, I’m away the proper status shows on the webpage device for HSM that I’m in armed away mode, but on the dashboard, it shows intrusion is disarmed and it should not, it should show that I’m armed away mode. This also happens with any other mode I set as well.

This image below is after downgrading back to 2.5.0.135 which I’m running again correctly showing status everywhere in the same images and testing as above with the latest version

The only change is software, I do no database changes to resolve this, just update and its broke and downgrade and it works.

Is there any solution to this or does this no longer work correctly on a C5 after 2.5.0.135 build? I’ve posted on the forums over a month ago, nothing but crickets.

I know it’s not the configuration I have as all I do is update firmware to break it or downgrade back to 2.5.0.135 and it’s working fine and matching again. Thoughts?

Does this issue persist in latest 2.5.1 builds?

Last version I tested was the 2.5.0.153 build and it happened there and haven’t tried anything past that at this point.

I’m more than happy to test this in a bit with 2.5.1.140 and then report back what happens. Is there anything specific I should post so there is more information or just report back? Thanks

Just updated to 2.5.1.140 and did a quick test and so far, it’s working. I’ll do a bit more throughout the day, but this looks promising. Thank you for the suggestion to try the new build.

Working perfectly marked solution is to update to 2.5.1.140 Thanks!