-
Notifications
You must be signed in to change notification settings - Fork 123
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MQTT not publishing any messages #652
Comments
sadly you gave very little information, |
Hey there, thanks for your reply. The meters are generating readings regularely (about once per second), and I can see them in the logfile. {
"retry" : 0,
"daemon": true,
"verbosity" : 15,
"log" : "/var/log/vzlogger.log",
"local" : {
"enabled" : false,
"port" : 8080,
"index" : true,
"timeout" : 30,
"buffer" : 600
},
"meters" : [{
"enabled" : true,
"protocol" : "sml",
"device" : "/dev/ttyAMA0",
}
],
"mqtt": {
"enabled": true,
"host": "192.###.###.###",
"port": 1883,
"id": "vzlogger",
"cafile": "",
"capath": "",
"certfile": "",
"keyfile": "",
"keypass": "",
"keepalive": 30,
"topic": "vzlogger/data",
"user": "####",
"pass": "####",
"retain": false,
"rawAndAgg": false,
"qos": 0,
"timestamp": false
}
} I've checked the config file for syntax errors with the online config editor tool. I also tried using the mosquitto test server instead of a local mqtt server, but I wasn't able to Here is what the full logfile looks like after starting the vzlogger service:
|
if you don't define any channels, no data will be published, |
i wonder if the documentation needs to be improved. |
(maybe the solution to #550 is to rip the mqtt code out of vzlogger and create that generic sml-to-mqtt gateway, based on just libsml? if that's what mqtt users expect?) |
MQTT does not seem to be working properly. Using the repository and building with
./install.sh vzlogger libjson libsml mqtt
and then setting up MQTT in thevzlogger.cfg
file, MQTT connects to the server properly, but no messages are published.The logfile shows no errors:
Running on Raspberry Pi 3
The text was updated successfully, but these errors were encountered: