Browser unresponsive.

[Kdiamond]

Now it works! Perfect.

It's also very smooth. No browser chocking anymore.

Thank you

Br,
Dali

[Michael McSharry]

I made certain the updater override file in the zip was for 6.0.0.1 and confirmed the install using this extracted file. I suspect the link to the 6.0.0.1 file is actually to the 6.0.0.0 file as I just edited the name when I changed from 6.0.0.0 to 6.0.0.1. I recreated the link so you can try again.

[Kdiamond]

Yes, I found version 6.0.0.1

http://mcssprinklers.com/HSPI_mcsMQTT_6_0_0_1.zip.

I did install it successfully by the instructions here:
https://forums.homeseer.com/forum/hs...ge-log-hs4-hs3

What I got was version 6.0.0.0 with an update option.



but when I update it seems it works but I get the same 6.0.0.0 version

[Kdiamond]

Thank you for reply, Michael.

I did 1,2. I don't use any Bluetooth. You say 6.x.x.x version? The one I have is 5.26.5.4 and HS4 Plugin Manager it will show no updates available.



Br,
Dali

[Michael McSharry]

My best guess is that you are accumulating new topics and letting the Association table become so big that it is cumbersome to manage. You can look at CPU statistics on Task Manager / HTOP or look at the CPU use from the Association table to the HS topic.

Another issue that is known is the MQTT Internal Broker will get into a high CPU use state under certain conditions. This was addressed with version 6.x.x.x of the plugin.

In the setttings for MQTT Page, General Tab I have couple suggestions
1. use checkbox to delete unassociated topics on shutdown. This will remove things that are not of interest and reduce the processing burden
2. The Topic Discovery setting default is to discover all new topics. This is good for initial setup, but should be change to the second radio position to only listen to associated topics. You can go back and forth between the two settings when you have a new device introduced into your system.
3. Bluetooth, unless filtered, introduces heavy burden. If you are using Bluetooth then the same guidance as item 2 should be used, but with settings on the Local Page, Bluetooth settings.

[Kdiamond]

Hi Michael.

I hope your doing well.

Over time Associations window has become really slow, chocking and timeout-ing the browser when using dropdowns, clear, rebuild filters. It freezes the browser for about 30sec for each step. It's really hard to work with it.



Also, I have created a new virtual device and add it to a new Floor, but it would fail to show the floor and also the device, even though I rebuild the filters. Is there any specific setting I need to apply to the device to show up in here?



Thank you

Br,
Dali