From an idea to your first readings

1. Start a build and describe what you want to measure, where the device will live, and what should happen when conditions change.
2. Answer the follow-up questions. For example: “Monitor temperature and humidity in my greenhouse. There is Wi-Fi and mains power.” Add the range and sampling interval you need if you know them.
3. Review the specification and any assumptions before moving ahead. Candidate parts are suggestions; they are not a final wiring plan or an order.
4. Create an account or sign in to save work. Use the same browser as your anonymous build so it can be associated with your account.

Sign-in uses an email code. If the service cannot send or verify it, use the error shown on the sign-in screen; delivery depends on the configured environment.

Include the measurements you need, indoor or outdoor conditions, network access, power source, and any alert thresholds. State units explicitly, such as degrees Celsius, and explain whether a threshold should only notify you or eventually control something.

Check the specification as the conversation develops. Correct an assumption by sending another message. A suggested part is a match from the registry, not confirmation that the full design has been validated.

If a reply takes too long, use “Check for a reply.” If the specification has not caught up, use “Refresh build details.” These controls retrieve the existing work; you do not need to repeat the request.

Generated wiring, downloadable firmware, enclosure artifacts, and checkout still require integration. A design preview alone does not confirm that a flashable device or purchasable kit is ready.

Guided flashing is not available yet. The portal does not currently provide a verified end-to-end flow for selecting a board, downloading its firmware, and provisioning a live device.

• Identify the exact board and revision, sensor models, and their required supply voltages.
• Wait for a validated wiring plan and a firmware artifact built for that exact configuration before connecting or flashing hardware.
• Keep Wi-Fi passwords and device credentials out of build messages and screenshots.

You can exercise ingestion without hardware using the repository’s local simulator instructions. They require a development checkout, PostgreSQL, and a locally provisioned device. The readings are fixtures, not measurements from a sensor.

The ingestion service validates each packet and acknowledges it after the database transaction commits. Retrying the same packet and sequence does not add duplicate readings. Reusing that sequence with changed content is rejected.

Latest readings describe sample time; last seen describes when the server received a packet. Delayed uploads can contain older samples. A missing point is a gap, not a zero reading.

The read API supports raw samples, minute averages, and hourly averages. Raw queries cover up to 24 hours at a time, minute queries up to 7 days, and hourly queries up to 366 days. Query-window limits are separate from retention: raw retention is approximately 90 days, minute retention approximately 7 days, and hourly summaries remain after raw expiry.

Rollups are processed separately and may be pending. Expired history is reported explicitly; oversized results require a narrower window or a coarser resolution. History access requires a valid account session and membership in the device’s tenant.

The read API provides stored fleet status, latest readings, and history. The screens available to you depend on the deployed portal version. Production event streaming, provisioning-derived widgets, and device onboarding still require integration. Demo data does not prove that your hardware is connected. Developers can use the telemetry API reference and storage and retention reference.

My build is still waiting for a reply.

Use “Check for a reply” when it appears. For a failed send, retry the same text using the conversation’s retry flow.

The simulator cannot upload.

Check that the local ingestion service and database are running and the credential file belongs to that device. Follow the local guide’s sequence-number instructions for each new invocation. Do not paste the credential into chat.

History is empty or unavailable.

Check the device, channel, and time range. Empty data, expired history, and pending rollups have different meanings. For API access, also verify your session and active tenant. Do not fill missing values with zeros.

Read Security and data handling for implemented controls and the policies still being defined.