Hi all,
I reported the issue here : https://github.com/collectd/collectd/issues/3834
Any help ?
Thanks,
Hi all,
I reported the issue here : https://github.com/collectd/collectd/issues/3834
Any help ?
Thanks,
I would do as advised on that issue: use a local MQTT server and check what are you publishing.
Setting up "vanilla" MQTT to talk to AWS-IoT is not a trivial task, at all. A collectd-module complicates issues even further.
I would simply manually simulate the collectd-data to be sent.
And, when this works, then to use the collectd-module instead. Which is not guaranteed to be free-of-bugs, I guess.
Plain MQTT I already used for comms with AWS-IoT, so you can be shure, this is possible. Whether collectd-plugin is usable, too, I can not decide.
Thanks for the comment. I've tested with a local Mosquitto.
Update here : https://github.com/collectd/collectd/issues/3834
On the same OpenWrt, I bridged a mosquitto broker to AWS and connect collectd-mod-mqtt to this local broker, and it's working ok. All topics are passed though without problem.
So, there is definitely a problem between collecd-mod-mqtt and AWS.
I have same problem: I set up the collectd with mqtt plugin, start a mosquitto local broker, and the collectd send nothing. And I cant figure out what is wrong:
the config:
<Plugin "mqtt">
# Send values to an MQTT server
<Publish "openwrt">
Host "localhost"
Port "1883"
ClientId "openwrt"
# QoS 0
Prefix "openwrt"
# Retain true
# StoreRates false
</Publish>
</Plugin>
start the mosquitto with command
mosquitto
than the collectd with
/usr/sbin/collectd -f -C /etc/collectd.conf
and nothing.
Thanx