6

A couple of options off the top of my head. Sonoff kit, can be flashed with open source firmware that allows control via MQTT/HTTP. While not sockets directly adding it into the cable is not hard. The Sonoff Pow does control and power monitoring. Belkin's WeMo sockets use SOAP messages and uPnP which is self describing (you can see my notes on working out ...


5

Looks like flespi is the way to go in your case. You may use flespi http channel to upload data in http with CURL (or alternatively use mqtt channel). The data you upload should be in format like: curl -X POST http://X.Y.Z.W:P/ -d {"ident":"123","humidity":51.00}, where ident is unique identifier for your sensor. Also you may pass "timestamp" with time of ...


5

If you already have curl to do the download there should be no reason not to use it to do a POST to push the data to another service. So you need to search for HTTP APIs for any provider you want to use. e.g. It's been a long time since I used it (back when they were called Pachube) but Xively have a HTTP POST API (https://developer.xively.com/docs/...


4

If you want to use a RESTlike Environment, you can setup: PHP CodeIgniter + MariaDB But you need to reconsider your requirements. Using REST over HTTP may require the use of intermediate techniques and a webservice based implementation. If you are planning a real-time application, it would be better to use a telemetry messaging protocol, as MQTT. In our IoT ...


4

Never let "anyone" add stuff via MQTT to a database ;) Once bad data gets into the database, any results from your analysis programs will be skewed at best, or down right wrong at worse. Any time you have MQTT traffic coming from "outside", you want to have a few things in place: DDoS protection so someone can't swamp your database, Topic Validation...is ...


4

There should be no need to use Authentication via HTTP first for MQTT devices. MQTT supports Authentication which can be linked to ACLs to control what topics a given user/device can publish/subscribe to. Authentication can be user/password at the MQTT protocol level or TLS certificate based the transport level. Most brokers support wildcard (and variable ...


3

Check out Wifiplug.co.uk they provide the hardware and open API for 3 pin plug (UK, ASIA etc) API here: Developer.wifiplug.co.uk Free API for hobbyists - excellent suppport too.


3

A roundabout answer. As per info at bottom of this answer, you get charged by a number of messages written, not by number of times someone reads the data. That means you can experiment with multiple GET requests without having to worry about a cost, so run your script and see what happens. NOTE: make sure that your script does not write any messages Here is ...


3

Most consumer IoT devices do not use port forwarding, they connect out to a central cloud based Command/Control server. This is for several reasons: Port forwarding limits the number of devices that can be deployed Port forwarding either requires the owner to be technically capable of enabling it or UPnP to be enabled on the router to open ports. Port ...


3

As per SIM800 AT command Manual, you can set HTTPParamTag to USERDATA and send content in HTTPParamValue. You can pack all key-value pairs into HTTPParamValue and parse to retrieve individual key-value pairs.


3

AWS IoT uses the MQTT protocol (and AWS APIs), not REST. There are two ways to solve your problem: Convert everything to MQTT: Have your web app send a message to AWS IoT (Luckily, they support websockets for just this purpose), and use the AWS mobile SDK to make your mobile app speak MQTT. If you need your components to be RESTful, then you should forget ...


2

If you do not want to bother with broker yourself and embed any authentication scheme inside it I have solution for you (non commercial, e.g. it is free): Per each instance of your small IoT platform you need to have separate flespi.io account(we call it customer). Your platform will have in configuration one flespi supertoken (for accessing flespi.io) and ...


2

Most smart plugs use cloud providers to toggle the power state of the device, there are a few (big) issues with this: If your internet is down you can't use it, even if you are on the same network. (And probably the biggest) data security, what data are these cloud servers able to access, what do they do with the data, what happens if they get hacked, what ...


2

After struggling to find smart plugs with an open API, I found a stable workaround that can work for a lot of personal projects. I noticed that a lot of smart plugs have an IFTTT service, from which you can query the different functionalities. As you can interact with IFTTT in a lot of different ways (mail, webhook, etc.), this could allow to create quite ...


1

Assuming the van as an ODB-2 port (most do) then you can just grab something like this. This assumes that you need something that reports in real-time, since you'd have to pay for a data plan. That one has an app so there must be some kind of api that it is reporting to; that system may have an open api you could leverage. Even if it doesn't, this one also ...


1

Firstly, how are you going to power your device? If you have a modern radio, or even a cigarette lighter USB adapter, then you can easily power an EDSP32, Raspberry Pi Zero W, BBC:Microbit, Arduino, etc. All of those could get the job done – with, in some cases, additionally Hat/Shields, so choose one that you are familiar with. I need to determine when a ...


1

May be it is simpler to use MQTT Broker that supports REST API by its nature? Like flespi broker which contain secure and private MQTT namespace, free to use and actively used by some home automations systems. The REST API for messages publishing is described here.


Only top voted, non community-wiki answers of a minimum length are eligible