Phantom script

Configuration
1

I have a phantom script I can’t find other than the log warning.

image

➜  /config find . -exec grep "pc_monitor" {} \; -print|more
                        "light.pc_monitor"
                    "entity_id": "light.pc_monitor",
                "entity_id": "light.pc_monitor",
                  "entity_id": "light.pc_monitor"
                        "light.pc_monitor"
                            "light.pc_monitor"
                          "entity_id": "light.pc_monitor"
./.storage/trace.saved_traces
        "entity_id": "light.pc_monitor",
        "unique_id": "pc_monitor",
./.storage/core.entity_registry
                  "entity": "light.pc_monitor"
./.storage/lovelace
                      "entity": "light.pc_monitor",
                      "entity": "light.pc_monitor",
                      "entity": "light.pc_monitor",
                      "entity": "light.pc_monitor",
./.storage/lovelace.lovelace_wallpanel
2023-12-06 19:18:52.468 WARNING (MainThread) [homeassistant.helpers.script.pc_monitor] PC Monitor: Already running
./home-assistant.log.1
light.pc_monitor:
./customize.yaml
grep: ./configurator.py: No such file or directory
grep: ./notebooks/GETTING STARTED.ipynb: No such file or directory
    entity_id: light.pc_monitor
      entity_id: light.pc_monitor
          - light.pc_monitor
          entity_id: light.pc_monitor
./automations.yaml
#      my_pc_monitor:
#        unique_id: my_pc_monitor
./switch.yaml
2023-12-06 19:36:44.175 WARNING (MainThread) [homeassistant.helpers.script.pc_monitor] PC Monitor: Already running
./home-assistant.log
      pc_monitor:
        unique_id: pc_monitor
./light.yaml
➜  /config
2

I think I may have found the culprit. This automation was basically a duplicate of what I’m doing in my Office Motion automation to turn on light.office_lights & light.pc_monitor so I’ve disabled it. Traces showed it triggering at the same time as the log warning so time will tell.

image
image693×629 29.6 KB

light.pc_monitor is a templated light entity based on a button sensor from HASS Agent. I guess that button must be seen as a script.

  - platform: template
    lights:
      pc_monitor:
        friendly_name: "PC Monitor"
        unique_id: pc_monitor
        availability_template: '{{ not is_state("binary_sensor.my_pc_is_active", "unknown") }}'
        icon_template: >-
          hass: monitor
        value_template: >-
          {{ is_state("sensor.windows_11_monitorpowerstate", "PowerOn") }}
        turn_on:
          service: button.press
          entity_id: button.windows_11_monitorwake
        turn_off:
          service: button.press
          entity_id: button.windows_11_monitorsleep

image
image942×522 17.5 KB