Announcement

Collapse
No announcement yet.

A lot of CM15A (Linux) debug output although debug is not checked

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

    A lot of CM15A (Linux) debug output although debug is not checked

    I installed the CM15A latest version (3.0.0.6) in order to be able to add an X10 device. Although I did not check the debug output in the configuration page of the plugin, I do get a lot of debug output in the HS log.
    Can it be switched off otherwise?
    ---
    Cor

    #2
    What OS are you running under and what version of HS are you running?
    Please post a bit of your log showing the debug messages you're referring to.
    Best regards,
    -Mark-

    If you're not out on the edge, you're taking up too much room!
    Interested in 3D maps? Check out my company site: Solid Terrain Modeling

    Comment


      #3
      I am running Debian Buster on a RPi4 4GB.

      Here is some output as a consequence of a movement sensor (HouseUnit B8) and the opening of a door with a X10 sensor on it (HouseUnit B7).
      apr.-28 17:48:11 CM15A DEBUG CM15A.callbackCheckTrigger(): EvCmd = 3, X10Cmd = 3, TempEvAddr = B9, Rec'dX10Addr = B7, TrigFired = False
      apr.-28 17:48:11 CM15A DEBUG CM15A.callbackCheckTrigger(): EvCmd = 2, X10Cmd = 3, TempEvAddr = B9, Rec'dX10Addr = B7, TrigFired = False
      apr.-28 17:48:11 CM15A DEBUG CM15A.callbackCheckTrigger(): EvCmd = 3, X10Cmd = 3, TempEvAddr = B9, Rec'dX10Addr = B7, TrigFired = False
      apr.-28 17:48:11 Event Event Trigger "Virtual devices 3-Achterdeur dicht"
      apr.-28 17:48:11 CM15A DEBUG CM15A.ParseRcv()2: Address = B7, LastCmd: Off, IsCmd = True
      apr.-28 17:48:11 CM15A DEBUG CM15A.ParseRcv()1: data = 04/28 17:48:11 Rx PL House: B Func: Off
      apr.-28 17:48:10 CM15A DEBUG CM15A.ParseRcv()2: Address = B7, LastCmd: Off, IsCmd = False
      apr.-28 17:48:10 CM15A DEBUG CM15A.ParseRcv()1: data = 04/28 17:48:10 Rx PL HouseUnit: B7
      apr.-28 17:48:09 CM15A DEBUG CM15A.callbackCheckTrigger(): EvCmd = 3, X10Cmd = 3, TempEvAddr = B9, Rec'dX10Addr = B8, TrigFired = False
      apr.-28 17:48:09 CM15A DEBUG CM15A.callbackCheckTrigger(): EvCmd = 2, X10Cmd = 3, TempEvAddr = B9, Rec'dX10Addr = B8, TrigFired = False
      apr.-28 17:48:09 CM15A DEBUG CM15A.callbackCheckTrigger(): EvCmd = 3, X10Cmd = 3, TempEvAddr = B9, Rec'dX10Addr = B8, TrigFired = False
      apr.-28 17:48:09 CM15A DEBUG CM15A.ParseRcv()2: Address = B8, LastCmd: Off, IsCmd = True
      apr.-28 17:48:09 CM15A DEBUG CM15A.ParseRcv()1: data = 04/28 17:48:09 Rx PL House: B Func: Off
      apr.-28 17:48:09 CM15A DEBUG CM15A.ParseRcv()2: Address = B8, LastCmd: On, IsCmd = False
      apr.-28 17:48:09 CM15A DEBUG CM15A.ParseRcv()1: data = 04/28 17:48:09 Rx PL HouseUnit: B8
      apr.-28 17:48:05 CM15A DEBUG CM15A.callbackCheckTrigger(): EvCmd = 3, X10Cmd = 2, TempEvAddr = B9, Rec'dX10Addr = B8, TrigFired = False
      apr.-28 17:48:05 CM15A DEBUG CM15A.callbackCheckTrigger(): EvCmd = 2, X10Cmd = 2, TempEvAddr = B9, Rec'dX10Addr = B8, TrigFired = False
      apr.-28 17:48:05 CM15A DEBUG CM15A.callbackCheckTrigger(): EvCmd = 3, X10Cmd = 2, TempEvAddr = B9, Rec'dX10Addr = B8, TrigFired = False
      apr.-28 17:48:05 CM15A DEBUG CM15A.ParseRcv()2: Address = B8, LastCmd: On, IsCmd = True
      apr.-28 17:48:05 CM15A DEBUG CM15A.ParseRcv()1: data = 04/28 17:48:05 Rx PL House: B Func: On
      apr.-28 17:48:05 CM15A DEBUG CM15A.ParseRcv()2: Address = B8, LastCmd: On, IsCmd = False
      apr.-28 17:48:05 CM15A DEBUG CM15A.ParseRcv()1: data = 04/28 17:48:05 Rx PL HouseUnit: B8
      apr.-28 17:48:04 CM15A DEBUG CM15A.callbackCheckTrigger(): EvCmd = 3, X10Cmd = 2, TempEvAddr = B9, Rec'dX10Addr = B7, TrigFired = False
      apr.-28 17:48:04 CM15A DEBUG CM15A.callbackCheckTrigger(): EvCmd = 2, X10Cmd = 2, TempEvAddr = B9, Rec'dX10Addr = B7, TrigFired = False
      apr.-28 17:48:04 CM15A DEBUG CM15A.callbackCheckTrigger(): EvCmd = 3, X10Cmd = 2, TempEvAddr = B9, Rec'dX10Addr = B7, TrigFired = False
      apr.-28 17:48:04 Event Event Trigger "Virtual devices 3-Achterdeur open"
      apr.-28 17:48:04 CM15A DEBUG CM15A.ParseRcv()2: Address = B7, LastCmd: On, IsCmd = True
      apr.-28 17:48:04 CM15A DEBUG CM15A.ParseRcv()1: data = 04/28 17:48:04 Rx PL House: B Func: On
      apr.-28 17:48:04 CM15A DEBUG CM15A.ParseRcv()2: Address = B7, LastCmd: On, IsCmd = False
      apr.-28 17:48:04 CM15A DEBUG CM15A.ParseRcv()1: data = 04/28 17:48:04 Rx PL HouseUnit: B7
      apr.-28 17:48:03 CM15A DEBUG CM15A.callbackCheckTrigger(): EvCmd = 3, X10Cmd = 2, TempEvAddr = B9, Rec'dX10Addr = B8, TrigFired = False
      apr.-28 17:48:03 CM15A DEBUG CM15A.callbackCheckTrigger(): EvCmd = 2, X10Cmd = 2, TempEvAddr = B9, Rec'dX10Addr = B8, TrigFired = False
      apr.-28 17:48:03 CM15A DEBUG CM15A.callbackCheckTrigger(): EvCmd = 3, X10Cmd = 2, TempEvAddr = B9, Rec'dX10Addr = B8, TrigFired = False
      apr.-28 17:48:03 CM15A DEBUG CM15A.ParseRcv()2: Address = B8, LastCmd: On, IsCmd = True
      apr.-28 17:48:03 CM15A DEBUG CM15A.ParseRcv()1: data = 04/28 17:48:03 Rx PL House: B Func: On
      apr.-28 17:48:02 CM15A DEBUG CM15A.ParseRcv()2: Address = B8, LastCmd: , IsCmd = False
      apr.-28 17:48:02 CM15A DEBUG CM15A.ParseRcv()1: data = 04/28 17:48:02 Rx PL HouseUnit: B8
      apr.-28 17:47:40 Device Control Device: Virtual status Device Valraam to Valraam dicht (0)
      apr.-28 17:47:40 Event Event Trigger "Virtual devices 15-Valraam dicht"
      apr.-28 17:47:40 Event Event Trigger "Valraam Valraam sluiten als afzuigkap uit"
      apr.-28 17:47:40 Device Control Device: Virtual status Device Afzuigkap to Afzuigkap uit (0)
      apr.-28 17:47:40 Event Event Trigger "Virtual devices 17-Afzuigkap uit"

      Comment


        #4
        Thanks for your system details and thank you for reporting the issue. Please download and install BETA v3.0.0.7 from https://forums.homeseer.com/forum/li...-beta-releases. The v.6 logging code was not checking the debug setting and this should be resolved in v.7

        Please let me know if you have any other issues with this version of the plugin. I will wait for feedback before releasing it to the HS updater.
        Best regards,
        -Mark-

        If you're not out on the edge, you're taking up too much room!
        Interested in 3D maps? Check out my company site: Solid Terrain Modeling

        Comment


          #5
          Thanks for your quick update. As it is about midnight here now I will check first thing tomorrow morning.
          I will let you know.
          ---
          Cor

          Comment


            #6
            Version 3.0.0.7 does switch off the debug output, great!
            I could make a new X10 device without a problem but I want to share some observations:

            1 - The features of the device is empty,while settings, status/graphics and CM15 are ok!

            2 - If I use the on/off switch in device view the icon does not change (in list and grid view) although the switch does work. I can see that because in the legacy device view the icon does change.

            Hope this helps.
            ---
            Cor

            Comment


              #7
              One more observation: In the help file Help.htm the reference to the picture (HS3_Procedure_Create_New_X10_Device.JPG) is not in capitals so an error is generated.
              ---
              Cor

              Comment


                #8
                Hi Cor, glad to know that the debug checkbox is now working! Also thanks for the feedback. Regarding your notes:
                1) Yes, 'Features' are new in HS4 and X10 devices do not have any features so the 'Features' tab will be blank.
                2) Did you check the Status/Graphics tab to be sure that there are icons assigned to the device values? I ask because this is working for me.
                3) Thanks for pointing out the help file upper/lower case issue, this has been resolved in BETA version 3.0.0.49.
                Best regards,
                -Mark-

                If you're not out on the edge, you're taking up too much room!
                Interested in 3D maps? Check out my company site: Solid Terrain Modeling

                Comment


                  #9
                  Hi Mark, as to point 2: Yes there are icons assigned to the device values (by default, see picture below) and I only see chaging icons in the legacy device management. In the HS4 devices tab it keeps showing 'off'.

                  As to point 3, you mentioned to make this change to 3.0.0.49 but I am using and was refering to the CM15A version 3.0.0.7.

                  Glad to help, regards,
                  Cor
                  Click image for larger version

Name:	image_88912.png
Views:	68
Size:	110.9 KB
ID:	1382632

                  Comment


                    #10
                    Hi Cor, sorry about the wrong plugin, I'll get the upper/lower case help file issue resolved for the CM15a Linux plugin.

                    Regarding your device icon issue in HS4, note that the plugin does not control theses and simply sets the device value in HS. HS then determines what to display to the user. Given all the changes between HS3 and HS4, and the fact that the CM15a Linux plugin is simply the HS3 version with some tweaks to allow device creation run under HS4, it is possible that there is some new issue that I'm not aware of. However, there has been no discussion of changes to setting device values in the developer forum. I'll check the latest docs to see if anything has changed. In the interim, you might want to post this issue in the HS4 Beta forum so that the HST dev team will see it.
                    Best regards,
                    -Mark-

                    If you're not out on the edge, you're taking up too much room!
                    Interested in 3D maps? Check out my company site: Solid Terrain Modeling

                    Comment

                    Working...
                    X