PJON VS async-mqtt-client

One idea I've been toying wit (but don't have the skills to implement) is a standard for hardware that's a bit more verbose than things like i2c or serial. I'd like one connector I can plug into a piece of hardware (a sensor, a servo, a keypad, etc) and have it just work. The protocol would have to be a bit more complicated, maybe something like PJON^1, and you'd need to deliver power at a few different voltages.

I've been calling it kitbash in my head, just throw a bunch of components together in various topologies and you're good to go. Considering you can get a very cheap microcontroller for something like 40 cents I can definitely see the appeal of adding a "kitbash port" to various pieces of hardware, even if it means adding a whole new microcontroller.

1: https://github.com/gioblu/PJON

When the physical layer of devices in the home don’t offer Wireless connectivity, hardware communication modules needs to be adopted to bridge the existing connectivity.

This protocol exists already is called PJON: https://github.com/gioblu/PJON

Until it ultimately relies on Amazon S3 and a commercial network provider this stuff looks rather useless. I hope IPFS will someday run on top of protocols like PJON ( https://github.com/gioblu/PJON ). Decentralization and democratization of networking will happen from the lower end, when the network infrastructure will be ours, and we will not be forced to pay multiple corporations to temporarily store our data or get it from one end to the other. We should build our own global, private network infrastructure and use it for free without the need of an ID or a contract. On top of this sort of infrastructure something like IPFS may have sense.

PJON supports mesh networking too, it is open-source and free to use, check it out: https://github.com/gioblu/PJON

its address space may be beneficial (more flexible, lower overhead) for many use cases.

Bitcoin should run over a network protocol like PJON https://github.com/gioblu/PJON and a private network infrastructure made by people.

Protocol specification: https://github.com/gioblu/PJON/blob/13.0/src/strategies/Soft...

Really cool thanks for the link. I have experimented a lot with the OOK modulation and optical communication described in the paper using just visible light LEDs as detectors and small laser diodes. A free-space optical link can be built in minutes, see https://github.com/gioblu/PJON/tree/master/src/strategies/An...

It should use PJON for communication: https://github.com/gioblu/PJON

So looking at the docs from the library you mentioned, in the limitations section it mentions that TLS 1.2 is not supported. That is definitely required for connecting to AWS IoT Core.

Good insight! Thanks for digging into the embedded code. Indeed, the library from which async-mqtt-client was forked has an outstanding issue to add wsMQTT support.

Most definitely! I'm using https://github.com/marvinroger/async-mqtt-client this to connect all my esps to a shared message bus.

#include

https://github.com/marvinroger/async-mqtt-client/blob/master/src/AsyncMqttClient.hpp onMqttPublish() is a callback of type OnPublishUserCallback.

Ah. In practice mqtt is lightweight enough of a protocol that it should rarely block long enough to hide a button press. But https://github.com/marvinroger/async-mqtt-client might be what you're looking for.