You wrote that you "plan on making sure everyone gets updated with a custom higher level protocol.".I looked at mqtt.
It seems with MQTT I would need a server AKA "broker". Since everything I want to do is on a LAN, I think it would add complications and maybe a single point of failure with that broker.
Is there a benefit I may have missed?
That protocol could be MQTT.
You do need a broker, but that could be running on one of the devices on the LAN. It is a single point of failure, but so is the LAN itself.
If you are doing something entirely peer-to-peer without any infrastructure then, yes, relying on a server somewhere is not what you want. But at some point you have to put a limit on exactly how much redundancy you're going to need "just in case" something fails. This amount of development is going to vary hugely between controlling a light bulb in your home, and controlling emergency lighting on an airport runway, for example.
You might also be developing this for fun, which is an excellent reason. But if you want to use this system for anything you might want to adapt something that already works.
Statistics: Posted by ame — Tue May 13, 2025 9:49 pm