Feature Request – Add “Force Arm” or “Auto Bypass” Support

[yalcinozturk]

Feature Request: Support force arming or auto bypass when zones are open

Hello 👋 First of all, thank you for your great work on this integration – it’s been very helpful for bringing AX Pro into Home Assistant.

I'm encountering a limitation related to arming the system through Home Assistant when certain zones (such as windows or doors) are left open.

Problem:

When I use the official Hik-Connect mobile app, I am able to arm the system even if one or more zones are open. This works because the AX Pro panel is configured to allow arming with open zones (either via auto-bypass or force-arm settings).

However, when I try to arm the system from Home Assistant using this integration, I receive an error like:

statusCode: 4
statusString: “Invalid Operation”
subStatusCode: “arming”
errorCode: 1073774621

I believe this is because the integration does not currently support sending a force arm or auto-bypass parameter when issuing the alarm_arm_away command.

What I'm asking for:

Would it be possible to extend the integration to support arming with open zones, similar to how the mobile app handles it?

This could be:

• A force_arm option (either configurable or always-on)
• Or detecting if zones are open and auto-applying bypass (if supported by the API)

Why this matters:

Many users leave windows partially open (e.g., for ventilation) and still want to activate their alarm. Currently, this use case works in the mobile app but fails in Home Assistant.

Additional Info:

• I'm using the latest version of hikaxpro_hacs from HACS.
• Same user credentials are used in both Home Assistant and mobile app.
• The user has full permissions and can arm/disarm manually with open zones via the app.
• The code_required prompt works fine – it’s only the arming behavior that’s blocked due to open zones.

Let me know if you need logs, API references, or if you'd like help testing any new feature.

Thanks again for your hard work on this!

[petrleocompel]

@yalcinozturk I understand your request. Sadly there is one big problem.

Missing API on Hikvision side. We are missing any calls which will locally do this. The ISAPI docs are not documenting any possibility how to do this. Otherwise It would be already implemented. It was also requested before by others.

I was in touch with some people about the documentation sadly to get full ISAPI doc is not really possible without "agreeing" to basically NDA. Also from what I got the ISAPI doc is kinda still updated anyway.

So I do not know how to fully proceed. My only hope is try to kinda "decompile" the HikConnect app and try to search for some API calls. But if they will be doing everything only with "cloud connection" we have no hope then.

[petrleocompel]

I have some update @yalcinozturk

Going trough the docs again and again noticed there is bypass methods.

• /ISAPI/SecurityCP/control/bypass
• /ISAPI/SecurityCP/control/bypass/<ID>

These could be used for bypassing. But question is ... can I get somehow list of those zones what cannot be activated ?

The implementation would have to be an option in settings... but it is not like "acknowledge" to bypass.
It would be "force bypass every time" no questions.
Even if you would not enable this option it would be possible to use "service action" to activate with bypass.

[yalcinozturk]

Hi again 👋

Thank you so much for diving back into the documentation and finding those bypass endpoints – that’s fantastic news! 🚀

The idea of having an optional setting for "force bypass every time" sounds like a great compromise, and exposing it via a service action makes it even more flexible for automation use cases. I’m definitely looking forward to seeing how this evolves.

If you decide to move forward with implementation, I’d be happy to test things and provide feedback.

Thanks again for your dedication – looking forward to the update!

Best regards,
Yalçın