io.net today’s IO is not the same thing as uptime
Keep block rewards, job earned and downtime in three columns. Only the first becomes today’s IO. A high uptime percent does not create IO by itself.
| Figure | Source | What the monitor does |
|---|---|---|
| Today’s IO | UTC-day block rewards for this device ID | Shown; blank if missing |
| Job earned / hire rate | One job on device details | Not shown and not added |
| Downtime and job uptime | Down percentage, downtime by date, job uptime percent | Not converted to IO or an online badge |
Direct answer
Today’s IO is block rewards. It is not uptime and it is not a hire rate. The window is the UTC calendar day from 00:00 until this read. The unit is IO. The device ID inside the summary must match the UUID you pasted, or the figure does not appear. A mismatch or a missing summary stays blank. Blank is not zero. The page shows 0 only when the summary itself says 0.
On the io.net monitor, do not multiply downtime hours by a price. Official device details can include down percentage, downtime by date, and uptime percent on a job. The monitor does not display those and does not convert them into IO.
What each field is
Block rewards answer one question: from UTC midnight until now, what does this device’s block-reward summary say? They do not answer how long the GPU was on, and they do not answer the hire rate.
In the documentation sample, one day’s downtime value is 281.508 with the note “down for 0 days and 0 hours and 4 minutes,” and another day is 12193.385 with a note of 3 hours and 23 minutes. Those are downtime records in the official sample, not IO. The sample job has uptime percent 100 and earned 0 at the same time. 100 does not become a reward by itself.
What to inspect, in order
- Confirm the device ID on the monitor is the UUID on the official details.
- Then read today’s IO. If a number is there, read it as IO. If it is blank, stop. Do not fill in 0.
- Then read the downtime note and job uptime on the official details by themselves. They explain duration. They do not rewrite today’s IO.
- If you have several saved devices, read today’s IO on each one. Binding the same UUID again on the same saved device does not duplicate the reward.
Action branch
- Today’s IO is 0 and job uptime is 100: both can be true together. Zero is block rewards. 100 is that job’s percent. Do not add them into income.
- Today’s IO is 2 and the official note says the device was down for hours earlier that day: 2 is still only the block-reward summary. It is not a net figure after downtime, and the monitor does not subtract again.
- Hardware is present and today’s IO is blank: block rewards are unavailable for this read. Check the same device in the official account. Do not estimate IO from a downtime percent.
Worked case (illustrative, not measured income)
Schematic reading: today’s IO is 0.00, a job in the shape of the official sample has uptime percent 100 and earned 0, and one day’s downtime note is 4 minutes. Report all three. Do not say “100% online, so there must be some IO,” and do not turn 4 minutes of downtime into a deduction other than the 0 IO already shown. Another schematic: today’s IO is 2.00 while a downtime note says the device was down earlier. 2.00 remains the summary figure. It is not an hourly wage spread across online minutes.
Free is five saved devices per project and Pro is 50. That quota does not change how IO is read. Continue with idle versus hired and connection and credentials.
Common questions
Why is today’s IO still 0 after a full night online?
Because today’s IO only reflects the block-reward summary. Online time or job uptime is not converted into IO. A returned 0 is 0.
Can a downtime note be used to estimate IO that was deducted?
No. Downtime stays on the official details. The monitor does not rewrite block rewards with it, and it does not invent a deduction when the line is blank.
Will two saved devices add the same IO twice?
No. Each record shows block rewards for its own device ID. Binding that same UUID again on the same saved device does not copy the IO.