Announcement

Collapse
No announcement yet.

HS4 AKBond Question

Collapse
This topic is closed.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    HS4 AKBond Question

    Originally posted by CJMH View Post
    😂
    I have rebuilt my Zee S2 system with HS latest 32GB image of HS4 (unlimited plugins). I restored the saved HS4 configuration. I had to reinstall the plugins and since the HS3 version of AKBond is not longer supported I installed the HS4 version of AKBond. I had to delete all the Bond devices and let AKBond recreate them and then fix all my events that reference the old Bond devices. OK so far.

    However, although AKBond is working (until it doesn't) I see the following messages in the log quite often. I did not see these message in the HS3 version of AKBond. I also had set the polling interval to 0 in the HS3 version and never had any problems with the HS3 version of AKBond running under HS4. Setting the polling interval to zero does not seem to work with the HS4 version or at least it is changed back to 5 seconds or 60 seconds depending on something.

    Code:
    8/11/2021 5:12:05 PM AK Bond Warning [1060] Sofa Fan.Bridge: Since BPUP is working - changing update rate: 60 sec (from 5)
    
    8/11/2021 5:12:00 PM AK Bond Warning [1064] Chriss Fan.Bridge: Since BPUP is not working - changing update rate: 5 sec (from 60)
    
    8/11/2021 5:12:00 PM AK Bond Warning [1063] Project Room Fan.Bridge: Since BPUP is not working - changing update rate: 5 sec (from 60)
    
    8/11/2021 5:12:00 PM AK Bond Warning [1060] Sofa Fan.Bridge: Since BPUP is not working - changing update rate: 5 sec (from 60)
    
    8/11/2021 5:06:14 PM AK Bond Warning [1060] Sofa Fan.Bridge: Since BPUP is working - changing update rate: 60 sec (from 5)
    
    8/11/2021 5:06:14 PM AK Bond Warning [1063] Project Room Fan.Bridge: Since BPUP is working - changing update rate: 60 sec (from 5)
    Also HS4 sometimes reports that it can't communication with AKBond and is restarting AKBond but has not yet or some message like that. At that point I have to reboot the Zee S2.

    Also at some point when looking at the installed plugins the AKBond status went from "OK" to "Loaded remotely" and I could not disable the AKBond plugin. I had to delete the AKBond plug and reinstall it.

    One other thing to note is that I have one (of 7) Bond fan (Gazebo Fan) that is having trouble staying connect to the WiFi. Not sure if that has anything to do wit hit or not.

    Any ideas as to what is going on or what to do?

    Thanks!

    System Profile:

    Code:
    Date/time=8/11/2021 5:35:28 PM EDT
    Version=HomeSeer HS4 ZEE S2 (Upg from HS3ZS2) Edition 4.1.18.0 (Linux)
    MONO Version=Mono JIT compiler version 6.12.0.122 (tarball Mon Feb 22 17:44:05 UTC 2021)
    
    License=Registered
    Confguration File=/usr/local/HomeSeer/Data/HomeSeerData.json
    Uptime=0 Days 18 Hours 10 Minutes 10 Seconds
    Lan IP=192.168.0.103 (HS4PiV5)
    Device Count=294
    Event Count=261
    Plugins Enabled=Z-Wave:,Tuya:,Harmony Hub:,AK Bond:
    Modules/Threads=83 Modules, 51 Threads
    Available Threads=399
    HomeSeer Memory Used=138 Mbytes
    Plugins Installed=AK Bond 4.0.0.22,Harmony Hub 4.0.13.0,Tuya 4.0.30.0,Z-Wave 3.0.7.0,Z-Wave UI 1.0.0.0
    Disk Size=29.72GB
    Bond Bridge Bond Bridge

    Code:
    192.168.0.135
    IP Address
    Polling period (default)
    Bond Push UDP Protocol is active - reduce polling to 60 sec
    ▼
    5 sec
    Delay between messages
    ▼
    200 ms
    Log
    
    Trace
    
    Add 'control' HS device to each Bond device
    
    Enable Bond Push UDP Protocol (recommended)
    
    Bond Bridge Project Room Fan.Bridge
    
    192.168.0.187
    IP Address
    Polling period
    Bond Push UDP Protocol is active - reduce polling to 60 sec
    ▼
    60 sec
    Delay between messages
    ▼
    200 ms
    Log
    
    Trace
    
    Add 'control' HS device to each Bond device
    
    Enable Bond Push UDP Protocol (recommended)
    
    Bond Bridge Susans Fan.Bridge
    
    192.168.0.134
    IP Address
    Polling period (default)
    Bond Push UDP Protocol is active - reduce polling to 60 sec
    ▼
    5 sec
    Delay between messages
    ▼
    200 ms
    Log
    
    Trace
    
    Add 'control' HS device to each Bond device
    
    Enable Bond Push UDP Protocol (recommended)
    
    Bond Bridge Chriss Fan.Bridge
    
    192.168.0.176
    IP Address
    Polling period
    Bond Push UDP Protocol is active - reduce polling to 60 sec
    ▼
    60 sec
    Delay between messages
    ▼
    200 ms
    Log
    
    Trace
    
    Add 'control' HS device to each Bond device
    
    Enable Bond Push UDP Protocol (recommended)
    
    Bond Bridge Garden Side Fan.Bridge
    
    192.168.0.129
    IP Address
    Polling period (default)
    Bond Push UDP Protocol is active - reduce polling to 60 sec
    ▼
    5 sec
    Delay between messages
    ▼
    200 ms
    Log
    
    Trace
    
    Add 'control' HS device to each Bond device
    
    Enable Bond Push UDP Protocol (recommended)
    
    Bond Bridge Sofa Fan.Bridge
    
    192.168.0.138
    IP Address
    Polling period
    Bond Push UDP Protocol is active - reduce polling to 60 sec
    ▼
    60 sec
    Delay between messages
    ▼
    200 ms
    Log
    
    Trace
    
    Add 'control' HS device to each Bond device
    
    Enable Bond Push UDP Protocol (recommended)
    
    Bond Bridge Gazebo Fan.Bridge
    
    192.168.0.175
    IP Address
    Polling period (default)
    ▼
    5 sec
    Delay between messages
    ▼
    200 ms
    Log
    
    Trace
    
    Add 'control' HS device to each Bond device
    
    Enable Bond Push UDP Protocol (recommended)
    
    Bond Bridge Bond Bridge
    
    192.168.0.155
    IP Address
    Polling period (default)
    Bond Push UDP Protocol is active - reduce polling to 60 sec
    ▼
    5 sec
    Delay between messages
    ▼
    200 ms
    Log
    
    Trace
    
    Add 'control' HS device to each Bond device
    
    Enable Bond Push UDP Protocol (recommended)
    
    Select type of Zeroconf/mDNS discovery (MonoZeroconf)
    ▼
    Auto
    Add new device manually if Discovery not working

    #2

    Originally posted by CJMH View Post
    Not sure how the answer to that question will help resolve the issue I am having, but as I remember in a previous thread on AKBond which now seems to be gone you stated that the HS3 (legacy) version of AKBond was no longer supported as of (as I remember) Jan, 2021.

    Any thoughts on the issue with the HS4 version of AKBond I presented above? Thanks!
    Ah, ok. I meant I don't want to support both versions, yes. But it still should work.

    That's a lot of issues you are suddenly having... I'll check one problem at the time (hopefully they are all connected).

    BPUP is Bond Push UDP Protocol, so the bridge notifies the plugin when state is changed, so you don't need constant polling. If BPUP is detected - I set the polling rate to 60 sec, just in case you add any new devices.

    In your case BPUP seems to be unstable, pretty strange. I need to check.

    Can you try disabling BPUP in settings. And set polling to 5-10 sec.

    Comment


      #3
      Also you can enable Log and check if there's anything suspicious

      Comment


        #4
        Originally posted by alexbk66 View Post

        Ah, ok. I meant I don't want to support both versions, yes. But it still should work.
        Yes I know it works as I have been using the legacy version under HS4 for over a year. It was working without issue with no polling at all. Any time I added a Bond device I simply disabled AKBond and re-enbabled it making sure the Bond device had just been powered on.

        The issue started when two things happened. I rebuilt my Zee S2 with the new 32GB image of HS4 that allows unlimited plugins and instead of installing the legacy AKBond I installed the HS4 version of AKBond.

        Originally posted by alexbk66 View Post

        BPUP is Bond Push UDP Protocol, so the bridge notifies the plugin when state is changed, so you don't need constant polling. If BPUP is detected - I set the polling rate to 60 sec, just in case you add any new devices.

        I do understand UDP and how it is used in Bond and AKBond.

        Originally posted by alexbk66 View Post

        Can you try disabling BPUP in settings. And set polling to 5-10 sec.

        Also you can enable Log and check if there's anything suspicious
        Re-enabled AKBond and made those changes. The Brightness function on the Bond Sofa fan is now working again. Now sure if that has to do with the changes or simply has to do with disabling and re-enabling AKBond. Will report back after some time has passed.

        BTW HS4 had been running on my Zee S2 for 12 hours with AKBond disabled and I had no issues (other than not being able to use Bond devices with HS)



        Comment


          #5
          If you need to re-enable BPUP and have any issues, please enable Log.

          I'll also check the source code for these issues.

          Comment


            #6
            How many bridges or SBB devices do you have? 7?

            I haven't tested BPUP with so many devices, can be an issue

            Comment


              #7
              I had been using the same devices in the legacy AKBond under the old HS4. I have turned off BPUP as you asked and still had many of the same problems. Child devices when an action was executed sometime says there was no such device (in the log). Status/Graphics entries disappearing. For instance Fan.Brightness would have all the % entries, but the increase brightness/decrease brightness would disappear. And the HS4 system would go into a hang state where things would take a minute to several minutes to take effect. All in all the HS4 system was very flakey.

              I had made two changes since everything was working (1 - rebuilt my HS4 system with the latest HS4-PI image and 2 installed the HS4 version of AKBond instead of the legacy AKBond).

              I decided to try to the legacy AKBond with the new HS4 I had rebuilt. I uninstalled AKBond, deleted all my Bond device, installed the legacy AKBond, power cycled all the bond devices, and reenabled the legacy AKBond. PBUP is also enabled in the legacy AKBond now. I also change the delays to 150ms to be safe. The system is working reliably now but I have one new issue and one question that I had before.

              When I restart the Raspberry PI system, AKBond does not recreate all the Bond devices. I have to disable AKBond and reenable before everything works correctly. This is new. I never had to do that before rebuilding the HS4 system.

              I also see message like the following for all Bond devices reoccurring in the log at random times. I saw these messages in the log before I rebuilt the system so they seem benign, but thought you should know:

              8/13/2021 9:50:29 AM Legacy-Plugin AK Bond Warning [1064]: Since BPUP is working - no need for polling, disabling

              Attached is the log after a reboot and then disabling and reenabling AKBond


              Attached Files

              Comment


                #8
                Thank you for providing info. Something weird. The warning about BPUP is working is normal. I'll check your logs.

                Comment


                  #9
                  I checked the log, it's for HS3 plugin version. Doesn't help much with HS4 version issues.

                  Comment


                    #10
                    BTW, regarding Sofa Fan (1060), even HS3 version has error
                    Code:
                    [1060]: [Bond Bridge] KSMWWCI97699 (192.168.0.138:80): Execute '/v2/sys/version/': Status: 'Error' (ConnectFailure). Error: 'Error: ConnectFailure (No route to host)'.

                    Comment


                      #11
                      Originally posted by alexbk66 View Post
                      BTW, regarding Sofa Fan (1060), even HS3 version has error
                      Code:
                      [1060]: [Bond Bridge] KSMWWCI97699 (192.168.0.138:80): Execute '/v2/sys/version/': Status: 'Error' (ConnectFailure). Error: 'Error: ConnectFailure (No route to host)'.
                      That error could have been caused by a temporary network issue. What I can tell you is I am not having any problems with the Legacy AKBond running on my HS4-Pi system except for a reboot causing me to have disable and re-enable the AKBond plug in to get all the Bond devices working. The same cannot be said for the HS4 version of AKBond. It is simply too unstable to run.

                      Originally posted by alexbk66 View Post
                      I checked the log, it's for HS3 plugin version. Doesn't help much with HS4 version issues.
                      The HS3 (legacy AKBond is the only AKBond plugin that will run on my HS4-Pi system reliably. If you will reread this thread you will see I gave up on the HS4 version of AKBond as it made the system unstable and continued to have many problems. Not just a single issue that would be relatively easy to track down. The HSI-Pi system would not not run for more than a short period of time (with HS4 version of AKBond) before starting to hang the system (even though I could SSH into Linux and see half of the memory being free and no delay issues using Linux). There were many other problems as well (See above)

                      So are you saying that there is no help available for the Legacy AKBond even though that is the only version that will run on a HS4-Pi system?

                      Comment


                        #12
                        I'm saying that to help with HS4 plugin version I need log for HS4 plugin version.

                        There's no complains from other users so far, so my only best guess is that your issues are caused by number of Bond devices you have. But to be sure I need the logs.

                        Comment


                          #13
                          I have already spent several days trying to get the HS4 version of AKbond to work on my rebuilt HS4-Pi system and I am not the only one effected by the HS system being down. Plus, every time I have to delete a Bond device I have a lot of reprogramming to do in the events and my experience with the HS4 version of AKBond is that it requires a lot of deleting of Bond devices to get things back running once things go haywire and it does not take long for thing to go amok.

                          One thing to note is the 32GB version of HS4-Pi (with unlimited plugins) is brand new and requires anyone with the older HS4 version to rebuild the Raspberry PI system from scratch. I may be the first person to do so. I don't know if the HS4 version of AKBond had the same problems running on the old HS4-Pi system or not since I has running the legacy AKBond with the older system.

                          If you tell me exactly how you want the HS4 version AKBond system set up I can make a copy of the HS4-Pi image I have now, which is running well on my Pi system right now (except the reboot issue), onto another 32GB sdcard and do some any experiments you need. Let me know how I should proceed ...

                          In the mean time is there anything you see in the log (sent above) with the legacy AKBond that would cause AKBond not to enumerate the Bond devices properly on reboot and require me to disable and then re-enable AKBond? This was not a problem with the old HS4 system running the legacy AKBond.

                          Comment


                            #14
                            One more thing to note. Disabling and re-enabling the legacy AKBond does not always end up with all Bond devices enumerated (created). Sometimes I have to disable and re-enable multiple times before all Bond devices are enumerated after a reboot.

                            Comment


                              #15
                              Originally posted by CJMH View Post
                              my experience with the HS4 version of AKBond is that it requires a lot of deleting of Bond devices to get things back running once things go haywire and it does not take long for thing to go amok.


                              If you tell me exactly how you want the HS4 version AKBond system set up I can make a copy of the HS4-Pi image I have now, which is running well on my Pi system right now (except the reboot issue), onto another 32GB sdcard and do some any experiments you need. Let me know how I should proceed ...
                              Please provide some constructive feedback which will help to fix any issues you face. Why do you need to delete devices? If " it requires a lot of deleting of Bond devices" - why didn't you report this earlier? I can't fix a problem if (a) I'm not aware about the problem and (b) I don't have any troubleshooting info, i.e. logs.

                              As I said, your issues might be caused by number of devices you have, especially I suspect that my BPUP implementation should be changed because I create BPUP listener for each device, but I suspect it should be single static instance listening for all UDP messages. But to test this I need another Bond bridge, I'll let you know when I have something for testing.

                              In the meantime, if you can experiment with HS4 plugin version and provide logs - it will save a lot of time, so I know in which direction to look.



                              Comment

                              Working...
                              X