Announcement

Collapse
No announcement yet.

ISY Insteon Beta 1.0.1.8 - Updated 1/11/2009

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

    #46
    Originally posted by bpwwer View Post
    Hi Paul,

    I just got the same message but I haven't had a chance to try it. I probably won't until sometime tonight. I'm not aware of any changes to the API that would effect the operation of the plug-in, but given the number of changes in the firmware, I'd suggest waiting until I have a chance to verify it.
    Ok, to follow up. I've upgraded my ISY to 2.7.9 and the plug-in appears to be working fine. I have not done exhaustive testing at this point. However, I do not see any signs that would indicate abnormal behavior.

    So this combination is "officially" blessed. At least as much as Alpha level firmware and a beta level plug-in can be.
    --
    Bob Paauwe
    ISYInsteon Plug-in
    http://www.bobsplace.com/ISYInsteon/

    Comment


      #47
      Issue?

      It may be unrelated to 1.0.6 and 2.7.9 but following was in log several hours after upgrading:

      1/8/2010 11:27:25 PM ISY Insteon ISY internal node () type is set to unknown.
      1/8/2010 11:27:25 PM ISY Insteon ISY internal node () type is set to unknown.
      1/8/2010 11:27:25 PM ISY Insteon ISY internal node () type is set to unknown.
      1/8/2010 11:27:25 PM ISY Insteon ISY internal node () type is set to unknown.

      Comment


        #48
        Just got this:

        This is unformatted text. It actually contains html code with drop down lists etc. Let me know if you want me to email html version.

        1/9/2010 8:26:20 AM ISY Insteon *** Condition UI support! ****
        1/9/2010 8:26:20 AM ISY Insteon ConditionUI: 1 -
        1/9/2010 8:26:20 AM ISY Insteon ConditionUI: 2 -
        1/9/2010 8:26:20 AM ISY Insteon *** Condition UI support! ****
        1/9/2010 8:26:20 AM ISY Insteon *** Condition UI HTML support! ****
        1/9/2010 8:26:20 AM ISY Insteon ConditionUIHTML: 1 -
        1/9/2010 8:26:20 AM ISY Insteon returning: ISY Weather Conditions Weather Bug Conditions
        Weather Value: TemperatureHigh TemperatureLow TemperatureTemperature Rateequalsnot equalsless thangreater thanhas beenminiumumexactly minutes
        1/9/2010 8:26:20 AM ISY Insteon ConditionUIHTML: 2 -
        1/9/2010 8:26:20 AM ISY Insteon returning: ISY Energy Monitor Conditions Weather Bug Conditions

        1/9/2010 8:26:20 AM ISY Insteon ConditionUIHTML: 3 -
        1/9/2010 8:26:20 AM ISY Insteon returning:
        1/9/2010 8:26:49 AM ISY Insteon *** Condition UI support! ****
        1/9/2010 8:26:49 AM ISY Insteon ConditionUI: 1 -
        1/9/2010 8:26:49 AM ISY Insteon ConditionUI: 2 -
        1/9/2010 8:26:49 AM ISY Insteon *** Condition UI support! ****
        1/9/2010 8:26:49 AM ISY Insteon ConditionUIHTML: 1 -
        1/9/2010 8:26:49 AM ISY Insteon returning: ISY Weather Conditions Weather Bug Conditions
        Weather Value: TemperatureHigh TemperatureLow TemperatureTemperature Rateequalsnot equalsless thangreater thanhas beenminiumumexactly minutes
        1/9/2010 8:26:49 AM ISY Insteon ConditionUIHTML: 2 -
        1/9/2010 8:26:49 AM ISY Insteon returning: ISY Energy Monitor Conditions Weather Bug Conditions

        1/9/2010 8:26:49 AM ISY Insteon ConditionUIHTML: 3 -
        1/9/2010 8:26:49 AM ISY Insteon returning:
        1/9/2010 8:26:56 AM ISY Insteon *** Condition UI support! ****
        1/9/2010 8:26:56 AM ISY Insteon ConditionUI: 1 -
        1/9/2010 8:26:56 AM ISY Insteon ConditionUI: 2 -
        1/9/2010 8:26:56 AM ISY Insteon *** Condition UI support! ****
        1/9/2010 8:26:56 AM ISY Insteon ConditionUIHTML: 1 -
        1/9/2010 8:26:56 AM ISY Insteon returning: ISY Weather Conditions Weather Bug Conditions
        Weather Value: TemperatureHigh TemperatureLow TemperatureTemperature Rateequalsnot equalsless thangreater thanhas beenminiumumexactly minutes
        1/9/2010 8:26:56 AM ISY Insteon ConditionUIHTML: 2 -
        1/9/2010 8:26:56 AM ISY Insteon returning: ISY Energy Monitor Conditions Weather Bug Conditions

        1/9/2010 8:26:56 AM ISY Insteon ConditionUIHTML: 3 -
        1/9/2010 8:26:56 AM ISY Insteon returning:
        1/9/2010 8:28:08 AM ISY Insteon *** Condition UI support! ****
        1/9/2010 8:28:08 AM ISY Insteon ConditionUI: 1 -
        1/9/2010 8:28:08 AM ISY Insteon ConditionUI: 2 -
        1/9/2010 8:28:08 AM ISY Insteon *** Condition UI support! ****
        1/9/2010 8:28:08 AM ISY Insteon ConditionUIHTML: 1 -
        1/9/2010 8:28:08 AM ISY Insteon returning: ISY Weather Conditions Weather Bug Conditions
        Weather Value: TemperatureHigh TemperatureLow TemperatureTemperature Rateequalsnot equalsless thangreater thanhas beenminiumumexactly minutes
        1/9/2010 8:28:08 AM ISY Insteon ConditionUIHTML: 2 -
        1/9/2010 8:28:08 AM ISY Insteon returning: ISY Energy Monitor Conditions Weather Bug Conditions

        1/9/2010 8:28:08 AM ISY Insteon ConditionUIHTML: 3 -
        1/9/2010 8:28:08 AM ISY Insteon returning:
        1/9/2010 8:28:18 AM ISY Insteon *** Condition UI support! ****
        1/9/2010 8:28:18 AM ISY Insteon ConditionUI: 1 -
        1/9/2010 8:28:18 AM ISY Insteon ConditionUI: 2 -
        1/9/2010 8:28:18 AM ISY Insteon *** Condition UI support! ****
        1/9/2010 8:28:18 AM ISY Insteon ConditionUIHTML: 1 -
        1/9/2010 8:28:18 AM ISY Insteon returning: ISY Weather Conditions Weather Bug Conditions
        Weather Value: TemperatureHigh TemperatureLow TemperatureTemperature Rateequalsnot equalsless thangreater thanhas beenminiumumexactly minutes
        1/9/2010 8:28:18 AM ISY Insteon ConditionUIHTML: 2 -
        1/9/2010 8:28:18 AM ISY Insteon returning: ISY Energy Monitor Conditions Weather Bug Conditions

        1/9/2010 8:28:18 AM ISY Insteon ConditionUIHTML: 3 -
        1/9/2010 8:28:18 AM ISY Insteon returning:
        1/9/2010 8:28:30 AM ISY Insteon *** Condition UI support! ****
        1/9/2010 8:28:30 AM ISY Insteon ConditionUI: 1 -
        1/9/2010 8:28:30 AM ISY Insteon ConditionUI: 2 -
        1/9/2010 8:28:30 AM ISY Insteon *** Condition UI support! ****
        1/9/2010 8:28:30 AM ISY Insteon ConditionUIHTML: 1 -
        1/9/2010 8:28:30 AM ISY Insteon returning: ISY Weather Conditions Weather Bug Conditions
        Weather Value: TemperatureHigh TemperatureLow TemperatureTemperature Rateequalsnot equalsless thangreater thanhas beenminiumumexactly minutes
        1/9/2010 8:28:30 AM ISY Insteon ConditionUIHTML: 2 -
        1/9/2010 8:28:30 AM ISY Insteon returning: ISY Energy Monitor Conditions Weather Bug Conditions

        1/9/2010 8:28:30 AM ISY Insteon ConditionUIHTML: 3 -
        1/9/2010 8:28:30 AM ISY Insteon returning:
        1/9/2010 8:28:37 AM Database Item Saving Event Security Partition Armed Stay
        1/9/2010 8:28:43 AM ISY Insteon *** Condition UI support! ****
        1/9/2010 8:28:43 AM ISY Insteon ConditionUI: 1 -
        1/9/2010 8:28:43 AM ISY Insteon ConditionUI: 2 -
        1/9/2010 8:28:43 AM ISY Insteon *** Condition UI support! ****
        1/9/2010 8:28:43 AM ISY Insteon ConditionUIHTML: 1 -
        1/9/2010 8:28:43 AM ISY Insteon returning: ISY Weather Conditions Weather Bug Conditions
        Weather Value: TemperatureHigh TemperatureLow TemperatureTemperature Rateequalsnot equalsless thangreater thanhas beenminiumumexactly minutes
        1/9/2010 8:28:43 AM ISY Insteon ConditionUIHTML: 2 -
        1/9/2010 8:28:43 AM ISY Insteon returning: ISY Energy Monitor Conditions Weather Bug Conditions

        1/9/2010 8:28:43 AM ISY Insteon ConditionUIHTML: 3 -
        1/9/2010 8:28:43 AM ISY Insteon returning:
        1/9/2010 8:28:49 AM ISY Insteon *** Condition UI support! ****
        1/9/2010 8:28:49 AM ISY Insteon ConditionUI: 1 -
        1/9/2010 8:28:49 AM ISY Insteon ConditionUI: 2 -
        1/9/2010 8:28:49 AM ISY Insteon *** Condition UI support! ****
        1/9/2010 8:28:49 AM ISY Insteon ConditionUIHTML: 1 -
        1/9/2010 8:28:49 AM ISY Insteon returning: ISY Weather Conditions Weather Bug Conditions
        Weather Value: TemperatureHigh TemperatureLow TemperatureTemperature Rateequalsnot equalsless thangreater thanhas beenminiumumexactly minutes
        1/9/2010 8:28:49 AM ISY Insteon ConditionUIHTML: 2 -
        1/9/2010 8:28:49 AM ISY Insteon returning: ISY Energy Monitor Conditions Weather Bug Conditions

        1/9/2010 8:28:49 AM ISY Insteon ConditionUIHTML: 3 -
        1/9/2010 8:28:49 AM ISY Insteon returning:
        1/9/2010 8:28:56 AM ISY Insteon *** Condition UI support! ****
        1/9/2010 8:28:56 AM ISY Insteon ConditionUI: 1 -
        1/9/2010 8:28:56 AM ISY Insteon ConditionUI: 2 -
        1/9/2010 8:28:56 AM ISY Insteon *** Condition UI support! ****
        1/9/2010 8:28:56 AM ISY Insteon ConditionUIHTML: 1 -
        1/9/2010 8:28:56 AM ISY Insteon returning: ISY Weather Conditions Weather Bug Conditions
        Weather Value: TemperatureHigh TemperatureLow TemperatureTemperature Rateequalsnot equalsless thangreater thanhas beenminiumumexactly minutes
        1/9/2010 8:28:56 AM ISY Insteon ConditionUIHTML: 2 -
        1/9/2010 8:28:56 AM ISY Insteon returning: ISY Energy Monitor Conditions Weather Bug Conditions

        1/9/2010 8:28:56 AM ISY Insteon ConditionUIHTML: 3 -
        1/9/2010 8:28:56 AM ISY Insteon returning:
        1/9/2010 8:29:03 AM Database Item Saving Event Security Partition Armed Stay
        1/9/2010 8:29:14 AM ISY Insteon *** Condition UI support! ****
        1/9/2010 8:29:14 AM ISY Insteon ConditionUI: 1 -
        1/9/2010 8:29:14 AM ISY Insteon ConditionUI: 2 -
        1/9/2010 8:29:14 AM ISY Insteon *** Condition UI support! ****
        1/9/2010 8:29:14 AM ISY Insteon ConditionUIHTML: 1 -
        1/9/2010 8:29:14 AM ISY Insteon returning: ISY Weather Conditions Weather Bug Conditions
        Weather Value: TemperatureHigh TemperatureLow TemperatureTemperature Rateequalsnot equalsless thangreater thanhas beenminiumumexactly minutes
        1/9/2010 8:29:14 AM ISY Insteon ConditionUIHTML: 2 -
        1/9/2010 8:29:14 AM ISY Insteon returning: ISY Energy Monitor Conditions Weather Bug Conditions

        1/9/2010 8:29:14 AM ISY Insteon ConditionUIHTML: 3 -
        1/9/2010 8:29:14 AM ISY Insteon returning:
        1/9/2010 8:29:22 AM ISY Insteon *** Condition UI support! ****
        1/9/2010 8:29:22 AM ISY Insteon ConditionUI: 1 -
        1/9/2010 8:29:22 AM ISY Insteon ConditionUI: 2 -
        1/9/2010 8:29:22 AM ISY Insteon *** Condition UI support! ****
        1/9/2010 8:29:22 AM ISY Insteon ConditionUIHTML: 1 -
        1/9/2010 8:29:22 AM ISY Insteon returning: ISY Weather Conditions Weather Bug Conditions
        Weather Value: TemperatureHigh TemperatureLow TemperatureTemperature Rateequalsnot equalsless thangreater thanhas beenminiumumexactly minutes
        1/9/2010 8:29:22 AM ISY Insteon ConditionUIHTML: 2 -
        1/9/2010 8:29:22 AM ISY Insteon returning: ISY Energy Monitor Conditions Weather Bug Conditions

        1/9/2010 8:29:22 AM ISY Insteon ConditionUIHTML: 3 -
        1/9/2010 8:29:22 AM ISY Insteon returning:
        1/9/2010 8:29:28 AM ISY Insteon *** Condition UI support! ****
        1/9/2010 8:29:28 AM ISY Insteon ConditionUI: 1 -
        1/9/2010 8:29:28 AM ISY Insteon ConditionUI: 2 -
        1/9/2010 8:29:28 AM ISY Insteon *** Condition UI support! ****
        1/9/2010 8:29:28 AM ISY Insteon ConditionUIHTML: 1 -
        1/9/2010 8:29:28 AM ISY Insteon returning: ISY Weather Conditions Weather Bug Conditions
        Weather Value: TemperatureHigh TemperatureLow TemperatureTemperature Rateequalsnot equalsless thangreater thanhas beenminiumumexactly minutes
        1/9/2010 8:29:28 AM ISY Insteon ConditionUIHTML: 2 -
        1/9/2010 8:29:28 AM ISY Insteon returning: ISY Energy Monitor Conditions Weather Bug Conditions

        1/9/2010 8:29:28 AM ISY Insteon ConditionUIHTML: 3 -
        1/9/2010 8:29:28 AM ISY Insteon returning:
        1/9/2010 8:29:35 AM ISY Insteon *** Condition UI support! ****
        1/9/2010 8:29:35 AM ISY Insteon ConditionUI: 1 -
        1/9/2010 8:29:35 AM ISY Insteon ConditionUI: 2 -
        1/9/2010 8:29:35 AM ISY Insteon *** Condition UI support! ****
        1/9/2010 8:29:35 AM ISY Insteon ConditionUIHTML: 1 -
        1/9/2010 8:29:35 AM ISY Insteon returning: ISY Weather Conditions Weather Bug Conditions
        Weather Value: TemperatureHigh TemperatureLow TemperatureTemperature Rateequalsnot equalsless thangreater thanhas beenminiumumexactly minutes
        1/9/2010 8:29:35 AM ISY Insteon ConditionUIHTML: 2 -
        1/9/2010 8:29:35 AM ISY Insteon returning: ISY Energy Monitor Conditions Weather Bug Conditions

        1/9/2010 8:29:35 AM ISY Insteon ConditionUIHTML: 3 -
        1/9/2010 8:29:35 AM ISY Insteon returning:

        Comment


          #49
          Originally posted by hart2hart View Post
          This is unformatted text. It actually contains html code with drop down lists etc. Let me know if you want me to email html version.

          1/9/2010 8:26:20 AM ISY Insteon *** Condition UI support! ****
          These are all my debugging messages as I try to get condition support working. They can be safely ignored.

          But since this beta is now required if you update the ISY firmware to one of the recent alphas, I went ahead and removed this non-working code. See the first post in this thread for a new version.
          --
          Bob Paauwe
          ISYInsteon Plug-in
          http://www.bobsplace.com/ISYInsteon/

          Comment


            #50
            Multiple ISY Programs Mapped

            Hi, I'm not sure if this is related to ISY 2.7.9 but I just upgraded and Homeseer now shows multiple instances of all my ISY Programs with separate unit codes. (see attached for example)

            ISY Scenes and Devices seem to have normal 1:1 mappings.

            Removing programs from ISY does not appear to remove them from Homeseer.

            Filter list in plug-in appears normal, except programs I delete from ISY still show there.

            Tried, restore, reset, reboot homeseer, etc.

            Very new at this so be gentle if I did something dumb...

            Thanks!
            Rob




            [IMG]file:///C:/DOCUME%7E1/Rob/LOCALS%7E1/Temp/moz-screenshot.png[/IMG]
            Attached Files

            Comment


              #51
              Hi Rob,

              I'm sorry you're having this problem. The plug-in uses the program ID that the ISY creates for each program as a link between the HomeSeer device record and the ISY program. If that changes (which it shouldn't be), then it can leave an orphaned HomeSeer device record. The other possible cause would be if the HomeSeer device record somehow got changed so that the plug-in is no longer associated with that record.

              There's no harm in removing those records from HomeSeer (other than the effort to fix any HomeSeer events or scripts that reference them).

              My suggestion is to delete the non-working program entries (or all of them if you can't tell which ones are currently working) from HomeSeer. If you do end up deleting all of them, the plug-in will recreate the correct entries the next time it restarts or if you re-sync the plug-in with the ISY from the button on the plug-in's status page.

              If you continue to have this problem, try to isolate what the steps are to reproduce it and I'll work with you to figure out what's causing and and we'll get it fixed.

              Originally posted by picc02766 View Post
              Hi, I'm not sure if this is related to ISY 2.7.9 but I just upgraded and Homeseer now shows multiple instances of all my ISY Programs with separate unit codes. (see attached for example)

              ISY Scenes and Devices seem to have normal 1:1 mappings.

              Removing programs from ISY does not appear to remove them from Homeseer.

              Filter list in plug-in appears normal, except programs I delete from ISY still show there.

              Tried, restore, reset, reboot homeseer, etc.

              Very new at this so be gentle if I did something dumb...

              Thanks!
              Rob
              --
              Bob Paauwe
              ISYInsteon Plug-in
              http://www.bobsplace.com/ISYInsteon/

              Comment


                #52
                Originally posted by bpwwer View Post
                Hi Rob,

                I'm sorry you're having this problem. The plug-in uses the program ID that the ISY creates for each program as a link between the HomeSeer device record and the ISY program. If that changes (which it shouldn't be), then it can leave an orphaned HomeSeer device record. The other possible cause would be if the HomeSeer device record somehow got changed so that the plug-in is no longer associated with that record.

                There's no harm in removing those records from HomeSeer (other than the effort to fix any HomeSeer events or scripts that reference them).

                My suggestion is to delete the non-working program entries (or all of them if you can't tell which ones are currently working) from HomeSeer. If you do end up deleting all of them, the plug-in will recreate the correct entries the next time it restarts or if you re-sync the plug-in with the ISY from the button on the plug-in's status page.

                If you continue to have this problem, try to isolate what the steps are to reproduce it and I'll work with you to figure out what's causing and and we'll get it fixed.
                Thanks Bob,

                I first tried deleting the bogus entries directly from Homeseer, but a resync would not re-create the correct entries (didn't try a restart). What did seem to do the trick was unchecking everything in the plug-in filter list which cleared everything out of homeseer, then re-checking them. As you said the only downside to this was the event/script references all broke but I only had a few so that was no big deal. All seems OK at the moment.

                I do get the following entries in the Homeseer log (for all devices/scenes/programs) every so often - are these normal? (logging is set to Warnings for plug-in):

                .<appears to be one line for each ISY device/scene/program>
                .
                .
                1/10/2010 12:14:09 AM ISY Insteon MAIN: ISY notification QueryAll not (yet) mapped to HomeSeer device.
                1/10/2010 12:14:09 AM ISY Insteon MAIN: ISY notification KPL Sink Load On not (yet) mapped to HomeSeer device.
                1/10/2010 12:14:09 AM ISY Insteon MAIN: ISY notification Daybreak not (yet) mapped to HomeSeer device.
                1/10/2010 12:14:09 AM ISY Insteon MAIN: ISY notification Sunset not (yet) mapped to HomeSeer device.
                1/10/2010 12:14:09 AM ISY Insteon MAIN: ISY notification Ext. Motion Disable not (yet) mapped to HomeSeer device.
                1/10/2010 12:14:09 AM ISY Insteon MAIN: ISY notification Guests Present not (yet) mapped to HomeSeer device.
                .
                .
                .

                For future reference, what is the proper procedure to "reset" the plug-in when installing an ISY update? I noticed the ISY version that the plug-in reports does not update to the newly installed version if I just do a resync. This morning I disabled the plug-in and then re-enabled it (via the Homeseer interfaces screen) which then reported the correct version, but it was at that point I first noticed all the bogus entries (it could have happened prior to that but I just didn't notice it). I'll pay more attention next update.

                Also I'm not clear what "Reset Device Types" does and when it should be used.

                Thanks again for your help!
                Rob

                Comment


                  #53
                  Originally posted by picc02766 View Post
                  Thanks Bob,

                  I first tried deleting the bogus entries directly from Homeseer, but a resync would not re-create the correct entries (didn't try a restart). What did seem to do the trick was unchecking everything in the plug-in filter list which cleared everything out of homeseer, then re-checking them. As you said the only downside to this was the event/script references all broke but I only had a few so that was no big deal. All seems OK at the moment.
                  For future reference, restarting the plug-in would have been a better way to get the devices recreated. I though a re-sync, would do basically the same thing as a restart. I'll have to go double check that feature to make sure it is still working.

                  I do get the following entries in the Homeseer log (for all devices/scenes/programs) every so often - are these normal? (logging is set to Warnings for plug-in):

                  .<appears to be one line for each ISY device/scene/program>
                  .
                  .
                  1/10/2010 12:14:09 AM ISY Insteon MAIN: ISY notification QueryAll not (yet) mapped to HomeSeer device.
                  1/10/2010 12:14:09 AM ISY Insteon MAIN: ISY notification KPL Sink Load On not (yet) mapped to HomeSeer device.
                  nsteon MAIN: ISY notification Guests Present not (yet) mapped to HomeSeer device.
                  You should only see this for devices/scenes/programs that you have the plug-in filtering. When the plug-in is querying the ISY for the device/scenes or programs, it checks to make sure the corresponding HomeSeer device exist. If it doesn't, it spits our that notice. (then if it's something being filtered, it ignores it, otherwise it should try to create a HomeSeer device record). If you are seeing this for all devices, then something is wrong.

                  For future reference, what is the proper procedure to "reset" the plug-in when installing an ISY update? I noticed the ISY version that the plug-in reports does not update to the newly installed version if I just do a resync. This morning I disabled the plug-in and then re-enabled it (via the Homeseer interfaces screen) which then reported the correct version, but it was at that point I first noticed all the bogus entries (it could have happened prior to that but I just didn't notice it). I'll pay more attention next update.
                  Normally, you don't have to do anything when updating the ISY's firmware. The plug-in will attempt to re-connect and should continue working just fine once the ISY has re-booted with the new firmware. There may be cases where enough has changed in the firmware that stopping and restarting the plug-in would be warranted.

                  You're right, that the plug-in doesn't update the firmware version on the status page. It only gets that information from the ISY when the plug-in starts.

                  Also I'm not clear what "Reset Device Types" does and when it should be used.
                  When the plug-in first creates a HomeSeer device record for a device, it sets some flags that tell HomeSeer what type of device it is. As new Insteon devices are introduced, the full capabilities of the device may not be known by the plug-in. If the HomeSeer device record needs to be updated later to take full advantage of the device, "Reset Device Types" tells the plug-in to do that.

                  This isn't done as part of the normal start up of the plug-in simply because it would slow down the start up process and I've tried to optimize that as much as possible.
                  --
                  Bob Paauwe
                  ISYInsteon Plug-in
                  http://www.bobsplace.com/ISYInsteon/

                  Comment


                    #54
                    Originally posted by bpwwer View Post

                    You should only see this for devices/scenes/programs that you have the plug-in filtering. When the plug-in is querying the ISY for the device/scenes or programs, it checks to make sure the corresponding HomeSeer device exist. If it doesn't, it spits our that notice. (then if it's something being filtered, it ignores it, otherwise it should try to create a HomeSeer device record). If you are seeing this for all devices, then something is wrong.

                    Bob, thanks for the detailed reply. If I do a resync I still get the "...not (yet) mapped..." messages in my Homeseer log although everything seems to be working normally otherwise.

                    There are 171 lines of this message, but after more careful examination, many of them are duplicates - I counted 133 unique ISY items. According to the plug-in my ISY has 62 Programs, 29 Scenes and 46 Devices.

                    Also there were these two unique lines about halfway through the list:
                    COMM: --> Thread was being aborted.
                    COMM: ISY network communication notification read timeout:

                    Clearly there is still something wrong with my setup, but I'm not too sure where to go from here. In the ISY console there does not seem to be any sign of bogus devices including if I do a "generate topology".

                    Thanks for any help you can provide!

                    Rob
                    Attached Files

                    Comment


                      #55
                      Originally posted by picc02766 View Post
                      Bob, thanks for the detailed reply. If I do a resync I still get the "...not (yet) mapped..." messages in my Homeseer log although everything seems to be working normally otherwise.

                      There are 171 lines of this message, but after more careful examination, many of them are duplicates - I counted 133 unique ISY items. According to the plug-in my ISY has 62 Programs, 29 Scenes and 46 Devices.
                      That sounds like it is working correctly. When you resync, it closes the connection to the ISY, clears out the list of devices, re-connects to the ISY and when the ISY sends the information for each device, it is re-mapped (or a new mapping is created if one didn't exist). Because of the asynchoronous way the ISY sends information, it is possible for the ISY to send information about a device before the plug-in has retrieved the device list from the ISY. That's really all this message means.

                      You should see these messages if you do a re-sync. You'll also see these for any devices that are filtered. It's a way to notify you that the plug-in saw a message for a device that isn't currently associated with any HomeSeer device.

                      If you are seeing them during normal operation (on non-filtered devices) or if you are still getting duplicate HomeSeer devices created, that would be a problem.

                      Also there were these two unique lines about halfway through the list:
                      COMM: --> Thread was being aborted.
                      COMM: ISY network communication notification read timeout:
                      Correct, that is the plug-in shutting down communication with the ISY so it can re-start it. That's really the cleanest way to get the plug-in and the ISY in sync.

                      Clearly there is still something wrong with my setup, but I'm not too sure where to go from here. In the ISY console there does not seem to be any sign of bogus devices including if I do a "generate topology".
                      Are you still getting duplicate HomeSeer devices? If not, then I don't think anything is wrong.

                      The re-sync operation isn't something that should need to be used in normal operation. There are cases where the ISY can get bogged down and communications between it and the plug-in can fail temporarily. If this happens, the device information could get out of sync between the ISY and the plug-in. This is very rare and only tends to happen when a lot of device changes are happening using the ISY console (adding / renaming / adding new programs).
                      --
                      Bob Paauwe
                      ISYInsteon Plug-in
                      http://www.bobsplace.com/ISYInsteon/

                      Comment


                        #56
                        Originally posted by bpwwer View Post
                        If you are seeing them during normal operation (on non-filtered devices) or if you are still getting duplicate HomeSeer devices created, that would be a problem.
                        Yes I am still seeing the "...not (yet) mapped..." messages in the Homeseer log during normal operation without doing a resync (or anything else). I am not filtering anything. Only changes are that I may have edited one or two of the programs on the ISY over the past 24 hours, but that's all. Log level of the plug-in is set to "Warnings".

                        I received a block of 95 such messages about 5 hours ago and then twice more about a minute apart approx. 12 hours before that. Beyond that I don't know the exact time frames but I have been seeing these for many days now. I'll watch the log more closely to see how often this recurs.

                        Within the 95 messages there are many "duplicates" if that means anything. There seem to be 1 or 2 such messages for each of my 62 ISY programs - I did not notice any Scenes or Devices in the list so it seems confined to programs.

                        Originally posted by bpwwer View Post
                        Are you still getting duplicate HomeSeer devices? If not, then I don't think anything is wrong.
                        No, aside from the duplicate "...not (yet) mapped..." messages in the log I am not aware of any duplicate devices within Homeseer or ISY.

                        Thanks again for your help,
                        Rob

                        Comment


                          #57
                          Hi Rob,

                          Thanks for the clarification. There are only two conditions that can lead to that message so it should be easy to track down which one it is. The messages from the ISY that are leading to that log message are going to happen whenever the ISY changes a program. This could be when a group of programs changes from true to false or if they are enabled or disabled or if they are executing or stopped.

                          You say they happen somewhat infrequently. That should help narrow down what is happening. Is there a program that enables a bunch of other programs at sunset and then disables them at sunrise for instance?

                          The two things that will cause the message are:

                          1) The ISY is sending a message with out the program ID. That seems unlikely but maybe there is something new going on with the new firmware and the plug-in isn't correctly parsing the message. By setting the plug-in log level to verbose debug, it will output all the raw messages it receives from the ISY. This is a lot of data so we don't want to do this unless we can reproduce the problem on-demand.

                          2) The plug-in thinks the program is suppose to be filtered. I know you said you aren't filtering anything, but just to double check. Go to the plug-in's configuration page and find the rows for a few of the programs that are generating the messages. Do they have a checkmark in the checkbox on the left? If they don't have checkmark, then that means the plug-in is suppose to ignore them (and will generate the warning message).


                          Originally posted by picc02766 View Post
                          Yes I am still seeing the "...not (yet) mapped..." messages in the Homeseer log during normal operation without doing a resync (or anything else). I am not filtering anything. Only changes are that I may have edited one or two of the programs on the ISY over the past 24 hours, but that's all. Log level of the plug-in is set to "Warnings".

                          I received a block of 95 such messages about 5 hours ago and then twice more about a minute apart approx. 12 hours before that. Beyond that I don't know the exact time frames but I have been seeing these for many days now. I'll watch the log more closely to see how often this recurs.

                          Within the 95 messages there are many "duplicates" if that means anything. There seem to be 1 or 2 such messages for each of my 62 ISY programs - I did not notice any Scenes or Devices in the list so it seems confined to programs.



                          No, aside from the duplicate "...not (yet) mapped..." messages in the log I am not aware of any duplicate devices within Homeseer or ISY.

                          Thanks again for your help,
                          Rob
                          --
                          Bob Paauwe
                          ISYInsteon Plug-in
                          http://www.bobsplace.com/ISYInsteon/

                          Comment


                            #58
                            Hi Bob, thanks for sticking with me on this!

                            Thanks for the clarification. There are only two conditions that can lead to that message so it should be easy to track down which one it is. The messages from the ISY that are leading to that log message are going to happen whenever the ISY changes a program. This could be when a group of programs changes from true to false or if they are enabled or disabled or if they are executing or stopped.

                            You say they happen somewhat infrequently. That should help narrow down what is happening. Is there a program that enables a bunch of other programs at sunset and then disables them at sunrise for instance?
                            After thinking about this for a while it dawned on me that I tend to see those messages whenever I am working with the ISY. Sure enough, all I have to do is edit and then Save a single program on the ISY and I get the batch of 95 messages in the Homeseer log. So it is easily repeatable.

                            If I understand you correctly though I should see a message for the program I changed but not for 95 of them. Note too that I only actually have 62 programs, the extra 33 lines are repeats.

                            The two things that will cause the message are:

                            1) The ISY is sending a message with out the program ID. That seems unlikely but maybe there is something new going on with the new firmware and the plug-in isn't correctly parsing the message. By setting the plug-in log level to verbose debug, it will output all the raw messages it receives from the ISY. This is a lot of data so we don't want to do this unless we can reproduce the problem on-demand.
                            OK, I set the plug-in to verbose, made a minor change to a single program on the ISY, clicked the programs "Save" button from the ISY console and attached the resulting log entries from homeseer. Hope this helps!

                            2) The plug-in thinks the program is suppose to be filtered. I know you said you aren't filtering anything, but just to double check. Go to the plug-in's configuration page and find the rows for a few of the programs that are generating the messages. Do they have a checkmark in the checkbox on the left? If they don't have checkmark, then that means the plug-in is suppose to ignore them (and will generate the warning message).
                            I just double checked and the programs/devices and scenes shown by the plugin do all have the checkmark.

                            Thanks again!
                            Rob
                            Attached Files

                            Comment


                              #59
                              Hi Rob,

                              I just posted a new version of the plug-in that I think will resolve this.

                              Originally posted by picc02766 View Post
                              Hi Bob, thanks for sticking with me on this!

                              After thinking about this for a while it dawned on me that I tend to see those messages whenever I am working with the ISY. Sure enough, all I have to do is edit and then Save a single program on the ISY and I get the batch of 95 messages in the Homeseer log. So it is easily repeatable.
                              This was the clue that pointed me in the right direction to figure out what was happening.

                              The ISY API for dealing with programs is different from the one for devices. When any program is changed (added or deleted), the ISY only notifies the clients that a program change happened, it doesn't provide any information about what the change was. So when the plug-in receives this notice it does the following

                              1) deletes all programs from it's internal list
                              2) queries the ISY for the updated program list
                              3) queries the ISY for the status of each program
                              4) re-build the mapping between ISY programs and HomeSeer devices

                              At steps 2 and 3 I was also trying to update the HomeSeer device records for each program. However, since the mapping was deleted in step 1, you would see the warning message about the programming not being mapped.

                              Step 2 would output one warning message for each program.
                              Step 3 would output one warning message for each program where the status was currently true.

                              That's why you would only see some duplicate message, not all.

                              I removed the code to try and update the HomeSeer device records from steps 2 and 3 and added a step 5 to update the HomeSeer device records after the mapping has been restored.

                              Long winded explanation, but I hope that makes sense now.
                              --
                              Bob Paauwe
                              ISYInsteon Plug-in
                              http://www.bobsplace.com/ISYInsteon/

                              Comment


                                #60
                                Hey Bob,

                                I have upgraded to 1.0.1.8 and now I have a lot of entires for my thermos, that contain no data, see the attached image.. is this normal, is this work in progress? I know that you are just carrying over all of the devices from the ISY plugin, but do we need all of these thermo entires??
                                Attached Files

                                Comment

                                Working...
                                X