add user_id of scheduler device with scheduler.run_action

[agentmnm]

Checklist

• [ check! ] I checked for similar existing requests (both open and closed) before posting.
• [ check! ] My request is generic, other users may benefit from it too.

Proposal

I propose that when a scheduled action is triggered, that the scheduler-component code is adding the edit: parent_id of the scheduler device, so one can read out who triggered the action of the entity in an automation.

Additional info

in my example I want to know who switched on / off or changed the temperature of a smart thermostat of a radiator. I have entities of the climate domain.
I am reading out the user_id (in an automation (that gets triggered when the climate entity changes)

Now, when I or an other user changes the thermostat via the HA-interface then I can read back the user_id with the statement

actions:
  - action: notify.persistent_notification
    metadata: {}
    data:
      message: >-
        {{ trigger.to_state.context.id }}, {{ trigger.to_state.context.parent_id }}, {{ trigger.to_state.context.user_id }}

In case a person changes it directly at the physical thermostat then it results in none as expected.

Unfortunately I also read back none when the scheduler executed the action of changing or switching on / off the thermostat.

It would be really helpful to know if the scheduler switched a device on or off, or a user did that.
This way you could pause further scheduled events of the entity for a period of time, or for the rest of the day or so...

Thanks and best regards, Martin

[agentmnm]

I wanted to add the link to a Howto in the home assistant community forum:

https://community.home-assistant.io/t/how-to-use-context/723136

[agentmnm]

I have to rephrase my initial proposal from user_id to parent_id
As it was not clear to me that the user_id is strictly reserved for a registered HA user.

I was experimenting with a helper push button. This push button when pushed by my user in the dashboard gets a user_id while the parent_id is none. When the button is pressed by an automation triggered by a schedule helper it gets a parent_id and the user_id is none

As a side note, I found out that when the automation is triggered by a calendar event the parent_id is also none. Is that a bug by HA? I will find out and come back...

[agentmnm]

Ok, I found why my calendar automation did not proved a parent_id
I used the calendar event trigger instead I should have used the state trigger of the calendar from off to on
And when you do that, you get a parent_id.

In the above provided link is a table when and when not parent_id is provided. Event trigger no, but state trigger yes.

[nielsfaber]

Scheduler is unable to provide a certain parent_id when executing an action.
The context information is internally handled by HA, it cannot be influenced from the side of scheduler.
If you think otherwise, please share any code example.
Here's the code that is executed to execute an action:

scheduler-component/custom_components/scheduler/actions.py

Lines 613 to 615 in b722eb4

	await async_call_from_config(
	self.hass,
	task,

[agentmnm]

Thank you. I understand.
I tested with the internal HA calendar, and it also has issues providing a parent_id

So I think I have to write an automation to check every time an attribute of let's say a light or a climate entity changes, if the change was invoked by scheduler.

One thing that is helpful for that is when a schedule is active the state is changing to triggered, so the state of a switch.schedule_my_schedule can be off, then the schedule will not get active; it can be on, then the schedule will get active at the set time (and date if given); and it can be triggered as long as the schedule is active.

If a schedule is given in single mode then triggered is held for exactly one minute long starting from the set time.
Let's say a schedule is switching on a light in single mode at 07:00 then the state changes from on to triggered at 07:00 and is changing back to on at 07:01

So to find out if scheduler switched on that light you would have an automation triggered by the state change of the light and look through all schedules that are triggered and check if among those a schedule switches that light and e.g. set a label for that light entity switched by scheduler otherwise it was switched by something / somebody else