Announcement

Collapse
No announcement yet.

Version 3.2.x.x

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • #16
    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.

    Comment


    • #17
      Originally posted by petez69 View Post
      Hi Michael

      Under filter associations I've ticked show all accepted only and click show selected associations, nothing shows. I've ticked all the filter boxes, nothing shows.

      I
      Thankyou..Pete

      Hope this is the right place....
      I did a fresh install of 3.2.5.2. I'm able to configure under the Manual tab an HS device which I can publish and it shows up in Node-Red. (btw. why can I not choose the topic I like?? The HS ID should be sufficient to identify the device..)

      In the Association tab nothing is listed. I checked also the "Include Non-Plugin HS Devices". In the "Filter Association Table by HS Device Categories" I can see the my floors, rooms etc. in the pull down menues. Should there not be an entry like "check all"?
      Maybe I do not understand the concept of the Association tab??

      Comment


      • #18
        Based upon you description I understand that you used the Manual Publish table to setup a topic that is associated with an existing HS device. You are able to change the HS device and a message is delivered to a subscribed node-red.

        The Device-Topic relationship should also be visible from the Association tab. To maximize the content of the visible associations the checkboxes for Include non-plugin and Include mcsMQTT devices should both be checked and the device and topic filters should have no selections. The Show button at the bottom then clicked to render the table.

        If this is not happening for you then I would like to see your \data\mcsMQTT.db and \config\mcsMQTT.ini files; either posted as zip or email mcsSolutions at CenturyTel dot net.

        If node-red or other client has been publishing messages to the same broker that mcsMQTT is connected then these messages should be visible in the association table if the Include MQTT Topics checkbox is checked and no filter selections made in the two pulldown selectors. The "Show Selected Associations" table builds the table. If there a lot of topics then the table can take a little while to build. Use of the filters to restrict the set of topic will improve the rendering time.

        Comment


        • #19
          Thanks for the quick response...

          here is the mcsMQTT.ini
          [General]
          DebugLog=0
          Version=3.2.5.2
          CreateStatusDevices="0"
          RefList="565,566,567,568,569,570,571,572,573,574,575,576,577 ,578,579,580"
          MQTTBroker="192.168.1.4"
          ShowRejected="1"
          ShowHomeseerSourced="1"
          DevicexFilter1=""
          DevicexFilter2=""
          AssociationRows=2
          DevicexFilter3=""
          DevicexFilter4=""
          ShowMQTTSourced="1"
          SegmentFilter1=""
          SegmentFilter2=""
          SegmentFilter3=""
          NoEnumeration="1"
          SegmentFilter4=""
          ShowOnlyAccepted="1"
          Disconnect="unchecked"

          Comment


          • #20
            The db file is on the email way..

            Comment


            • #21
              Your database looks good with 290 HS devices and 35 mcsMQTT topics. Your ini file indicates to "Show All Only Accepted". To see the discovered topics in the Association table you need to uncheck this text box.

              You also have 9 entries Accepted that all point to HS device 29. This looks to be a bug in the plugin where it is storing the same information multiple times. It should not affect anything, but I will fix it.

              Device 29 is setup such that when Device value changed it will transmit the value on topic "RaspiHS3/mcsMQTT/Buero|Oben|RSTempIst". Was this your intention?

              I also see in your .ini that "Disconnect" was stored as unchecked and this should have been stored as "0". This will cause the inability to persist a disconnect state through restarts. Again, I will fix, but should not affect what you are doing now.

              Comment


              • #22
                Tank you,

                I have unchecked "Show All Accepted only" but nothing shows up. Here is again the mcsMQTT.ini file
                General]
                DebugLog=0
                Version=3.2.5.2
                CreateStatusDevices="0"
                RefList="565,566,567,568,569,570,571,572,573,574,575,576,577 ,578,579,580"
                MQTTBroker="192.168.1.4"
                ShowRejected="1"
                ShowHomeseerSourced="1"
                DevicexFilter1=""
                DevicexFilter2=""
                AssociationRows=328
                DevicexFilter3=""
                DevicexFilter4=""
                ShowMQTTSourced="1"
                SegmentFilter1=""
                SegmentFilter2=""
                SegmentFilter3=""
                NoEnumeration="1"
                SegmentFilter4=""
                ShowOnlyAccepted="0"
                Disconnect="unchecked"

                Rejected Selection, Outbound Selections and Inbound Selections are checked only. All the other field are blank.

                Comment


                • #23
                  and yes, topic "RaspiHS3/mcsMQTT/Buero|Oben|RSTempIst" was my intention and works.

                  Comment


                  • #24
                    I see where I have a significant corruption of the database as was shown in your data with all non-plugin devices having the same information. I though it was duplicates, but it was an overwrite of the others when an association is made. Delete your database in your case or go back to an earlier one before recent non-plugin devices were associated.

                    Update to 3.2.5.3 and see if you have better success. I did not see anything specific with your setup, other than the database. I will look again if you continue to have issue.

                    Comment


                    • #25
                      I deleted everything with mcsMQTT in the Data dir and upgraded to 3.2.5.3. Still the same result.
                      Is it possible that something is wrong with user right management? Im not logging in with HomeSeer but with PI. Here is the detailed file list in the Data dir before I upgraded and deleted the mcsMQTT files. The next one is after I upgraded and new mcsMQTT files have been created.
                      drwxr-xr-x 6 pi pi 4096 Apr 1 01:07 .
                      drwxr-xr-x 21 pi pi 4096 Apr 1 01:03 ..
                      drwxr-xr-x 2 pi pi 4096 Apr 16 2016 Backup
                      drwxr-xr-x 2 pi pi 4096 Jan 4 17:06 Energy
                      -rw-r--r-- 1 root root 2930688 Apr 1 01:06 HomeSeerData.hsd
                      -rw-r--r-- 1 root root 2910208 Mar 29 15:38 HomeSeerData_1.hsd
                      -rw-r--r-- 1 root root 2904064 Mar 28 12:07 HomeSeerData_10.hsd
                      -rw-r--r-- 1 root root 2910208 Mar 29 15:38 HomeSeerData_2.hsd
                      -rw-r--r-- 1 root root 2910208 Mar 31 16:56 HomeSeerData_3.hsd
                      -rw-r--r-- 1 root root 2910208 Mar 29 15:14 HomeSeerData_4.hsd
                      -rw-r--r-- 1 root root 2904064 Mar 28 13:44 HomeSeerData_5.hsd
                      -rw-r--r-- 1 root root 2875392 Mar 23 00:15 HomeSeerData_6.hsd
                      -rw-r--r-- 1 root root 2869248 Mar 19 16:24 HomeSeerData_7.hsd
                      -rw-r--r-- 1 root root 2910208 Mar 31 17:07 HomeSeerData_8.hsd
                      -rw-r--r-- 1 root root 2878464 Mar 23 10:08 HomeSeerData_9.hsd
                      drwxr-xr-x 2 root root 4096 Apr 1 00:15 ImperiHome
                      drwxr-xr-x 3 pi pi 4096 Mar 31 17:15 Z-Wave
                      -rw-r--r-- 1 root root 2228 Apr 1 01:04 mcsMQTT Debug.txt
                      -rw-r--r-- 1 root root 24576 Mar 31 17:21 mcsMQTT.db~
                      -rw-r--r-- 1 root root 20480 Mar 31 17:20 mcsMQTT.db~3_31_2018_5_21_05_PM
                      -rw-r--r-- 1 root root 24576 Mar 31 17:21 mcsMQTT.db~3_31_2018_5_21_39_PM
                      -rw-r--r-- 1 root root 24576 Mar 31 17:21 mcsMQTT.db~3_31_2018_5_22_13_PM
                      -rw-r--r-- 1 root root 24576 Mar 31 17:21 mcsMQTT.db~3_31_2018_5_22_47_PM
                      -rw-r--r-- 1 root root 24576 Mar 31 17:21 mcsMQTT.db~3_31_2018_5_23_21_PM
                      -rw-r--r-- 1 root root 24576 Mar 31 17:24 mcsMQTT.db~3_31_2018_5_24_42_PM
                      -rw-r--r-- 1 root root 53248 Apr 1 01:02 mcsMQTT.db~4_1_2018_1_04_04_AM
                      -rw-r--r-- 1 root root 8192 Mar 31 17:20 mcsMQTThistory.db


                      After the upgrade:

                      /usr/local/HomeSeer/Data $ ls -al
                      total 31232
                      drwxr-xr-x 6 pi pi 4096 Apr 1 01:11 .
                      drwxr-xr-x 21 pi pi 4096 Apr 1 01:03 ..
                      drwxr-xr-x 2 pi pi 4096 Apr 16 2016 Backup
                      drwxr-xr-x 2 pi pi 4096 Jan 4 17:06 Energy
                      -rw-r--r-- 1 root root 2930688 Apr 1 01:06 HomeSeerData.hsd
                      -rw-r--r-- 1 root root 2910208 Mar 29 15:38 HomeSeerData_1.hsd
                      -rw-r--r-- 1 root root 2904064 Mar 28 12:07 HomeSeerData_10.hsd
                      -rw-r--r-- 1 root root 2910208 Mar 29 15:38 HomeSeerData_2.hsd
                      -rw-r--r-- 1 root root 2910208 Mar 31 16:56 HomeSeerData_3.hsd
                      -rw-r--r-- 1 root root 2910208 Mar 29 15:14 HomeSeerData_4.hsd
                      -rw-r--r-- 1 root root 2904064 Mar 28 13:44 HomeSeerData_5.hsd
                      -rw-r--r-- 1 root root 2875392 Mar 23 00:15 HomeSeerData_6.hsd
                      -rw-r--r-- 1 root root 2869248 Mar 19 16:24 HomeSeerData_7.hsd
                      -rw-r--r-- 1 root root 2910208 Mar 31 17:07 HomeSeerData_8.hsd
                      -rw-r--r-- 1 root root 2878464 Mar 23 10:08 HomeSeerData_9.hsd
                      drwxr-xr-x 2 root root 4096 Apr 1 00:15 ImperiHome
                      drwxr-xr-x 3 pi pi 4096 Mar 31 17:15 Z-Wave
                      -rw-r--r-- 1 root root 1226 Apr 1 01:11 mcsMQTT Debug.txt
                      -rw-r--r-- 1 root root 16384 Apr 1 01:11 mcsMQTT.db
                      -rw-r--r-- 1 root root 8192 Apr 1 01:11 mcsMQTThistory.db

                      Comment


                      • #26
                        Can you provide mcsMQTT.db again after the upgrade? The mcsMQTT_Debug.txt may also be useful. If you have not already then check your HS log for any errors reported. The files are being generated so should not be rights. I am confused about not logging in via Homeseer. Are you running the plugin from a different computer than Homeseer. If you are, then the Config file will be in the HS\Config and the data will be on the same computer as the plugin.

                        Comment


                        • #27
                          Michael

                          I'll get you the requested debug shortly. Its easter long weekend in Australia and we are off camping, the weather is stunning

                          CHeers
                          HS 2.2.0.11

                          Comment


                          • #28
                            Whenever convenient is fine. Do update to the latest as I found a database write error today.

                            Comment


                            • #29
                              Originally posted by Michael McSharry View Post
                              Can you provide mcsMQTT.db again after the upgrade? The mcsMQTT_Debug.txt may also be useful. If you have not already then check your HS log for any errors reported. The files are being generated so should not be rights. I am confused about not logging in via Homeseer. Are you running the plugin from a different computer than Homeseer. If you are, then the Config file will be in the HS\Config and the data will be on the same computer as the plugin.
                              The information requested are send via email.

                              The standard HS3 (not the Raps version..) is installed on a RPi3 under Raspian Jessy. I have no additional linux users created and just use the standard user "pi". Your plugin runs on the same RPI. In the HS3 Log is nothin recorded in relation to the mcsMQTT. Just to complete the picture, on the same RPI runs also Mosquitto and Node-Red. (each of them with its on DB..). The usual CPU load is under 10%.

                              Thank you,

                              Comment


                              • #30
                                Moving from MQTT PI

                                I must be doing something wrong. No matter what I do I can't get HS to trigger any event when a mcsMQTT device is update.

                                What am I doing wrong?

                                PS: Version 3.2.5.3

                                .
                                Attached Files
                                RJ_Make On YouTube

                                Comment

                                Working...
                                X