New answers tagged

0

Google Cloud Platform is much more than a simple MQTT broker. It is an eco-system with a lot of cloud services. It has an IoT Core which supports MQTT as connection protocol. There are many resource about how to setup it as a broker. Here is one for example: Steps to Install MQTT Broker on Google Cloud. As for the other part of the question. Here is a Paho ...


0

Although I have accepted @hardillb answer. But I am writing this answer to share the another approach that I came across when researching around this. Ok so idea is to use IP Broadcasting. So what I have done is, my edge device is continuously emitting an UDP messages over broadcast IP that contains the itself IP. The micro-controller ESP listen to UDP ...


6

The correct response to this is DNS with different versions for LAN and public Internet. For finding devices on the local network you want to use the mDNS (also known as Avahi or Bonjour) and you want to publish your broker using the _mqtt._tcp service. Setting up Avahi on the Raspberry pi to publish the service is relatively simple, and there are mDNS ...


3

Here's one way: The actual business logic of your system would have a certain API. That API needs to have some doXYZ methods, some getXYZ methods and some events of onXYZ. What I'm assuming you're asking is "How do I make this available via MQTT and via HTTP based transports?" If you were doing something in the cloud, I would say take a look at ...


1

One thing that could have helped someone answer was the info on what the situation was when you saw no data. i.e, was the Arduino still functioning (i.e, perhaps you had code that blinked the LED and that was still working) ? Was the modem still functioning (i.e, was still responding to the Arduino) ? Some areas to look into: Find a way to troubleshoot it. ...


1

Your publishing code needs to run the client loop as well otherwise it will only send 1 TCP/IP packet which will limit the sending size to what ever the MTU is on the network. Adding the same timed period with the client loop running will work, but a better solution would be to use the single shot wrappers included in the Paho library that will ensure that ...


2

DDOS protection should be at the network level, not in the application. By the time it's made it down the TCP/IP stack to the application, it's too late and your machine is already on it's knees


Top 50 recent answers are included