10000 MQTT last_reported not updated · Issue #139989 · home-assistant/core · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

MQTT last_reported not updated #139989

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

Closed
erkr opened this issue Mar 6, 2025 · 7 comments
Closed

MQTT last_reported not updated #139989

erkr opened this issue Mar 6, 2025 · 7 comments

Comments

@erkr
Copy link
erkr commented Mar 6, 2025

The problem

For my P1 Meter (checked with MQTT Explorer), values are published every 30 seconds.

The MQTT integration is apparently not updating last_reported when both the published state and attributes remained the same.

Current behaviour (3rd is wrong imo):
1: State change: last_changed, last_updated, and last_reported are updated -> correct
2: attributes only change; last_updated, and last_reported are updated -> correct
3: same state and attributes published by device; only last_reported should update, but doesn’t!

What version of Home Assistant Core has the issue?

Core-2025.2.4

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

MQTT

Link to integration documentation on our website

https://www.home-assistant.io/integrations/mqtt/

Diagnostics information

No response

Example YAML snippet

Anything in the logs that might be useful for us?

Additional information

No response

@home-assistant
Copy link
home-assistant bot commented Mar 6, 2025

Hey there @emontnemery, @jbouwh, @bdraco, mind taking a look at this issue as it has been labeled with an integration (mqtt) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of mqtt can trigger bot actions by commenting:

  • @home-assistant close Closes the issue.
  • @home-assistant rename Awesome new title Renames the issue.
  • @home-assistant reopen Reopen the issue.
  • @home-assistant unassign mqtt Removes the current integration label and assignees on the issue, add the integration domain after the command.
  • @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
  • @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

(message by CodeOwnersMention)


mqtt documentation
mqtt source
(message by IssueLinks)

@jbouwh
Copy link
Contributor
jbouwh commented Mar 6, 2025

May be your issue is a duplicate of #121978

Try to set force_update in the entities config.

@erkr
Copy link
Author
erkr commented Mar 7, 2025

@jbouwh
Yes you are right, that issue is related but was rejected back then.
Reason I filed a new issue was because of changes in derivative sensor: #83496
There it was confirmed last_report support is lacking in MQTT,See
this PR just opened. Thanks!

@mikefrantz
Copy link

I have several Ring cameras 3rd gen and all of them come in but one of them to MQTT, can you give me some guidance on why or how to repair it? Thanks for all your work on the Ring integration. It is much appreciated.

@erkr
Copy link
Author
erkr commented Mar 11, 2025

@mikefrantz for support, please use discord. Your problem is not related to this issue

@jbouwh
Copy link
Contributor
jbouwh commented Mar 11, 2025

The MQTT docs were updated to inform users how MQTT deals with state updates.
home-assistant/home-assistant.io#37856

See: https://www.home-assistant.io/integrations/mqtt/#entity-state-updates

The linked PR is an opt in to allow disabling suppressing state writes. The default behavior is that MQTT will suppress state writes when a state was not changed.

@jbouwh jbouwh added the wontfix label Mar 12, 2025
@jbouwh jbouwh closed this as not planned Won't fix, can't repro, duplicate, stale Mar 12, 2025
@erkr
Copy link
Author
erkr commented Mar 13, 2025

I will use force_update. Thanks

@github-actions github-actions bot locked and limited conversation to collaborators Apr 12, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

5 participants
0