Greetings all, sorry for a potential repeat question (trying to catch up with all what has changed but failed to find full confirmation, beyond a potential similar Q 19d ago but with no answer).
For my sanity due to ST shuting out webCore. Does this mean there’s no longer a way to create a simple HTTP request trigger for instance a light to blink a few times? While I have a few similar ones, the most basic and important to me is a lamp blinking when certain criterias are met in a web app (this was triggered with a simple CURL turning a lamp connected to ST on of a few times).
Is there any alternative way to do this with some free integration. I found the keyword “http request” in relation tto Sharptools, but as a paid feature… and I had hoped to have some alternatives to consider (as a non coding, tech person).
3) Use your own server to handle requests to/from the internet
But if you’re trying to connect via the internet, and you don’t want to use any outside services, you need to first communicate to an always-on server device in your own home, then have that handle the webhooks. So this method requires both a hub and a server device. It’s doable, and a community developer has created a project called edgebridge you can use to do that, but obviously it’s much more technically complicated than SharpTools and has its own costs.
Hubitat, a competing hub brand to smartthings, has now added Webcore as part of its primary features, and there are some community members here who have created code that will let you communicate between a smartthings account and a hubitat hub, typically creating proxy virtual devices, so that means you can run webcore on hubitat, and have it act on devices connected to smartthings.
Hubitat runs almost everything locally, and does use groovy, but it usually requires more technical expertise to set up than smartthings. And while it has an app, it’s not as polished: some people use Sharptools as the family interface to hubitat for that reason.
Anyway, this method does require buying hubitat hub and setting it up and getting it running, as well as setting up the custom code on the smartthings side so that you can talk to each other. It’s more expensive and more work than just paying the sharptools license, but there are people who had a really big investment of time and energy in webcore who decided to go that direction. Choice is good.
There are a couple different projects to do this. Hubithings Replica does not require a SmartThings/Aeotec hub if you don’t have one already. So it’s a good choice for people who are using webcore to manage Wi-Fi and cloud integration devices. And it offers a two-way integration.
Mira does require a smartthings/Aeotec hub, but then the good news is that the integration between the two hubs is fully local.
You could also use MQTT to communicate between the two, but that’s technically the most complex in this category, and probably only makes sense if you’re already running an MQTT broker. So I mention it for completeness, but I don’t think it sounds like something you yourself would be interested in.
5) IFTTT does have webhook processing as part of its free tier
Normally, I would probably have listed this first, but the integration was recently rewritten to work with the new architecture and it was a little flaky to start with. So I’m not even 100% sure that it’s working right now, although the company does intend that it will.
Also, each free account is limited to 3 rules and I don’t know if that’s enough for your use case.
Technically, IFTTT on the free tier is, if anything, a little easier to use than webcore, and does not require a smartthings hub or another device. But it also is a much simpler rules engine, unless you pay for the subscription.
I think it’s definitely worth looking at, but, like I said, I don’t even know if it’s actually working right now.
So there are several options for the new architecture, but free and easy may be harder to accomplish unless the Ifttt integration is working and can handle the details of what you want to do.
Using the term “one way integration” is not exactly correct.
It’s designed to share real or virtual devices that exist in Hubitat with ST by creating mirrored virtuals on the ST side. The integration and communication is bidirectional for those devices, a state change on either side will update the other.
What’s “one way” is that it’s not designed to share real ST devices back to HE (however you can work around this too). But usually when one discusses “ways” or unidirectional/bidirectional they mean the communication or replication of state, which Mira does in both directions.
Thanks for a lot of information, I have a ST v3 hub for reference. So I see I need to look into a few options, maybe check IFTTT if they have updated and what I need is on the free path. It’s external website http request to a LAN local IP, so Webhook Edge Driver seem to be too advanced if I then first need a server to handle things between local LAN (the SST device) and the internet.
The suggested approach to the restful ST API is also worth a look I guess if I can figure out stuff as partly a non-coder.