Announcement

Collapse
No announcement yet.

All Bond Devices found and created in HS3 except 1?

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

    All Bond Devices found and created in HS3 except 1?

    I just loaded the BOND Plug in to test it out. I recycled the BOND Bridge power within 10 minutes and my HS3 Devices were populated and I thought all was well. Upon closer examination, it looks like one device is missing. I have 6 ceiling fans, and 3 fireplaces defined within Bond, all devices except for one fireplace were populated within HS3. I see this in the log and wonder if the Warning has anything to do the missing Bond Device?

    Thanks for any assistance you can provide.
    Code:
     
    Jul-14 2:40:41 PM Warning Exception adding a (single VGPair) pair to the collection: Item has already been added. Key in dictionary: '1' Key being added: '1'
    Jul-14 2:40:39 PM AK Bond Warning [477]: Creating device type: CF, id: 02bc935f 'New Fan'
    Jul-14 2:40:36 PM AK Bond Warning [477]: Creating device type: CF, id: 671b583d 'Jason’s Fan'
    Jul-14 2:40:33 PM AK Bond Warning [477]: Creating device type: CF, id: 63c5aac7 'Jenelle’s Fan'
    Jul-14 2:40:29 PM AK Bond Warning [477]: Creating device type: CF, id: 743b14cb 'Office Fan'
    Jul-14 2:40:28 PM AK Bond Warning [477]: Creating device type: FP, id: 5a6eace4 'Home Theatre Fireplace'
    Jul-14 2:40:26 PM AK Bond Warning [477]: Creating device type: FP, id: 22633649 'Bedroom Fireplace'
    Jul-14 2:40:23 PM AK Bond Warning [477]: Creating device type: CF, id: 2f12313d 'Ceiling fan'
    Jul-14 2:40:19 PM AK Bond Warning [477]: Creating device type: CF, id: 6e8a736f 'Chris’ Fan'
    Jul-14 2:40:12 PM AK Bond Warning [477]: Set token: 8d12952e753c68d7 ()

    #2
    Hi Dhuras can you please:

    0. Send me PDF of the Bond Config page - see https://forums.homeseer.com/forum/wi...or-bond-plugin
    1. PLUG-INS => AKBond => Config Page - enable Log for the Bridge
    2. PLUG-INS => Manage - enable Developer Mode (checkbox next to "Installed Plug-ins")
    3. Stop the plugin
    4. Start the plugin

    Remember to uncheck the Developer Mode when finished.

    See if there's any relevant messages in the HS log and the console window.
    Please send me the logs i.e.
    Code:
     
    Jul-15 12:39:49 AK Bond [1777]: {"_":"3b7cb996","1756f1e7":{"_":"da845b64"},"47cc0984":{"_": "da85160a"},"2e65abcb":{"_":"19be1797"},"4a28142a":{"_":"760 9f268"},"28d6a6ad":{"_":"38319d07"},"22917b51":{"_":"069aa40 7"},"66a19b40":{"_":"a0791f3b"}}
    Jul-15 12:39:49 AK Bond [1777]: Execute cmd: /v2/devices/
    Jul-15 12:39:49 AK Bond [1777]: {"name":"My Bridge","location":"My Room","bluelight":255,"_":"a07cd5ff"}
    Jul-15 12:39:49 AK Bond [1777]: Execute cmd: /v2/bridge/
    Jul-15 12:39:49 AK Bond [1777]: {"target":"zermatt","fw_ver":"v2.10.21","fw_date":"Wed Feb 19 15:31:13 UTC 2020","uptime_s":500944,"make":"Olibra LLC","model":"BD-1000","branding_profile":"ZERMATT","bondid":"ZZCC63031","upg rade_http":true,"api":2,"_":"210b7809"}
    Jul-15 12:39:48 AK Bond [1777]: Execute cmd: /v2/sys/version/

    Comment


      #3
      Thank you Dhuras for providing the info.

      So the good news (for me) - the plugin creates all devices reported by the Bond Bridge:
      Code:
      "6e8a736f", "2f12313d", "22633649", "5a6eace4", "743b14cb", "63c5aac7", "671b583d", "02bc935f"
      And the bad news (for you) - that means the problem with the Bridge.

      I created a topic for you in Bond support forum https://forum.bondhome.io/t/one-devi...2-devices/1652

      Please register in the forum and continue there - the Bond guys are very helpful (good news).

      Comment


        #4
        Can you also check the template name for the missing device (if you use Android) -

        Click image for larger version

Name:	Screenshot_20200716-004828.png
Views:	27
Size:	146.6 KB
ID:	1402689

        Comment


          #5
          Thank you checking things out from the Plug-in side; I have joined the Bond Support forum and will follow-up on that front. The Template field doesn't show up in the IOS app, so unfortunately I cannot provide the Template...

          Comment


            #6
            I was poking around the Bond IOS app and noticed that 1 of my devices does not have a Device Id --- and this is the missing device. Strange because it shows up separately in the IOS app and is controllable so not sure why this has happened, but I strongly suspect this is why one of the Devices was not created in the Bond Plug-In. The other strange thing is on the Device Page for this Device, there is no ... on the upper right of the screen to get into settings .,... there are 2 tiny slide switches instead.

            Comment


              #7
              ...from Bond Support:

              Likely, depending on when the device was added to the Bond Bridge, it was stored as a Cloud device instead of a local device. INSTEAD OF DELETING, just try adding it again as a new device.
              If that new device is auto detected and added as a local device (shows up in API), all good.
              If that new device is also not showing up in API, delete new device and add it again, this time using advanced mode and bypass database matching; raw record each button. That should force that new, new device to be locally stored and accessible via API.

              If either step 1 or step 2 succeed, delete original device.

              Comment


                #8
                Originally posted by Dhuras View Post
                ...from Bond Support:

                Likely, depending on when the device was added to the Bond Bridge, it was stored as a Cloud device instead of a local device. INSTEAD OF DELETING, just try adding it again as a new device.
                If that new device is auto detected and added as a local device (shows up in API), all good.
                If that new device is also not showing up in API, delete new device and add it again, this time using advanced mode and bypass database matching; raw record each button. That should force that new, new device to be locally stored and accessible via API.

                If either step 1 or step 2 succeed, delete original device.
                I saw that, but did you try?

                Comment


                  #9
                  I tried following the instructions from Bond, but was unsuccessful. (Device was recreated with RFP15 template, but still not showing up). For some reason, Bond is not exposing the device to the API, hence, its an issue with the Bond Bridge and NOT this plug-in.

                  Comment


                    #10
                    Originally posted by Dhuras View Post
                    I tried following the instructions from Bond, but was unsuccessful. (Device was recreated with RFP15 template, but still not showing up). For some reason, Bond is not exposing the device to the API, hence, its an issue with the Bond Bridge and NOT this plug-in.
                    Just to make sure - when you re-create the fireplace - do you check the response to Execute cmd: /v2/devices/ request to see if it still returns 8 devices? I.e.

                    Code:
                    {"_":"ede23c23",
                    "2f12313d":{"_":"3866c2e2"},
                    "22633649":{"_":"77744500"},
                    "743b14cb":{"_":"31c90ae2"},
                    "6e8a736f":{"_":"bb08006b"},
                    "02bc935f":{"_":"f965acef"},
                    "63c5aac7":{"_":"40242243"}, 
                    "5a6eace4":{"_":"f58e2f45"},
                    "671b583d":{"_":"1631ce9c"}}

                    Comment


                      #11
                      Yes, its still creating just 8 devices; I now actually have 10 (old fireplace, new fireplace not populated).

                      Comment


                        #12
                        Did you try latest Bond FW v2.13.0?

                        Comment


                          #13
                          Hi, I finally was able to up[grade firmware to beta 2.14 and have re-added the problem fireplace device ....from what I can tell from the Bond Device screen, I think this did the trick however, my trial for Bond plug-in has required. I would like to confirm that the plug-in now adds this device ... I will purchase plug-in but would like to confirm this first with a temporary registration or something, is that possible.

                          Comment


                            #14
                            Originally posted by Dhuras View Post
                            Hi, I finally was able to up[grade firmware to beta 2.14 and have re-added the problem fireplace device ....from what I can tell from the Bond Device screen, I think this did the trick however, my trial for Bond plug-in has required. I would like to confirm that the plug-in now adds this device ... I will purchase plug-in but would like to confirm this first with a temporary registration or something, is that possible.
                            I'm not managing the trials, that's HST responsibility.
                            What you can do - if you have another PC - install HS trial there (under different email address).
                            But in any case - even if there's a problem - I will fix it.

                            Comment

                            Working...
                            X