#Input select seems to change without being actually changed on a dashboard or automation.

24 messages · Page 1 of 1 (latest)

warm wigeon
#

I have a long standing issue where now and then an input select I use in automation all of a sudden seems to get changed without a direct cause.

this is the one I cannot explaint:
Arnoud changed to Net Thuis triggered by action Input select: Select
06:19:51 - 6 hours ago - arnoud

a normal one:
Arnoud changed to Thuis triggered by automation Mark person as home triggered by state of Arnoud
06:19:51 - 6 hours ago

How can I debug this issue to find out what caused this?

warm wigeon
#

I have a sneaking suscpicion this might be changed by webhook which I use on my phone for tasker, is there a way to confirm this?

noble mural
#

Have you checked the logbook entries for the input select? If an automation changed it then it should mention that

#

Otherwise you'll have to look through traces for automations that touch that entity

#

But yeah what you're explaining can be a difficult thing to track down

warm wigeon
#

Yeah I posted the logbook entries in the OP

noble mural
#

Do you happen to use node red or anything else that might be changing the entity?

warm wigeon
#

no

noble mural
#

If you suspect the webhook, you could create a temporary automation that also listens to that webhook and post a persistent notification or something to help troubleshoot when it happens

warm wigeon
#

hmm good idea

noble mural
#

Although I don't follow that entirely, because if you suspect the webhook then I would think you already have an automation using the webhook and you should see that automation in the logbook or see its traces. Though I've never used a webhook so not super familiar

warm wigeon
#

yeah my bad, from tasker I access the API with a long lived token, so not a webhook, subtle difference i just learned while searching how to trigger on an api call

noble mural
#

Ah ok. You could look at raw logs for that request and see if it lines up with when the input changes

warm wigeon
#

and looking at the events in event-viewer I can't at all differentiate between an api or a dashboard call. they are exactly the same ( except for the context: id:)

noble mural
#

Yeah maybe something like the user id in the context

warm wigeon
#

user id is the same now, so if I wanted I can make a new user just for tasker

noble mural
#

Though since you generated the token with your user it might be tied to that user id

warm wigeon
#

yeah it's also the same currently

noble mural
#

Yeah good idea. I'd just look at the HA log file first though

#

Do you know how to? It's possible you'll have to change the log level

warm wigeon
#

yeah, I know the raw logs, and indeed I need to change the log level to log somthing on that particular part, I already checked, nothing currently logged on the timestamps I triggered thinks by hand

noble mural
#

Yeah I'd think at least info level but might need to go lower. You can also enable it per integration so less to sift through

warm wigeon
#

I'm pretty conviced it's the API call from tasker that f's it up, so not a HA issue, but something I need to troubleshoot in tasker.

#

as the API calls look 100% the same in the event viewer as if you do it via the dashboard, same as I see in the logbook.