Announcement

Collapse
No announcement yet.

"Device address already exists" errors in startup logs, but all is working..

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

    "Device address already exists" errors in startup logs, but all is working..

    This is the error I get when the system starts up. All seams to be working but is this something I need to be concerned about? I am running v 4.0.4.5 of the plugin.

    HTML Code:
     12/17/2022 17:00:16   AK Bond   Error   [2054] 'Master Bedroom Fan': Device address already exists 'ZZCJ10423..'  
    12/17/2022 17:00:16   AK Bond   Error   [2054] 'Master Bedroom Fan': Device address already exists 'ZZCJ10423..'  
    12/17/2022 17:00:16   AK Bond   Error   [2054] 'Master Bedroom Fan': Device address already exists 'ZZCJ10423..'  
    12/17/2022 17:00:16   AK Bond   Error   [2054] 'Master Bedroom Fan': Device address already exists 'ZZCJ10423..'  
    12/17/2022 17:00:16   AK Bond   Error   [2054] 'Master Bedroom Fan': Device address already exists 'ZZCJ10423..'  
    12/17/2022 17:00:16   AK Bond   Error   [2054] 'Master Bedroom Fan': Device address already exists 'ZZCJ10423..'  
    12/17/2022 17:00:15   HomeSeer   Starting Plug-In   Initializing plugin SDJ-Health ...  
    12/17/2022 17:00:14   HomeSeer   Info   Plugin SDJ-Health has connected. IP:127.0.0.1:64853  
    12/17/2022 17:00:07   AK Bond   Warning   [2047] 'My Bridge': Creating device 'CF': 'Master Bedroom Ceiling Fan' (794bea12 'B4')  
    12/17/2022 17:00:04   HomeSeer   Plug-In   Finished initializing plug-in SDJ-Health  
    12/17/2022 17:00:04   HomeSeer   Starting Plug-In   SDJ-Health loaded in 44556 milliseconds  
    12/17/2022 16:59:24   AK Bond   Error   [2049] 'Family Room Fan': Device address already exists 'ZZCJ10423..'  
    12/17/2022 16:59:24   AK Bond   Error   [2049] 'Family Room Fan': Device address already exists 'ZZCJ10423..'  
    12/17/2022 16:59:24   AK Bond   Error   [2049] 'Family Room Fan': Device address already exists 'ZZCJ10423..'  
    12/17/2022 16:59:24   AK Bond   Error   [2049] 'Family Room Fan': Device address already exists 'ZZCJ10423..'  
    12/17/2022 16:59:24   AK Bond   Error   [2049] 'Family Room Fan': Device address already exists 'ZZCJ10423..'  
    12/17/2022 16:59:24   AK Bond   Error   [2049] 'Family Room Fan': Device address already exists 'ZZCJ10423..'  
    12/17/2022 16:59:18   AK Bond   Warning   [2047] 'My Bridge': Creating device 'CF': 'Family Room Ceiling Fan' (5416f79d 'B4')  
    12/17/2022 16:59:18   AK Bond   Info   Running on Windows - using MonoZeroconf  
    ​

    #2
    I'll check. It shouldn't be an issue, I just added more checks.

    [EDIT]

    I can't reproduce the issue, do you get it on every start-up?

    Comment


      #3
      I’ve never contacted you about it, but I get the same errors at almost every startup of HS. I also get lots of the warnings at the top of this screenshot. Everything is working.

      Click image for larger version

Name:	64A97DF2-B7AE-481B-BEB6-710E8C36E136.jpg
Views:	94
Size:	130.4 KB
ID:	1581667
      HS4 Pro, 4.2.19.0 Windows 10 pro, Supermicro LP Xeon

      Comment


        #4
        Originally posted by randy View Post
        I’ve never contacted you about it, but I get the same errors at almost every startup of HS. I also get lots of the warnings at the top of this screenshot. Everything is working.
        I need to check "Device address already exists" errors, but I don't get them, so it's harder to find.

        Regarding BPUP warnings - it only bounces if there are comms issues, but you don't seem to have any errors in the log.

        Comment


          #5
          randy RobCrisp The two dots are actually part of the address? Can you please check if the device with this address actually exists? What device is it?

          Comment


            #6
            AJ11979 is the Bond device. I don’t find an AJ11979..

            Click image for larger version

Name:	4EDC72D8-42E0-4B46-8579-C22954DF2835.jpg
Views:	87
Size:	16.7 KB
ID:	1581820
            HS4 Pro, 4.2.19.0 Windows 10 pro, Supermicro LP Xeon

            Comment


              #7
              Originally posted by alexbk66 View Post

              I need to check "Device address already exists" errors, but I don't get them, so it's harder to find.

              Regarding BPUP warnings - it only bounces if there are comms issues, but you don't seem to have any errors in the log.
              I would not understand comms issues. The bridge is within 5 feet of a UniFi AP. My network is robust and reliable. I’ll monitor it with UniFi and with my Network monitoring plug-in to see if it drops.
              HS4 Pro, 4.2.19.0 Windows 10 pro, Supermicro LP Xeon

              Comment


                #8
                I'm having the exact issue with Device address already exists errors. I'm also seeing the Bond Bridge referenced twice in the AK-Bond Plug-In drop down. One of the devices is identified by the address "ZZFA88578" and the other is simply identified as "Bond Bridge". But they are exactly the same. I've shut down the plug in, deleted all devices, rebooted the Bond Bridge and enable the plugin. All devices get re-created but with the same errors. But everything seems to work.... hmmm. Images attached

                ​ ​
                Cheers!
                Craig​

                AK-Bond Version 4.0.4.5

                HS4 Pro Edition 4.2.16.0 (Windows) on Windows 10

                Click image for larger version  Name:	ak-bond errors.jpg Views:	0 Size:	312.0 KB ID:	1581887Click image for larger version  Name:	ak-bond menu.jpg Views:	0 Size:	172.7 KB ID:	1581888Click image for larger version  Name:	ak-bond zzfa88578.jpg Views:	0 Size:	23.0 KB ID:	1581889Click image for larger version  Name:	ak-bond bond bridge.jpg Views:	0 Size:	22.3 KB ID:	1581890

                Comment


                  #9
                  BETA 4.0.4.6 - Fixed adding the Bridge device in menu twice

                  It's caused by mDNS returning only the bridge ID (i.e. "ZZFA88578"), then after I create the devices and communicate with the bridge - I get the bridge name configured in the App, so I rename the devices.

                  Comment


                    #10
                    This is still happening. Don’t know if it was addressed in the beta. Let me know if you need more information.

                    Click image for larger version  Name:	6E0D3436-9AAC-4927-88DA-2BEC93DAF99B.jpg Views:	0 Size:	98.3 KB ID:	1582323
                    HS4 Pro, 4.2.19.0 Windows 10 pro, Supermicro LP Xeon

                    Comment


                      #11
                      Originally posted by randy View Post
                      This is still happening. Don’t know if it was addressed in the beta. Let me know if you need more information.
                      BETA 4.0.4.6 fixes the other issue garciacg described.

                      I'm still looking into "Device address already exists" error. Unfortunately I can't reproduce.

                      Comment


                        #12
                        BETA 4.0.4.7 - Fixed "Device address already exists" error

                        Comment


                          #13
                          Thanks! I no longer get the errors.

                          Comment


                            #14
                            Originally posted by randy View Post
                            I would not understand comms issues. The bridge is within 5 feet of a UniFi AP. My network is robust and reliable. I’ll monitor it with UniFi and with my Network monitoring plug-in to see if it drops.
                            Do you still get BPUP warnings?

                            Comment


                              #15
                              Originally posted by alexbk66 View Post

                              Do you still get BPUP warnings?
                              Yes, still happening. Might be less frequently.

                              Click image for larger version

Name:	58743022-E235-4B7D-9311-44F84E1F4205.jpg
Views:	119
Size:	71.6 KB
ID:	1583009

                              HS4 Pro, 4.2.19.0 Windows 10 pro, Supermicro LP Xeon

                              Comment

                              Working...
                              X