# How to monitor multiple IOTA Train at Home devices from one browser

Build a named device list, check status and partial rewards, and choose browser storage or Google sync for a practical multi-device monitoring workflow.

- Canonical: https://iotahome.site/en/blog/monitor-multiple-iota-devices
- Publisher: IOTA Watch
- Published: 2026-10-01
- Updated: 2026-10-01

When several Macs run IOTA Train at Home, opening each machine’s app is useful for local checks but inconvenient for a quick overview. IOTA Watch brings public device readings into one browser: reported activity, reward totals and training history. Training continues in the official app on each Mac; the browser is a monitor, not a remote control.

## Start with a separate Miner ID for each machine

Copy the public Miner ID from each device’s official Miner screen. The [Macrocosmos FAQ](https://docs.macrocosmos.ai/product-and-services/tah/faqs) distinguishes a device’s hotkey from the coldkey used for payouts: devices have different hotkeys even when they share a payout address. Adding the same ID twice does not monitor two machines.

- Open [My devices](https://iotahome.site/en/app) and add the complete Miner ID

- Give it a name that identifies the machine, such as its room or your existing inventory label

- Repeat on the other Macs and check each name against its source machine

Do not rely on the first few address characters to distinguish devices. Naming the list reduces mistakes when reviewing a machine that is waiting or renaming a device later.

## Choose where the list should live

Without signing in, IOTA Watch stores up to three devices in the current browser. This is convenient for checking a small setup on one computer. A different browser or phone will not automatically receive that local list; clearing browser storage can remove it.

Google sign-in supports up to ten devices in an account-bound list. Use the same Google account when opening the monitor elsewhere. Check the list after switching accounts or signing out: the local and signed-in storage modes are different. The [account and device-list guide](https://iotahome.site/en/learn/google-account-device-list) explains the product limits and storage behavior.

## Read the overview in a consistent order

Start with the data-source ages and warnings. Then filter device statuses to narrow down machines worth checking. An old official sample, waiting state or zero throughput is not enough to conclude that a Mac has disconnected.

Review rewards after checking coverage. When only some devices have usable earnings data, the aggregate is marked partial. That total represents the known devices; it should not be compared with a fully covered total as though both represent the same fleet.

- For a waiting device, compare its run with the [network view](https://iotahome.site/en/network)

- For a device absent from a complete scan, check its full ID and official app

- For one unusual trend, open device details and select the relevant run and time range

## Keep a portable backup

Export the device list as JSON before changing browsers or clearing site data. Import and export move public IDs and names; they do not migrate local training sessions, wallet credentials or payout settings. Store the file where you can retrieve it and verify the restored names after import.

A useful routine is simple: check freshness, review exceptions, inspect reward coverage, then open the official app only where a local check is needed. Start with [finding a Miner ID](https://iotahome.site/en/learn/find-miner-id) and the [data freshness guide](https://iotahome.site/en/learn/data-sources-and-freshness).

## Sources and implementation

- [Macrocosmos · TAH support and FAQs](https://docs.macrocosmos.ai/product-and-services/tah/faqs)
- [Macrocosmos · TAH user guide](https://docs.macrocosmos.ai/product-and-services/tah/tah-user-guide)
- [IOTA Watch · source code](https://github.com/molimao/iota)