> For the complete documentation index, see [llms.txt](https://docs.net2grid.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.net2grid.com/net2grid-energy-ai-edge-on-han-port/functionality.md). # Functionality NET2GRID EnergyAI® Edge on HAN port offers flexible data delivery, letting you choose exactly the data modes your use case needs, from real-time bursts to efficient batch processing, plus direct local access to the hardware itself. ## Triggered Real-Time Data On-demand, high-frequency power updates, activated only when needed, such as when a user opens an app to check live usage. Use case: * **Real-Time Monitoring & Engagement:** Customers typically only check their energy app once a month, at bill time, and static data doesn't build habits. When the app opens, it triggers a live 1-second power feed alongside recent consumption history, powering interactive power charts. This gives users real-time information (e.g., checking if the oven was left on, monitoring high-load appliances, getting alerts for usage spikes) and shifts brand perception from "billing utility" to energy partner, improving app engagement and NPS. ## Edge Events Real-time alerts, detected and triggered locally on the device the moment they happen; no round trip to the cloud required to spot the event. Edge Events cover two types of local detection: * **Power Alerts:** Triggered when instantaneous power crosses a predefined threshold, for both import (offtake) and export (feed-in). This lets you flag both directions of unusual activity (e.g., a spike in consumption from a high-load appliance switching on, or a surge in solar export) the instant it happens on the meter, rather than waiting for the next scheduled reading. * **Capacity Peak Alerts:** Triggered when consumption exceeds a configured threshold within a specific rolling interval (e.g. 900 seconds). This supports capacity-based tariff monitoring and peak-shaving use cases, flagging exactly when a household is at risk of breaching a capacity limit. ## Continuous Interval Data (15 min) Reliable, regularly reported energy readings on a fixed interval; the backbone data mode for backend forecasting, trading, and billing. Use cases: * **Intraday Forecasting & Trading:** Most utilities operate with delayed meter reads, leaving a real-time blind spot exactly when intraday markets move. Continuous interval streams from across the portfolio feed short-term forecasting models in real time, giving trading desks actual visibility into how the portfolio is behaving right now, not hours after the fact. This reduces portfolio imbalance costs and enables more confident intraday market positioning. * **Reliable Dynamic Tariff Billing:** Dynamic tariff billing requires timely 15-minute data, but delayed DSO clearing and meter communication gaps often create missing data blocks that force risky bill estimations. By reading 15-minute interval data directly from the HAN port, NET2GRID EnergyAI® bypasses DSO delays and delivers a continuous, 100% complete data stream, preventing revenue leakage from estimated data, reducing billing disputes, and giving the operational confidence to scale dynamic tariffs safely. ## Continuous Dynamic Data Streams only when a meaningful power change occurs (e.g. a delta greater than 100W), at up to 1-second resolution; efficient enough to run continuously. Use case: * **HEMS Optimization & Orchestration:** Home energy management systems typically optimize individual devices in isolation, without knowing total home load, which leads to poorly informed automation decisions. Continuous dynamic reporting gives HEMS providers a reliable, real-time view of total home load, enabling smarter automation and synchronization across household energy assets, improving load management and strengthening the value proposition for flexibility services. ## Asynchronous High-Resolution Data (1 sec) 1-second power measurements, buffered on the device and delivered to the cloud in optimized batches for offline, asynchronous processing rather than streamed live. Use case: * **Deeper Analysis on High-Resolution Data:** High-frequency data gives richer detail for energy analytics, but streaming it live significantly increases cloud load and transmission costs for use cases that don't need it in real time. By buffering high-resolution measurements on the device and transmitting them in optimized batches, NET2GRID EnergyAI® provides access to high-fidelity historical data, enabling customer segmentation, improved forecasting accuracy, and high-fidelity consumption charts, all through cost-efficient asynchronous handling. ## Direct LAN API Access Beyond cloud streaming, NET2GRID EnergyAI® Edge on HAN port also exposes a local LAN API directly on the device, enabling direct communication with the hardware over the home network for measurements, device status, and other data, without needing to go through the cloud. This supports seamless local integration and asset management use cases, for example, retrieving live readings or device health directly on-site, independent of cloud connectivity. See the [LAN API](https://docs.net2grid.com/lan-api/) reference section for the full set of available endpoints. --- # 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.net2grid.com/net2grid-energy-ai-edge-on-han-port/functionality.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.