Thanks for your reply. I was able to solve the problem in the meantime and it was exactly what you described.
I downloaded the MQTT diagnostic information and found
},
"device": {
"id": "9daxxxxxxxxx",
"name": "Amcrest AD110",
"name_by_user": null,
"disabled": false,
"disabled_by": null,
"entities": [
{
"device_class": null,
"disabled_by": "integration",
"disabled": true,
"entity_category": "diagnostic",
"entity_id": "sensor.ad110_version",
"icon": null,
"original_device_class": null,
"original_icon": "mdi:package-up",
"state": null,
"unit_of_measurement": null
},
{
"device_class": null,
"disabled_by": "integration",
"disabled": true,
"entity_category": "diagnostic",
"entity_id": "sensor.ad110_serial_number",
"icon": null,
"original_device_class": null,
"original_icon": "mdi:alphabetical-variant",
"state": null,
"unit_of_measurement": null
},
{
"device_class": null,
"disabled_by": "integration",
"disabled": true,
"entity_category": "diagnostic",
"entity_id": "sensor.ad110_host",
"icon": null,
"original_device_class": null,
"original_icon": "mdi:ip-network",
"state": null,
"unit_of_measurement": null
}
]
There are three hidden sensor entities
![AD110](https://community-assets.home-assistant.io/original/4X/1/d/7/1d7ce9f4c874e3f92ae589bc976704dd74bca3c3.png)
and HA says “The entity does not exist.”
![AD110_Host](https://community-assets.home-assistant.io/original/4X/5/c/3/5c30699ec7add14f32df3a5a895f093306babfc7.png)
But these entries were still in the MQTT database. So these three entities were reloaded after a HA reboot. I deleted them from the MQTT database and the “spook” was over. ![:grinning: :grinning:](https://community.home-assistant.io/images/emoji/twitter/grinning.png?v=10)