I have played with the ESP8266 modules before..
- captive portals (mostly used as GUI's to control/interact with the connect project
- reach out and dump data to some custom PHP script (hosted on my own domain/server)..
but I have never used any of these IoT 'services' to be honest.
I keep seeing the 'buzz word' MQTT.. etc..etc.. yadda yadda..
but I'm having troubling grasping some things about it.. and am hoping some conversation clears things up for me.
I understand that MQTT is a publish/subscribe messaging protocol...
but is this a constantly connected/polling type of connection? So you are always using bandwidth, needing to be connected to be able to 'get' the response/pushed data..... is this correct?
What is the difference between this and having some script on the internet and you request every so often?
- I read this MQTT protocol was designed to be lightweight... but with todays bandwidth/connections is that an issue any more? (maybe with multiples or professional grade stuff?)
** I read it also has more offerings like LWT (Last Will and Testament) messages? So seems a bit more robust than a simple script that gets polled every so often.
Lastly.. is it possible to set-up/install your own MQTT server?
I see things like Mosquito and mqtt-server... but have read much about them yet.
Maybe possible to install ona home computer/server that gets opened up to the internet via router access or something? but what about shared domain hosting? (and thoughts/feedback on that?)
I even saw some articles about installing it on a RaspPI??? (that would be fun first RaspPi project for me IMO!)