mcsMQTT for HS4

[Guest]

You can download it from your site . with HSPI in front of the last part of the url

[Michael McSharry]

I know it can be downloaded, but then one needs to install it. I expected experienced users to be able to do this, but those not familiar with HS4 alpha/beta process would have a hard time.

In this particular case with the Relays I know I am able to control them with either plugin running on HS4.

[Guest]

ha ok got it. Is the release version gonna be 5.3.4.0?

[Michael McSharry]

Yes it will, unless I submit new version before it actually gets published. I have been testing the new Shelly 1.7 firmware and have some updates to roll out for both mcsShelly and mcsMQTT.

[Baxe]

HST approved the HS4 plugin, but I do not see it published to the updater yet. How did you install it?

The warning are expected since the Statistics devices were created in an earlier plugin version before HS4 considerations were implemented.

The debug from mcsMQTT will contain info about what happens when a relay is attempted to be controlled. General Tab, Enable Debug, Control a Relay, Debug output in \Data\mcsMQTT\mcsMQTT Debug.txt. Post file as a zip.

Sorry late respond,

It was the plugin shop on HS 4 software

Sending debug file from mcsMQTT later today.

I updated to HS4 by uploading the files from HS3, so I still have my HS3 installation

//Jens

[Baxe]

HST approved the HS4 plugin, but I do not see it published to the updater yet. How did you install it?

The warning are expected since the Statistics devices were created in an earlier plugin version before HS4 considerations were implemented.

The debug from mcsMQTT will contain info about what happens when a relay is attempted to be controlled. General Tab, Enable Debug, Control a Relay, Debug output in \Data\mcsMQTT\mcsMQTT Debug.txt. Post file as a zip.

Hi,

The file is 48mb after zipp it, and is to big to send

//Jens

[Michael McSharry]

I suspect you are running a HS3 plugin in HS4. In either case, delete the existing debug file and let a new one be created. The info of interest is current data so the old data does not matter. To delete it you many need to disable the plugin, delete it, enable the plugin.

[Baxe]

I suspect you are running a HS3 plugin in HS4. In either case, delete the existing debug file and let a new one be created. The info of interest is current data so the old data does not matter. To delete it you many need to disable the plugin, delete it, enable the plugin.

New debug.txt

//Jens

[Michael McSharry]

Your debug contains the following that shows the plugin is responding to the HS control action. The attached contains additional debug on the return status. Unzip the file to replace the one that exists in the bin\mcsMQTT folder. As indicated before I am able to control relays with both plugins so I know the basic functionality exists.

2020-07-08 05:42:05 17811 | SetIOMulti 1608, oCAPI.ControlType=Button, MQTTReceiveRefDictionary.Contains=True
2020-07-08 05:42:05 17816 | CommandControllableDevice 192.168.1.165/RELAY1=Off
2020-07-08 05:42:05 17816 | SetIOMulti 1609, oCAPI.ControlType=Button, MQTTReceiveRefDictionary.Contains=True
2020-07-08 05:42:05 17816 | CommandControllableDevice 192.168.1.165/RELAY2=On
2020-07-08 05:42:05 17888 | SetRelay 0 Off
2020-07-08 05:42:05 17892 | SetRelay 1 On

[Baxe]

Your debug contains the following that shows the plugin is responding to the HS control action. The attached contains additional debug on the return status. Unzip the file to replace the one that exists in the bin\mcsMQTT folder. As indicated before I am able to control relays with both plugins so I know the basic functionality exists.

2020-07-08 05:42:05 17811 | SetIOMulti 1608, oCAPI.ControlType=Button, MQTTReceiveRefDictionary.Contains=True
2020-07-08 05:42:05 17816 | CommandControllableDevice 192.168.1.165/RELAY1=Off
2020-07-08 05:42:05 17816 | SetIOMulti 1609, oCAPI.ControlType=Button, MQTTReceiveRefDictionary.Contains=True
2020-07-08 05:42:05 17816 | CommandControllableDevice 192.168.1.165/RELAY2=On
2020-07-08 05:42:05 17888 | SetRelay 0 Off
2020-07-08 05:42:05 17892 | SetRelay 1 On

New debug file after replace whith your file...

//Jens

[Baxe]

Your debug contains the following that shows the plugin is responding to the HS control action. The attached contains additional debug on the return status. Unzip the file to replace the one that exists in the bin\mcsMQTT folder. As indicated before I am able to control relays with both plugins so I know the basic functionality exists.

2020-07-08 05:42:05 17811 | SetIOMulti 1608, oCAPI.ControlType=Button, MQTTReceiveRefDictionary.Contains=True
2020-07-08 05:42:05 17816 | CommandControllableDevice 192.168.1.165/RELAY1=Off
2020-07-08 05:42:05 17816 | SetIOMulti 1609, oCAPI.ControlType=Button, MQTTReceiveRefDictionary.Contains=True
2020-07-08 05:42:05 17816 | CommandControllableDevice 192.168.1.165/RELAY2=On
2020-07-08 05:42:05 17888 | SetRelay 0 Off
2020-07-08 05:42:05 17892 | SetRelay 1 On

My start upp log have this error can that have somfing to do whith this problem?

//Jens

[Michael McSharry]

Your HS log a normal startup for mcsMQTT. There are other plugin messages that have no effect on mcsMQTT. What is of interest is the debug log from mcsMQTT.

2020-07-08 22:03:49 HomeSeer~!~Info~!~Plugin mcsMQTT has connected. IP:127.0.0.1:65411
2020-07-08 22:03:49 HomeSeer~!~Starting Plug-In~!~Initializing plugin mcsMQTT ...
2020-07-08 22:03:49 Legacy-Plugin~!~mcsMQTT~!~Version 5.3.0.4 Registered with Homeseer
2020-07-08 22:03:49 HomeSeer~!~Starting Plug-In~!~Plugin mcsMQTT started successfully in 361 milliseconds
2020-07-08 22:03:49 HomeSeer~!~Starting Plug-In~!~mcsMQTT loaded in 661 milliseconds
2020-07-08 22:03:49 HomeSeer~!~Plug-In~!~Finished initializing plug-in mcsMQTT

The mcsMQTT log shows that there is no response from the IP Relay when commands are given or when status is requested. It looks to me as if your network topology has changed and the computer you are running HS is not seeing return data from the unit or the data is not getting to the Relay IP.

We have other discussions on this board about how the Relay IP does not work in many configurations. When I used Wireshark to take I look I saw that the Relay IP had the multicast bit set. This means that routers should not forward the data. Only end points on the same physical LAN will see it.

[Baxe]

Strange it works on my HS3 configuration


Skickat från min iPhone med Tapatalk Pro

[Michael McSharry]

Are HS3 and HS4 on the same computer?

[Baxe]

Are HS3 and HS4 on the same computer?

Yes


Skickat från min iPhone med Tapatalk Pro