Device Information

This page was machine-translated. The Japanese page is the official version.

The Information section of the Device Details page displays detailed information about a device.

Details

Device ID

Example: abcdef0-1234-5678-9abc-def012345678

A unique ID that identifies the device. It is assigned automatically when the device is registered and does not change until the device is unregistered.

Device name

Example: !test-device-10000000abcd1234-abcdef0-1234-5678-9abc-def012345678

A name that you can set and change freely to manage the device. By default, a name is generated automatically, as in the example above.

Names can include non-ASCII characters, such as test-device-01 written in Japanese.

Hostname

Example: test-device-10000000abcd1234

The hostname used to access the device over a network. Usually, you do not need to change it unless, for example, an application running on the device must be accessed from outside the network.

Host version

Example: 4.1.0

The version of the OS image used when the device was set up.

Device type

Example: Raspberry Pi 4 Model B

The type of device hardware.

Firmware type

Example: Raspberry Pi (Bookworm)

The type of firmware installed on the device.

Hardware ID

Example: 10000000abcd1234

A unique ID for the device’s Raspberry Pi hardware. Setting up the device again with a rewritten SD card assigns a new device ID, but the hardware ID remains unchanged.

Registration date

Example: 2024-04-12 14:52:41

The date and time when the device was registered.

Uptime

Example: 123d 4h 56m 7s

The amount of time the device has been running since it was started.

Wi-Fi (in priority order)

Example: test_ap1

The SSID of the Wi-Fi network to which the device is connected. You can configure multiple Wi-Fi endpoints. The device tries to connect to them in order, starting with the highest priority. Reorder the endpoints to change their priority.

Wired network settings

Settings for the wired networks used by the device. See Wired Network Settings.

Prevent updates

See Preventing automatic firmware updates by the Agent.

Firmware configuration

See Pinning the firmware version.

Automatic reboot wait

Example: When the network has been disconnected for 10800 seconds

If communication between a device and Actcast is interrupted, the device tries to restore the connection autonomously, including by restarting the device when necessary. By default, restoring communication takes priority over keeping Acts running. Depending on your use case, however, you may prefer to keep Acts running even if that makes connection recovery less reliable.

When automatic reboot wait is enabled, Acts continue running while the device is disconnected. During the configured wait period, the device attempts to reconnect to Actcast without stopping Acts. If communication is not restored before the period expires, the OS restarts.

Specify the wait time in seconds. The allowed range is 3,600 seconds (1 hour) to 604,800 seconds (7 days).

mDNS settings

This setting controls whether mDNS is enabled. When enabled, you can access the device over the network using its hostname.

For example, if the hostname is test-device-123, you can access the device at test-device-123.local.

[wsl2]
dnsTunneling=false