Association Table Not Populating Topics From Broker

[rcrules]

I am finally in the process of transitioning to HS4 (on a virtual machine). I have decided to start a new installation instead of the migrate in place method.

I installed HS4 and then mcsMQTT v5.16.0.7. I have a working mcsMQTT HS3 system (bare metal) with no known problems. After installing the plugin, and successfully connecting to the broker, the only topics on the Association Table are of the Sub: MQTT/ variety. I have compared the "General" tab settings between the HS3 and HS4 systems and they appear to be setup the same way (minus the machine specific settings).

The debug file didn't contain anything these untrained eyes could see. I'm sure it is something stupid (me perhaps). 😁

[Michael McSharry]

The debug shows that you have a MQTT broker at 192.168.0.4 and mcsMQTT has successfully connected to it. Is there any other client connected to this same broker? It looks like no MQTT traffic exists with this broker.

The MQTT/ topics are the statistics for mcsMQTT operations. The payload column contains the stats and it shows the same thing that the debug shows.

[rcrules]

Hi Michael, thanks for the quick reply!! The broker is on the same machine as HS3. The HS3/mcsMQTT system works correctly with all of the other clients (currently). The new HS4 system doesn't want to play in the sandbox with the other kids, I guess. 😉

[Michael McSharry]

Is the broker at 192.168.0.4 the same broker being used by the other clients.?

I see from the debug that mcsMQTT is subscribing to all (#) topics from this broker, yet no message was communicated from this broker to mcsMQTT. Could you have a Client ID problem where the broker is sending the messages to the wrong mcsMQTT client?

[rcrules]

I'm starting think I can't do what I'm trying to do. I am trying to run two discrete Homeseer systems while controlling the same sonoff/etc devices with one broker. I don't know if the attached "Rube Goldberg" diagram helps. 😜

[Michael McSharry]

This looks like a reasonable configuration. The HS3 computer is setup to use the internal broker. I assume the HS3 computer is seeing things being updated in its Association table. What seem to be happening is the HS3 mcsMQTT internal broker does not recognize the HS4 mcsMQTT as a client. Note that HS4 statistics shows it did publish a LWT topic. Is this topic visible in the HS3 Association table?

It has been a long time since I used VM and never tried it for MQTT traffic. I would think that if a connection is being made then it is not a network issue. It just seems the subscription from HS4 is not being recognized.

[rcrules]

Note that HS4 statistics shows it did publish a LWT topic. Is this topic visible in the HS3 Association table?

Yes, it does show the HS4 LWT in the HS3 Association Table. 🤔

[rcrules]

I shutdown the HS4 virtual machine never to be started again. I shutdown HS3 and installed HS4 onto the same machine as HS3 (NUC). I started up HS4 on the NUC (using the co-located EMQx broker) with nothing but MQTT/ topics in the Association table (aka the same results).

I shutdown the EMQx broker. In HS4 I made the MQTT server 127.0.0.1 which lit up mcsMQTT's internal broker. On the Association table it connected to the internal broker but (the same results).

I shutdown HS4 never to be started again. 😁 Started HS3. I made the MQTT server 127.0.0.1 which lit up mcsMQTT's internal broker. Everything works normally.

[rcrules]

Thanks for the plug-ins and all the support you put into it!! HS4 is going back to sleep for a few more months.