POST + https request in EDGE

I wrote a cloud connected driver once, and hosted it on there is examples and the auth side is really easy. Probably easier than Lua (if you’re starting fresh with Lua)

As for why edge drivers are blocked for internet traffic, I don’t think it’s anything to do with security.

When you step back and think about it, a few things are probably important considerations

  • When Samsung builds the dev tools, apis and device integrations their primary targets are the device manufacturers, not tinkerers. Most of the device manufacturers who have APIs for their devices already, as well as their own oAuth setups and clouds.

  • The massive majority (I think more than 90%+) of smartthings users do not own a hub, therefore cannot run edge drivers - building internet devices on edge (or even encouraging it in anyway) would bar those users from integrating those devices. Cloud connected devices are available to users who do not have a hub.

That’s the way I see it anyway


If you have an always-on computer on your LAN - an existing server or Raspberry Pi, or whatever (Linux/Windows/Mac) - just use my edgebridge app and you can send any requests to anywhere.

EDIT: I should have mentioned that the Lua library on Edge for https does not support a proxy option. The http one does, however. Regardless my edgebridge app handles both since you are sending an http message to it and can tell it to forward an https message. Not something that would be allowed in a production environment by any means, but for home LAN the exposure is pretty low.

Fair enough. The way I see it is that Groovy DTHs had to be used, if not abused, for all devices and in order to facilitate this there was little restriction on what handlers could do. This meant that it was possible to develop purely virtual devices, or to add virtual functionality to physical devices, in ways that weren’t really in keeping with the app/device model.

Now Edge has come along we are seeing that happening in spades, largely encouraged by the prospect of local execution on the hub, and you’d barely know apps existed any more. However the Edge environment is designed for certain hub connected devices and doesn’t provide functionality they don’t obviously need and that is proving limiting.