Feat: post api boxes

[mashazyu]

This PR adds POST functionality for creating new boxes (devices) via the API and updates the data format returned by the /users/me/boxes endpoint to match the openSenseMap API specification.

Changes

• Implement POST /api/boxes endpoint for creating new devices with sensors.
• Ensure that returned device data is backwards compatible for both POST /boxes and GET /users/me/boxes
• Convert last measurement data to string format (this format is expected by the app)
• I hope I fixed ts and lint issues for current pr, but I didn't address anything prior

Testing

I have been testing current PR with senseBox:bike app.

1. After login, I get boxes data in the format supported by current version of senseBox:bike app.
2. I can create new box via app.

Open questions

• What attributes should be returned after box is created and at /users/me/boxes? Is it ok not to return attributes with null values (like it was done before)?
• Is it ok to return last measurement as string, not as double?
• What should be returned as device.acces_token?

[Copilot]

Pull Request Overview

This PR implements POST functionality for creating new devices (boxes) via the API and updates the data format for the /users/me/boxes endpoint to match the openSenseMap API specification.

• Adds a new POST /api/boxes endpoint for creating devices with sensors
• Updates the /users/me/boxes endpoint to return data in openSenseMap-compatible format
• Ensures measurement values are returned as strings instead of numbers for app compatibility

Reviewed Changes

Copilot reviewed 12 out of 12 changed files in this pull request and generated 3 comments.

Show a summary per file

File	Description
app/routes/api.boxes.ts	New POST endpoint implementation with comprehensive OpenAPI documentation
app/routes/api.users.me.boxes.ts	Updated to use device transformation and include JWT token in response
app/models/device.server.ts	Enhanced createDevice function to return sensors and support additional fields
app/models/sensor.server.ts	Modified to cast measurement values to text format
app/lib/device-transform.ts	New utility for transforming device data to openSenseMap API format
app/lib/devices-service.server.ts	Added Zod schema for validating box creation requests
app/schema/sensor.ts	Added TypeScript type for lastMeasurement JSON field
tests/	Added comprehensive test coverage for new functionality
app/routes/api.ts	Updated route configuration to enable POST /boxes

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[scheidtdav]

Regarding your open questions:

• What attributes should be returned after box is created and at /users/me/boxes? Is it ok not to return attributes with null values (like it was done before)?

Yes thats ok. Whatever was done before is currently our goal.

• Is it ok to return last measurement as string, not as double?

It was probably string before, so again: Yes thats ok.

• What should be returned as device.acces_token?

I am frankly somewhat confused by this. Where does this field even come from?
Why would a device respond with an access token if the client just did a request for which a token is required. That implies the client already having a token. Do we even need this?

[mashazyu]

@scheidtdav, thank you very much for the review and feedback!

Per our conversation I removed access_token mentions and addressed your comments.

Last question - because current PR was based on some other PR, which was based on another PR, now i contains commits from one/all of those prs. How would you like me to proceed? I could create a new pr and cherry-pick only my changes? Or there is a better way?

[scheidtdav]

@mashazyu Don't worry about those. Its a bit of a leftover from how we approached the migration previously.
Those commits are all already on dev, but because we squash and merge GitHub cannot figure out which ones to ignore for this PR. There are only your changes though :-)