Updates & Feature Releases 🚀

Miner IP addresses are now visible on the Tickets table

• The Tickets table has a new Miner IP column, and the IP also appears on the ticket detail view, so a ticket tells you which machine to reach without a trip through the miners table to look it up.

  This is aimed squarely at triage. Working down a list of open tickets, you can go from the ticket to the machine in one step, which matters most when you are clearing a backlog of alerts across a large site. When a ticket is tied to more than one miner, the IPs appear in the same order as the miners on that ticket. Tickets opened against something other than a miner leave the value blank rather than showing a placeholder, so a populated cell always means there is a real machine behind it.
   

Two new remote miner actions: Advanced Thermal Management (ATM) & Overclock

Available from the Miners Table and Actions menu on a miner in Site Map Lite. 

• ATM (Advanced Thermal Management) sets the miner's temperature thresholds and its LuxOS ATM settings, including the ramp timings, temp buffer, and profile minimum and maximum, in one dialog. 

• Overclock sets a tuning profile for the miner, with the options matched to what that model and firmware support. 

Both act on a single machine, so you can tune a miner from the same place you are already triaging it. They appear only on active miners that have reported in and run firmware supporting the command. Alerting for the miner is held for twenty minutes after you apply, so the ramp does not generate noise while the machine settles.

New Generic DNP3 RTU client for utility/QSE integrations

• Foreman now offers a single, generic DNP3 outstation point map for power integrations. Previously, each utility or QSE integration was built individually, which meant every new one was custom work. A utility or QSE that implements the published point map will now integrate with Foreman without bespoke development on either side. This matters most if you are working with a utility or scheduling coordinator on demand response or curtailment signalling and want a defined contract to hand them rather than a negotiation. 
  • Talk to your customer success manager about the point map if this applies to your site.

Fixes & Improvements 🛠️

• Power Event History Export Performance
  Exporting from Power Event History is now much faster and produces a usable file for large events. The export was generating one column per unique miner in the event, so a single event covering 12,745 miners produced 12,745 extra columns. Miner targets are now represented without inflating the column count, which matters most for full site curtailment events.
   
   
• Row Limits on Triggers and the Partner Dispatches API
  Page size limits are now applied as intended. On the Triggers page, selecting a larger rows-per-page option returns the number of rows you asked for, up to 100. On the partner dispatches endpoint, requests are capped at 50 records per page, so integrations relying on a single very large page should page through results instead.