mcsMQTT V5.5.2.0 update debends

[Pete]

Just updated plugin to V5.5.2.0 on Homeseer 3. mcsMQTT fails to start with critical error. "CRITCAL:Plugin has disconnected"

It keeps trying to start but never does. Disabled it for time bean.

[Michael McSharry]

Do you have any debug information in the mcsMQTT or HS logs?

[Pete]

Just looked and have a debug text file. Deleted it just now and tried to start the plugin.

This is what it shows:

9/16/2020 5:32:55 PM 9 | mcsMQTT Version 5.5.2.0 running at /opt/HomeSeer, HS is at /opt/HomeSeer
9/16/2020 5:32:55 PM 16 | mcsMQTT HS Plugin InitHW ComputerName= ICS-HS3Pro
9/16/2020 5:32:55 PM 104 | mcsMQTT Debug InitHW Database Ready
9/16/2020 5:32:56 PM 344 | mcsMQTT Debug Receive Ready
9/16/2020 5:32:56 PM 344 | mcsMQTT Debug Trigger Ready
9/16/2020 5:32:56 PM 417 | HW Init Complete
9/16/2020 5:32:56 PM 419 | Background Init Started
9/16/2020 5:32:57 PM 1808 | Background Init Received
9/16/2020 5:32:58 PM 3094 | Background Send
9/16/2020 5:32:59 PM 3338 | Background Init Filters - Background Complete
9/16/2020 5:32:59 PM 3339 | Spawning MQTT Threads
9/16/2020 5:32:59 PM 3345 | Background Init MQTT - Background Complete Sign FilePath
9/16/2020 5:32:59 PM 3345 | Background Init Folders - Background Complete
9/16/2020 5:32:59 PM 3350 | Background Complete
9/16/2020 5:32:59 PM 3350 | Delayed SetIOMulti Complete
9/16/2020 5:32:59 PM 3350 | Calling MQTTclient for Broker 1
9/16/2020 5:32:59 PM 3351 | MQTT Thread Client Created for Broker 1
9/16/2020 5:32:59 PM 3351 | MQTT Thread Client ID=mcsMQTT on ICS-HS3Pro
9/16/2020 5:32:59 PM 3351 | Calling MQTT Connect
9/16/2020 5:32:59 PM 3351 | Pre-connect oMQTTClient(0) is Nothing=False
9/16/2020 5:32:59 PM 3357 | MQTT Thread Broker 1 192.168.244.150 Connect Response=0
9/16/2020 5:32:59 PM 3357 | MQTT Broker 1 Connection Accepted, Connected=True to broker 192.168.244.150
9/16/2020 5:32:59 PM 3362 | MQTT Subscription Start for Broker 1
9/16/2020 5:32:59 PM 3362 | MQTT Subscription Topics being selected for Broker 1
9/16/2020 5:32:59 PM 3362 | MQTT Subscription Topics selected for Broker 1
9/16/2020 5:32:59 PM 3363 | MQTTSubscribe List / Option=2 to
9/16/2020 5:32:59 PM 3363 | homeassistant/nodes

Looked at the INI file and see:

[General]
DebugLog="0"
Version=5.5.2.0
ShowHomeseerSourced="1"

I was just getting ready to set up the new lightning sensor and saw an update and decided to update.

Can I downgrade to previous version of the plugin?

[Michael McSharry]

The mcsMQTT debug log looks fine, but you do have a rather restrictive subscription list. Not an error, but just an observation.

Anything from the HS log to provide some hints? I have been doing all my testing with HS4, but did not expect any difference under HS3.

[Guest]

I am also on linux here. I was having a lot of those type of issue with plugins on 5.1.6. Reverted back to 5.1.4, but the issue was still there (so maybe something broke my system with 5.1.6).

Loaded a backup from 4 days before and all was good . Maybe this is worth a try if you have one.

[Guest]

I didn’t think about trying this at first, but maybe you can check the systemd log for this .
Just change HomeSeer for wtv is your hs service name.

journalctl -u HomeSeer.service -b

[Pete]

The mcsMQTT debug log looks fine, but you do have a rather restrictive subscription list.

Yes I had just done that to get the new Lightning sensor. I am doing only MQTT with Home Assistant and have many devices.

I do not want to put all of those devices in to Homeseer. Redid the whole mcsMQTT configuration with the last revision and the GDO debacle.

Deleted all of the databases in mcsMQTT and all of the devices that used to be there and recreated all of the stuff I wanted to see. This was done last week.

Here is what the Homeseer 3 log shows.

Homeseer 4 here is only in test mode started from scratch on it with no import from HS3. HS3 and HS4 are running on two Ubuntu servers.

Personally for me HS4 is from production mode at this time.

Sep-16 5:35:57 PM mcsMQTT Version 5.5.2.0 Registered with Homeseer
Sep-16 5:35:57 PM Starting Plug-In Plugin mcsMQTT started successfully in 74 milliseconds
Sep-16 5:36:00 PM mcsMQTT MQTTClient is Connected to broker 1 at 192.168.244.150
Sep-16 5:36:00 PM Info Plugin mcsMQTT with instance: has disconnected
Sep-16 5:36:27 PM Warning I/O interface mcsMQTT is down, executable is not running, restarting ...
Sep-16 5:36:27 PM Info Plugin mcsMQTT has connected. IP:127.0.0.1:45496
Sep-16 5:36:42 PM Starting Plug-In mcsMQTT loaded in 15015 milliseconds
Sep-16 5:36:42 PM Starting Plug-In Initializing plugin mcsMQTT ...
Sep-16 5:36:42 PM mcsMQTT Version 5.5.2.0 Registered with Homeseer
Sep-16 5:36:42 PM Starting Plug-In Plugin mcsMQTT started successfully in 74 milliseconds
Sep-16 5:36:45 PM mcsMQTT MQTTClient is Connected to broker 1 at 192.168.244.150
Sep-16 5:36:45 PM Info Plugin mcsMQTT with instance: has disconnected
Sep-16 5:37:12 PM Warning I/O interface mcsMQTT is down, executable is not running, restarting ...
Sep-16 5:37:12 PM Info Plugin mcsMQTT has connected. IP:127.0.0.1:45502
Sep-16 5:37:27 PM Starting Plug-In mcsMQTT loaded in 15016 milliseconds
Sep-16 5:37:27 PM Starting Plug-In Initializing plugin mcsMQTT ...
Sep-16 5:37:27 PM mcsMQTT Version 5.5.2.0 Registered with Homeseer
Sep-16 5:37:27 PM Starting Plug-In Plugin mcsMQTT started successfully in 73 milliseconds
Sep-16 5:37:31 PM mcsMQTT MQTTClient is Connected to broker 1 at 192.168.244.150
Sep-16 5:37:31 PM Info Plugin mcsMQTT with instance: has disconnected
Sep-16 5:37:57 PM Warning I/O interface mcsMQTT is down, executable is not running, restarting ...
Sep-16 5:37:58 PM Info Plugin mcsMQTT has connected. IP:127.0.0.1:45508
Sep-16 5:38:12 PM Starting Plug-In mcsMQTT loaded in 15016 milliseconds
Sep-16 5:38:13 PM Starting Plug-In Initializing plugin mcsMQTT ...
Sep-16 5:38:13 PM mcsMQTT Version 5.5.2.0 Registered with Homeseer
Sep-16 5:38:13 PM Starting Plug-In Plugin mcsMQTT started successfully in 66 milliseconds
Sep-16 5:38:16 PM mcsMQTT MQTTClient is Connected to broker 1 at 192.168.244.150
Sep-16 5:38:16 PM Info Plugin mcsMQTT with instance: has disconnected
Sep-16 5:38:43 PM Warning I/O interface mcsMQTT is down, executable is not running, restarting ...

[Guest]

Pete . I had the exam same symptoms... as yours . 15 secs for the plugin(s) to start.

[Pete]

I did not do a backup before upgrading the plugin. HS3 on the two Ubuntu servers is not running as a service. Rather it just starts on boot.

Second HS3 box is not running mcsMQTT. HS4 box has mcsMQTT plugin but it is not enabled at this time.

[Pete]

I had the exam same symptoms... as yours . 15 secs for the plugin(s) to start.

Here let it try starting for a few minutes and it keep trying and failing to start.

[Pete]

Just looking at the HS4 box and it is stull running v.5.5.1.4.

Copying that version over to the HS3 box.

The plugin v5.5.1.4 doesn't show up in the HS3 box.

Copied more plugin files and changed the INI file plugin version to 5.5.1.4

Is the plugin different for HS4 than for HS3?

[Michael McSharry]

Every version of the plugin is on http://mcsSprinklers.com with a filename pattern of mcsMQTT_w_x_y_z.zip. For example mcsMQTT_5_5_1_8.zip is the one that I would suggest.

[Pete]

Thank you Michael. Site is currently down via Firefox and Chrome.

This site can’t be reached
mcssprinkler.com’s server IP address could not be found.

[Michael McSharry]

Missing an s. It has been updated

[Pete]

I went to the INI file and disable the /homeassistant/nodes search and disabled the auto create pieces and plugin starts fine and fast now.

EnableAutoDeviceCreation="0"
SubscriptionTemplate=""
WildcardTemplate=""

Sep-16 6:45:38 PM Starting Plug-In Initializing plugin mcsMQTT ...
Sep-16 6:45:38 PM mcsMQTT Version 5.5.2.0 Registered with Homeseer
Sep-16 6:45:38 PM Starting Plug-In Plugin mcsMQTT started successfully in 66 milliseconds
Sep-16 6:45:38 PM Starting Plug-In mcsMQTT loaded in 500 milliseconds
Sep-16 6:45:38 PM Plug-In Finished initializing plug-in mcsMQTT
Sep-16 6:45:42 PM mcsMQTT MQTTClient is Connected to broker 1 at 192.168.244.150

So will leave the plugin at Version 5.5.2.0 on HS3.

and

manually add my new lightning sensor stuff...