Btw the “id” is indeed the id of the value. I know it’s useless in 99% of the cases, but it’s been there since the beginning cuz we wanted to adhere to REST best practices of having a unique ID per object.
I think I understand the concept of subscribing to “last value” := “/lv”.
This is a really pretty nice, to allow easy handling/parsing on embedded devices like the Arduino.
However, this was not fully what I wanted to ask.
i am looking for the more verbose response and it turned out, that
using MQTT the there is NO “count” keyword/value returned (as it used to be with HTTP/GET).
And I am wondering, if it woud be possible to add it (again) to the return string.
Got it, well the GET returns a count as the default behaviour of the HTTP protocol. So we’re not sending any count ourselves; it is part of the HTTP protocol. As a reference, here’s what we return in the payload in both APIs: