Hi folks. So I thought I'd kick off the forum with a question of mine, that has come about from a perspective of a consumer of the data coming out of the stats hub.
I have created a little program that can run on a RaspberryPi (or anything really) and listens for the stats packets coming out of the Secure Stats Hub, and have been sending that to various cloud-based logging platforms (ThingSpeak, Librator and ElasticSearch) just to play around with it.
On behaviour that I have found particularly inconvenient from a data-consumer point of view is the sparseness of the reports. I realise there is a battery efficiency element to the TRV transmissions, but I think processing the data is possibly quite a bit harder than necessary.
Here, for example, is a snapshot of last week's data from one of my TRV. It's hard to tell what the TRV was "thinking" during the quiet gaps.
I would like to request/propose that related data always be sent together, even if not really changed. So for example, If temperatures are being reported, I would like to see both Current and Target temperatures to be transmitted, and possibly Humidity too, just so it can be processed as a single "environment" update event.
Slow-changing and unrelated metrics such as battery voltage are totally fine to be reported at a different frequency.