Announcement

Collapse
No announcement yet.

AK Bond PI disconnects, restarts, reverts to IP: 127.0.0.1

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

    AK Bond PI disconnects, restarts, reverts to IP: 127.0.0.1

    So, I recently installed a couple of Emerson Aero ECO EFC985L series outdoor fans. Great fans, lousy controllers IMHO.
    I'm trying to open a discussion up with Emerson Engineering on how they can improve their controllers, but we'll see how that goes. We are only talking about the AK Bond PI config, the Bond Bridge Pro is still accessible from its app and the fans are functioning fine. so this issue is in the PI itself.

    Anyway, the reason for my post here is I am having issues with the AK Bond PI disconnecting, restarting, and coming up with a local useless IP of 127.0.0.1

    Since the issue is intermittent, it may take 12 hrs or more before it happens again and if I open up logging, the log will most likely generate TB of data in 12 hrs. Below is what is logged on a similar outage but is almost useless from a troubleshooting standpoint.
    Code:
    07/29/2021 08:33:17 AK Bond Info Running on Linux - using MonoZeroconf 
    07/29/2021 08:33:01 HomeSeer Starting Plug-In Plugin AK Bond started successfully in 394 milliseconds 
    07/29/2021 08:33:01 AK Bond Info 07/29/2021 08:33:01 AK Bond ver. 4.0.0.22 (4.0.1.10) 
    07/29/2021 08:33:01 HomeSeer Starting Plug-In Initializing plugin AK Bond ... 
    07/29/2021 08:33:00 HomeSeer Starting Plug-In AK Bond loaded in 15036 milliseconds 
    07/29/2021 08:32:46 HomeSeer Info Plugin AKBond with instance AK Bond has connected. IP:127.0.0.1:50550 
    07/29/2021 08:32:45 HomeSeer Warning I/O interface AK Bond is down, executable is not running, restarting ... 
    07/29/2021 08:32:31 HomeSeer Info Plugin AK Bond with ID: AKBond and Instance: has disconnected
    I'm currently on HS4 Linux 4.1.17.0 What can I do to help in diagnosing this issue?

    Thanks,
    PCK

    #2
    If plugin is restarting, there should be error messages in log. It could be related to mDNS (Zeroconf) discovery, not sure. Try disabling discovery in plugin settings.

    Comment


      #3
      Ok, let me try that and I'll update when I catch another error.

      Comment


        #4
        Originally posted by PCK View Post
        coming up with a local useless IP of 127.0.0.1
        What do you mean? Are you referring to log "Plugin AKBond with instance AK Bond has connected. IP:127.0.0.1:50550"?
        This only means that plugin is running locally to HS4.

        Comment


          #5
          On the settings screen of your PI. Once its set to an IP, in my case it does not auto discover, I have to set it manually, after some amount of time. it reverts back to 127.0.0.1 and at that point it no longer communicates to the Bond Bridge Pro. The Bond Bridge Pro is still functioning as confirmed by the app, but the PI no longer communicates to the Bridge.

          After your comment about disabling discovery, I did just that after setting it back up and so far it has not failed. So we will see what happens.

          Comment


            #6
            Can you try to investigate why auto discovery isn't working? On Linux it's using avahi, but I'm not an expert in Linux

            Comment


              #7
              Sorry for the delays in getting back on this, I have been traveling on business so my home time has been limited.......

              Ok, so what I am seeing is auto discovery is not working, and even if I disable auto discovery and set an IP manually, if I restart Homeseer or even the PI, the manual IP I set completely disappears and reverts back to 127.0.0.1 which stops communication to the Bridge Pro. I am forced to re-setup the PI every time.

              I checked and the linux avahi daemon is installed and running on my ubuntu system.

              So I see two issues, 1. the plugin does self discovery does not function, and 2. saving a manual IP configuration doesn't work either.


              PCK

              Comment


                #8
                Nobody reported any of this problem, so it needs more investigation.

                Regarding discovery, can you Google for avahi troubleshooting? I'm not an expert in Linux.

                Regarding saving manual IP config, I'll check. But like you, I'm not home, so it may take some time.

                I suggest in the mean time, please enable Log and see if you can find any clues.

                Comment


                  #9
                  I've looked at all the avahi discovery troubleshooting for ubuntu systems to no avail. avahi doesn't really buy you anything after initial setup so why make this more difficult than it needs to be? Just allow for a manual ip or host name to be entered in the config file, and have it loaded when the PI comes up, problem solved.

                  I have enabled logging but other than the scanning of devices every 5 seconds, there is no other useful info in the logs.

                  I have also reached out to Bond Support questioning why this is only a one way, sending only device. If it can send commands it should be able to listen for commands from a devices remotes. That way it would keep HS4 in sync since Bond is unable to query a device. Will see what improvements are made in this regard in the future.

                  Comment


                    #10
                    Bond do describe IP discovery here http://docs-local.appbond.com/#secti...ng-the-Bond-IP i.e.
                    Code:
                    avahi-browse -a | grep bond
                    Also, they do have Bond Push UDP Protocol (BPUP)

                    Setting IP manually also is implemented in my plugin. I can't check now as I'm not home.
                    But may I ask you again - once the IP is lost, make sure the Log is enabled, clear log and enter the IP manually - and copy log messages.

                    Comment

                    Working...
                    X