Inkbird discovering new devices on restart

[bschatzow]

The problem

New devices discovered that are not nee

What version of Home Assistant Core has the issue?

Not sure. Been an issue for awhile

What was the last working version of Home Assistant Core?

2024.2024.2.0b1

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Inkbird

Link to integration documentation on our website

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

Diagnostics information

No response

Example YAML snippet

N/A

Anything in the logs that might be useful for us?

No info on the new device when discovered, I e. Temp, humidity, battery etc. old Device s are still showing correctly.

Additional information

None

[home-assistant[bot]]

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

Code owner commands

Code owners of `inkbird` 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 inkbird` 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)}}

---

inkbird documentation inkbird source _{^{(message by IssueLinks)}}

[bschatzow]

If anything since the month

[bschatzow]

If anything since the monthly update this has gotten worse. The system keeps discovering new Inkbird devices. I only have 2.

[bschatzow]

Still seeing more Inkbird devices discovery on reboot. Currently on the 2024.4B

[issue-triage-workflows[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[bschatzow]

Still here on 2424.7b5