docs/reference.rst @mqtt_trigger and callbacks #707
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
It says four variables, but lists five, removed "four". I was tripped up by a null message with a payload_obj listed as a required function parameter, give a hint for not specifying it as a required parameter. Moved qos before payload as I listed the arguments in order, and needed it to not be last for payload_obj to be optional and qos not. Fixed the Wildcard formatting, the two bullet points were all made into one paragraph with "- + matches" confusing as I didn't think - was a wildcard, it needed the blank line to render them as bullet points.
Give @pyscript_compile and lambda as another work around for python callback functions.
|
Thanks for the doc updates! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I just got bit by a couple things and wanted to contribute back to improve the documentation.
I think they are all minor changes or formatting and straight forward.
The biggest hurdle I had was trying to query the history, I was wanting yesterday's value, and everything in Home Assistant is geared around the most recent value. In my case I was monitoring my car's TPMS and was wanting the leak rate, so now - yesterday. I tried the Derivative sensor, but it does weighted averages for the time period, and since there's a large block of time each day that the car isn't available to get the pressure completely throws off the average leak rate.
I see the asyncio Futures page list
print(await fut)for getting the future value, but that doesn't seem to work. The best I've done isfuture.add_done_callbackwith all the drawbacks of needing to pass a compiled python function or lambda, it does work for what I need.