Device Config Creep

[rsmanning]

The problem

I've noticed this issue a couple times before and deleted a device and recreated it to get rid of the problem but recently when it happened I searched and posted about it on Reddit . Every once in awhile I'll add a device and shortly after, not always right away, I'll go to look at it will have pulled in device info from a different unit. I'll include a recent example in the pic below:

This is the device page for brand new Sonoff smart plug I just flashed with Tasmota and configured MQTT to connect it to Home Assistant. The reference to ESPhome and the offline (Black Freezer...) sensor data is a board I'm still building out thats offline I was working on a couple days prior. I don't know why some of that ESPhome device data is creeping into my Tasmota device page. In the past I've seen device pages for other ESPhome light switches suddenly have other ESPhome switch data so up on their page as well. Very strange and their are no automations or scenes using ether of these currently.

What version of Home Assistant Core has the issue?

2024.7.2

What was the last working version of Home Assistant Core?

Unknown

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Not one in particular

Link to integration documentation on our website

No response

Diagnostics information

No response

Example YAML snippet

I don't think it matters but this is the Yaml for the "Black freezer" reference above:

esphome:
  name: garage-freezer-2
  friendly_name: Garage Freezer 2
  platform: ESP8266
  board: d1_mini

# Enable logging
logger:

# Enable Home Assistant API
api:
  encryption:
    key: 

ota:
  - platform: esphome
    password: 

wifi:
  ssid: !secret wifi_ssid
  password: !secret wifi_password

  # Enable fallback hotspot (captive portal) in case wifi connection fails
  ap:
    ssid: "Garage-Freezer-2"
    password: "XHukys270w7U"

captive_portal:

one_wire:
  - platform: gpio
    pin: D4

sensor:
  - platform: dallas_temp
    address: 0x1b0000006a704928
    name: Black_Freezer Temp_C3
    id: temp_c3
    resolution: 9
  - platform: template
    name: Black_Freezer Temp_F3
    id: temp_f3
    lambda: return id(temp_c3).state * 9/5+32;
    update_interval: 1s
  - platform: dallas_temp
    address: 0x850000006c2aa028
    name: Veggie_Freezer Temp_C7
    id: temp_c7
    resolution: 9
  - platform: template
    name: Veggie_Freezer Temp_F7
    id: temp_f7
    lambda: return id(temp_c7).state * 9/5+32;
    update_interval: 1s

Anything in the logs that might be useful for us?

No response

Additional information

No response

[rrooggiieerr]

Very unlikely, but do your devices happen to have the same mac address?

[joostlek]

Can you post your .storage/device registry file? (Don't have the exact name, I'm on mobile)

[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.