You may need to create a new device, but not change the driver. Will let you know for sure.
OK - I have about 50 devices to create and configure with the correct topics and messages so Iâd better wait or Iâll have to recreate them all.
I am trying to move from Hubitat Rules Engine to Web Requestor on Smarttthings to make a local POST call.
In Hubitat Rules Engine, I have the following:
Send POST to: http://192.168.0.147:5000/api/v1/alarmdecoder/send?apikey=WOGUYPJL2JAA -->(json) body: {
âkeysâ: âaâ
}
I can make a successful call using curl formatted as follows:
curl -H âContent-Type: application/jsonâ -X POST -d â{âkeysâ:âaâ}â âhttp://192.168.0.147:5000/api/v1/alarmdecoder/send?apikey=WOGUYPJL2JAAâ
I created what I thought was the equivalent in Web Requester (see attached screenshot) but when I execute the Request, I get an HTTP Response code of 422. One thing I notice is that the word keys seemingly gets capitalized to Keys in the main Settings screen. However, when I actually try and edit the body, the word keys is not capitalized (See screenshot).
Hoping someone can get me some guidance of what I might be doing wrong.
When on the device settings screen it is true that it wants to capitalize the first character of every field value. Thatâs a quirk of the SmartThings app. But this is done only for display, so you can ignore it. Just be sure that while you are actually editing the field, that the punctuation is as you want.
It is possible that the device you are communicating with wants to see a Content-type header included in the message, so try adding that to the request Headers field:
Content-type=application/json
(curl is probably automatically adding that for you)
That was it! I appreciate the help!
Love the driver. It would be nice if I could give custom names to the requests. For example, âHarmony TV Offâ instead of âWeb Request #1â.
It says you donât have a hub to install the driver toâunless you have a hub, you wonât be able to proceed.
Question to extracting keys/values from external source using this driver.
Any way I can get the value of âlevelâ key extracted using "Response key to extract".
Source looks like this:
[
{
"id": "KRJP",
"level": "3",
},
{
"level": "3",
"time": "2024-07-28 19:58:02",
}
]
Checking if I can use this driver to get data on high water level from a river next to my parents.
Tried already [0].level etc.
Will it work or is the source in totally bad format?
Has anyone using the Web Requestor Multi v 1.2 ever had an issue where requests 6 and above all have a delay of around 6 seconds before they fire? Am I missing something? First 5 have no delays. I love this driver @TAustin! Just trying to figure out this lag.
Thanks!
Hi @TAustin,
I have a specific use case where I need to handle 2000-3000 characters response.
I have a bunch of sensors based on EspEasy that I currently use with HomeAssistant. I want to use the sensors with smart things. EspEasy exposes data in json format. I thought about reading the json data from EspEasy, but the json size is up to 3000 characters, and the driver limit is 1024.
A question and an idea;
Is there a hard limit for response size, where you experienced issues with the driver?
Maybe it would be an idea to create an alternative version of the driver that could handle larger responses. For 95% users the standard, stable driver would be fine. For some users (like me), the alternative, use-at-your-own-risk driver would do the trick.
Does it make sense?
Thanks
Lech
Todd has not been active in this forum since April and is not actively doing development with ST at this point in time.
That is super sad, I hope everything is good with him. His efforts and awesome development rescued me from getting lost in the smart home scene. I guess that things will eventually break with no further fixes or fine tuning 
I understand Todd is no longer active here but was hoping some âlurkerâ may be able to point me in the right direction. Iâve had this running since inception without a hitch. I had to rebuild my router recently and this app stopped working. Itâs been so long since initial setup I donât recall if any settings to the router were required. All requests are on the LAN, same box actually, but no joy. Anyone have any thoughts?
Thanks,
Rick
Hi @raisingskell As the de facto boss of Web Requestor now, I can say thereâs no settings in the router to change. It should just work. Itâs working for me still. The usual advice applies, turn on/off, reinstall etc good luck!
Hi Alwas, Thanks for the quick reply. Thatâs what I was afraid of. Too many lengthy Web Requests. Good opportunity to convert them to Rules. Thanks.
Hi. Is it possible to adapt this driver to act as a Locker from my Hikvision Doorbell DS-KV6113-WPE1(B)?
It uses HTTP PUT to send commands to Open door though its internal relay.
The URL is: http://admin:[PASSWORD]@[IP-ADDRESS]/ISAPI/AccessControl/RemoteControl/door/1
I need to send a PUT to <RemoteControlDoor><cmd>open</cmd></RemoteControlDoor> to unlock the door.
Hi @vctgomes Unfortunately thereâs no more adapting of this driver as the original author is not in the community anymore, and we donât have anyone left with the requisite technical skills to be able to modify it, so itâs only workarounds from now on.
I havenât used that driver but it seems to support PUT in some places like the pre-configured web requests, check the github GitHub - toddaustin07/webrequestor: Web Requestor Edge Driver , you just need to prefix âPUT:â to the address, like âPUT:http://âŚâ.
I guess you can create one of those preconfigured addresses and just invoke it without having to modify the driver.
Hey all, Iâve been using this driver for a while now⌠but have a new device to trigger with a url, but I cannot get the url to be accepted⌠every time, it just says âNot configuredâ, does any of you out there have any idea how I can get this accepted?
http://10.0.1.117/bha-api/open-door.cgi?r=ghcbby@1&username=ghbhytk0002&password=6Hldd69YS
Iâve tried alternatives like:
http://ghbhytk0002:6Hldd69YS@10.0.1.117/bha-api/open-door.cgi?r=ghcbby@1