--- title: How to Turn BESS Error Codes into Action description: "Turn BESS error codes into action: how TWAICE groups and prioritizes error codes and what to do about them." --- [Skip to content](https://support.twaice.com/knowledge/how-to-turn-bess-error-codes-into-action#main-content) ![TWAICE Help CenterWordmark (2)](https://support.twaice.com/hs-fs/hubfs/Wordmark%20(2).png?width=138&height=28&name=Wordmark%20(2).png) Open main navigation Close main navigation - [Contact us](mailto:support@twaice.com) [Contact us](mailto:support@twaice.com) How can we help you? - There are no suggestions because the search field is empty. 1. [Help Center](https://support.twaice.com/knowledge?hsLang=en) 2. [Platform Features](https://support.twaice.com/knowledge/platform-features?hsLang=en) 3. [Alerts & Anomalies](https://support.twaice.com/knowledge/platform-features?hsLang=en#alerts-anomalies) # How to Turn BESS Error Codes into Action ## Learn how the Error Codes feature turns BESS subsystem error codes into prioritised, actionable insights, with a step-by-step walkthrough. **On this page** - [How the new Error Codes feature works](https://support.twaice.com/knowledge/how-to-turn-bess-error-codes-into-action#h_4df4a11cca) - [What Error Codes provide](https://support.twaice.com/knowledge/how-to-turn-bess-error-codes-into-action#h_9ee97b8602) - [Using Error Codes - Step by Step](https://support.twaice.com/knowledge/how-to-turn-bess-error-codes-into-action#h_17515f0193) - [Daily status](https://support.twaice.com/knowledge/how-to-turn-bess-error-codes-into-action#h_1d2c404f2a) - [Fleet overview](https://support.twaice.com/knowledge/how-to-turn-bess-error-codes-into-action#h_f17704efa1) - [Overview of error codes table](https://support.twaice.com/knowledge/how-to-turn-bess-error-codes-into-action#h_a5082cb3dd) - [Group errors your way](https://support.twaice.com/knowledge/how-to-turn-bess-error-codes-into-action#h_6b0aafa76f) - [Detailed error view](https://support.twaice.com/knowledge/how-to-turn-bess-error-codes-into-action#h_8d2ab13058) - [Alert Configuration](https://support.twaice.com/knowledge/how-to-turn-bess-error-codes-into-action#h_3d118b0f62) - [Notification configuration](https://support.twaice.com/knowledge/how-to-turn-bess-error-codes-into-action#h_85d0dd95ec) - [Create a notification](https://support.twaice.com/knowledge/how-to-turn-bess-error-codes-into-action#h_6712b528a9) - [How notifications decide to fire](https://support.twaice.com/knowledge/how-to-turn-bess-error-codes-into-action#h_9d05c45c6b) - [Manage your notifications](https://support.twaice.com/knowledge/how-to-turn-bess-error-codes-into-action#h_124fbad531) - [Mute notifications](https://support.twaice.com/knowledge/how-to-turn-bess-error-codes-into-action#h_15fadf79cc) Error codes are generated across multiple BESS subsystems, but making sense of them at scale is challenging. TWAICE’s new Error Codes feature brings native component errors (e.g. from the BMS and PCS) into a single, structured view – helping teams prioritize issues, spot patterns, and process error codes faster: **To use Error Codes, you may need to onboard additional error code sensors. Please reach out to your Customer Success Manager to get set up!** ### How the new Error Codes feature works The new Error Codes feature can be found under "Operations" on the TWAICE platform. The error codes are generated directly by the BESS and represent fixed, device-defined conditions. You cannot modify what triggers an error code, but you can decide how it is treated within your monitoring setup. You can adjust its severity level and enable or disable it based on your operational priorities. Error Codes provide a consistent, central place to understand the latest state of your assets. You always see the most recent condition for each component rather than dealing with long lists of repeated alarms. This reduces noise, improves clarity, and gives you a more accurate picture of what is happening across your fleet. ### What Error Codes provide - **BESS defined conditions:** Error codes come directly from the BESS and follow fixed logic determined by the device manufacturer. Triggers cannot be changed. - **Centralized view of issues:** Error Codes consolidate all device level faults into a clean overview showing the current state without duplication or outdated alarms. - **Severity categories:** You can classify each code as critical, moderate, or minor. This helps your operations team prioritize quickly and communicate impact clearly. ("Moderate" is the default severity setting) - **Breach history at a glance:** See how often each error code has occurred, when it last appeared, and whether it is a recurring issue or a new development. - **Operational and safety visibility:** Error codes highlight conditions that may affect performance, revenue, or safety, giving you a dependable baseline for monitoring all components in your energy storage system. ### Using Error Codes - Step by Step ### Daily status Start with a quick snapshot of errors that occurred each day to understand whether new conditions have emerged or ongoing ones are escalating. ### Fleet overview This section summarizes the current state across your fleet: - Donut chart showing counts of racks in Critical, Moderate, or No error states - Total numbers of Critical and Moderate errors, including how many racks are affected This helps you quickly identify urgent issues and reduces the effort of scanning through large alarm lists. [![](https://support.twaice.com/hubfs/Knowledge%20Base%20Import/image-Oct-20-2026-12-28-57-4967-PM.png)](https://downloads.intercomcdn.eu/i/o/thagvi83/99585748/a354af0c2b5533851cdf1d207685/image.png?expires=1792501200&signature=2912f12fa792f38622398bb8fc94d3ed07d1eaae0a137ba5df8fa89c1ce37128&req=2dxqzV39qD9k2hL085ZhofbGsfH6sY3zNMMG3AU1s0ryIefIdt4mZNyOgKkd%0AFgsoTatNeS1LxPfZ%0A) ### Overview of error codes table This table brings all error codes and associated components into one structured view. Each row shows: - Severity counters - Error code name and component - Expandable rows to see which racks were affected - Seven day trend line showing stability or escalation - Last occurrence timestamp Search through the list of alerts by typing a component or alert name. Use the eye icon to open detailed rack views and the download icon to export the list. [![](https://support.twaice.com/hubfs/Knowledge%20Base%20Import/image-Oct-20-2026-12-29-01-1564-PM.png)](https://downloads.intercomcdn.eu/i/o/thagvi83/102142674/fac2fa6cc3a0f646d85059fb2013/image.png?expires=1792501200&signature=281b8af91b537bfb3961a07adaf434afafb7e56d69defec612057dff6b674dae&req=0dVtxFz4qjAslxv889osp9KWalk4Zdn85BsDHIYUyRS5uy9fErHk6595d4a3%0A%2B8Qm8a7iNcFWrs9RrA%3D%3D%0A) ### Group errors your way You can group the table using the Group by menu: - Alert (default) - Component type - None This makes it easy to organize the list according to how your team operates. [![](https://support.twaice.com/hubfs/Knowledge%20Base%20Import/image-Oct-20-2026-12-29-06-5600-PM.png)](https://downloads.intercomcdn.eu/i/o/thagvi83/98580580/ed954e988c1986cb0d39b93d6c77/image.png?expires=1792501200&signature=a3adca41bf57e06719b525d72599d5377fb7c0a311fd8a97dd1f92ba5d48a01a&req=2d1qzVj%2FpDdk2hL085ZhofrzInGKMlYSbOmOGLPSo0bUjodukBzrQxtWjsfo%0A22ji0l%2FzPU%2FkMNxq%0A) ### Detailed error view Click the eye icon on any entry to open its detailed view. - **Occurrence history and transitions:** See exactly when the error occurred and how its severity state changed over time. This reveals whether the issue appears sporadically or follows a pattern. - **Time series chart:** Expand the chart to review the relevant sensor values over time and compare them against severity thresholds for context. - **Rack level history:** Inspect the history of the same error code within a specific rack to understand local patterns or anomalies. - **Alert description:** Gives more context to the alert as well as resolution hints, as configured. - **Export options:** Export the overview table or the rack detail view as CSV. [![](https://support.twaice.com/hubfs/Knowledge%20Base%20Import/image-Oct-20-2026-12-29-11-3045-PM.png)](https://downloads.intercomcdn.eu/i/o/thagvi83/102143249/08276d0d283a1d08c444e47fd2e3/image.png?expires=1792501200&signature=268912351adaee60b5090ebcd5127f23285e4a2011972c3080f4e2262623ce64&req=0dVtxFz5rjMhlxv889osp9zVHeyVSJGtIitKRmuNYNe43D69Q1ErhD11k0o%2B%0AMQNnuXo2SvaqzO%2FzZQ%3D%3D%0A) ### Alert Configuration In the Configuration tab, you can tailor how Error Codes behave in your workflow. While you cannot change the logic that triggers an error code, you can adjust how the system surfaces that code. - **Enable or disable codes:** Use the switch to temporarily disable codes that are not relevant to your operations. - **Adjust severity classification:** Assign each error code a severity category that aligns with your operational philosophy: critical, moderate, or minor. - **Add description:** Enter a description and resolution hints. It will then be shown when the alert gets triggered. These options let your team prioritize effectively without altering the underlying BESS logic. [![](https://support.twaice.com/hubfs/Knowledge%20Base%20Import/image-Oct-20-2026-12-29-16-1274-PM.png)](https://downloads.intercomcdn.eu/i/o/thagvi83/81353721/c8c4cfcc61594a40e0d84380cdd7/image.png?expires=1792501200&signature=32d552a99b61c9b1f459f0fe113ff447e1b2f008e37f1e909e4c098ec437f333&req=2NRswFv9rjZk2hL085ZhocFgEHOg7gndVc77%2Bdv2oZGutyjApkWVkMigvgrG%0ADVfCQSURB2dakYbI%0A) Error Codes provide a reliable, structured view of device level conditions across your fleet. With clear severity, history, and trends, you get transparency and actionable context without unnecessary noise. ### Notification configuration Error Codes tell you what happened. Notifications make sure the right people hear about it, without an inbox full of duplicates. In the **Notification configuration** tab you decide which error codes trigger an email, who receives it, and how often. [![](https://support.twaice.com/hubfs/Knowledge%20Base%20Import/image-Oct-20-2026-12-29-21-4107-PM.png)](https://downloads.intercomcdn.eu/i/o/thagvi83/170215386/d1e6af032bb69f387ba2c19993f0/image.png?expires=1792501200&signature=f7162336287b579511c102e81039bca1d9153885c6897fc3ecd5112870da58a5&req=0dJvx1n%2Frz8ulxv889osp8MuwOBLed8L3le%2BaNU3iDnDdI1uIQl3stQ1NdrH%0AMIR7NgxemPHMzsebBw%3D%3D%0A) ### **Create a notification** Click **Add notification** to open the 3-step setup. You can create as many notifications as you need - for example, one for fire-related critical codes going to the on-call team, and a separate one for moderate BMS codes going to asset management. **Step 1 - Define scope:** Give the notification a name, then select the error codes it should cover from the table (severity, alert code, alert name, and component type are shown for each). Search by code or name to narrow the list; a live counter shows how many codes you have selected in total. The panel at the bottom previews the coverage: you will be notified when **any** of the selected codes is triggered. The optional **Notification description** is for your own reference — it is not shown to email recipients. [![](https://support.twaice.com/hubfs/Knowledge%20Base%20Import/image-Oct-20-2026-12-29-26-7397-PM.png)](https://downloads.intercomcdn.eu/i/o/thagvi83/170215595/246fb08859413fb37ec6a377744c/image.png?expires=1792501200&signature=b3c87e2f8dc2987c8481593b0d2b266e552eb8a653fe8e3cf5bbfbff22289b09&req=0dJvx1n%2FqT4tlxv889osp6sbhCHH6PRX%2B2jAm1OPaSq9WmyE08b4KFuhAvTi%0AzqSrD0DbEn8fq%2BKG4Q%3D%3D%0A) **Step 2 - Delivery:** Add one or more recipient email addresses. Notifications are sent immediately as error codes occur, with a cool-down applied per error code - **set to 30 minutes by default**, adjustable in minutes, hours, or days. The cool-down is the noise control: if the same error code is triggered again inside that specified window, no further email goes out for that code. Other error codes are unaffected and will still send. [![](https://support.twaice.com/hubfs/Knowledge%20Base%20Import/image-Oct-20-2026-12-29-31-0904-PM.png)](https://downloads.intercomcdn.eu/i/o/thagvi83/170215950/9745b7a8862c6cc6b8060c0e44ff/image.png?expires=1792501200&signature=3a5c28b02ef71c8fdb4500a545f7c93a73ce26f7b4c3e0f8971adb90a9c37af3&req=0dJvx1n%2FpTIolxv889ospzWvxfIU3k2b5FNuoJ4vfHDv0TPN3MUhAQ7SVJws%0AhkSwElVh%2B3capQM7LA%3D%3D%0A) **Step 3 - Review & confirm:** Review the full setup on one page and see a preview of the email your recipients will receive. Add yourself to the recipient list first if you want to try it, then use Send test notification to send yourself a sample, then **Save** to activate. [![](https://support.twaice.com/hubfs/Knowledge%20Base%20Import/image-Oct-20-2026-12-29-36-1485-PM.png)](https://downloads.intercomcdn.eu/i/o/thagvi83/170216085/b07e05a7f0487a79fdd294a5c3a8/image.png?expires=1792501200&signature=41e4d7fd5a0dc8095bfad966d8ea1ace2c224ac1b735399b8d34f4f3dc9dd24d&req=0dJvx1n8rD8tlxv889osp5sompp5ExReJcfkViww4w2B5jKRPBhVIr%2B9LYmD%0Az9K6ZYka0T8tcUszHQ%3D%3D%0A) ### **How notifications decide to fire** Emails are sent on a change of state, not repeatedly while a condition persists - and you get one email per error code breach, however many components are affected by it. On sites with many components flapping in and out of an error state, this is the difference between a handful of useful emails and hundreds of unusable ones. Each error code has its own cool-down, so a critical code is never held back because an unrelated moderate one fired first. Emails point to the site and component level and link straight into the platform, where you get the live detail. ### **Manage your notifications** The table lists every notification you have set up, showing what it applies to, its delivery settings, and its recipients. Click the alert code count to open a side panel with the full list of subscribed error codes. Use the switch to turn a notification off temporarily - the configuration is kept, so you can turn it back on without setting it up again. The pencil icon opens it for editing; the trash icon deletes it. If an error code is later disabled under Rule configuration, it stays part of your notification but will not trigger an email. [![](https://support.twaice.com/hubfs/Knowledge%20Base%20Import/image-Oct-20-2026-12-29-42-4884-PM.png)](https://downloads.intercomcdn.eu/i/o/thagvi83/170216458/ccabc5c0d377ba99eb310b8d9afa/image.png?expires=1792501200&signature=bde7c4f4b512fd7addf4c64cdf95003a0b49bc28ca37446626bdaf31f8abcc35&req=0dJvx1n8qDIglxv889osp%2BI4nnlJwBRmkliQpijldAq4%2FpJcOnkhQ8O5Rcrl%0APnl06lce5ps8cvn5tg%3D%3D%0A) ### Mute notifications Before planned maintenance or a component replacement, use **Mute notifications** to pause outgoing emails. Muting stops the emails, not the monitoring: rules keep being evaluated, and everything they trigger stays listed on the Alert overview for the whole time the mute runs. **Important:** a mute applies to every recipient on the system, not just you. It sits in front of the emails, so everyone subscribed stops hearing about the muted components until the mute ends. When you set up a mute, you make three choices: - **Components:** by default, the mute covers the whole system. To mute less, open the component list, search for the components affected, and select only those, for example a single PCS. The duration and reason apply to all selected components. - **How long:** 1, 2, 4 or 8 hours, until a custom date, or until you turn it back on. Timed mutes end automatically and notifications resume. If you mute until you turn it back on, nothing is sent until you do. - **Why (optional):** add a short reason, such as the maintenance ticket number. It is shown in the banner and is the only thing that explains the silence to your colleagues, so we recommend always filling it in. While a mute is running, a banner above the notifications table lists each active mute with the components it covers, the time remaining, and the reason, if one was given. Muting does not change your individual notifications; each one resumes exactly as it was configured. Reach out to us for questions and feedback! © 2026 TWAICE Technologies GmbH [twaice.com](https://www.twaice.com)      [Privacy](https://www.twaice.com/legal/data-protection-notice)      [Imprint](https://www.twaice.com/legal/legal-notice)