Device infrastructure
Credentials, readings, history, alerts, compatible commands and firmware updates.
Read the API guide →Provision devices, collect telemetry and connect supported business systems. Add energy forecasts and customer-specific predictions through our APIs, while you build your application.
For developers and integrators building equipment, energy and water applications.
Use the capabilities your application needs. Software connections and forecasting can work without registering physical devices.
Credentials, readings, history, alerts, compatible commands and firmware updates.
Read the API guide →Read supported asset, geographic and laboratory records. Preserve source identities and link them to your installations.
Explore integrations →Use weather-informed solar forecasts, battery scenarios and supported customer-specific prediction services.
Read the API guide →Monitor water sensors, calculate consumption and price reviewed usage with utility-supplied tariffs.
Read the API guide →Integrate supported prediction APIs without assembling the training, evaluation and model-serving infrastructure yourself.
Estimate solar generation for the next 1–7 days using weather and installation specifications. Model battery charge and shortfalls from explicit assumptions.
Read the API guide →Train supported load, grid, battery, solar, runtime or recommendation models using your workspace’s approved examples.
Read the API guide →Use shared training methods with separate customer data, model versions, evaluation gates and rollback.
Read the API guide →Distinguish trained predictions, physical calculations and rule-based estimates. Check method, model version and data readiness.
Read the API guide →Predictions are estimates. Customer-specific training needs separate authorization, suitable history and a model that passes evaluation; some services use rules or physics when no eligible model is available. Battery lifespan and water-usage forecasting are future work.
SAP/Maximo read profiles are pilots requiring customer-installation validation. The same device foundation also supports energy and water measurements.
See more integration workflows →Explore device behaviour before your board is ready. Generate synthetic telemetry, inject faults, estimate memory and battery budgets, and test unreliable connections.
Start standalone without an account. Connect a Telematric workspace when you need its APIs. OTA is optional.
Supply the location and installation specifications. Receive hourly estimates, daily totals and provider provenance.
Read the forecast contract →// Set the API origin and key on your server.
const response = await fetch(new URL(
'/v1/solar/forecast',
process.env.TELEMATRIC_API_ORIGIN
), {
method: 'POST',
headers: {
'X-API-Key': process.env.TELEMATRIC_API_KEY,
'Content-Type': 'application/json'
},
body: JSON.stringify({
latitude: 4.89, longitude: 7.13,
days: 7, capacity_kwp: 5, inverter_kw: 4
})
});
if (!response.ok) throw new Error('Forecast unavailable');
const { forecast } = await response.json();Start with the SDK and USB setup path. Buffer readings, handle compatible commands and deliver supported firmware updates with deployment tracking.
Read the ESP32 guide →Use the C/C++ source SDK for telemetry, commands and serial provisioning. Supply your board’s network, verified TLS and durable storage drivers.
Read the STM32 guide →ESP32 OTA needs compatible firmware and bootloader configuration. STM32 physical validation is pending; STM32 OTA and browser flashing are not implemented.
Use supported SAP/Maximo read profiles, selected Giswater records and permitted laboratory results alongside device data. Configure credentials and confirm mappings in your workspace.
Check supported scope and prerequisites →Our console helps you configure, test and troubleshoot. Your backend uses the APIs; you choose how to visualize the data and act on supported events.
Connect devices and supported systems. Add forecasts and AI insights when your application needs them.