How do I configure a condition for physical press vs electronic activation?

[homeassken]

How do I configure a switch condition for physical press vs electronic activation? In other words, if I press it physically it does one thing. If it’s activated by other means, it does something else?

[123 (Taras)]

Automation determine who changed input

Yes. If the value of the input_number is changed by an automation, trigger.to_state.context.user_id will be none otherwise it will be a long alphanumeric string representing the user’s identifier. If you simply check that user_id is not none it will mean it was changed by a user (via the UI). Whatever automation you are using to call the custom MQTT script, will need to check trigger.to_state.context.user_id (assuming it employs something like a State Trigger that reports context.user_id).

[homeassken]

So, there are 3 ways to trigger a switch: physical press, automation, or user interface selection. It appears here to say that if it’s turned on via automation it will user_id none, but how do I differentiate between physical press and someone turning on via UI? I’m assuming physical press would also be user_id none.

[123 (Taras)]

@homeassken

how do I differentiate between physical press and someone turning on via UI?

Refer to the table in the following post:

Request for Generic Thermostat "heater" switch to act as a thermostat physical switch

Here’s how the context object usually behaves depending on who or what was the trigger’s source. Action id parent_id user_id Physical Not Null Null Null Automation Not Null Not Null Null UI Not Null Null Not Null If your tests show that the behavior fails to match any of the combinations in the table, or corresponds to an unexpected combination, then it’s potentially an anomaly and something that might need to be reported. EDIT Corrected typo.