4 ms·
I just wish more of these companies would add support for a locally runnable IFTTT equivalent, or at least something like MQTT support so you can bake your own.
by zyxley 10y ago
I just wish more of these companies would add support for a locally runnable IFTTT equivalent, or at least something like MQTT support so you can bake your own.
- reportingsjr 10y agoThere is startup near me called losant[1] that pretty much does this. Their protocol is basically MQTT with a few small additions so if they /did/ shut down it wouldn't be quite as difficult to get up and running. Unfortunately all of the neat IFTTT style stuff is all on their servers. They don't have nearly as many inputs and ouputs as IFTTT yet, but it is still enough to do some pretty neat stuff. They have also made it really easy to do reasonably secure stuff with your own electronics. [1] Kind of difficult to find, because the just changed their name. http://losant.com http://losant.com
- tdicola 10y agoLook at running OpenWRT on a cheapo consumer router (I use a TP-Link router, but nowadays TP-Link is being stupid and shutting down the ability to load custom firmware so avoid them). You can install all kinds of packages like mosquitto MQTT server.
- crymer11 10y agoHuginn[0] support would be fantastic, but MQTT would definitely suffice. 0 - https://github.com/cantino/huginn https://github.com/cantino/huginn
- googlryas 10y agoYeah - I bought some belkin wemo devices, thinking that I could use their "smart" light switch to control an outlet on the other side of the room which it wasn't wired for. It ended up working, but because the comms had to go through IFTTT servers, the lag was something like 10-15 seconds, which is awful when you want to just turn on a light.
- nl 10y agoThe Wemo mobile app works on the local network and doesn't require IFTTT (?)
- kefka 10y agoAbsolutely true. MQTT exists, as does CoAP and AMQP. There's also simple JSON blobs that can be emitted under an API. None of these things are hard... ... But they do free you from the company. And these days, ball-and-chaining you to their servers is the big "In" thing to do. Now for me, I'm a big fan of Node-Red. It's best described as a IFTTT for your machine/network. Runs locally, and just works. I also use PageNodes, a client-only modification of Node-Red. You can use it here: http://ipfs.io/ipfs/QmSCrZUPkqH4gsncsD7tGXPiFpymsbwmywsHXLDhBtSQ6T/ http://ipfs.io/ipfs/QmSCrZUPkqH4gsncsD7tGXPiFpymsbwmywsHXLDh... (It's an IPFS link, and is on the permanent web. That link will always work as long as machines are hosting it.) EDIT: Really? Multiple -1's for a valid criticism of "companies want you locked in to their network"? We just got done with Google killing off a whole platform because of extensive tie-in to 'cloud servers'. I'm just giving a converse answer how to approach the problem.
- imglorp 10y agoCheck out http://nodered.org/ http://nodered.org/