Did you try this out with the Bond Bridge and get it to work?
Yes. I am testing out a pre-release version of the driver, but it does work. There is still a good amount of setup since it isnāt a dedicated driver though
Iām on Android using Bond firmware v2.29.7-Beta running local wifi.
If your doing some tests, Iād love for you to keep me in mind.
A Web Requestor driver update has been pushed out that expands the usefulness of the driver by allowing users to provide HTTP ābodyā data in their configured web requests. This is useful wherever you need to send additional data such as json, xml, or other text along with the HTTP request URI and endpoint.
The way this is implemented is in device settings for the first 5 configurable HTTP requests, there is a companion setting field where you can provide the optional body data. If 5 requests are not sufficient for your needs, you can always create more web requestor devices!
Some other changes made in this driver update:
- added option to use a PUT method for configured web requests
- code changes to reduce the number of extra entries in history caused by resetting/blanking out device detail screen fields when executing a web request
- limited the displayed response data to 1024 characters ; this is to prevent any SmartThings app glitches that have been shown to happen when large http responses are received. Although the response field in the device details screen tends to cut off the data shown, you can usually see the first 1024 characters in device history. Note that the response data attribute will still have the entire returned data for access from Rules or SmartApps.
Note: HTTP bodies and PUT methods are not supported for on-the-fly requests sent as arguments from routines or Rules.
Once this driver has been updated on your hub; confirmed by checking for driver version:
2022-02-01T18:50:15.503557
ā¦you should see the new optional body fields available in device settings. If you donāt, try creating a new web requestor device.
Thanks to @blueyetisoftware for the original request and testing!
3 Likes
Thank you! This driver has been awesome for experimentation with the many LAN connected devices that have REST apis.
1 Like
Awesome stuff!!
Curious if anyone is using this driver to control LIFX lights locally? I know there is a LIFX LAN protocol but still trying to wrap my head around it.
I think my hub doesnāt like this update. Iām using this to send a webhook into my local Home Assistant instance whenever the SmartThings more changes. I didnāt get my usual notification this morning, so I went investigating.
Trying to execute a web request just results in the spinning circles and eventually a generic network error. It was last working as of 11:01pm Eastern time last night.
Iām sorry youāre having trouble. Can you try creating another web requestor device? That will tell us if the driver is even (re) installed and functioning.
Creating a new device worked. I also tried rebooting the hub, and that got my original device working as well. Thanks for the assistance!
Glad youāre back up and running! Sometimes these driver updates have hiccups.
A driver update has just been pushed out to fix a problem that would have caused the driver to stop working with the upcoming hub firmware update.
Driver Version 2022-05-13T17:50:11.90298
No further action needed, and no change will be apparent to users.
2 Likes
Hey Todd,
I should have noticed this sooner - but this stopped working for me with this update. Iām using this to send webhooks to my local Home Assistant instance, but since this update it has been showing **Failed for the HTTP Response Code.
The URLs Iām using are HTTPS, to a local IP, on a non-standard port (8123).
Please let me know if there are any other details I can provide to help troubleshoot. Thanks!
1 Like
Hi. Iām aware of an HTTPS bug in Edge so this might be a result. Iām out of town for a couple more days but will get on it when I return. Iām sorry for the inconvenience.
2 Likes
I managed to get https working on v43. Let me know if you need a hand with it
3 Likes
Hi - I havenāt been able to reproduce the issue yet, but can you please confirm what level firmware you have on your hub?
Thanks.
My hub is in the beta (although I donāt remember if there is currently a beta firmware out there or if itās in production right now) but Iām on firmware 43.4.
1 Like
Are you able to capture logs with the CLI?
Assuming the command to capture logs is similar to what it was a few months back, yes I can pull that tonight when I get home from work.
1 Like
I went to test this out and pull some logs - but it seems to have started working again after I fired off a handful of tests, go figure. Seems as though the driver was maybe just stuck or something. Anyways, thanks for taking the time to try and replicate this!
Weird! But glad itās working now. If it happens again, fire up the logging to try and capture whatās going on.