mcsMQTT Version 6

[syedamerali]

cannot seem to find CSMQTTHS4_2020.* files in http://mcssprinklers.com/HSPI_mcsMQTT_6_0_0_2.zip

It must be a typo, the files are called MCSMQTTHS4_2020.*

I was facing cpu problems and have managed to update to 6.0.0.2 - let us see how the cpu usage is now. It will be a couple of days till I report back because that is how long it takes for the cpu usage to build up.

[Michael McSharry]

They are at http://mcsSprinklers.com/mcsMQTTHS4_6002.zip and http://mcsSprinklers.com/HSPI_mcsMQTT_6_0_0_2.zip

[syedamerali]

Happy to report no problems; cpu or otherwise.

[IanIreland]

They are at http://mcsSprinklers.com/mcsMQTTHS4_6002.zip and http://mcsSprinklers.com/HSPI_mcsMQTT_6_0_0_2.zip

I'm getting a 404 for the HS4 version.

[Michael McSharry]

http://mcsSprinklers.com/HSPI_mcsMQTT_6_0_0_6.zip is current link posted for the Updater package. Just the dll is http://mcsSprinklers.com/mcsMQTTHS4_6006.zip

[Michael McSharry]

Continuation of discussion from post 8 at https://forums.homeseer.com/forum/hs...ge-log-hs4-hs3 about Ubuntu VM internal broker restart

I discarded the heartbeat message when received as a test to let the failure detection logic operate when the heartbeat is not received and then attempt to restart the internal broker. The console shows the sequence where heartbeats are being sent and then after three were not received a restart was performed. During the restart process there were various failures at the socket level with mcsMQTT client failures are reconnecting to the internal broker (since the internal broker was stopped) until finally the thread was aborted and then the internal broker started again with success.

The address in use error was not observed. It could be Linux vs. Windows socket handling or it could be VM vs. physical hardware. I may be able to setup a Pi with Linux, but first step should be to look at the full debug log from /data/mcsMQTT/mcsMQTT Debug.txt. Debug needs to be enabled from the top of the General tab of the MQTT page.

[ocxoman]

Michael,

Thank you for all the hard work.
I started over with a brand new installation of Ubuntu and HS4Pro. I installed both mcsMQTT and the ZWave plugins. Then restored my HS3 configuration to HS4Pro. Everything moved over without issues except that the local broker was not operational. I saw a new update to 6.0.5.0 was available and updated mcsMQTT. The local broker started with no issues immediately after the update. All is working well now. devices are showing up.
Strange how the plugin worked fine in HS3 before but didn't in HS4 on my system.

Jim

[Michael McSharry]

Good to hear it all worked out in the end.