It isn't I want to be annoying in what I am saying.
(The long story)
Raspberry Pi Model B Rev 2
PRETTY_NAME="Raspbian GNU/Linux 9 (stretch)"
Raspberry Pi reference 2018-03-13
Generated using pi-gen, https://github.com/RPi-Distro/pi-gen, 00013d7972122d1304aacda8fff5098f073ceb43, stage5
IP address 192.168.0.99
That is my MQTT Broker
All machines on the network have their
MQTT nodes set to talk to it.
It is Stretch and as much as it is great, the people at RasPi updated the kernel a while back and it killed the ability for the device to be a WAP, which I wanted.
Buster (supposedly) supports WAP and it has become really annoying not having the WAP, so I decided to update.
192.168.0.99 powered down. SD card out. New SD card in with Buster.
Set it up as the same IP address as the old SD card, as basically it is going to be the same machine anyway.
So, with the IP set, I plug in the Cat-5 cable and
sudo apt update and then
sudo apt -y upgrade.
This took about 30 minutes.
During this time machine a sent a message out via MQTT and machine b received most of the command.
Note: Now and then even with the old card that would happen. So as I said: it could be a problem with the node at the end. Not my problem.
I am stating that the MQTT message got through when I did not have a broker machine.
How is this possible?
Or as I keep asking: Does BUSTER come with MQTT pre-installed?
Though that can't be true as my thermometer which also uses MQTT was screaming that it couldn't find the BROKER.