Where can I check multiple Macs running IOTA together?
Track multiple IOTA Train at Home Macs using public Miner IDs. Learn which IDs to add, how to sync your list and when to check the official app.
Plain text versionWhat do I need from each Mac?
Copy the public Miner ID, or device hotkey, from IOTA Train at Home on each Mac. Give each machine a recognizable name. Several machines can share a payout coldkey, so keep their separate Miner IDs in the monitoring list.
How do I keep the list in one place?
Open IOTA monitoring and add each Miner ID. A signed-out list stays in the current browser. Use the same Google account to sync it across computers and phones, and export a JSON backup before clearing browser data.
How should I read activity and rewards together?
Check the last successful fetch time before reading reported activity and accounted rewards. IOTA's day begins at 00:00 Hong Kong time and includes pending and settled records. USD is a market estimate. Activity and reward sources have separate clocks; an old sample alone does not establish that a machine is offline.
When should I check the Mac itself?
Use the official app on that machine to confirm startup, connectivity or runtime logs. The browser monitor does not read local logs or control training. See data sources and freshness for interpreting missing or old results.
Common questions
Do I need an account, a wallet connection or a subscription?
Public lookups and a local device list can be used without private keys or seed phrases. Google sign-in syncs your list. Free supports 5 devices per project; Pro supports 50, with new subscriptions at US$2.99/month or US$16.99/year. Private io.net and Vast.ai data requires sign-in and platform read credentials; real-account integration still needs further verification.
Does old data or zero rewards mean my device has failed?
Check the last successful fetch time and source first. Failed refreshes preserve previous results; missing fields are not filled with zero. A valid IOTA daily total of zero may mean no matching accounted records yet. Old samples and zero throughput alone do not prove that a device is offline. Inspect runtime logs in the official app on that machine.