connector
connector copied to clipboard
Auto-configured data connector block based on Telegraf
The published Readme refers to Browser on both the BalenaHub published build as well as the source.
Bumps [pyjwt](https://github.com/jpadilla/pyjwt) from 2.0.0 to 2.4.0. Release notes Sourced from pyjwt's releases. 2.4.0 Security [CVE-2022-29217] Prevent key confusion through non-blocklisted public key formats. https://github.com/jpadilla/pyjwt/security/advisories/GHSA-ffqj-6fqr-9h24 What's Changed Add support for Python...
Currently when autowire finds a MQTT server with the name "mqtt" it connects as a data input source using both "sensors/#" and "balena/#" as topics. Consider allowing the user to...
I tried to run the internetspeedtest fleet on my NUC and got the error ``` Error: no matching manifest for linux/amd64 in the manifest list entries ``` The connector service...
Currently you can provide a custom `telegraf.conf` file by extending the block image but that disables autowire feature. Consider allowing both behaviours simultaneously.
Currently, when using the External HTTP Listener plugin, data posted to this endpoint from multiple sources ends up in the same place within InfluxDB. This works if you have two...
I'm running a device with the sensor service from balenaSense, I've changed the port to 7575 in the code, tried `EXPOSE 7575` in the Dockerfile, and tried setting the port...
Use case: I want to pull two different types of data from two completely different endpoints with different authorization.