What I understand you are indicating is that the plugin does receive the message traffic, but it does not respond to it because the Accept checkbox is clear.
\Config\mcsMQTT.ini has a setting "Version=x.x.x.x". It only existed before 3.2.x.x. It is used in 3.2.x.x to know if the database has been cleaned up to work with 3.2.x.x. It is ignored by earlier versions. If you are going back and forth between earlier and older versions you need to pay attention to this line in the file. When 3.2.x.x starts with an older database and the Version=x.x.x.x is present then it will not process it and will be confused.
Try the following process
Assume you are starting with working 3.1.4.0
Stop mcsMQTT from HS Plugin Page
Edit mcsMQTT.ini to remove the line with Version=x.x.x.x
Use updater to install latest
Enable mcsMQTT from HS Plugin Page
Assure DebugLog checkbox is set from General Tab
Observe if Accept checkboxes are present and for general operation.
If all is good then great. If not then restore to 3.1.4.0 and working database and email to mcssolutions at centurytel dot net.
What I would like is the backup database that is working for you and the database that is created with latest from updater. mcsMQTT_Debug.txt and mcsMQTT.ini.
With versions prior to 3.2.0.0 the PED was considered the master repository of associations and starting with 3.2.0.0 it is the database. While there was some logic to try to sync the two, there was not a total scrub. Another option that exists if you continue to have problems is to perform this scrub as the database is being cleaned by 3.2.x.x. First, however, is to perform the above and see what your two databases look like.
I did put more error information in SetIOMulti with 3.2.5.2 so that should help with that issue too. It will go the the debug file.
\Config\mcsMQTT.ini has a setting "Version=x.x.x.x". It only existed before 3.2.x.x. It is used in 3.2.x.x to know if the database has been cleaned up to work with 3.2.x.x. It is ignored by earlier versions. If you are going back and forth between earlier and older versions you need to pay attention to this line in the file. When 3.2.x.x starts with an older database and the Version=x.x.x.x is present then it will not process it and will be confused.
Try the following process
Assume you are starting with working 3.1.4.0
Stop mcsMQTT from HS Plugin Page
Edit mcsMQTT.ini to remove the line with Version=x.x.x.x
Use updater to install latest
Enable mcsMQTT from HS Plugin Page
Assure DebugLog checkbox is set from General Tab
Observe if Accept checkboxes are present and for general operation.
If all is good then great. If not then restore to 3.1.4.0 and working database and email to mcssolutions at centurytel dot net.
What I would like is the backup database that is working for you and the database that is created with latest from updater. mcsMQTT_Debug.txt and mcsMQTT.ini.
With versions prior to 3.2.0.0 the PED was considered the master repository of associations and starting with 3.2.0.0 it is the database. While there was some logic to try to sync the two, there was not a total scrub. Another option that exists if you continue to have problems is to perform this scrub as the database is being cleaned by 3.2.x.x. First, however, is to perform the above and see what your two databases look like.
I did put more error information in SetIOMulti with 3.2.5.2 so that should help with that issue too. It will go the the debug file.
Comment