Entities

The integration creates entities across ten platforms. The device state is polled every 30 seconds and all entities update automatically. The table below gives a quick overview; each platform is described in detail below.

Platform	What it controls	Available on
Button	App navigation and notification dismissal	All devices
Light	Display on/off and brightness	SKY only
Notify	Legacy notification service (wraps `show_message`)	All devices
Number	Display brightness (%) and speaker volume (%)	non-SKY / all (if audio available)
Scene	Activate an installed app widget	All devices
Select	Display brightness mode (auto / manual)	non-SKY only
Sensor	Wi-Fi signal strength (diagnostic, disabled by default)	All devices
Switch	Display power and Bluetooth on/off	All (availability-gated)
Text	Bluetooth broadcast name	All (Bluetooth available)
Update	Firmware update tracking	All (OS ≥ 2.3.0)

Button

Four stateless button entities are created per device. Each button triggers an immediate action on the device when pressed. Available on all LaMetric models.

Entity	Action
`next_app`	Advance to the next installed app on the display
`previous_app`	Return to the previous installed app
`dismiss_current_notification`	Dismiss the notification currently shown on screen
`dismiss_all_notifications`	Clear the entire notification queue

Light SKY only

One light entity is created for every LaMetric SKY device. It controls the full LED matrix display — brightness and on/off — in a single entity. Non-SKY devices (e.g. LaMetric Time) do not get a light entity; their brightness is controlled via the Number and Select entities instead.

On/off — turns the display on or off.
Brightness — adjusts display brightness. The HA 0–255 scale is mapped linearly to the range reported by the device, respecting any power-related caps (e.g. lower max when USB-powered).

Streaming host The Light entity is also the target for the pixel streaming entity services (start_stream, send_stream_data, stop_stream) and exposes the current stream status and canvas dimensions as extra state attributes. See the Pixel Streaming page for full details.

Notify

A legacy notification platform that allows calling notify.lametric_hass_local from automations and scripts. Internally it wraps the show_message service. Available on all devices.

Prefer show_message The show_message service exposes all notification options (icon, sound, priority, cycles). The notify platform is provided for compatibility with automations that use the standard HA notify pattern.

Number

Up to two number entities are created per device, depending on hardware availability. Both are placed in the Configuration entity category.

Entity	Unit	Availability
`brightness`	%	non-SKY devices only
`volume`	%	All devices with audio hardware

The valid range for each entity is read directly from the device on every poll, so it automatically reflects hardware limits (e.g. a lower brightness cap when USB-powered).

brightness vs. brightness_mode Changing brightness while brightness_mode is auto is accepted but has no visual effect until brightness_mode is switched to manual.

Scene

One scene entity is created for every installed app widget on the device. The list is updated on each coordinator refresh, so widgets added or removed via the LaMetric app are reflected automatically without restarting Home Assistant. Available on all models.

scene.turn_on — brings the target widget to the foreground on the display.
activate_action — activates the widget and additionally triggers a widget-specific action. See the Entity Services page.

Each scene entity carries an is_active state attribute that is true when the widget is currently shown on the display.

Select non-SKY

One select entity (brightness_mode) controls how the display brightness is determined on non-SKY devices. SKY devices do not have this entity.

auto — the device adjusts brightness automatically using its ambient light sensor.
manual — brightness is fixed to the value set via the brightness Number entity.

Screensaver target The brightness_mode select entity is also the target for the set_screensaver entity service. See the Entity Services page.

Sensor

One diagnostic sensor entity (rssi) reports the Wi-Fi signal strength as a percentage (0–100). It is placed in the Diagnostic category and is disabled by default. Enable it in the entity registry to use it in dashboards or automations. Available on all devices.

Switch

Up to two switch entities are created per device, depending on the capabilities reported by the device. Both are placed in the Configuration entity category.

Entity	Controls	Created when
`display_on`	Turns the display on or off	Display on/off is supported by the device
`bluetooth_active`	Enables or disables Bluetooth	Bluetooth hardware is available on the device

Text

One text entity (bluetooth_name) is created when Bluetooth hardware is available. It sets the Bluetooth broadcast name of the device (1–248 characters). The change takes effect immediately. Placed in the Configuration entity category.

Update

One firmware update tracking entity is created for devices running OS 2.3.0 or later. Older firmware does not expose update information and will not get this entity.

The entity shows the currently installed version and the latest available version. When they differ, Home Assistant marks the entity as having an update available.

Informational only Firmware installation is managed through the LaMetric mobile app. This entity cannot trigger an update — it only reports the available version.