Announcement

**Michael McSharry** · February 10, 2020, 10:39 PM

Do you have a MQTT broker installed on the same computer as HS? It was an oversight I discovered with mcsMQTT. I put a check in for this as some other things in 5.1.1.5 which is available at http://mcsSprinklers.com/mcsShelly_5_1_1_5.zip. You will want HSPI_MCSSHELLY.exe into the HS folder and mcsMQTT_2020.dll into the \bin\mcsMQTT folder.

I am bouncing around between HS3 and HS4 for my plugins now and finding things I want to change in the HS3 one as I am trying to keep things as close as possible between HS3 and HS4.

If you enable the Developer mode checkbox on the Plugin page then there may be more information of failure in the console that is a popup. The error for multiple brokers showed in the console window.

**Ironzey** · February 11, 2020, 01:29 PM

I didn't have any MQTT brokers installed.

I just installed mcsMQTT and got the same result.

I'll try 5.1.1.5 when I get home.

Just to confirm, mcsShelly does net require an external MQTT broker? Meaning I shouldn't have any other MQTT brokers plugged into Homeseer.

**Michael McSharry** · February 11, 2020, 02:52 PM

Confirming that no external broker is needed. Just need the plugin and Shelly device.

If you are using mcsMQTT then you will not want to use mcsShelly. mcsMQTT will recognize all the Shelly devices. The only difference is the default configuration that is tailored to only Shelly devices in mcsShelly.

There was another user who had issue with Linux install. I thought that was due to broker, but may be something else. Are you running Linux or Windows?

I am traveling today and ran out of time to pursue matter related to triggers and actions. The most current version of mcsShelly and mcsMQTT are at http://mcsSprinklers.com/mcsShelly_5_1_1_6.zip and http://mcsSprinklers.com/mcsMQTT_5_1_1_6.zip. They share the same \bin\mcsMQTT\mcsMQTT_2020.dll from the zip. The HSPI_MCSSHELLY.exe goes in the HS folder. I will resume tomorrow.

**Ironzey** · February 11, 2020, 07:14 PM

Ok, I installed 5.1.1.6. It still didn't work. I'm going to wait till HS4 comes out and rebuild everything from a clean start.

If I run into any problems at that point I'll post again.

Thanks for the help.

**Michael McSharry** · February 12, 2020, 10:24 PM

I worked quite a-bit with this plugin and mcsMQTT plugin with Linux the last two days and found some thing at the startup that were different than Windows and failed in Mono. I put a version that worked well for me at http://mcsSprinklers.com/mcsShelly_5_1_1_7.zip. It would be nice if you can give it try to as a minimum confirm that the problems you were seeing are no longer present. Same two file and locations as prior post.

**Michael McSharry** · February 13, 2020, 01:06 PM

Looks like 5.1.1.7 is available via updater now.

**Xaq** · June 28, 2020, 10:35 PM

Michael,

I'm getting the same issue, the plugin starts and runs for a few minutes and then windows chucks the "HSPI_MCSSHELLY has stopped working" error. I am running mcsShelly 5.3.0.4 and HS3 Pro Edition 3.0.0.548.

The HSLog shows:

Calling HSEvent in plugin mcsShelly, Instance :Object reference not set to an instance of an object.

Other than that, I can't find any other meaningful error messages to help me troubleshoot. Any help would be appreciated.

**Michael McSharry** · June 29, 2020, 11:35 AM

I understand what it happening. When using an internal broker a heartbeat message is used, but I forgot to include the heartbeat topic in the list of topics mcsShelly client is subscribing so after three minutes an abort/restart attempt is occurring. The restart is having an issue of port 1883 being released by the original internal broker so I am improving this logic. I will get an update today that addresses the primary and secondary issue.

Another way to deal with the issue is on the General Tab, Inbound Management section, Topic Discovery radio. Set it to the top option of discovering all MQTT topics. This will allow the heartbeat through.

**Michael McSharry** · June 29, 2020, 12:22 PM

The update is at http://mcsSprinklers.com/mcsShelly_5_3_3_5.zip
Unzip HSPI_MCSSHELLY.exe into HS folder and mcsMQTT_2020.dll into \bin\mcsShelly folder

The silver lining is that the heartbeat failure recovery was a hidden issue and it got fixed at the same time.

**Xaq** · June 29, 2020, 12:33 PM

Michael,

Thank you for the quick response! I have the files updated and it appears stable. I'll report back if I encounter any other issues in the future.

**Jayhawk** · August 15, 2020, 08:21 PM

I am having this problem... plugin "down" and restarting every 3 minutes.
I am running HS3 but posting here since this topic is not in HS3 thread.
Just installed the plugin from the HS3 plugin installer for the first time today... it is successfully controlling a Shelly 1 relay.
Version 5.3.0.4 Registered with Homeseer
HomeSeer Version: HS3 Pro Edition 3.0.0.548
Operating System: Microsoft Windows 7 Home Premium - Work Station

I did the work-around you indicated above and this did stop the problem (10 minutes and still running): "Another way to deal with the issue is on the General Tab, Inbound Management section, Topic Discovery radio. Set it to the top option of discovering all MQTT topics. This will allow the heartbeat through."

However I suspect would be best to have more limited MQTT Inbound... This is the only MQTT device I have at present. Does ver 5.3.0.4 for HS3 have the fix you indicate above?

**Michael McSharry** · August 16, 2020, 01:29 PM

The current version of mcsShelly is at http://mcsSprinklers.com/mcsShelly_5_5_1_4.zip. HSPI_MCSSHELLY.exe goes in HS3 folder. MCSMQTT_2020.dll goes in \bin\mcsShelly folder. The heartbeat issue has been resolved in all versions since 5.3.3.5.

I would not be concerned about inbound MQTT traffic. It is generally event based so does not put much load on the system.

**Jayhawk** · August 16, 2020, 06:54 PM

Thanks, Michael.
And thanks so much for this plugin!

**Michael McSharry** · August 16, 2020, 07:30 PM

If you think you will have other devices that use MQTT protocol then I suggest you use mcsMQTT rather than mcsShelly. Both can accomplish the same thing with the Shelly devices but mcsMQTT can do more.

Announcement

Plugin keeps stopping...

Plugin keeps stopping...

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment