Error code of App

[Roberto Tokici]

I get an error code

11008 no authentication

When I switch to the Zone list – from the home tab – while system is armed.

I dont know how to post a picture, the image link just shows me a source and destination

Thnaks.

[Roberto Tokici]

Then the alarm goes off instantly – when you arm a zone that is set to force arm and is faulted.

Am i missing an option that auto bypasses the zone when faulted and forced armed?

[Michael Burrell]

Roberto,

11008 is “No Authorization” and indicates that a command was sent that the control determined is not authorized.

The most common reason for this is when a disarm command is sent using the Installer PIN, but the system was armed without it. There is a built in safety feature that prevents the Installer PIN from disarming a system that was previously armed using any other method. This includes user PINs, single key arming where no PIN is used, and scheduled arming such as auto arm or rules.

This error can also occur if an installer or user attempts to make a change that their authentication level does not allow. This is less common, as the system typically does not present options that are not permitted. For example, if installer level programming were somehow accessed using a master code and a change was sent to the panel, the panel would reject that change.

If you are connected in the app using the Installer PIN, there are very few cases where changes would be blocked, with the main exception being the disarm scenario mentioned above. If you attempt to edit the system while it is armed, you would instead see a different error code, 11028, which is “Not Allowed while Armed.”

Can you provide a bit more detail on what you are seeing?

Were you authenticated to the panel through the app as an installer or as a user?

Which mobile app were you using, and what version?

Also, can you provide the control firmware version?

Sorry for all the questions, just trying to narrow this down.

Thanks,
Mike

[Roberto Tokici]

This happens on the login for master user, not the admin

V0.13.356

Hardware 0.0.1.4

Firmware 0.0.6.2

Boot 0.0.2.24

 

[Michael Burrell]

Thanks for the information – I will get with the team Monday to look into this. My assumption there is a call being made that is not permitted when armed.

Also – Is it consistent? Does it happen each time?

I will update this thread when I have additional information.

Thanks,

Mike

[Michael Burrell]

Roberto,

I apologize — I completely missed your second post earlier and only saw the first one.

Regarding your question:

“Then the alarm goes off instantly – when you arm a zone that is set to force arm and is faulted.
Am I missing an option that auto bypasses the zone when faulted and force armed?”

I’m not entirely sure I understand the exact sequence of events that is causing the alarm activation, but I’ll address the core of your question.

There is an option under Area Settings called “Auto Bypass.” I’ll explain how that works along with Force Arm, since they are similar in behavior but function differently.

Force Arm (zone setting):
When Force Arm is enabled on a zone and that zone is not ready at the time of arming, the system will temporarily bypass the zone (logs in history as “Inhibited”). Once the zone becomes secure, it is automatically restored (Enabled in the history) and no longer bypassed.

Auto Bypass (area setting):
When Auto Bypass is enabled, any zones that are not ready at the time of arming are automatically bypassed for the entire duration of that armed period. These are logged in History as “Auto Bypassed”.

When both are enabled:
Force Arm effectively overrides Auto Bypass. Zones configured for Force Arm will not remain bypassed for the full arming period. Instead, they follow the Force Arm behavior and restore once they become secure.

If your goal is to have a zone remain bypassed for the entire arming period, you would need to disable Force Arm on that zone and rely on Auto Bypass instead.

This behavior exists because the two features conflict in intent. Force Arm is designed to include the zone in the system once it becomes secure, while Auto Bypass is designed to exclude it for the entire armed state. Prioritizing Force Arm ensures the system does not unintentionally leave a zone unprotected.

You can still use Auto Bypass at the area level, it will simply exclude any zones that have Force Arm enabled.

Again, I apologize for missing that part of your question earlier.

I’ll follow up once I have more information on the error code. In the meantime, please let me know if you have any questions on Force Arm vs Auto Bypass.

Thanks,
Mike

 

[Roberto Tokici]

All good. That’s what I was looking for.

 

But either way the Error code still pops up under the master user.

[Michael Burrell]

Good deal. I will talk with engineering and let you know what we find on the error message.

[Michael Burrell]

Roberto,

I worked with Engineering today, and after some detailed testing we were able to identify the issue you are seeing with Error 11008, “No Authorization.”

This is a bug that appears to only affect Android. When a user has “Automations” disabled under User Groups and then navigates to Zones/Sensors, the page attempts to load data from an automation related entry (outputs). Since that user does not have authorization to request that information, the error is presented.

This was not intended behavior. We have resolved the issue and will be publishing an Android update that will hopefully be available tomorrow. We have tested the fix and uploaded the release for processing in the Google Play Store.

I appreciate you bringing this to our attention, and I apologize for the issue.

If you have any questions, please let me know.

Thanks,

Mike

[Author]

Posts