In very unstratified with my current MQTT setup.
I often encounter problems with all or parts of my Zigbee devices becoming unavailable.
While I’m not entirely sure if it’s the MQTT server, the zigbee2mqtt software or my SLZB-06, I want to troubleshoot everything after the other. My mosquito instance is a very old docker container and it doesn’t get any updates anymore. So I want to replace that first.
Is it possible to just setup another container with a better version in the same IP address (after taking the old one offline of course) and with the same user/password combination without any further actions needed?
I’d assume that both zigbee2mqtt and all other devices using MQTT (tasmota plugs, Nuki locks and so on) will just use the new server to publish their messages and read their topics. But is this true or will I have to reconfigure anything else or will I lose history in HA or anywhere else?
Sorry, I may have phrased the question wrong. It’s less about the possibility of setting up a new container on the same IP (I know how to do that ;)) and more about the implication of doing so.
I’m not sure if I have to reconfigure all devices and other software (z2m, HA and so on) to work with that new MQTT container. Maybe because the newer software will miss any past messages, or anything like that.
I’m afraid of losing any relevant history. Primarily historic data of entities in HA. I’ve had bad experiences with things like that happening in the energy dashboard, for example.
IMHO, chances of the MQTT broker being the problem in a Z2M setup are very low.
I think it’s equiv to blaming the envelope if your letter doesn’t arrive at it’s intended destination.
Just one caveat: everything that was published to your old MQTT server with a “retain” flag will be lost and would need to be re-published to the new server.
It also stores retained messages, and therein lies the caveat.