#Tag Scan automation inconsistent

1 messages · Page 1 of 1 (latest)

midnight pasture Oct 17, 2025, 3:22 PM

Hello! Until today, all of the nfc tag scan automations have worked as if by magic flawlessly. Today I am getting inconsistent results and am not sure how to troubleshoot it.

When I get a successful tag scan, there is a correlating trace available in the automation config. In the cases where it fails, there is also no trace. I've downloaded the logs from the mobile device and I see tag_scan events when it's successful, but I don't see anything when it's not successful. When it's not successful, I see a wait symbol on the screen for about 15 seconds and then it disappears, but the automation doesn't run.

How do I debug this? I see 503 error in the client logs that might be related?

midnight pasture Oct 17, 2025, 3:43 PM

I looked into it some more and the client is littered with 503 errors for webhook failures.

I am able to load the app, though (and see my HA dashboard, make changes, etc) when this happens, so I know things aren't hard down.

If A webhook request goes to Nabu Casa, but isn't forwarded into my HA instance, how could I tell that? I don't see any way to get any logs from the Nabu Casa dashboard or anything. Is it possible to detect the condition where webhooks aren't reaching HA? I guess I could setup a prober or something to test them every minute or something? I'm kind of at a loss here. This automation is pretty important.

Should I assume it's nabu casa availability? I tried a different webhook and it also is going through inconsistently.