Hi. Are you not able to do this with the options available in automation routines? If not, you might find useful my timer/counter utility driver which could give you some additional ways to trigger an automation - either every n seconds/hours/days/weeks, or based on a simple counter.
Can you elaborate on what you need to do with the response?
The webserver on your ESP8266 would need to be able to accept an additional parameter to invoke the command you want. Or it would need to provide alternate endpoints - one for open, and one for close. Right now itâs just displaying a simple web page with buttons, expecting the user to press one of them from a browser. The web page is in fact being returned to webrequestor, thus the text you see in the response data field. So you know itâs working, but itâs returning a web page which you really canât do anything with in webrequestor.
Is it possible your webserver accepts something like this?
In another thread, Graham suggested this thread to possibly solve my problem with Photon Particle and smartthings (ST). I made a device that uses a Particle to drive a servo that opens a remote HVAC vent in my garage. It used to show up as either on or off in ST. Now it only shows âconnectedâ in ST and will not control the device. The driver is now shown as âLAN Thingâ and I used ti have it set up with a handler in the old ST. It worked for 2 years flawlessly. unfortunately I am not very knowledgeable about how the various software components work together so cannot determine if your driver is a good solution path for my issues. Searched Particle Photon and edge drivers and came up empty handed. Any help is greatly appreciated as the HVAC device I designed was an awesome help in my garage and is now basically useless.
For Alexa integration, youâll need to do it through the creation of some automations, since you wonât be able to control webrequestor directly from Alexa. One way to do it is to create a virtual switch that you can control via Alexa. Then create a couple automation routines: one to execute the specific webrequest for open when the switch is âonâ, and one to execute the specific webrequest for close when the switch is âoffâ. Youâll find that when you define actions in automation routines for a webrequestor device, youâll be able to choose which âslotâ number to execute. The downside of this setup is having to use the terms âonâ and âoffâ with Alexa instead of âopenâ or âcloseâ. There might an alternative to this with using a virtual blind device to address that, which I think can be controlled from Alexa.
A more stream-lined way to do the automations would to use Rules, where you can actually specify the webrequest itself within the rule. See the readme file for more info and an example.
Thatâs usually because something is wrong with the format of the request string. Double check it for correct syntax or post screenshot here so I can take a look.
I think Andriod app is showing things slightly different from what I see in my iOS-based app. Can you check the extra fields you arenât using like Body, More Body, and Headers for both request #1 and #2, and make sure they contain âââ (double dashes)? Iâm seeing âCustom trigger=â in your body field - is that something you typed?
I donât have a Yamaha receiver and donât author any drivers. I was suggesting that the person who wrote Rules to use with this driver to control their Yamaha amp publish those Rules for others to use.
Hi - a have installed the Web Requestor and it appears to be working OK with my SmartThings hub. I am trying to replace a SharpTools routine to play a sound file on a tablet running ActionTiles. The SharpTools string is:
Arguement 1: playSound
Arguement 2: {âurlâ:âfile:///sdcard/download/rooster.mp3â}
I assume I would need to use a web Requestor POST command but how do I structure the URL? The IP is http://192.168.1.xxx:2423
You may need to do a bit more digging to find the expected HTML request format, as that doesnât really tell you anything specific. You need to know how those two arguments are expected. Typically they are going to either provided as arguments in the HTML request something like this: