Definition 

The Device health currently monitors for four types of issues for inverters and batteries:

• Unresponsive fault

• API fault

• Command fault

• Manufacturer fault

Unresponsive fault

Battery or inverter impact

• Our optimisation will run on out-of-date data. For example, the optimisation might think that the battery is 50% full when it is actually 90% full. In this case, the engine might not make the best decision

• The devices could be stuck in the last mode that was set.

• There will be gaps in the data, so the last data they see will be from the last time the devices were responsive.

• If the issue has happened repeatedly, there will be intermittent gaps in the data.

Customer experience impact

• Depending on the customers’ tariffs and optimisation status, the customer could have lower savings/earnings because Zoa was unable to change the device modes (for example, through missed arbitrage opportunities) or set a suboptimal mode given the out-of-date data

API fault

The Manufacturers API returns errors when queries for the inverter are consistently over a period of at least 30 minutes. This could be an issue with the API, with authorisation, or with Zoas' query. 

Battery or inverter impact

• If Zoa is not able to read data from the API for a period of 15 minutes, then optimisation won’t run

• If Zoa is not able to write to the API, then we won’t be able to set modes, and the battery will remain in the last mode set

Customer experience impact

The customer could have lower savings/earnings because we were unable to change the device modes or set a sub-optimal mode, given the out-of-date data.

Command fault

The inverter did not respond to a command from Zoa for at least 30 minutes. e.g. Asking the inverter to charge, discharge or go into balance mode.

Battery or inverter impact

If the inverter does not respond to a command, it means that optimisation won't be working to its greatest effect (if at all).

Customer experience impact

A customer might not notice that their battery is not changing modes. They will be able to see their battery modes changing within the Optimisation History; however, if the battery doesn't change state, it won't show up here.

Manufacturer fault

This is an error collected from the device manufacturer itself, different manufacturers will use different errors. These are listed below:

GivEnergy faults 

(`field=latestSystemData.status`)

Solis faults 

(`field=inverterDetails.state`)

Solax faults 

(field=inverterDetails.inverterStatus`)