-
Notifications
You must be signed in to change notification settings - Fork 69
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
[Feature Request] MQTT Topic No Readout #23
Comments
In my case Home Assistant consumes the MQTT messages and the |
Yeah, that would be a work around. I have no last_updated (using NodeRed), but i could use a trigger with delay i think. |
Or you could implement your own
That won't be a a big deal to implement and I already thought about publishing info/debug messages via MQTT. |
I just started with Node-red (because its easy to feed mqtt to Homematic). So iam not deep into it. Anyway, thanks for this project. Grüße nach Aachen und Bonn :) |
Does MQTT also work if no MQTT user and password is set? In my environement no mqtt user is necessary. |
Yes, thats how i use it |
Hi,
thanks for your Project.
After I finally managed to compile it (the release binary is a little older ;) and it worked, I realized that a function to monitor the Device (Readout) would be nice.
Could one also set a timeout from reading the SML telegram via MQTT?
The LWT is good if the ESP dont work anylonger, but dont tell anything about the Meter.
So over one minute no new telegram -> error.
I saw in the code :
DEBUG("Did not receive an SML message within %d seconds, starting over.", READ_TIMEOUT);
but I have no clue how to publish this in MQTT ( A simple "error" "noerror" would be better anyway).
Maybe thats an easy one for you to add.
Danke
The text was updated successfully, but these errors were encountered: