Reply To: Showing live temperature on my own web page: MQTT websocket or another way?

The documentation lists MQTT 3.1.1 for devices (8883 TLS, 1883 if the profile allows it) and HTTPS, with no MQTT over websocket. So the path from the browser to the broker is closed, and I think that’s a good thing, because the device token is the device’s identity, not the reader’s identity.Reading is done through the REST API. For the latest values there is this endpoint:

GET /tenant/<tenantId>/api/telemetry/latest?kind=iot_device&entityId=<cihazId>&keys=temperature,humidity
Authorization: Bearer sk_live_...

But you shouldn’t put the API key in the browser either, same problem. At home I did it like this: there is a 20-line Flask application on a Raspberry Pi, and the key is stored in its environment variable. The page asks Flask at /sera, Flask asks Hermetry, and it returns only two numbers.When creating the key, on the API Keys page give only telemetry read permission (there is a ready-made Read only preset in the modules), and enter the home’s external IP in the IP allowlist. The key is shown only once, so don’t forget to copy it.Details: History API and the authentication page. Even simpler, build a small dashboard in Hermetry and invite your mother to the organization as a user, but if you want a single-number page for your phone, the Flask route is convenient.