raw packet storing about ruuvicollector

[ojousima]

As a quick note, I looked into this a while ago and it seemed that InfluxDB didn't support storing strings as values. I'm not sure if the data payload could be represented as a really big integer, though.

Even if the data can be represented as an integer, InfluxDB probably cannot use the time series compression on data (or even worse, it might do lossy compression, I don't know enough about internals of InfluxDB).

[DG12]

Perhaps for influx a series of integer fields
" InfluxDB stores all integers as signed int64 data types. "

Or stored into a SQL (MySQL, SQLlite ) database or
even output to a binary file(s) which could be lifetime managed with logrotate

[Scrin]

This is actually loosely related to what I've been planning to do with the Ruuvi Gateway; I'm planning on creating a new application (actually.. I started prototyping already) that receives the (raw) data from the gateway (either HTTP POST or MQTT) and process+store it to InfluxDB in the same format as RuuviCollector, making it a convenient drop-in replacement for those who want to switch from a raspberry running RuuviCollector to that.

When that's done I'm planning to add HTTP POST and/or MQTT support to RuuviCollector (or make a separate application) to make it possible to use RuuviCollector (or the separate application) as a replacement for the gateway, which in turn means it'll send any data from RuuviTags, not just the supported formats. Perhaps this is something you could use?

InfluxDB does support strings, but they're not really that well compressed and kind of weird to have in a TSDB in the first place, so some processing should be done before long term storage anyway. This could be done either directly by having an application receive the data with HTTP POST or MQTT. You could even just have a simple bash script subscribe to the MQTT and process your custom data for long-term storage.

[Scrin]

ruuvi-go-gateway has now reached reasonable stability to recommend using it, currently it supports sending all manufacturer-specific data with company identifier 0x0499 either over HTTP POST or MQTT. If you have a use for a feature not yet supported (such as sending all manufacturer specific data instead of limiting to ruuvi-only), feel free to open an issue there