Here are some known issues with Chromeboxes and Chromebases as well as Google Meet hardware. If available, we list a workaround to help troubleshoot the issue.
After updating to Chrome OS version 72, some devices start on the sign-in screen. To resolve this issue, restart the Chromebox to return it to the Google Meet state. You might need to restart it more than once.
Chromebox: Compatibility issue with Logitech Rally
Due to an Intel USB 3 compatibility issue, Logitech Rally requires the following hardware and software for successful operation:
|Chromebox version||Chrome OS version|
|CN62||M73 or later|
|CN65||M71 or later|
Chromebox error message: Chrome OS is missing or damaged
If you see the error message Chrome OS is missing or damaged, try to:
- Wipe and re-enroll the device. Learn more about wiping and re-enrolling a device.
- Recover the Chromebox with a USB stick and the Chromebook Recovery Utility extension. Learn more about recovering a Chrome OS device.
Note: you can use the utility to create a recovery USB for Chromeboxes or Chromebooks.
If these steps do not fix the issue, please file a support ticket.
If your Chromebox crashes repeatedly or fails to start, it might have a defective component. So that we can investigate, file a support ticket.
To be able to present again, you can:
- Restart the Tap Controller.
- Present to Meet using a computer or mobile device.
To ensure the best experience, administrators set Google-approved peripherals as default. Therefore, after each meeting, the device resets to these peripherals.
If you want to use a different peripheral, you need to ask your admin to set it as default in the Google Admin console. For details, see Set a default peripheral.
If your admin doesn’t want to change the default setting, you can manually set the peripheral before the meeting:
- On the device, click Settings Audio.
- Find and select your peripheral.
- Unplug all other peripherals before you start the next meeting.
Calendar and time zone issuesDelay in assigning calendar resources
After a user is granted admin access, it takes up to 24 hours before that new admin user can assign a resource to Google Meet hardware. Users who experience the issue after 24 hours should contact support.
Some Google Meet hardware doesn't retain the user-defined time zone setting after the initial setup, and return to the default time zone.
To resolve this issue, change the time zone using the following method:
Changing the time zone using the Google Admin console
From the Admin console Home page, go to DevicesGoogle Meet hardware and on the right, click Settings.
Some features require the Chrome devices for meetings with Calendar privilege.
- Scroll down to the Time Zone field and select the correct time zone.
- Click Save.
Camera issuesThe Huddly GO camera disconnects during meetings
- Switch the USB connector from the Chromebox front port to the rear port.
- Switch the USB 3.0 cable to a USB 2.0 cable. Note: This will disable the camera auto-zoom feature.
Some Google Meet hardware users in Japan can experience camera flickering during calls. This is the result of the device overwriting the anti-flickering setting from 50Hz to 60Hz. To resolve this issue:
- Set the device to GMT +09:00 Eastern Indonesia Time (Jayapura Time) to change the power frequency setting while staying in the same time zone.
- Restart the device.
- Schedule the meeting through Calendar.
- Create the meeting on a personal device.
HDMI cable issuesMimo touchscreen error message: Sorry, this room isn't configured properly to support HDMI
When connecting the HDMI cable, if the message Sorry, this room isn't configured properly to support HDMI shows on the Mimo or the external display, try these approaches:
- Ensure that the USB cable connecting to the Mimo is seated properly.
- If you’re using a USB hub, connect the cable directly to the USB port on the Chromebox. If it works without the hub, make sure the hub has the latest firmware.
- If the steps above fail, the problem could relate to a bad cable or cabling misconfiguration, such as the USB cable to the Mimo, the HDMI cable to the computer that is presenting, or an HDMI converter. Replace these with Qualified peripherals for Google Meet hardware kit.
When presenting to a room using HDMI, the presentation stream might not start, or it starts without audio.
Make sure the Mimo touchscreen is connected to power correctly and uses qualified USB 3.0 cables. See our configuration guide for specific details. Sometimes, this issue occurs even if the cables are set up correctly.
Contact support for more details.
Managing meeting invitationsEmail addresses in meeting invitations
Gmail ignores the dot within usernames. For example, firstname.lastname@example.org and email@example.com are delivered to the same inbox. For more information, see Getting someone else's mail.
If a user's email username has one or more dots, meeting invitations sent from a Chromebox must match the exact address, with the dots included. Otherwise, invitations won't let the invitee in and the user will see the error This party is over.
Power outagesChromebox resets when it loses power
If your Chromebox has a Kingston solid-state drive (SSD), it might unenroll and reset to the initial setup screen when there is a loss of power.
Check if your device has a Kingston SSD
- Connect a USB keyboard to the device.
- Restart the Chromebox.
As the device is starting, press Ctrl+Alt+s.
- At the bottom of the screen, click Browse as guest.
- In the Chrome browser window, enter chrome://system.
- Scroll to the storage_info section and click Expand.
- Confirm the model number of the Advanced Technology Attachment (ATA) device is KINGSTON RBU-SNS4151S316GG2.
If your device is affected by this issue, contact the Chromebox manufacturer to request a hardware replacement.
Google, Google Workspace, and related marks and logos are trademarks of Google LLC. All other company and product names are trademarks of the companies with which they are associated.