Make a GET Request happening by itself?

#1

I have a piston that will make a GET request when a SmartThings multisensor senses acceleration. It’s calling a URL hosted on a server I control. It works well!

The problem is, the server is receiving these web requests sporadically when the sensor has not been triggered. The multisensor shows no events. My piston with the GET request doesn’t show anything in the logs (which is set to full). The piston did not execute.

I would think something else is triggering this URL but that’s not the case. I wrote the app specifically for this purpose, I require a simple auth token, and the server logs show similar source IP addresses as the ones used when the piston legitimately fires.

Would like to determine if webcore is firing these GET requests on its own.

doorbell piston anonymized
doorbell piston anonymized.png1178×695 38 KB

#2

Can you turn logging to full and post what you get when the GET request gets call when you don’t think it should?

#3

Look in your caches, look at your variables on the receiving system.

I had a remotely similar issue. When announcements were coming out of Tasker and Notifications for Android TV, they were containing old notifications. It does not do me any good when I get “calendar reminder: front door was opened at 3:30pm”. That is not an item from my calendar!

So as the final step in any notification process, I have a notification that contains nulls followed by variable clear statements. That way the assorted variables get blanked out, and then next time the routine fires it can contain only current data.

#4

When I posted this I also made a couple of other changes. I changed my security token - both on the app and on the piston. I updated webcore from the repo (not that I was running anything very old, I think I updated a week ago too.) Either way, it hasn’t recurred since then.

When this was happening though, trace on the piston was set to full and nothing was being logged, which is why I didn’t think the piston was triggering it.

#5

Saw another entry in my logs to trigger my web app, but with the old auth key. Dug further and found the source IP address is part of Google’s crawler ranges. I don’t know how Google got the URL with embedded key in the first place but clearly they see way too much of my browser traffic.

Anyhow, mystery solved and nothing’s wrong with WebCore!