I'm trying to save data from Ruuvi Gateway MQTT to InfluxDB, but I see no data saved.

$ ./ruuvibridge
[2022-7-4 22:55:59] [info] RuuviBridge starting up, version: v0.1.14
[2022-7-4 22:55:59] [info] Starting data sources
[2022-7-4 22:55:59] [info] Starting MQTT subscriber, mqtt_subscription: ruuvi/+, target: tcp://localhost:1883, topic_prefix: ruuvi
[2022-7-4 22:55:59] [info] Starting data sinks
[2022-7-4 22:55:59] [info] Starting InfluxDB sink, target: http://127.0.0.1:8086, bucket: ruuvi, measurement_name: ruuvi_measurements, minimum_interval: 0s
[2022-7-4 22:55:59] [info] Starting MQTT sink, topic_prefix: ruuvitag, minimum_interval: 5s, target: tcp://localhost:1883
[2022-7-4 22:55:59] [info] Starting processing

$ cat config.yml
# Easiest option: let RuuviBridge poll the gateway for measurements
gateway_polling:
  # Flag to enable or disable gateway polling
  enabled: false
  gateway_url: http://ip.or.hostname.of.the.gateway
  interval: 10s

# Recommended option: Have the gateway send the measurements to a MQTT server and let RuuviBridge subscribe to updates in real time
mqtt_listener:
  # Flag to enable or disable subscribing to a topic on a MQTT server
  enabled: true
  # MQTT broker url, including scheme (tcp, ssl or ws), hostname or IP address, and port
  broker_url: tcp://localhost:1883
  # Client ID, required for persistent sessions and has to be unique on the MQTT server
  client_id: RuuviBridgeListener
  username: <obfuscated>
  password: <obfuscated>
  # Topic prefix to subscribe to, expecting RuuviTag measurements to be published as <topic_prefix>/<mac>
  # You can use + character as a single-level wildcard, for example if you have the gateway mac address in the topic
  # for example: ruuvi/+ as the topic prefix would match the topic ruuvi/<gateway_mac>/<tag_mac>
  topic_prefix: ruuvi

# Third option: Configure Ruuvi Gateway to send measurements here via the custom http server setting
http_listener:
  # Flag to enable or disable the http listener
  enabled: false
  # Port to listen on. Cannot be the same as prometheus listen port if enabled
  port: 8080

# Extra processing of the values
processing:
  # Extended values are enabled by default but can be disabled by changing extended_values to false
  extended_values: true
  # Filter which tags are considered. Valid options:
  # none - no filtering is done, all tags are processed (default)
  # named - only tags which have a name configured will be processed
  # allowlist - only mac addresses listed in filter_list will be processed
  # denylist - mac addresses listed in filter_list will be skipped
  filter_mode: none
  # List of mac addresses to allow or deny if filter_mode is either allowlist or denylist
  filter_list:
    - FFEEDDCCBBAA
    - F0E1D2C3B4A5

# Supports both InfluxDB 1.8 and 2.x
influxdb_publisher:
  # Flag to enable or disable publishing the processed data to InfluxDB
  enabled: true
  # Minimum interval for measurements to publish per tag. InfluxDB handles frequent updates very efficiently due to delta compression so the default is no limit
  minimum_interval: 0s
  # URL for InfluxDB, including scheme, hostname and port
  url: http://127.0.0.1:8086
  # For InfluxDB 1.8 the auth_token is username and password in format "username:password"
  auth_token: <obfuscated>:<obfuscated>
  # This is ignored for InfluxDB 1.8
  org: ""
  # For InfluxDB 1.8 the bucket is the database name, with optional retention policy in format "database/retentionpolicy"
  bucket: ruuvi
  # Measurement name to use
  measurement: ruuvi_measurements
  # Uncomment to add additional tags to a series
  #additional_tags:
  #  mytag: myvalue
  #  myothertag: myothervalue

# Prometheus exporter for data
prometheus:
  # Flag to enable or disable exporting the measurements and RuuviBridge diagnostics in prometheus exposition format
  enabled: false
  # Port to listen on. Cannot be the same as http listener port if enabled
  port: 8081

# Publish the parsed and processed data back to MQTT. Can be the same server or a different one.
mqtt_publisher:
  # Flag to enable or disable publishing the processed data to a MQTT server
  enabled: true
  # Minimum interval for measurements to publish per tag. Accepts values in go duration format ( https://pkg.go.dev/time#ParseDuration ), for example 1m30s
  minimum_interval: 5s
  # MQTT broker url, including scheme (tcp, ssl or ws), hostname or IP address, and port
  broker_url: tcp://localhost:1883
  # Client ID, required for persistent sessions and has to be unique on the MQTT server
  client_id: RuuviBridgePublisher
  username: <obfuscated>
  password: <obfuscated>
  # Topic prefix where to publish, in format <topic_prefix>/<mac>
  # If you use the same server for a source, be sure to use a different topic prefix to avoid conflicts!
  topic_prefix: ruuvitag
  # Uncomment to enable creating Home Assistant MQTT discovery topics
  #homeassistant_discovery_prefix: homeassistant

# Optional names for the tags with the key being the mac address and value being the desired name
tag_names:
  <obfuscated>: Makuuhuone
  <obfuscated>: Parveke
  <obfuscated>: Sauna
  <obfuscated>: Olohuone

# Logging options for RuuviBridge itself
logging:
  # Type can be either "structured", "json" or "simple"
  type: simple
  # Valid logging levels from most verbose to least verbose: trace, debug, info, warn, error, fatal, panic
  level: info
  # Include timestamp in the log line. Can be useful to turn off with certain logging systems which add their own timestamps
  timestamps: true
  # Whether to include the log caller in the logs. This will increase the size of logs but it helps in troubleshooting in some cases
  with_caller: false

# Enable or disable debug mode. This will print all received measurements to the console among other debuggy things, useful for development, testing and troubleshooting purposes.
debug: false

$ influx -username <obfuscated> -password <obfuscated>
Connected to http://localhost:8086 version 1.8.10
InfluxDB shell version: 1.8.10
> use ruuvi
Using database ruuvi
> SELECT * FROM ruuvi_measurements
>

Data is shown when running:

mosquitto_sub -u <obfuscated> -P <obfuscated> -h 127.0.0.1 -p 1883 -t 'ruuvi/<obfuscated>/<obfuscated>'

Any tips?

Temperature related UnitOfMeasurement i.e. degree character seems to be coded as (U+00BA). I think correct one is (U+00B0). Using (U+00BA) as s degree character looked weird in Home Assistant:

..and it was not possible to move the sensor to Homekit without customizing the entity.

Hi, this adds state_class of type measurement to Home Assistant MQTT to allow using Long Term Statistics:

• https://www.home-assistant.io/blog/2021/08/04/release-20218/#long-term-statistics
• https://developers.home-assistant.io/docs/core/entity/sensor/#long-term-statistics

Great bridge to transfer data to Home Assistant. Thanks! However, one question. RuuviBridge decodes data from my RuuviTag like this:

{
    "name": "Postilaatikko",
    "mac": "xx:x...",
    "timestamp": 1650901857,
    "data_format": 5,
    "temperature": 6.875,
    "humidity": 42.0975,
    "pressure": 100399,
    "accelerationX": -0.192,
    "accelerationY": -1.076,
    "accelerationZ": -0.076,
    "batteryVoltage": 3.016,
    "txPower": 4,
    "rssi": -84,
    "movementCounter": 114,
    "measurementSequenceNumber": 6553
}

But I can not find ruuvitag_MAC_movementCounter MQTT topic under homeassistant/sensor and probably for that reason I can find only these sensors in my Home Assistant:

I'd like to see the Movement counter data in Home Assistant. Is this a missing feature or something else maybe?

This allows to add arbitrary tags per series. I use that to add more information about the data, like the location the ruuvi tags are located which this instance of the ruuvibridge processes.

Hi, first of all thanks for the great program. My goal is to have my ruuvi gateway (firmware v1.12.4) collect the data from my 6 ruuvi pro sensors (firmware v.3.31.1) and send it to my local server, where I can display it with Grafana.

I was following the tutorial from ruuvi to set-up an installation for receiving the data, https://ruuvi.com/connecting-ruuvi-gateway-to-a-private-server/ but it failed at the glue logic.

Afterwards, I found your program which seems to be just the right fit. Unfortunately, neither of the 3 offered methods (to receive data from the gateway) seem to work at first.

1. My first try with RuuviBridge was polling the data from the gateway. I can access the gateway in the local network, and had it fully set-up

Ruuvi Gateway’s IP address: 192.168.1.144 Subnet mask: 255.255.255.0 Gateway: 192.168.1.1 DHCP server: 192.168.1.1

and can see the history under http://192.168.1.144/history history.json.txt

root@debianvm:/home/tim/ruuvi_bridge# docker-compose up
Starting ruuvibridge ... done
Attaching to ruuvibridge
ruuvibridge    | [2022-10-29 10:14:56] [info] RuuviBridge starting up, version: git-01695bace9705e53f52735e6e15640f39125ce9c
ruuvibridge    | [2022-10-29 10:14:56] [info] Starting data sources
ruuvibridge    | [2022-10-29 10:14:56] [info] Starting gateway polling, target: http://192.168.1.144, interval: 10s
ruuvibridge    | [2022-10-29 10:14:56] [info] Starting data sinks
ruuvibridge    | [2022-10-29 10:14:56] [info] Starting InfluxDB sink, minimum_interval: 0s, target: http://192.168.1.69:8086, bucket: ruuvi, measurement_name: ruuvi_measurements
ruuvibridge    | [2022-10-29 10:14:56] [info] Starting processing
ruuvibridge    | [2022-10-29 10:14:56] [error] Failed to get history from gateway, target: http://192.168.1.144, interval: 10s, error: Get "http://192.168.1.144/history": net/http: HTTP/1.x transport connection broken: unexpected EOF

Mosquitto also had problems (I guess this is a problem from Docker and how to forward ports, I don't have experience with Docker) and the third HTTP method stayed silent and never received data. So I went back to the first method, where RuuviBridge is polling the data.

Going back to the first HTTP/1.x error, I though that the data format from ruuvi maybe changed (since I had no problem to download the history data on the browser). It turns outs, that during setup of the Ruuvi gateway it should be not optional to take the API key, but is absolutely necessary to copy it and place it in the config.yml of RuuviBridge. Maybe I missed it in the description, but it would be great if you can add to the comment that it is necessary to add the API key.

Currently, there is no way to distinguish between multiple gateways, rather than running multiple instances of RuuviBridge (what I currently do and works). I'd like to suggest teaching RuuviBridge to distinguish between multiple Gateways.

An example could be:

influxdb_publisher:
  [...]
  additional_tags:
    location: $gateway_name

gateway_names:
  XXXXXXXXXXX: LocationA
  YYYYYYYYYYY: LocationB

(That's just a partial config to show the idea)

This approach would make it mandatory to configure the Gateways to publish to a predefined format:

mytopic/$GW_MAC/$TAG_MAC

We could also find a way to make the topic format configurable, if desired.

What do you think about this idea? I'm open to refine it if needed.