Entities¶
Each Google Home device gets the entities below. The examples use a device named Living Room that isn't in an area, with Home Assistant in English. If your entity IDs repeat the room, see Room name twice in entity IDs. In other languages, see Entity names in other languages.
| Entity | Example | What it does |
|---|---|---|
| Alarms sensor | sensor.living_room_alarms |
Time of the next alarm, with all alarms in its attributes |
| Timers sensor | sensor.living_room_timers |
Time of the next timer, with all timers in its attributes |
| Alarm events | event.living_room_alarm_events |
Last observed alarm event: ringing, snoozed or stopped |
| Timer events | event.living_room_timer_events |
Last observed timer event: ringing or stopped |
| Device sensor | sensor.living_room_device |
The device's IP address and connection details |
| Do Not Disturb switch | switch.living_room_do_not_disturb |
Turns Do Not Disturb on or off |
| Alarm volume | number.living_room_alarm_volume |
Sets the alarm volume, from 0 to 100% |
| Reboot button | button.living_room_reboot |
Reboots the device |
| Update sensor | binary_sensor.living_room_update |
Whether the device says a firmware update is waiting |
| Wi-Fi network sensor | sensor.living_room_wi_fi_network |
Name of the Wi-Fi network the device uses. Disabled by default. |
| Signal strength sensor | sensor.living_room_signal_strength |
The device's Wi-Fi signal strength. Disabled by default. |
| Uptime sensor | sensor.living_room_uptime |
Estimated time of the device's last boot. Disabled by default. |
The device page also shows the device's firmware version.
If you turn on Bluetooth tracking, each phone or other Bluetooth device you track also gets a tracker entity.
The alarms sensor, timers sensor, event entities, switch and alarm volume are added once the device answers successfully. If a device has only a device sensor, a reboot button, an update sensor, and disabled Wi-Fi and uptime sensors, see No alarms or timers sensors. A device without alarms and timers, such as a Chromecast Audio, doesn't get these entities.
Entities become unavailable, for example, while a device is unplugged or after you remove it from the Google Home app. See When entities are unavailable.
Alarms sensor¶
The state is the time of the next alarm, such as 2026-03-07T15:26:17+01:00. It is unavailable when no alarm is set, or when all alarms are inactive, missed or of unknown status. That is only its state: the sensor keeps its attributes, and actions still run on it.
To start automations at the time of the next alarm or timer, see Automation examples.
The state is an ISO 8601 timestamp, as is the state of the Home Assistant mobile app's next alarm sensor, such as sensor.phone_next_alarm. You can use both in the same automations.
| Attribute | Description |
|---|---|
next_alarm_status |
Status of the next alarm, or none if there are no alarms |
alarm_volume |
Alarm volume in percent, the same value as the alarm volume entity |
alarms |
List of all alarms, with the next one first. Inactive, missed and unknown alarms come last. |
Each alarm in alarms has these keys:
| Key | Example | Description |
|---|---|---|
alarm_id |
alarm/6ed06a56-8a58-c6e3-a7d4-03f92c9d8a51 |
ID of the alarm. Use it to delete the alarm. |
fire_time |
1772893577 |
When the alarm goes off, as a Unix timestamp in seconds |
local_time |
2026-03-07 15:26:17 |
When the alarm goes off, in Home Assistant's time zone |
local_time_iso |
2026-03-07T15:26:17+01:00 |
The same time in ISO 8601 format, convenient for automations |
status |
set |
Status of the alarm |
label |
Wake up |
Name of the alarm, if you gave it one. None if the device leaves it out. |
recurrence |
[1, 2, 3, 4, 5] |
Days of the week the alarm repeats on. Following Google's convention, the week starts on Sunday: 0 is Sunday, 1 is Monday, and 6 is Saturday. None if the device leaves it out. |
Timers sensor¶
The state is the time the next timer goes off, such as 2026-03-07T15:26:17+01:00. It is unavailable when no timer is set, or when all timers are paused or of unknown status. That is only its state: the sensor keeps its attributes, and actions still run on it.
| Attribute | Description |
|---|---|
next_timer_status |
Status of the next timer, or none if there are no timers |
timers |
List of all timers, with the one that goes off next first. Paused and unknown timers come last. |
Each timer in timers has these keys:
| Key | Example | Description |
|---|---|---|
timer_id |
timer/6ed06a56-8a58-c6e3-a7d4-03f92c9d8a51 |
ID of the timer. Use it to delete the timer. |
fire_time |
1772893577 |
When the timer goes off, as a Unix timestamp in seconds. None while paused. |
local_time |
2026-03-07 15:26:17 |
When the timer goes off, in Home Assistant's time zone. None while paused. |
local_time_iso |
2026-03-07T15:26:17+01:00 |
The same time in ISO 8601 format. None while paused. |
duration |
0:10:00 |
Length the timer was set for, as hours:minutes:seconds |
remaining |
0:07:45 |
Time left on a paused timer, as hours:minutes:seconds. None for other timers, which have fire_time instead, or if the speaker doesn't report it. |
status |
set |
Status of the timer |
label |
Pasta |
Name of the timer, if you gave it one. None if the device leaves it out. |
To use the time left in a template or automation, convert remaining to seconds with as_timedelta. For example, {{ as_timedelta('0:07:45').total_seconds() }} gives 465 seconds. remaining is None unless the timer is paused, and as_timedelta fails on None, so check first, for example with timer.remaining is not none.
Alarm and timer status¶
| Status | Meaning |
|---|---|
none |
There is no alarm or timer |
set |
The alarm or timer is set |
ringing |
The alarm or timer is ringing right now |
snoozed |
The alarm rang and was snoozed. Alarms only. |
inactive |
The alarm is inactive. Alarms only. |
missed |
The alarm was missed. Alarms only. |
paused |
The timer is paused. Timers only. |
unknown |
A status the integration doesn't know yet, such as one newer firmware adds. These come last, and the sensor's state never shows their time. |
Timers have no snoozed status. If you snooze a ringing timer, it restarts and its status goes back to set.
Alarm and timer events¶
Use these entities with Home Assistant's Event received trigger to react to each observed alarm or timer, including those that aren't next by fire time. See React to observed alarm and timer events for setup, examples and limits.
For precise timing at the reported due time, use a time trigger on the alarms or timers sensor. Home Assistant schedules it from the known due time; a ringing event waits for a successful poll and can arrive later. See When the trigger runs for the time trigger's requirements and limits.
Each entity's state is the timestamp when Home Assistant published its latest event. Until an event is seen it is unknown; after a restart it may show the restored last event. That history is not a new event. The entities remain available when their lists are empty, subject to the device's availability.
Alarm event types are ringing, snoozed and stopped; timer types are ringing and stopped. Stopped describes the observed end of ringing tracked under a reported ID, including its removal, rather than proof of dismissal. A changed ID can produce stopped for the old ID and ringing or snoozed for the new one without proving physical cessation or identity. A same-ID ringing-to-snoozed alarm produces snoozed only. Polling can miss an entire ring, and startup, reload, recovery from a failed update and reappearance start with a silent baseline.
Every event includes these attributes, except that only timer events have duration and only alarm events have recurrence. In an automation, read them from trigger.to_state.attributes to retain that event's values when several items change together:
| Attribute | Meaning |
|---|---|
event_type |
ringing, snoozed or stopped |
item_id |
The ID reported by the speaker, such as alarm/… or timer/… |
label |
The item's label, or null when it has none |
fire_time |
The item's fire time in Unix seconds, or null if a timer has none. For snoozed, the time the snooze ends: the integration doesn't get the time the alarm was first due. |
duration |
Timer events only. The length the timer was set for, such as 0:10:00, the same as duration in the timers sensor. |
recurrence |
Alarm events only. Days of the week the alarm repeats on, such as [1, 2, 3, 4, 5] (0 is Sunday, 6 is Saturday), the same as recurrence in the alarms sensor. null if the speaker leaves it out or sends anything other than a list of whole numbers. |
observed_at |
ISO 8601 time when the poll response was received, not the exact physical transition time |
previous_status |
The status in the preceding successful observation, or null for a new ID |
status |
The newly observed status, or removed when that ID left a complete list |
Ringing and snoozed use the current item's label, fire time, duration and recurrence. Stopped keeps the last ringing item's values, so a recurring alarm advancing to tomorrow still identifies the occurrence that ended. A poll's event values are kept even if an action changes the sensor's lists before the event is published. Each item produces a separate event, while the entity's current state holds only the latest one.
Device sensor¶
The state is the device's IP address on your network. If no IP address is available for the device, or the device hasn't answered 5 updates in a row, the sensor is unavailable and the device details listed below are hidden. The sensor appears under Diagnostic on the device page.
| Attribute | Description |
|---|---|
device_id |
Google's ID for the device |
device_name |
Name of the device in the Google Home app |
home |
Name of the device's home in the Google Home app. None if the home has no name. A renamed home's new name shows once the integration next gets your device list from Google, usually within about 20 minutes. |
ip_address |
IP address of the device |
available |
true if the device answered its alarms or information request without an error at the last update, which it does even while it rejects its token or is still starting. false otherwise, for example while the device is offline. |
auth_token |
Token Home Assistant uses to talk to the device |
Warning
Anyone who can see the device sensor in Home Assistant can read auth_token and use it to control the device from your network until the token expires, usually within a day. Only give Home Assistant access to people you trust with your devices.
Do Not Disturb switch¶
Turns Do Not Disturb on or off on the device. It appears under Configuration on the device page. If the request to the device fails, Home Assistant shows an error and the switch keeps its old setting; see If a setting or reboot fails.
Alarm volume¶
Sets how loud alarms ring on the device, from 0 to 100%. It appears under Configuration on the device page. If the request to the device fails, Home Assistant shows an error and the old volume stays; see If a setting or reboot fails. The volume of music and other media is a separate setting that you change on the Google Cast media player; see Other integrations for the same devices.
Reboot button¶
Press it to reboot the device. It appears under Configuration on the device page. It sends the same request as the Reboot device action. To press it from an automation or script, use the button.press action:
action: button.press
target:
entity_id: button.living_room_reboot
The button is unavailable until Home Assistant finds the device on your network, and once the device hasn't answered 5 updates in a row. If the device goes offline, pressing the button before then fails with an error; see If a setting or reboot fails.
Not every device supports rebooting. A device can accept the request, so there's no error, even when it doesn't restart. With debug logging on, the log then shows "Successfully asked Living Room to reboot." If the device doesn't restart, reboot it from the Google Home app or unplug it for a minute.
The button's state is the time it was last pressed in Home Assistant, even a press that failed, not when the device last restarted. The Reboot device action and the Google Home app don't set it. Home Assistant keeps it when it restarts, unless the button is unavailable when Home Assistant stops.
Update sensor¶
The sensor is on, shown as Update available, when the device says that a firmware update is waiting to be installed, and off, shown as Up-to-date, when it says there's none. It's unknown until the device has said, and becomes unknown if the device answers without saying. It appears under Diagnostic on the device page. Like the device sensor, it's unavailable while Home Assistant doesn't know the device's IP address.
The sensor shows only what the device itself reports. The integration doesn't compare the device's firmware version with the versions Google publishes; to check, compare them yourself. It can't install updates either: Google installs them on its devices by itself. Before you rely on the sensor, for example in an automation, be aware that:
- Google doesn't document what the device's report means. Google releases each update in stages, so a device may report no update while other devices already run a newer version; Google's page lists a version only once every device can get it. A device in Google's preview program may also not report preview updates.
- No device has been seen reporting an update yet.
The integration checks each device when Home Assistant starts or the integration reloads, then at most every 20 minutes, at the first update after that. A check that fails keeps the last values. Running Refresh devices doesn't check sooner.
Firmware version¶
The device page shows the device's firmware version next to Firmware, in the form Google lists it:
- For a speaker, its Cast firmware version, such as
3.77.512345, as on Google's Nest firmware versions page. - For a display, such as a Nest Hub, its system firmware version, such as
31.20260101.103.1234567, as on the same page. - For a Chromecast Audio, its Cast firmware version, such as
1.56.123456, as on Google's Chromecast firmware versions page.
The integration checks it with the update sensor. While the integration doesn't know the version, for example while the device is offline after Home Assistant starts, the page shows the last version it knew.
Wi-Fi sensors¶
The Wi-Fi network sensor shows the name (SSID) of the Wi-Fi network the device is connected to. The signal strength sensor shows how strong the device's Wi-Fi signal is, in dBm, such as -55: the closer to 0, the stronger. Use them to check a device that often becomes unavailable, for example whether it uses the network you expect and how weak its signal is. Both appear under Diagnostic on the device page.
As a rough guide to what the signal strength means:
| Signal strength | What it means |
|---|---|
| -67 dBm or higher | Strong: meets or exceeds the suggested minimum for voice calls and video streaming |
| -68 to -70 dBm | Okay: meets or exceeds the suggested minimum for email and web browsing |
| -71 to -80 dBm | Weak: the connection may be unreliable |
| Below -80 dBm | Very weak: the device may have trouble staying connected |
These ranges are a rough guide from Understanding RSSI, not figures from Google. If a device's signal is weak, try moving it or your router, or adding a mesh Wi-Fi point.
Every device gets both sensors, including a device without alarms and timers, but they're disabled by default. To enable one, go to Settings > Devices & services > Google Home and select the device. In the Diagnostic card, select the disabled entities, such as +3 disabled entities, then the sensor. In its settings, turn on Enabled and select Update. Home Assistant adds it about 30 seconds later.
A Nest Hub reports its Wi-Fi network but not its signal strength, so its signal strength sensor stays unknown. Other displays may not report a signal either. What a device connected by Ethernet reports isn't known, as none has been checked.
The integration reads both values when it checks the update sensor, so a value is usually up to 20 minutes old, and a short drop in the signal between checks doesn't show. A sensor is unknown until the device reports its value, and becomes unknown again if an answer leaves it out. A check that fails keeps the last values. Like the device sensor, both sensors are unavailable while Home Assistant doesn't know the device's IP address.
Uptime sensor¶
Enable the uptime sensor to compare the estimated time of a device's last boot with periods when it was unavailable. It shows a timestamp, rather than a running duration, and doesn't confirm that a reboot happened. Its name comes from Home Assistant's own localized name for this kind of sensor; no integration translation string is added.
Every device gets the sensor under Diagnostic, including devices without alarms and timers. It's disabled by default; enable it in the device's settings, as with the Wi-Fi sensors. It's unknown until the device reports valid uptime, and becomes unknown if an answer omits it or gives an invalid value. Uptime has been observed on a speaker and a display using current Cast firmware; older models, other displays and Chromecast Audio are unverified and may leave the sensor unknown.
The estimate is the time Home Assistant received the device's answer minus how long the device said it had been running. It's sampled with the update sensor, using an existing request, normally every 20 minutes. After a reboot, the previous boot time stays until the next due check, normally up to 20 minutes and longer while the device doesn't answer or polling is off. A failed check keeps the previous estimate. The downloaded diagnostics include booted_at, the latest estimate before Home Assistant smooths it, even while the sensor is disabled.
Home Assistant ignores differences of less than 60 seconds between estimates, keeping the displayed time steady through ordinary sampling jitter and a restart of the device's local connection without a reboot. Keep these limits in mind when comparing its history:
- Two boots less than a minute apart can appear as one if a check sees the first boot.
- Changes or drift in the clocks can move the estimate without a reboot. Restarting Home Assistant, reloading the integration or recovering from unknown starts a new baseline, which can shift the displayed time slightly too.
- Becoming unavailable and available again appears in the sensor's history even when the underlying boot time stays the same.
When entities are unavailable¶
All entities of a device are unavailable:
- Once Google no longer lists the device, for example after you remove it from the Google Home app, until the integration removes the device. See Remove a device.
- Once the device hasn't answered 5 updates in a row, for example while it's unplugged. At the default 15-second interval, that's usually after one to two minutes. With a shorter interval, a speaker that restarts can miss 5 updates and become unavailable for a moment; with a longer one, it takes longer to notice.
- After the device's update fails unexpectedly, until its next update that works. This affects only that device, also when Home Assistant starts: a device that fails then gets its entities at its first update that works. With polling off, run Refresh devices, or reload the integration.
When the integration can't get your device list from Google, the devices it already has keep updating and their entities stay available. As the integration starts, it has no devices yet, so this doesn't apply: depending on the cause, Home Assistant tries the setup again, the integration starts without devices, or Home Assistant asks you to sign in again. Until the integration gets the list, the entities are unavailable.
Some entities are also unavailable on their own:
- On a device without alarms and timers, such as a Chromecast Audio, the alarms sensor, timers sensor, event entities, switch and alarm volume, if it had them. Reloading the integration or restarting Home Assistant brings them back only if the device then answers for these features.
- The device sensor, reboot button, update sensor, Wi-Fi sensors and uptime sensor, while Home Assistant doesn't know the device's IP address.
- The alarms sensor, timers sensor, event entities, Do Not Disturb switch and alarm volume, once Home Assistant hasn't known the device's IP address for 5 updates in a row. This happens when Google's list misses the device once and lists it again before Home Assistant finds it; until then, the sensors show no alarms and the settings have default values; event entities retain their last-event history. From the first update with the address, only the other conditions apply: they show those values until the device sends its own, and become unavailable once it hasn't answered 5 updates in a row.
Entities that became unavailable because the device didn't answer are available again at the next update the device answers, after it finishes starting. Being available again doesn't always mean new values; see Alarms, timers or settings stop changing.
Home Assistant usually skips an unavailable entity without an error, so an action on it does nothing and doesn't fail. Refresh devices is an exception: it still runs, so it can bring the device back. For the integration's other actions, see Unavailable sensors.
If a setting or reboot fails¶
Turning Do Not Disturb on or off, setting the alarm volume and pressing Reboot fail with an error that names the device and says why when the request to the device fails, for example because the device has just gone offline. For each message and what to do, see A setting or reboot fails.
The error stops your automation or script at this step, unless you let it continue. If one action targets several entities, Home Assistant runs it on all of them and shows only the first error. For several reboots, use Reboot device, which names every device that failed.
Room name twice in entity IDs¶
By default, Home Assistant starts new entity IDs with the device's area. A device named Speaker in the Living Room area gets sensor.living_room_speaker_alarms. Google Home device names often contain the room already, so a device named Living Room speaker in that area gets sensor.living_room_living_room_speaker_alarms.
To avoid this for entities added later, do one of the following:
- Rename the device in Home Assistant without the room, such as Speaker. The device keeps its name in the Google Home app.
- Remove Area in Settings > System > Entity ID format and select Save. This is a global setting for new entity IDs, not just Google Home ones. Integrations that suggest their own entity IDs don't use it.
Entities you already have keep their entity IDs. Changing them is optional. Go to Settings > Devices & services > Google Home and select the device, such as Living Room speaker. Open the ⋮ menu and select Recreate entity IDs. This:
- Builds the entity IDs from the current device name and entity ID format. Do one of the steps above first. Otherwise a device whose name contains its room gets the room twice in all its entity IDs.
- Uses each entity's name and doesn't change it: the name you gave it, otherwise its default name in the language Home Assistant uses for entity IDs. See Entity names in other languages.
- Changes each entity ID of the device that differs from the one Home Assistant would create now, including any you changed yourself. Entity IDs that already match stay the same.
Home Assistant lists the old and new entity IDs before it changes them. If a new entity ID still contains an earlier device name, cancel. Open that entity's settings, select the restore icon (Restore default name) next to its name, select Update, then recreate the entity IDs again.
After you confirm, update the automations, scripts and manually configured dashboard cards that use the entity IDs that changed. See Customizing entities.
Entity names in other languages¶
Home Assistant shows these entities' names in its language, such as Wecker for the alarms sensor in German, or in English where a translation is missing. To correct a translation, see Translate the integration. The update, signal strength and uptime sensors' names are Home Assistant's own names for those kinds of sensors, which Home Assistant translates itself.
In Catalan, Czech, Danish, Dutch, Finnish, French, German, Hungarian, Indonesian, Italian, Norwegian Bokmål, Norwegian Nynorsk, Polish, Portuguese, Romanian, Slovak, Spanish and Swedish, Home Assistant also builds new entity IDs from the translated names. In German, the alarms sensor of a new device named Living Room gets sensor.living_room_wecker. In other languages, such as Russian or Japanese, entity IDs use the English names, as in the table at the top of this page. The update, signal strength and uptime sensors follow Home Assistant's own translations instead, so in some other languages, such as Lithuanian, their entity IDs are translated while the others are in English. What counts is the language set for Home Assistant itself, not the language in your user profile.
Entities you already have keep their entity IDs in every language. In the languages listed above, a new device's entity IDs can then differ from those of your other devices, and Recreate entity IDs changes the existing ones to the translated names too, unless you gave an entity a name of your own. Check the list of changes before you confirm.