The following errors are used to communicate the reason for not accepting an acting request. All errors are added from the backend:
The acting request generated by the mobile device is only valid for a specific period - in this example: 30 seconds. If it takes the system longer to transfer the request to the backend, the backend denies processing the request at all.
The error can occure, if the time of the mobile device is not correct, the communication via Bluetooth took very long or the communication between gateway and backend is slow.
There is currently an active booking for the requested resource, so the request is denied.
To solve this problem, please try the action later, when the booking is finished or cancel the booking.
The user has no permission to access the requested unit.
The user has no permission to access the requested actuator.
The actuator acting request tried to perform an action, which is not available on the actuator.
Please make sure, that the requested action is matching the available actions on the actuator. This error is mostly a setup problem.
The actuator acting request tried to perform an action, for which the user as no permission.
Please make sure, that the permissions are set correctly for the user.
The actuator acting request tried to perform an action, for which the user has no permission at the moment.
The actuator acting request tried to perform an action, but the user has no periods defined in which the action would be allowed.
The user does not have a valid active permission for the requested action.
The following errors are specific for the implementation on iOS
The Bluetooth Low Energy manager was not available. This can happen if the action was triggered too fast after booting the app.
The mobile device couldn’t connect to the requested object. This is mostly an error, based on movement of the mobile device during the action.
The following errors are specific for the implementation on Android