Updates & Feature Releases 🚀

Issues and Errors tabs on the miner details page

The Issues card on the miner details page now has two tabs, Issues and Errors, so you can see everything wrong with a miner without leaving its page.

Previously, this card was removed from the page whenever a miner had nothing to report, and when it did appear, it only highlighted issues, either System or Custom, tagged as a failure or a warning. Vendor error codes lived in a separate Errors column on the miners table, which meant jumping back to the list to read them while you were diagnosing a single machine. Now the card is always on the miner details page, and it shows the miner's error codes alongside its issues.

The card stays in the same spot in the right rail, and the Issues tab opens by default every time. Each tab shows a count, including zero, so you can tell at a glance whether a miner has anything to look at.

• Issues shows the same System and Custom issues as before, tagged as a failure or a warning.
• Errors shows the vendor error codes reported by the miner, matching the Errors column on the miner list exactly.
• Both tabs show a clear empty state when there is nothing to report.

Owning client and hosting context on miner details

The miner details page now shows the client that owns a miner together with its hosting client when there is one. In co-located hosting setups, a client name on its own can be ambiguous, so the page now makes it clear which party is the hosting client and which is the sub-client before you take action on a machine.

The client name has a copy control that works the same way as the miner ID copy control, so you can paste it into a ticket, message, or search in one click. The miner details header was also rebalanced to fit the new information cleanly.

API Improvements

This release includes several updates for customers and partners who connect to Foreman through its APIs. All of the changes below are documented on our public API page. Learn more about Foreman APIs here.

→ Retired and in-storage miners in the Miners and Assets APIs

The Miners API can now return retired and in-storage miners when you ask for them. Filtering by miner state for retired or in-storage previously came back empty, because those miners were left out before the filter was applied. Requests without a state filter return the same active fleet as before, so existing integrations are unaffected.

The Assets API now tells you the state of the miner each asset is linked to. Assets tied to retired or stored hardware were previously indistinguishable from active equipment, which made reconciling inventory against your live fleet harder than it needed to be.

• Filter the Miners API by retired or in-storage to get those miners back.
• Each asset now includes its linked miner's state: deployed, in repair, in storage, or retired.
• Assets with no linked miner show an empty value for that field.

→ Client list in the Power Partner API

Power partners can now request a list of the clients they work with, including each client's name and whether curtailment opt-in is currently turned on. Before this, partners needed to already know their client IDs and had no way to see opt-in status.

That matters because a dispatch sent to a client with opt-in turned off is accepted but will not curtail the site. With this list, partners can confirm a site is ready to respond before sending a dispatch and can quickly understand why a site did not curtail.

• Results include client ID, client name, and curtailment opt-in status.
• Changes to opt-in made in Power Control settings show up on the next request.
• Deleted and deactivated clients are left out of the list.

→ Attach devices when creating tickets through the Tickets API

Customers who create maintenance tickets through the Tickets API can now attach devices at creation time. Previously, devices included in the request were dropped, even though they appeared when reading tickets back. Tickets created this way now show their attached devices both in the API response and on the ticket in Foreman.

• Attach miners, external devices, inventory items, and asset items by ID and device type.
• Attaching an inventory item takes the requested quantity from stock, and the request is rejected with a clear message if there is not enough on hand.
• Devices that cannot be found are skipped, and the ticket is still created.
• Invalid requests, such as an unknown device type or the same device listed twice, return a clear error message.

Fixes & Improvements 🛠️

Trigger history block loads reliably

• The trigger history block on the dashboard could occasionally fail to load if a trigger's most recent event was being updated at the same moment the block was reading it. The block now handles that case gracefully and shows the trigger without a last event instead of an error, so your dashboard stays usable while triggers are firing.

Bitaxe miner support

• Foreman now recognizes Bitaxe miners.