> For the complete documentation index, see [llms.txt](https://docs.myrspoven.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.myrspoven.com/integrations/overview/bms-integrations/schneider.md). # Schneider myCoreAI integrates with Schneider Electric **EcoStruxure Building Operation (EBO)** following the same pattern as other BMS integrations: myCoreAI reads sensor and meter values out of EBO and writes a limited, agreed set of setpoints back. This page covers what is specific to EBO. ## Integration model On the EBO side, a dedicated **Myrspoven** top-level folder holds three subfolders: * **Read** — every value myCoreAI reads from EBO (indoor temperatures, pressures, energy meters, equipment status, current setpoints). * **Write** — every setpoint myCoreAI writes back into EBO. * **Overwrite Bindings** — bindings that route written values to the actual EBO points, with a fallback template that takes over if writes stop. Two connection paths are supported: 1. **On-premise** via the Myrspoven edge — a virtual server in the building network bridging EBO to the Myrspoven cloud. 2. **Cloud-based** via a Schneider SmartConnector. This path requires an additional failsafe (see [Failsafe time](#failsafe-time-cloud-integrations)). EBO retains control of the building. myCoreAI only reaches the signals listed in Read, Write, and Overwrite Bindings. ## Monitoring Two surfaces provide a quick health check. **myPortal Blueprint view.** Each sensor carries a color-coded status. | Colour | Meaning | | ---------- | ---------------------------------------------- | | Black | Sensor disabled or broken | | Red | One degree or more above the threshold | | Orange | Above the threshold | | Light blue | Below the minimum threshold | | Blue | One degree or more below the minimum threshold | **EBO ProcessViewer.** The **Myr\_D** and **Myr\_DS** processes sit under the Myrspoven folder. * **Myr\_D** — binary on/off indicator. Green means myCoreAI is running. * **Myr\_DS** — indicates a successful write into EBO. Brief red states are normal and clear within 15 minutes. Persistent red: confirm the write process is enabled, then check the **spov** process for an active error. The cloud icon above each sensor in EBO shows the setpoint chosen by myCoreAI. To pause optimization on a single circuit, open the cloud display's control panel and deactivate that circuit. The loop reverts to its original setpoint. ## Sensor readings out of range 1. **Check the bottleneck list.** It surfaces sensors running too cold or too hot. Adjust the sensor's Min/Max, or disable a sensor in a bad location. 2. **Account for the environment.** Drafts, poor insulation, and direct sunlight produce misleading readings. Fix the physical cause before adjusting the model. 3. **Choose the right scope.** To shift the whole building warmer, raise Max on all sensors. To stop a single outlier from dominating, lower its Min. 4. **Adaptive min/max is provisional.** Under building settings, adaptive min/max limits how far myCoreAI may deviate from the original setpoint. Remove the restriction once the underlying issue is resolved. ### RMSE and automatic fallback Each building has an **RMSE limit** (default 1.7) tracking sensor deviation from expected behavior. When the limit is exceeded, myCoreAI deactivates automatically and the building reverts to EBO's original control logic. To restore optimization: 1. Fix the underlying sensor issue. myCoreAI does not resume while large deviations remain. 2. Remove the **Myr\_DS** lock by double-clicking it. ### SmartConnector dropped its connection Symptoms: read process turns red, signals start dropping, orange dot appears on **Myr\_DS** and **Myr\_D**. Recovery: restart the SmartConnector. ## Verifying data accuracy in EBO When commissioning or auditing a building, walk through the three Myrspoven folders and confirm the values. **Read folder** (`Myrspoven → Read`) For a Read signal, the left arrow (`<-`) in the Signalkey indicates the source of the value; the bidirectional arrow indicates the logging point used downstream. **Write folder** (`Myrspoven → Write`) * Every value must match what appears in the EBO image. Mismatch: check the Signalkey. For a Write signal, the left arrow shows the EBO write value read back; the right arrow shows the write value held on the Myrspoven side. **Overwrite Bindings folder** (`Myrspoven → Overwrite Bindings`) * Values must match the corresponding Write folder values. Mismatch means the binding key is wrong. * Missing or faulty values mean the Signalkey needs checking. For an Overwrite Binding, the left arrow points to the **Myr\_ut** template (holding the fallback value); the right arrow points to the signal being written. ## Failsafe time (cloud integrations) SmartConnector-based integrations require a **Failsafe Time** parameter — a watchdog on the data flowing from myCoreAI into the cloud connector. * **Duration:** 900 seconds (15 minutes). * **Behavior:** if no updated value arrives within the window, the failsafe deactivates the cloud-side integration and reverts to default values. The building continues on EBO's own logic rather than stale setpoints. The failsafe guarantees that an outage on the myCoreAI side cannot leave EBO running indefinitely on outdated values. ## What partners provide To onboard an EBO building: * The agreed signal list — read points and writable setpoints. * An EBO user with access to the **Myrspoven** folder structure (Read, Write, Overwrite Bindings). * Either a virtual server for the Myrspoven edge or a SmartConnector setup. * A point of contact at the Schneider integrator for commissioning. For general troubleshooting not specific to EBO, see [Troubleshooting](/troubleshooting/overview.md). --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.myrspoven.com/integrations/overview/bms-integrations/schneider.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.