Wild guess. Maybe the first one was added as a device in the automation, while the others were added as entities? Compare the yaml of both automations & check
The Studio Heater automations seems to be using only the Studio sensor’s temperature capability (not motion), is that correct? In that case, that sensor’s “Motion detection” capability wouldn’t be expected to show any related connection.
Whereas your PIR Detection automation is using the Hall sensor’s motion capability, so seeing the related motion-related automation connections for it is expected.
I notice I have an automation that uses the Studio PIR indirectly but it uses an area and I can see the automation listed under the area so I guess that explains this also.
triggers:
- trigger: motion.detected
target:
area_id: 964920c5170011ebb06e1365cc5e8f7e
options:
behavior: each