"Show as" entities' Activity log not showing the Automation it was triggered by

[roelanddewindt]

My initial initial question on the HA community forum did not result in anything hopeful, so I am raising it here as a potential improvement for Spook.

In Home Assistant, the “Show as” feature allows an entity (e.g., a switch) to be exposed as another type (e.g., a light). The new entity reflects the same device state but depends on the original entity.

When an automation calls the original entity (for example switch.turn_on`), the action is logged only for that entity. The derived entity created via “Show as” does change state, but its activity log does not show which automation triggered the change.

Request for Spook:
Detect situations where an automation targets the source entity of a “Show as” mapping instead of the derived entity. If possible, restore the missing automation context for the derived entity. If restoring the attribution is not technically feasible, Spook should at least report this as a detected issue. I'm baffled that HA doesn't connect the dots itself.

Goal
Improve automation traceability and debugging clarity. Ultimately, automations should be updated to use the newer derived entities (e.g., the light) instead of the original ones (e.g., the switch). However, because the activity log of the derived entity currently does not reveal which automation triggered it, tracking down those legacy automations is harder than necessary. Detecting or flagging these cases would help identify and update them.