8

Typically, files are uploaded using a HTTP POST from a web form (I assume that's what you're thinking of when you say file upload). The exact format of the request tends to look a bit like this, as defined in RFC 1867. The ESP8266 has an Arduino library, which contains a module called ESP8266HTTPClient. There's a basic example available here, to help get ...


7

I'm not sure MQTT would really fit your needs well. MQTT has the concept of 'retained messages', kept by the server and sent to clients as soon as they connect. But you can only have one retained message for each topic; not a queue of messages. If the client is connected to the broker, you can send packets in order and the order is generally preserved (in ...


5

a service provider [...] (at minimum cost)? [...] something like Spotify Well actually there are plenty of providers "like" Spotify (depending on the definition of "likeness") and predating Spotify by decades: Internet radio stations, e.g.: http://www.radiocaroline.co.uk SHOUTcast alone has 20k+ stations. Find an extended list of providers on Wikipedia (...


5

MQTT should be more than fast enough for your architecture, given a decent WiFi network. I run about 30 sensors (ESP8266, Feather MO, Arduino Uno, etc.) all using MQTT back to a Mosquitto Broker running as a Docker Container on an 15yo laptop, which connects back out to my control software and displays, and it all works just fine. I'm pushing close to 2 ...


5

From what you're asking, I believe you should use MQTT protocol, it seems to fit your architecture. You'll need to have a mqtt server/broker that will receive the data from the device and then send them to the app. Simply put in MQTT protocol you'd have "topics" that the client (your app) will subscribe to. The device will push it's data to the topic and ...


4

It looks like a pretty standard Bluetooth Low Energy (BLE) device so assuming the manufacturer hasn't done something strange (e.g. like fitbit) then you should be able to use any language that has BLE GATT support to connect to the device and then subscribe to the characteristics for each of the different data fields. For NodeJS there is the noble which is ...


4

I agree to Aurora's answer—there may be better solutions to implement queue instead of MQTT, but still in MQTT it is absolutely possible. You need MQTT broker and clean=false (in MQTT 3.x) or with appropriate expiration period (MQTT 5.0). Then, the logic is pretty straightforward. You have persistent(but not connected) client session, that is subscribed ...


2

Yes, and since Kylo is based on top off Apache NiFi, you can start with NiFi documentation. Great starting point for Apache NiFi can be Apache NiFi Videos and video Build a Simple Flow - Part1 Good references are Apache NiFi JIRA pages. All what you have to do in first step is to create three(3) basic processor objects: 1) Receiving yours sensor data ...


2

May be a bit biased here, since I've worked with this technology a fair amount and enjoyed it, but I'd go with a Raspberry Pi, personally probably the Raspberry Pi 3. The board will cost ~$30, plus a microSD (unless you opt for a network boot which would save you that cost). Audio input will be possible through USB. Bluetooth, WiFi, and ethernet are all ...


1

This really depends on how the camera manufacture has set things up, but it will not go via the Google Assistant device (in this case the speaker). Google Assistant Camera support works in much the same way as any other Chromecast video stream. This means that Google Assistant will send 2 URLs to the TV. The first is to the viewer application. This is ...


1

Sorry, this is too long for a comment, and there is the beginning of an answer in it, especially if I get more info from the OP. Can you define "cheap"? Sub $5? $10? $120? $50? And, what does "Arduino input" mean? Pin comparability? Code comparability? sing he Arduino IDE? For instance, ESP32 comes with BT & WiFI out of the box, and is certainly ...


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