Common errors in Evoko Home
This article explains how to resolve common error messages encountered in Evoko Home and Evoko Liso.
Evoko Home errors
500: Access is denied. Check credentials and try again.
This error can occur if the Evoko Home Service Account is missing permissions.
- Ensure that the Evoko Home Service Account is a member of the Senders Group.
- Ensure that the Senders Group has the Mail.Send role.
- Ensure that the Evoko Home Service Account is being used as the Sender email.
Graph Migration errors in Evoko Home
X out of Y resources cannot be synced if you migrate to Microsoft Graph. Proceed anyway? Inaccessible resources will be deactivated in Evoko Home. Check logs for details.
This error can occur during Microsoft Graph API migration if the Resource Group is missing rooms or permissions.
- Ensure that the Resource Group includes the necessary rooms.
- Ensure that the Resource Group has the Calendars.ReadWrite role.
Failed to connect to Microsoft Graph, please check the access details! Access is denied. Check credentials and try again. [500]
This error can occur if the Evoko Home Service Account is missing permissions.
- Ensure that the Evoko Home Service Account is a member of the Senders Group.
- Ensure that the Senders Group has the Mail.Send role.
- Ensure that the Evoko Home Service Account is being used as the Sender email.
Failed to connect to Microsoft Graph, please check the access details! The User.ReadBasic.All or User.Read.All permission is required. The GroupMember.Read.All or Group.Read.All permission is required. [500]
This error can occur if the Evoko Home Azure AD application is missing permissions.
- Ensure that the Azure AD Application has Application permissions for User.Read.All and Group.Read.All.
- Ensure that the permissions have had Admin Consent granted for your Organization.
Evoko Liso errors
Internal Server Error! Something went wrong.
This error can occur if the Evoko Home server is configured to sync with Microsoft 365 using OAuth authentication.
See this article for details.
Please make sure that the device with the X MAC address is deleted from the server. Make sure that the device registration period is open if pairing key is not required and try again.
This error can occur if the device registration timer in the Evoko Home Global Settings has not been started.
Make sure to start the timer before attempting to pair the Evoko Liso with Evoko Home.
Microsoft 365 Authentication Failure – Expired Azure Client Secret (AADSTS7000222)
This indicates that the Microsoft Entra ID (Azure AD) application client secret used by the device has expired. As a result, the device is no longer able to authenticate with Microsoft 365.
To resolve the issue, please renew the client secret for the apps registration used by the room booking system. When creating the new secret, make sure to copy and use the Secret Value (not the Secret ID) and update it in the Global Settings of Evoko Home.
Once the configuration has been updated and saved, the changes should propagate to the device. You can then verify the connection status in the Evoko Home application, where a successful authentication message should be displayed if the configuration is correct.