MQTT Transport issue service discovery

[brad-decker]

Having an issue with service discovery on MQTT, probably just a user error but i'd appreciate some guidance.

const Moleculer = require('moleculer');

const { ServiceBroker, Transporters: { MQTT: MqttTransport } } = Moleculer;

const transporter = new MqttTransport('mqtt://localhost:1883');

const broker = new ServiceBroker({
  logger: console,
  transporter,
});

broker.createService({
  name: 'engagedAction',
  actions: {
    create() {
      return 'hello world';
    },
  },
});

broker.start().then(() => broker.call('engagedAction.create')).then(r => console.log(r));

I run this then I switch to terminal where I create an identical ServiceBroker and call $node.services and the service from the other node is never there. I have confirmed that both nodes are connected to my MQTT service and i can see messages posting in the backend. Any thoughts on the step i'm missing?

[brad-decker]

Answered my own question. The node name was the same on both clients so it screwed up the service discovery most likely thinking it should only have to look internally or something. I changed the nodeID on one service and it worked.