v0.1.0
Tasmota Support
The major theme of this release is the tasmota support. The support was implemented in #14. The two major changes are the support of nested structures in the MQTT JSON payload and an arbitary position of the device ID in the MQTT topic path.
Breaking Changes
The configuration has a breaking change.
Before this release the exporter appended a /+
to the mqtt.topic_path
configuration string. Beginning with this release, the exporter subscribes exactly to the given wildcard pattern. If you configured the topic path foo/bar
until now, you have to change the value to foo/bar/+
.
Changelog
43f4611 Add comment to config.yaml.dist to show eternal presentation to prometheus
0a30033 Add complete local development stack
7b5796b Add sensor name filter config
800b8c0 Append source topic to metrics
f13c36a Breaking: Don't append + automatically to the topic
451f4c0 Change default port as suggested in prometheus/docs#1649
2f2a8de Fix port in docker run
ebeed6e Merge pull request #10 from oxplot/sensor-name-filtering
acf2988 Merge pull request #12 from hikhvar/use-timestamps
ecb0011 Merge pull request #13 from hikhvar/fix-docs
09cc6b1 Merge pull request #14 from hikhvar/support-tasmota
29eb925 Moved to gojsonq to support nested paths
ec23d61 Rename RegexpFilter to use it for device id extraction too
5680206 Support arbitrary position of device id in topic
627c526 Update hack config
d55b834 Updated gosund example
cdb02b9 Updated readme
8d0c1e0 gofmt cmd/