Announcement

Collapse
No announcement yet.

HST Compose plug-in not working after upgrade to 2.3.0.19 from 2.2.0.66

Collapse
This topic is closed.
X
X
Collapse
 
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts
Previous template Next
    #1

    HST Compose plug-in not working after upgrade to 2.3.0.19 from 2.2.0.66

    I just upgraded from HS 2.2.0.66 to 2.3.0.19 and none of my Lightolier Compose devices are working.

    It appears that HS doesn't call the Compose Scenes plug-in when controlling Compose devices, although the plug-in is shown in the "Plug-Ins" page, and HS does seem to initialize the plug-in at startup:

    1/2/2009 8:34:05 AM Startup Checking for available plug-ins
    1/2/2009 8:34:05 AM Info Found plug-in: AC-RF2 Processor, version: 1.0.2956.38478
    1/2/2009 8:34:05 AM Info Found plug-in: Compose Scenes, version: 2.0.0.4
    1/2/2009 8:34:05 AM Info Found plug-in: Compose CPLCOMM, version: 1.1.2365.32277
    1/2/2009 8:34:05 AM Info Found plug-in: Applied Digital Ocelot, version: 2.1.0.0
    1/2/2009 8:34:05 AM Startup Restoring device status
    1/2/2009 8:34:05 AM Startup Initializing Plug-Ins
    1/2/2009 8:34:05 AM Info Initializing Plug-in: Compose Scenes
    1/2/2009 8:34:05 AM COM Plugin Calling InitIO
    1/2/2009 8:34:05 AM Compose Scenes Compose Plug-in version 2.0.4
    1/2/2009 8:34:06 AM Info Finished initializing plug-in Compose Scenes
    1/2/2009 8:34:06 AM AC-RF2 Processor AC-RF2 Processor Plugin Version Release 1.0.2956.38478 Has Registered. Plugin Copyright (c) 2008 - AutomationCraft, LLC.
    1/2/2009 8:34:06 AM Info Initializing Plug-in: AC-RF2 Processor
    1/2/2009 8:34:06 AM AC-RF2 Processor Device #1 Initializing - (W800RF32 receiver on Com 4)
    1/2/2009 8:34:07 AM AC-RF2 Processor The RF receiver was initialized on Com 4 - Ready to start I/O
    1/2/2009 8:34:07 AM Info Finished initializing plug-in AC-RF2 Processor
    1/2/2009 8:34:07 AM Info Initializing X10 Plug-in: Compose CPLCOMM On COM Port 5
    1/2/2009 8:34:07 AM Info Initializing Plug-in: Compose CPLCOMM
    1/2/2009 8:34:07 AM Info Finished initializing X10 interface Compose CPLCOMM

    When setting my Kitchen lights e.g. to Scene C from the HS status page, this is now shown in the HS log, and the lights do not change:

    1/2/2009 9:42:42 AM Info Device: Kitchen Lights (D10) Value set to 4

    Before with HS 2.2.0.66, doing the same would log this:

    12/28/2008 5:25:46 AM ~!~Compose Scenes~!~Successful in setting D10 to (C) Scene C
    12/28/2008 5:25:46 AM ~!~Compose CPLCOMM Info~!~Sending DJck (D10 - Scene C Command)

    CPLCOMM shown above is my basic X10 plug-in that communicates with my Lightolier panel via RS232. HS is properly calling my X10 plug-in for non-Compose device types. Only requests to control Compose devices from HS are getting lost, i.e., they are not being processed by the Compose Scenes plug-in and thus not being passed to my X10 plug-in for transmission to the lighting panel.

    In the reverse, when CPLCOMM receives an RS232 message from the Lightolier panel (indicating manual dimmer press), CPLCOMM notifies HS via X10Event() and HS seems to handle the update correctly, showing the new status / scene in the UI. For example, pressing Scene B button on my Kitchen keypad causes the following log entry, and then the HS UI correctly shows Scene B.

    1/3/2009 8:28:09 AM Compose CPLCOMM Info Received DJpk (D10 - Scene B Command)
    1/3/2009 8:28:09 AM X10 Received D10 (Kitchen Lights) D Preset Dim 3
    Last edited by dschoppe; January 3, 2009, 08:44 AM. Reason: Describe issue more concisely.
    Tags: None
    #2
    Ticket #18490 submitted.

    Comment

      #3
      No response on my ticket yet, but I went ahead and installed the BETA Compose Scenes plug-in (vers 2.1.3049.25423) from the updater. It's a DLL versus the old OCX, but it's behaving exactly the same way - not being called by HS. Thus, I have X10 control only over non-Compose devices that bypass the Compose Scenes plug-in.

      Attached is an image showing the properties of the "Compose dimmer" device type in my system. I think these are unchanged from HS 2.2.066, but I can't recall.

      Is anyone using the Compose Scenes plug-in with HS 2.3.0.19?
      Attached Files

      Comment

        #4
        I think I may have found the problem. My existing Compose devices (after the HS 2.3.0.19 upgrade) all had their misc property in the DeviceClass set to:

        &HFFFFC900

        When I tried to create a new Compose device, I noticed it's misc value was different:

        &H0000C900

        Clearing the most significant 16-bits from the old compose device misc values (with a script/event) seems to have done the trick. HS is now calling the Compose Scene plug-in and requests are now reaching my X10 CPLCOMM plug-in to issue commands to the panel.

        HS logging does seem more verbose than before, with prints appearing from both the Compose Scenes plug-in and HS itself. Don't remember seeing both previously, but the lights are at least now working:

        1/3/2009 11:10:55 AM Info Command sent to Kitchen Lights: D10 Preset Dim Dimval: 3 Data: 0
        1/3/2009 11:10:55 AM Compose Scenes Successful in setting D10 [Kitchen Lights] to (B) Scene B
        1/3/2009 11:10:55 AM Info Device: Kitchen Lights (D10) Value set to 3
        1/3/2009 11:10:55 AM Compose CPLCOMM Info Sending DJpk (D10 - Scene B Command)

        Comment

          #5
          Don,

          This appears to be my problem as well but I'm a little lost on the solution.
          Where do I see the device class?
          Can you send me the script event or explain how I can write on to fix the problem. I have less than one dozen compose addresses so it may be easier to fix them manually if I knew where to look.

          Comment

            #6
            shersh,

            The following script should work to print out (to the HS log) information about the devices, including the misc field. Replace A1, A2, etc. in the main sub with your actual compose device addresses. If the upper bits in the misc flag are indeed set (all F's) then uncomment the last couple of lines of the script and re-run it to clear them. After, when you shutdown HS, the device database will be saved and the new values should "stick". Just let me know if you have any questions or problems.

            Best,
            Don


            Code:
            Sub Main(param as Object)
    LogDeviceInfo("A1")
    LogDeviceInfo("A2")
End Sub

Public Sub LogDeviceInfo(ByRef device As String)
    'Log specified device's current status, value, and string
    Dim dval As Long = hs.DeviceValue(device)
    Dim dstat As Integer = hs.DeviceStatus(device)
    Dim dstr As String = hs.DeviceString(device)
    hs.WriteLog("Debug", device & " Status=" & dstat & " Value=" & dval & " String=" & dstr)

    'Log specified device's DeviceClass properties
    Dim dvRef As Long = hs.GetDeviceRef(device)
    Dim dv As Object = hs.GetDeviceByRef(dvRef)
    hs.WriteLog("Debug", device & " Misc=" & Hex(dv.misc))
    hs.WriteLog("Debug", device & " Graphics=" & dv.graphics)
    hs.WriteLog("Debug", device & " Values=" & dv.values)
    hs.WriteLog("Debug", device & " Buttons=" & dv.buttons)

    'Clear most significant 16 bits of misc
    'dv.misc = dv.misc And &H0000FFFF
    'hs.WriteLog("Debug", device & " Updated Misc=" & Hex(dv.misc))

End Sub

            Comment

              #7
              Thanks Don,

              I'll give it a shot tomorrow.

              Comment

                #8
                Don,

                Thank you that script did the trick. I'm back in business!

                Comment

                  #9
                  Originally posted by shersh View Post
                  Don,

                  Thank you that script did the trick. I'm back in business!
                  You're welcome, glad it helped!

                  Don

                  Comment

                  Previous template Next
                  Working...
                  X