Would you please show me what to do to get the Ruuvi Gateway discovered by the MQTT integration? I followed your instructions in your Github and made the Ruuvitag MAC changes in āparsetagā function node and set up the MQTT broker information. But the Gateway does not show up under the MQTT integration. I have enabled auto-discovery in the MQTT broker. Oh, the āRuuviā and āsend to haā nodes show connected.
BTW, The MQTT broker is receiving messages from the Ruuvi Gateway when I listen to the ruuvi/# topic.
Can you see the config message being sent correctly for each tag/measurement_type? Should be in a topic like
homeassistant/sensor/ruuvitag_xxxxxxxxxxxx_type
MQTTexplorer is a good tool to see what messages are flowing in your broker.
Also did you check your HA config/integrations MQTT if you have the entities without devices. I did end up in this situation while developing the script. If I remember correctly I had to remove the āorphanā ruuvi entities before I got the devices shown correctly.
Sorry. Hard to give exact help with this info. Hope you get it running.
Can this flow listen to more than 1 Ruuvi Gateway? Instruction on how please.
How often does the Ruuvitag sensor broadcast itās bluetooth data? Can that be changed?
How often does the Ruuvit Gateway broadcast itās MQTT data? Can that be changed?
I see no reason why listening several gateways would not work.
That I am not sure. It depends on the firmware. I found this link to ruuvi lab which says.
The 2.5.9 firmware has 3 modes:
RAWv2-fast (broadcast every 1285ms, green LED blinks, theoretical battery life 4 years)
RAWv2-slow (broadcast every 6425ms, green LED blinks, theoretical battery life 6 years)
RAWv1-fast (broadcast every 1285ms, red LED blinks, theoretical battery life 4 years)
I did not find any info on how often the gateway sends the info. I have limited the node-red flow to send the info once / minute. This can be changed by changing this line
if (lastmsg+60<ms) {
The value 60 here is the number of seconds to wait before allowing the next message to pass thru for the device. Hmmā¦ This should be a parameterā¦ Maybe in next version
Would it be possible to get step by step instructions for installing the Gateway client package?
Have tried unsuccessfully install the package in HA OS terminal, Installed Pyscript in HACS, made pyscript integration and copied package files to python folder. None of these seems to do the trickā¦
Is there any plans to get official integration or HACS integration?
We are looking into how we could support RuuviTags in HA, either through the official Bluetooth Sensor integration or through Gateway and MQTT / HTTP. I cannot promise a schedule for the support yet.
Seconded, Iāve tried to get my 10 Ruuvitags and the gateway to work in HA for a few times already and just canāt do it. Itās getting to the point where Iām considering selling everything and buying sensors from a Chinese manufacturer that has official HA support. Iām sure the Ruuvitags are far more accurate but it doesnāt matter if I canāt get them to work.
It would be a good start to get beginner proof introductions, how to get existing solution to work in HA (If solution is doable for āaverage Joeā).
Have been really happy with my Ruuvi tags and Gateway, but it is a big con that I only get sensors visible in HA via iFrame-card in Lovelace. That solution shows me the temperatures, but does not allow me to use data further and off course it is cloud dependent.
Hopefully we see HA supported solution in the future for Ruuvi tags and Gateway.
I finally managed to get it working, it was an issue with pyscript configuration. Just out of curiosity, is there any way to limit the rate of MQTT messages the gateway is sending? With just nine Ruuvitags my CPU usage goes from 1% to 14% even though my J5005-based HA server is far more powerful than a Raspberry Pi. I could see that becoming an issue with a low-powered system and a lot of Ruuvitags.
We donāt have a rate limit on MQTT, original idea is to let the subscribers to decide how much they want to process. We have rate limiting built in HTTP which batches the messages.
Weāll consider rate limit on MQTT as a feature, but we might also decide that once we support multiple HTTP targets only HTTP is used as a rate-limited data transfer mechanism.
I just bought 12pcs of Ruuvi sensors and 1pcs of Ruuvi Gateway and Iām really enjoying using them.
I configured them to the Home Assistant with Mosquitto + MQTT + pyscript-ruuvi-gateway and got it finally working. The instructions werenāt too good in the internetā¦
Unfortunately now this thing takes 60-80% of my CPU (old Intel Atom 1,46GHz).
So some kind of slowing down parameter option to Ruuvi Gateway or official (more efficient) integration to Home Assistant would be very welcomed indeed.
Thanks for the information about MQTT throttling use-case. @Alexey letās keep this in mind when we implement whitelisting, maybe we could add throttling at the same time?