Announcement

Collapse
No announcement yet.

Ocelot Device Does Not Show Up in List for Event Triggers

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

  • Ocelot Device Does Not Show Up in List for Event Triggers

    I do not suspect this to be a ADIOcelot issue but figured someone might have a suggestion.

    I am running HS 2.1.115 with ADIOcelot 1.13.0.2. I hadn't made any changes with my Ocelot since moving to HS 2.X and I just now added an input for a float switch monitoring the water level in my sump pump. The new device shows on HS Status page and updates when I manually trigger the switch. However, when I go to create an event, the device is not listed in the devices list and so I am unable to create an event that triggers when the float switch indicates high water.

    Is there something simple I am missing? Should I not be using HS 2.1.115?

    Any suggestions would be appreciated.
    Jim Doolittle

    My Twitter
    My Hardware & Software

  • #2
    Jim,
    I think there's a problem with HomeSeer and or the Ocelot plugin but try running this script and see if it doesn't fix the device and allow it to show up. There seems to be a problem with this bit not getting set on new devices.

    Sub Main
    dim en
    dim dv

    set en=hs.GetDeviceEnumerator
    do while not en.Finished
    set dv = en.GetNext
    dv.misc = dv.misc and not &H20000
    loop

    End Sub
    -Rupp
    sigpic

    Comment


    • #3
      I have a ticket open with Rich for this. What he had me check last night was if bit H&20000 is set on in the device misc property. I think they just added this somewhere after 88 - the bit prevents the device from being listed in the device status dropdown. Try clearing that bit and see if the devices show up.

      I was likely going to post something tonight to ask Michael if he could look within the plugin code. It appears that what's happening is that when a device is created all the high bits are getting set on- i.e. the misc property is FFFF8000 when it probably should be 00008000. What I haven't heard yet is whether the bits are getting set within HS or within the plugin. (It looks like a signed integer rollover to me is happening somewhere but that's a total shot in the dark)

      jim

      edit: should have known I took too long typing to beat Rupp

      Comment


      • #4
        ADIOcelot has all the upper bits set to 0. There was another user that posted a similiar problem and he submitted a help desk ticket as well.

        Comment


        • #5
          Script worked! Thanks Rupp.
          Jim Doolittle

          My Twitter
          My Hardware & Software

          Comment


          • #6
            I heard back from Rich on this. I had posted some additional ifnormation to him that I had experimented with a vbscript setting the misc property of a virtual device. Only the following statement caused a problem "dv.misc = &h8000". He replied with the following:

            RJH wrote:
            "The problem is that we changed the dv.misc field from a short (VB6 Integer), to a vb.net Integer (VB6 Long). This gives us more bits. However, in VBScript the constant "&h8000" is always interpreted as a short (16 bits). So when you assign it to dv.misc, it converts it to a negative number. The trick is to tell VBScript that the constant is a long. Declare it like this: &h8000& I tried your script with this change and it worked ok."

            It does work within a vbscript using Rich's suggestion.

            Michael, new devices created by adiocolet plugin in HS 2.1 are created with the high bits set on (FFFF8000 vs. 00008000 ) - is it perhaps getting changed by the conversion between vb6 and vb.net systems?

            Also, after reading a little bit it looks like having the other high bits set might also cause problems. So far they've used &h10000 (restrict to ON/OFF device actions only) and &h20000 (don't list in status triggers). So I modifed the above script to reset all the high bits and restricted it to change just adiocelot devices. I'll add it below for anyone that might need it.
            jim

            Sub Main
            dim en
            dim dv
            set en=hs.GetDeviceEnumerator
            do while not en.Finished
            set dv = en.GetNext
            if dv.interface = "ADIOcelot" then
            dv.misc = dv.misc and not &HFFFF0000
            end if
            loop
            End Sub

            Comment


            • #7
              This script worked form me.

              Thank you Rupp and Jim.

              Best regards,
              Clement

              Comment


              • #8
                Ocelot devices not available as triggers

                For Michael.

                I also put in a help ticket (100-11206) as follows:

                "In the process of creating a CONDITIONAL event, when I select DEVICE as a Trigger, only the first 16 devices are available. There are no scroll bars and a blank is shown after the 16th device (Ocelot variables). This system contains over 100 devices (Ocelot variables & I/O)

                This problem is not present when selecting action devices."

                Greg Hughes from the Help Desk wrote:

                "This is an ongoing problem with the ADIOcelot plugin. I would recommend asking Michael if he has addressed this problem via the Homeseer bulletin board in the ADIOcelot plugin forum."

                Well, I was unable to locate the above mentioned forum, so I posted here.

                I am presently using HS 2.1.142.0

                My previous build HS 2.1.102.0 worked fine. I was advised to upgrade by Homeseer to correct a memory leak.

                Any help would be appreciated.

                JC

                Comment


                • #9
                  ADIOcelot plugin forum

                  I must have been drunk. Found the proper forum. Will try the new update.

                  Sorry about the mixup.

                  JC

                  Comment


                  • #10
                    Jcc,
                    What did you mean by "Found the proper forum"?
                    -Rupp
                    sigpic

                    Comment


                    • #11
                      Your right it's not a "forum" but a thread, the one preceding this one.


                      JC

                      Comment


                      • #12
                        Missing devices (refer to post Dec 10th)

                        After going through most of the ADIOcelot plugin thread (all 5 pages) I realized that the last post was March of this year. This means that I am already running the latest version so my initial post is valid.


                        So Michael, any comments on HS's comment?

                        JC

                        Comment


                        • #13
                          The latest version of the plugin, 1.14.4, is in the first post of the Adiocelot plugin thread. Michael edits the post so there is a list the changes and the latest plugin in always in the same place.

                          If you have devices that were created using the older version of the plugin then you need to run the script posted earlier in this thread to fix them.
                          jim

                          p.s. just checked and see that 1.14.4 is in the updater now as well.

                          Comment


                          • #14
                            Sorry for the late reply.

                            Thank you for pointing that out to me. I will implement the upgrade and script this week.

                            Happy New Year to all!

                            JC

                            Comment


                            • #15
                              I'm having this problem as well but runing the above script doesn't help.
                              When I try to create a CONDITION script and select devices the OCelot devices arent' listed.

                              I'm running the latest version of both homeseer and adiocelot on Win XP.

                              Any ideas?

                              Thanks
                              JOel

                              Comment

                              Working...
                              X