MQTT bridge and controlling remote devices

Configuration
1

I have an electric smoker at my parents house and i am setting up a meat thermometer that i want to read and do automations with in both instances. Im going to use a NodeMCU together with an NTC thermistor (https://esphome.io/components/sensor/ntc.html) and publish the current temperature as an MQTT message so i get them to my own Home Assistant instance too via abridge connection. I could perhaps get the thermometer to connect directly to my MQTT broker too, but i want them to be able to read it if they are using the smoker without them having access to my HA. Ive bridged the two MQTT brokers in Home Assistant but i don’t know how to get the MQTT devices to show up on the other respective instances in Home Assistant. For now while i am testing and trying to get it to work i have some plugs flashed with Tasmota in both locations, but the bridge is not sending anything over. I can see that it makes a connection though when i check the logs in Home Assistant.

This is what i have in mosquitto.conf:

connection external-bridge  
address ADDRESS:8883  
topic # both 0 
remote_username USERNAME 
remote_password PASSWORD 
bridge_cafile /etc/ssl/certs/ca-certificates.crt 
bridge_insecure true

It connects but then i see no topics in either the brokers from the other one. I am probably doing something wrong but i can’t figure out what and the documentation wasn’t exactly light reading (https://mosquitto.org/man/mosquitto-conf-5.html). Please tell me what to change to get the information to pass over.

2

I apparently forgot to fully configure MQTT on the remote broker, so now it works when i add MQTT local devices to the remote location. One problem though, i can’t turn them on and off. It updates fine, i can see on the remote instance of Home Assistant that i turn a switch off, but i can’t turn the switch off with the remote instance of HA only with the local one. Any ideas why this is? The bridge seems to work fine.

- platform: mqtt
  name: "Fönster kök"
  state_topic: "stat/sonoff-kok/POWER"
  command_topic: "cmnd/sonoff-kok/POWER"
  availability_topic: "tele/sonoff-kok/LWT"
  qos: 1
  payload_on: "ON"
  payload_off: "OFF"
  payload_available: "Online"
  payload_not_available: "Offline"
  retain: true

This is what the switch looks like in both my local and remote instance, and as i said it shows up in the remote instance but i can’t control it there.

3

I solved it on my own. I changed QOS in the bridge connection from 0 to 1 and now it works just fine.