-
-
Notifications
You must be signed in to change notification settings - Fork 7.8k
Explain how mqtt sensors are influenced with expire_after
option when a retained payload was used
#40043
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
Conversation
…en a retained payload was used
✅ Deploy Preview for home-assistant-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Co-authored-by: c0ffeeca7 <38767475+c0ffeeca7@users.noreply.github.com>
@c0ffeeca7 Thanks for reviewing, may be you can have a final look? |
What is meant by "Note that when a sensor's value was sent retained to the MQTT broker"? |
The sensors state is sent to a topic. The user can set a "retain" flag to retain the last send value at the broker. When a client subscribes to that topic, it will receive the last retained value upon subscription. When there is no retain flag clients will only receive live values after they have subscribed. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you, @jbouwh 👍
Proposed change
Explain how mqtt sensors are influenced with
expire_after
option when a retained payload was usedType of change
current
branch).current
branch).next
branch).next
branch).Additional information
Checklist
current
branch.next
branch.