Determine how a switch (Shelly 1) was turned on?

[vaderag]

This might be a really obvious thing I’m missing or it may simply be impossible…
I have a Shelly1 which can be triggered by physical switch or by an automation (or Alexa)

I’d like to take an action based on if it’s physically switched (only) - is there any way to determine this?

Thanks

[parautenbach (Pieter Rautenbach)]

Is it possible to know when physical button is pressed?

Hi, Does anyone know if it’s possible to determine, within a script or automation, if a physical button on a light or switch was pressed? I am trying to find a way to differentiate between a physical button press versus the associated HA light, switch, fan entity being switched on/off from HA. I would like to perform different actions based on physical switch, timer, motion, etc. My devices are wifi Sonoff lights & switches running Tasmota & are configured as manual MQTT entities. Maybe the …

Find out who has triggered

I would love to detect which user has triggered a switch or script. This means, I need to know server side who was logged on and caused the event (for example flipped the switch). This can be used to notify only that user for example, or only users that are actually at home. it seems that the events are missing a user context Has anyone ideas for this?

Know which user triggered UI event

I want to be able to know which user was the one that e.g. changed state of input_boolean toggle and use that info in an automation. Use case: a user “locks” some resources (e.g. lights, switches) for certain period of time or until s/he unlocks them. So when locked, only the user that locked them can change their state etc. How would I go about that? I saw that user_id is populated in UI triggered events {... "context": {... "user_id": "d4dc8..." }} , but context is not available in automatio…

Determine if switch was turned on by human or HA (reliably?)

Hello! First post, n00b to HA! I spent hours trying to figure this out. “SHORT” question: How do I reliably determine that a light-switch toggle was the result of a HA automation? I’ve seen the suggestion to use trigger.to_state.context.parent == none, which works when the light turns on via motion, but it doesn’t work on another automation, where I turn the lights off via a time_pattern & motion check. Inspecting the trace.json, I don’t see anything I can key off of. LONGER explanation: …

Detecting Method Used to Turn on Light

Hi All, Is it possible for HA to detect what method was used to turn on a light? I’d like to trigger an automation if the light switch was turned on manually via the wall vs an automation or user turning it on via the HA Dashboard. Thanks!

[vaderag]

So in summary… “maybe, but probably not”

[parautenbach (Pieter Rautenbach)]

No, there are many answers. You should spend some time reading. The answer is there.

[vaderag]

I think I can take a guess at it actually

Appears that if I use the physical switch on the Shelly1 it doesn’t give a “triggered by” in the device history, so I should be able to use that fact

Sadly this is also the case with using Alexa (although I wonder if I could use a helper instead to track that)

Need to do a bit more reading as I can’t see how I can grab the triggered_by in NodeRed right now, but guessing it’s possible

Edit, looks like grabbing payload.new_state.context.user_id will give me a null value or an encoded UserID for the Shell1 depending on how it’s turned off…

[parautenbach (Pieter Rautenbach)]

Have a look at this: Work with "Triggered by" in automations - #8 by 123.

[vaderag]

Yeah, I looked at that and ran my own tests - my table didn’t match
I never get a ParentID on any route. On automations (at least using my nodeRed setup) they are triggered by Supervisor user
The best I can do is distinguish by user being null or not, null being Alexa or Physical

[123 (Taras)]

@vaderag

(at least using my nodeRed setup) they are triggered by Supervisor user

Correct. Node-Red is external to Home Assistant so whatever work it performs is labeled with the generic reference “Supervisor”.

[parautenbach (Pieter Rautenbach)]

@vaderag

at least using my nodeRed setup

This completely changes the original request. Maybe there’s a way to inject the additional context you need from NR and use that in HA.

[vaderag]

It really doesn’t change the original request at all? The request was to know how the switch was turned on (physical, alexa or automation)
I don’t actually need to know anything about nodeRed (although I do as I noted about)

I have Physical/Alexa or automation, but no way to separate the physical/alexa (although I will sort that out with a helper)

[pdwonline (When a goat is on the net)]

I think there is a kind of solution: If you create template switch that activates the actual switch you can then use the template switch in your automation, but in the l UI, you define the actual switch…

[vaderag]

Yeah, I think that’s the only way at this point, and what I’m planning on doing (with the helper) if I need to - at the moment the physical/Alexa combined knowledge is proving enough