MQTT crashes and restarts when topic received

[Timon]

Actually even when I used auto.local it still seems to pickup the loopback address. I think the reason is that I don't have a local DNS server so the IP address is picked up using bonjour. Bonjour will tend to do that when you reference yourself.

The one thing I haven't tried is having mcsMQTT build a whole new device whenever it sees a new topic so I may give that a try.

I may just remove mcsMQTT completely then reinstall just incase something else might have gotten damages if I don't find anything else.

[Pete]

Not sure if it would matter to use the loop back address (127.0.0.1) or the actual IP of the Mosquitto server; but you could give it a try maybe?

Thinking here put the Mosquitto server on my HS3 Pro Linux box and internally using the Loopback and externally using the actual IP of the server. Noticed too that the docker stuff uses another IP internally...

[Timon]

Ok, that works so I can play.

I have a program running that is publishing 3 topics which is the CPU case temp plus the temp of the two cores. I don't want mcsMQTT to publish and of these topics, just subscribe to them.

I mcsMQTT can see them going by in the statistics Last Received Topic tab so they are being seen.

I already have the three devices I for the three topics.

I then went to the Add/Edit tab and pasted in one of the topics. "auto/NUC8i3/Package id 0", and when it came up I set the reference field at the bottom for the device I want to contain that topic.

At that point the device does receive the published data but the plugin crashes.

Not much shows up in the debug log.

I'm tired and going to bed. Maybe I'll think more clearly in the morning.

2/3/2019 11:17:32 PM    0    | mcsMQTT Version 3.4.18.2 running at /opt/HomeSeer, HS is at /opt/HomeSeer
2/3/2019 11:17:32 PM    5    | mcsMQTT InitHW ComputerName= auto, IOEnabled=False
2/3/2019 11:17:32 PM    71    | mcsMQTT Debug InitHW Database Ready
2/3/2019 11:17:32 PM    78    | mcsMQTT Debug Receive Ready
2/3/2019 11:17:32 PM    79    | mcsMQTT Debug Trigger Ready
2/3/2019 11:17:32 PM    115    | HW Init Complete  
2/3/2019 11:17:32 PM    115    | Background Init Started  
2/3/2019 11:17:32 PM    128    | Background Init Received  
2/3/2019 11:17:34 PM    1683    | Background Send  
2/3/2019 11:17:37 PM    4384    | Background Init Filters - Background Complete  
2/3/2019 11:17:37 PM    4385    | Spawning MQTT Threads  
2/3/2019 11:17:37 PM    4385    | mcsMQTT Debug MQTT Ready
2/3/2019 11:17:37 PM    4390    | MQTT Thread Not Connected Yet  
2/3/2019 11:17:37 PM    4390    | Calling MQTTclient  
2/3/2019 11:17:37 PM    4391    | MQTT Thread Client Created  
2/3/2019 11:17:37 PM    4391    | MQTT Thread Client ID=mcsMQTT on auto  
2/3/2019 11:17:37 PM    4391    | Calling MQTT Connect  
2/3/2019 11:17:37 PM    4395    | MQTT Thread Broker auto.local Connect Response=0  
2/3/2019 11:17:37 PM    4395    | MQTT Broker Connection Accepted, Connected=True  
2/3/2019 11:17:37 PM    4398    | MQTT Subscription Start  
2/3/2019 11:17:37 PM    4398    | MQTT Subscription Topics being selected  
2/3/2019 11:17:37 PM    4398    | MQTT Subscription Topics selected  
2/3/2019 11:17:37 PM    4398    | MQTTSubscribe List /  NoDiscovery=False to  
2/3/2019 11:17:37 PM    4398    | #  

[Michael McSharry]

Remove contents of /data/mcsMQTT folder and delete /config/mcsMQTT.ini when plugin is not running

[Timon]

There is some old stuff that doesn't need to be there from my initial testing. What's the quickest way to start over?

[Michael McSharry]

The file of interest is \Data\mcsMQTT\mcsMQTT Debug.txt. It will contain more information if the Debug checkbox is used from General tab or access to the browser is not possible then editing config\mcsMQTT.ini so the Debug line is
DebugLog="1"

Note also the 15 seconds it took HS to load the plugin once the plugin established connection with HS. This looks to be excessive to me.

[Timon]

Just setup a package that would send temperature information via MQTT so I'm not able to actually try doing something useful with MQTT on HS3.

Data is coming in but the MQTT plugin is crashing every time it receives a topic.

Running the standard Mosquitto broker so nothing special there.

The Broker is running on the same computer as HS3. The computer is an Intel NUC8i3 running a very lite load.

Here is what's in the log. I'll supply any more information needed.

Feb-03 4:12:31 PM

Info

Plugin mcsMQTT has connected. IP:127.0.0.1:33836

Feb-03 4:12:31 PM

Warning

I/O interface mcsMQTT is down, executable is not running, restarting ...

Feb-03 4:12:16 PM

Info

Plugin mcsMQTT with instance: has disconnected

Feb-03 4:12:16 PM

Device Control

Device: Sensors Abode CPU Case Temp to 36 °C (36) by/from: CAPI Control Handler

Feb-03 4:12:05 PM

mcsMQTT

MQTTClient is Connected

Feb-03 4:12:01 PM

Starting Plug-In

Plugin mcsMQTT started successfully in 202 milliseconds

Feb-03 4:12:01 PM

mcsMQTT

Version 3.4.18.2 Registered with Homeseer

Feb-03 4:12:01 PM

Starting Plug-In

Initializing plugin mcsMQTT ...

Feb-03 4:12:01 PM

Starting Plug-In

mcsMQTT loaded in 15002 milliseconds

Feb-03 4:11:46 PM

Info

Plugin mcsMQTT has connected. IP:127.0.0.1:33818

Feb-03 4:11:45 PM

Warning

I/O interface mcsMQTT is down, executable is not running, restarting ...