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

Illuminance entity of Aquara P1 Motion sensor got deactivated #134648

Closed
Kaese83 opened this issue Jan 4, 2025 · 4 comments
Closed

Illuminance entity of Aquara P1 Motion sensor got deactivated #134648

Kaese83 opened this issue Jan 4, 2025 · 4 comments

Comments

@Kaese83
Copy link

Kaese83 commented Jan 4, 2025

The problem

Illuminance entity of Aquara P1 Motion sensor got deactivatedwith update to core2025.1.0
In Zigbee2MQTT it is still available and readable.

What version of Home Assistant Core has the issue?

core-2025.1.0

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

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

@home-assistant
Copy link

home-assistant bot commented Jan 4, 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)

@andyblac
Copy link

andyblac commented Jan 4, 2025

this I due to the new Zigbee2MQTT 2.0 update, not the core, just go to the device and enable it, it was using a different sensor type. this has now been fixed in the new 2.0 update.
Screenshot 2025-01-04 at 12 45 29

@Kaese83
Copy link
Author

Kaese83 commented Jan 4, 2025

Thanks for your help, i didn't see the option to activate right away.
It's working now.

@jbouwh
Copy link
Contributor

jbouwh commented Jan 4, 2025

Closing as this seems no issue with Home Assistant core.

@jbouwh jbouwh closed this as not planned Won't fix, can't repro, duplicate, stale Jan 4, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants