Jan-Piet Mens

For posterity, I'll repeat my opinion: > @apt brokers can carry millions of topics. I would *not* want that feature or my iOS would go ‘boom!’ But maybe I'm just...

> if that is already known from the request headers by which I assume you mean HTTP request headers. If so, please keep in mind that MQTT doesn't have those,...

> like described here If iOS is spelled `iOS`, then Android should be spelled `Android`, whereby I would use lowercase only on both.

Temperature etc sounds like a good idea as long as such sensors are generally available on devices. (On our iOS app we submit barometric pressure in `p` for instance.) These...

Gladly, though if you kick me in the direction of where the possible values are documented, I'll gladly take the task. I'm going to assume the data will be quite...

The only data I'd be interested in from above list would be ambient air pressure, relative humidity, and temperature, but as it's the _device's_ temperature it doesn't make much sense...

@brunseba thoughts?

As I think you're indicating: this used to work pre API changes.

I still see ``` 1669855031: Client otrec disconnected, not authorised. ``` so there’s either a mismatch in user/password or there’s an ACL forbidding the client from accessing the MQTT broker....

The console output is printed to stdout/stderr.