Skip to content
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

Open
Marv2190 opened this issue May 29, 2021 · 6 comments
Open

[Feature Request] MQTT Topic No Readout #23

Marv2190 opened this issue May 29, 2021 · 6 comments

Comments

@Marv2190
Copy link

Marv2190 commented May 29, 2021

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

@syssi
Copy link
Contributor

syssi commented May 29, 2021

In my case Home Assistant consumes the MQTT messages and the last_updated timestamp of the sensor gets updated on each message. This is all I need to trigger automations.

@Marv2190
Copy link
Author

Yeah, that would be a work around. I have no last_updated (using NodeRed), but i could use a trigger with delay i think.
Maybe for SMLreader v2 this is an option.

@mruettgers
Copy link
Owner

mruettgers commented May 29, 2021

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 last_updated using a flow variable, that is being monitored by a periodic trigger.

Maybe for SMLreader v2 this is an option.

That won't be a a big deal to implement and I already thought about publishing info/debug messages via MQTT.
Right now debug messages are being published as server sent events in the upcoming version.

@Marv2190
Copy link
Author

I just started with Node-red (because its easy to feed mqtt to Homematic). So iam not deep into it.
In the moment a tried the trigger node (with delay that set it self back with a new message), and it works pretty well. But Info/debug would be a nice to have, ofc. And most of them i found in the code - so its just a giveover to mqtt. :)

Anyway, thanks for this project.

Grüße nach Aachen und Bonn :)

@trombose009
Copy link

Does MQTT also work if no MQTT user and password is set? In my environement no mqtt user is necessary.

@Marv2190
Copy link
Author

Marv2190 commented Jul 9, 2021

Yes, thats how i use it

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants