This was a bit tricky to get working, but in the end it works and looks like that: mqtt:Ĭonst size_t CAPACITY = JSON_ARRAY_SIZE(3) ESP32 with ESPHome GatewayĪs a third option and as always 'because I can' I'm using an ESP32 microcontroller with Esphome to receive advertisements, prepare them in the same format as the Ruuvi Gateway and let it process using RuuviBridge. Seems to have a good Bluetooth antenna on it. I'm running that on a Raspberry Pi Zero W and I'm alway pleased how good the reach of it is. Then again RuuviBridge picks the data up. It listens for BLE advertisements from RuuviTags and publishes them on a MQTT topic, in the same format as the Ruuvi Gateway. The companion project to RuuviBridge is ruuvi-go-gateway, which behaves the same as the actual Ruuvi Gateway. I only own one official Ruuvi Gateway, but I wanted to have the same process on other places, that's why I use some alternatives on different places. All of this is running on my little Kubernetes K3s machine. Then RuuviBridge picks them up, processes them and stores the data in an InfluxDB 2 timeseries database.

The Ruuvi Gateway is connected to the local Mosquitto MQTT broker, publishing the measurements there. I pre-ordered one as soon as it was available and received it a few months ago. Ruuvi Gatewayįinally, a viable BLE gateway exists, the Ruuvi Gateway. In this article I'll show you how I use them today. In the meantime I have over 18 RuuviTags deployed on many places and the setup has changed quite drastically since 2017. It's seldom that I stick for such a long time with the same gadget, that means something. The first article I wrote about them is dated back to 2017: RuuviTag with C.H.I.P - BLE - Node-RED - InfluxDB and Grafana.

I'm a big fan of RuuviTags since a long time.

Esphome raspberry pi zero