Has anyone got this combination working? I’ve followed the tutorial, I already have an MQTT broker running for other IoT devices, so I am trying to use this…
I can see that it is connecting to my mqtt broker as I see this in the logs:
1604863109: New client connected from 172.24.1.180 as Telegraf-Output-ODz3V (p2, c1, k0).
1604863141: Saving in-memory database to /data/mosquitto.db.
1604864087: Client Telegraf-Output-ODz3V disconnected.
… but nothing is actually published…
Hi Rahul,
I disabled authentication on my mqtt broker (using mosquito) but no dice!
For now, I’ve got it publishing to its own broker installed on the Pi running BalenaSense and then using NodeRed to move to my broker… How would I modify the telegraf.config file, when I modify this and reboot it seems to revert back to the original configuration.
I’ve also noticed that even after many hours, the accuracy score hasn’t progressed from ‘1’. I had used the same sensor with an arduino board using the official BSEC libraries and I would see this reach 3 after a few hours… could there be something awry?
I also don’t see values for bVoc and calculated co2, but maybe this is because the accuracy score hasn’t hit 3 yet…
Any thoughts really appreciated
Thanks in advance!
Hi Dan,
In order to edit the telegraf.conf file, you would need to clone the repository locally to your workstation, make your edits, and then push those changes to your device with balena push <app-name>
using balenaCLI.
Are the steps you used to deploy the applications come from this original post?
John
Hi there, I just want to follow up regarding the settings. All the settings on the Home Assistant side are saved to a persistent volume, but on the balenaSense side, Telegraf can only be modified by device variables (as mentioned here: https://github.com/balenalabs/balena-sense#data-outputs) or by the method John mentioned above, making changes to a local copy and re-pushing.
I hope you managed to have everything up and running now.
Georgia
1 Like