Announcement

Collapse
No announcement yet.

HAI Plugin Beta - v3.0.1.13

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

    HAI Plugin Beta - v3.0.1.13

    Changes in this version:
    • Changed Unit device creation to use HLC range values.
    • Fixed postback issue when adding more than 7 devices at a time.
    • Added more logging around removing devices from the HAI Plugin page.


    Attached is the plugin and updater_override.txt files. Here's how to install this beta without using the updater:
    • Copy the attached zip file to your Updates3/Zips folder.
    • Copy the attached updater_override.txt file to the HS3 root folder.
    • From the Manage Plugins page, click on Update Listing.
    • You should see the HAI Plugin Beta listed.
    • Select and install the plugin.


    **Note - if you are using Linux, make sure you copy the updater_override.txt file and preserve the /r/n line feeds - transfer it in binary and you should be fine.

    When finished, remove the updater_override.txt or you will not be able to install plugins from the HS store.



    ***Backup your current installation so you can revert back if needed!!
    Last edited by rmasonjr; April 1, 2016, 08:43 AM.
    HS4Pro on a Raspberry Pi4
    54 Z-Wave Nodes / 21 Zigbee Devices / 108 Events / 767 Devices
    Plugins: Z-Wave / Zigbee Plus / EasyTrigger / AK Weather / OMNI

    HSTouch Clients: 1 Android

    #2
    Thanks Rob...all went well!

    Install/Update of package HAI Plugin Beta was successful.

    HAI 3.0.1.13
    - Pete

    Auto mator
    Homeseer 3 Pro - 3.0.0.548 (Linux) - Ubuntu 18.04/W7e 64 bit Intel Haswell CPU 16Gb
    Homeseer Zee2 (Lite) - 3.0.0.548 (Linux) - Ubuntu 18.04/W7e - CherryTrail x5-Z8350 BeeLink 4Gb BT3 Pro
    HS4 Lite - Ubuntu 22.04 / Lenovo Tiny M900 / 32Gb Ram

    HS4 Pro - V4.1.18.1 - Ubuntu 22.04 / Lenova Tiny M900 / 32Gb Ram
    HSTouch on Intel tabletop tablets (Jogglers) - Asus AIO - Windows 11

    X10, UPB, Zigbee, ZWave and Wifi MQTT automation-Tasmota-Espurna. OmniPro 2, Russound zoned audio, Alexa, Cheaper RFID, W800 and Home Assistant

    Comment


      #3
      Good! I think bypassing the updater will help me by getting some builds faster and not bogging down HST. I probably should have been doing this all along
      HS4Pro on a Raspberry Pi4
      54 Z-Wave Nodes / 21 Zigbee Devices / 108 Events / 767 Devices
      Plugins: Z-Wave / Zigbee Plus / EasyTrigger / AK Weather / OMNI

      HSTouch Clients: 1 Android

      Comment


        #4
        Yes; Thank you Rob.

        Update took less than 5 minutes.

        A quick check on the thermostat....

        Current HS3 V.13 status indicated unholded where as it is holded.

        Only bringing this up because I unholded it a couple of days ago and didn't check on the default Omnistat (this is my fault) setting of 55 (and its been zero and below here) and going to bed the other night wife mentioned that bedroom was a bit chilly willy.

        See the X-10 devices and UPB devices now. I do not see the Z-Wave devices at this time. They are in the beyond above and below (in between) UPB devices.

        Unrelated to OP got a 2 day Amazon Prime delivery this morning and it came from an Amazon van and driver (he had an Amazon logo on his shirt/coat). First time seeing this. (well thinking the last Sunday delivery was in a generic van?).
        Last edited by Pete; January 19, 2016, 01:24 PM.
        - Pete

        Auto mator
        Homeseer 3 Pro - 3.0.0.548 (Linux) - Ubuntu 18.04/W7e 64 bit Intel Haswell CPU 16Gb
        Homeseer Zee2 (Lite) - 3.0.0.548 (Linux) - Ubuntu 18.04/W7e - CherryTrail x5-Z8350 BeeLink 4Gb BT3 Pro
        HS4 Lite - Ubuntu 22.04 / Lenovo Tiny M900 / 32Gb Ram

        HS4 Pro - V4.1.18.1 - Ubuntu 22.04 / Lenova Tiny M900 / 32Gb Ram
        HSTouch on Intel tabletop tablets (Jogglers) - Asus AIO - Windows 11

        X10, UPB, Zigbee, ZWave and Wifi MQTT automation-Tasmota-Espurna. OmniPro 2, Russound zoned audio, Alexa, Cheaper RFID, W800 and Home Assistant

        Comment


          #5
          Heh - that is a bit chilly

          Can you change the thermostat off Hold, then back to Hold and post the logs? I might have added enough debug info in there to spot whats up.

          Wouldnt that be funny if Amazon bought UPS? I guess to some degree they already 'own' them in sheer volume of packages.
          HS4Pro on a Raspberry Pi4
          54 Z-Wave Nodes / 21 Zigbee Devices / 108 Events / 767 Devices
          Plugins: Z-Wave / Zigbee Plus / EasyTrigger / AK Weather / OMNI

          HSTouch Clients: 1 Android

          Comment


            #6
            Thank you Rob and will do. I didn't enable any logging this time such that I will enable the logging shortly.

            Amazon built a gigantic warehouse nearby a few months back. I am waiting though for the drone deliveries.

            I keep hearing rumors about that whole UPS, FedEx and USPS stuff...oh and DHL and TNT (TNT was from the EU - but I think it scared some folks seeing delivery trucks marked TNT).

            IE: no one wants to buy or subcontract USPS right now cuz they are totally broke and not a viable business (sad note). FedEx got dinged over the holidays due to the stormy weather and had folks voluntarily deliver packages sans pay. (really dedicated employees) and UPS is now trying to get back the business that they have lost to FedEx and USPS by lowering their prices and eliminating services.
            - Pete

            Auto mator
            Homeseer 3 Pro - 3.0.0.548 (Linux) - Ubuntu 18.04/W7e 64 bit Intel Haswell CPU 16Gb
            Homeseer Zee2 (Lite) - 3.0.0.548 (Linux) - Ubuntu 18.04/W7e - CherryTrail x5-Z8350 BeeLink 4Gb BT3 Pro
            HS4 Lite - Ubuntu 22.04 / Lenovo Tiny M900 / 32Gb Ram

            HS4 Pro - V4.1.18.1 - Ubuntu 22.04 / Lenova Tiny M900 / 32Gb Ram
            HSTouch on Intel tabletop tablets (Jogglers) - Asus AIO - Windows 11

            X10, UPB, Zigbee, ZWave and Wifi MQTT automation-Tasmota-Espurna. OmniPro 2, Russound zoned audio, Alexa, Cheaper RFID, W800 and Home Assistant

            Comment


              #7
              Units! I've got ALC units!!!

              Thanks, Rob....now the work begins in earnest on this end.

              Tom

              Comment


                #8
                Originally posted by lakemirror View Post
                Units! I've got ALC units!!!

                Thanks, Rob....now the work begins in earnest on this end.

                Tom
                Awesome - are you able to control them ok?
                HS4Pro on a Raspberry Pi4
                54 Z-Wave Nodes / 21 Zigbee Devices / 108 Events / 767 Devices
                Plugins: Z-Wave / Zigbee Plus / EasyTrigger / AK Weather / OMNI

                HSTouch Clients: 1 Android

                Comment


                  #9
                  Here are the thermostat debug logs.

                  From the HS3 GUI (showed unholding where as it was holding) put a hold. Waited a bit then put an unhold. Worked fine. Status showed on PCA fine when changing it.

                  Then I put a hold via PCA and saw the hold on HS3 GUI. I then did an unhold from PCA but it did not change the HS3 GUI.


                  1/19/2016 1:17:46 PM [2] [UNSOLICITED: SystemEvents]
                  1/19/2016 1:19:47 PM [2] [SetIOMulti: CC.Ref=[740] CC.ControlValue=[1]]
                  1/19/2016 1:19:47 PM [2] [-->name=[holdmode] val=[1] tstat=[1]]
                  1/19/2016 1:19:47 PM [2] [SetHoldMode: 1 1]
                  1/19/2016 1:19:49 PM [2] [UNSOLICITED: ExtendedStatus]
                  1/19/2016 1:19:49 PM [2] [---->Thermostat]
                  1/19/2016 1:19:49 PM [2] [coolsetpointtext=[78] temptext=[72] fanmode=[1] heatsetpointtext=[72] holdstatus=[1] mode=[1] protocol=[HAI Omnistat
                  1] HorC_Status=[0] outdoortemp=[20] type=[Auto Heat/Cool] zigbeeaddr=[0000] zwavenode=[0]]
                  1/19/2016 1:19:59 PM [2] [SetIOMulti: CC.Ref=[740] CC.ControlValue=[0]]
                  1/19/2016 1:19:59 PM [2] [-->name=[holdmode] val=[0] tstat=[1]]
                  1/19/2016 1:19:59 PM [2] [SetHoldMode: 1 0]
                  1/19/2016 1:20:00 PM [2] [UNSOLICITED: ExtendedStatus]
                  1/19/2016 1:20:00 PM [2] [---->Thermostat]
                  1/19/2016 1:20:00 PM [2] [coolsetpointtext=[78] temptext=[72] fanmode=[1] heatsetpointtext=[72] holdstatus=[0] mode=[1] protocol=[HAI Omnistat
                  1] HorC_Status=[0] outdoortemp=[20] type=[Auto Heat/Cool] zigbeeaddr=[0000] zwavenode=[0]]
                  1/19/2016 1:20:02 PM [2] [UNSOLICITED: ExtendedStatus]
                  1/19/2016 1:20:02 PM [2] [---->Thermostat]
                  1/19/2016 1:20:02 PM [2] [coolsetpointtext=[85] temptext=[72] fanmode=[1] heatsetpointtext=[62] holdstatus=[0] mode=[1] protocol=[HAI Omnistat
                  1] HorC_Status=[0] outdoortemp=[20] type=[Auto Heat/Cool] zigbeeaddr=[0000] zwavenode=[0]]
                  1/19/2016 1:20:14 PM [2] [UNSOLICITED: ExtendedStatus]
                  1/19/2016 1:20:14 PM [2] [---->Thermostat]
                  1/19/2016 1:20:14 PM [2] [coolsetpointtext=[85] temptext=[72] fanmode=[1] heatsetpointtext=[62] holdstatus=[0] mode=[1] protocol=[HAI Omnistat
                  1] HorC_Status=[0] outdoortemp=[20] type=[Auto Heat/Cool] zigbeeaddr=[0000] zwavenode=[0]]
                  1/19/2016 1:20:49 PM [2] [UNSOLICITED: ExtendedStatus]
                  1/19/2016 1:20:50 PM [2] [---->Thermostat]
                  1/19/2016 1:20:50 PM [2] [coolsetpointtext=[85] temptext=[72] fanmode=[1] heatsetpointtext=[62] holdstatus=[255] mode=[1] protocol=[HAI Omnistat
                  1] HorC_Status=[0] outdoortemp=[20] type=[Auto Heat/Cool] zigbeeaddr=[0000] zwavenode=[0]]

                  Did it again remotely from PCA and watched debug...(didn't see HS3 GUI change though).

                  1/19/2016 1:25:41 PM [2] [---->Thermostat]
                  1/19/2016 1:25:41 PM [2] [coolsetpointtext=[85] temptext=[72] fanmode=[1] heatsetpointtext=[62] holdstatus=[255] mode=[1] protocol=[HAI Omnistat
                  1] HorC_Status=[0] outdoortemp=[21] type=[Auto Heat/Cool] zigbeeaddr=[0000] zwavenode=[0]]
                  1/19/2016 1:25:49 PM [2] [UNSOLICITED: ExtendedStatus]

                  1/19/2016 1:26:31 PM [2] [UNSOLICITED: ExtendedStatus]
                  1/19/2016 1:26:31 PM [2] [---->Thermostat]
                  1/19/2016 1:26:31 PM [2] [coolsetpointtext=[85] temptext=[72] fanmode=[1] heatsetpointtext=[62] holdstatus=[0] mode=[1] protocol=[HAI Omnistat
                  1] HorC_Status=[0] outdoortemp=[21] type=[Auto Heat/Cool] zigbeeaddr=[0000] zwavenode=[0]]
                  1/19/2016 1:26:49 PM [2] [UNSOLICITED: ExtendedStatus]

                  1/19/2016 1:27:04 PM [2] [UNSOLICITED: ExtendedStatus]

                  Looks like locally to the HS3 plugin / GUI the hold and unhold thing is a zero and a one. Remotely via PCA it is getting a zero and two fifty five thing.
                  - Pete

                  Auto mator
                  Homeseer 3 Pro - 3.0.0.548 (Linux) - Ubuntu 18.04/W7e 64 bit Intel Haswell CPU 16Gb
                  Homeseer Zee2 (Lite) - 3.0.0.548 (Linux) - Ubuntu 18.04/W7e - CherryTrail x5-Z8350 BeeLink 4Gb BT3 Pro
                  HS4 Lite - Ubuntu 22.04 / Lenovo Tiny M900 / 32Gb Ram

                  HS4 Pro - V4.1.18.1 - Ubuntu 22.04 / Lenova Tiny M900 / 32Gb Ram
                  HSTouch on Intel tabletop tablets (Jogglers) - Asus AIO - Windows 11

                  X10, UPB, Zigbee, ZWave and Wifi MQTT automation-Tasmota-Espurna. OmniPro 2, Russound zoned audio, Alexa, Cheaper RFID, W800 and Home Assistant

                  Comment


                    #10
                    Just tested and they work fine. Took a while to get them all enabled in the plugin page as the page reloads after every selection. Got my flags ok too. Happy camper on this end.

                    Comment


                      #11
                      Originally posted by lakemirror View Post
                      Just tested and they work fine. Took a while to get them all enabled in the plugin page as the page reloads after every selection. Got my flags ok too. Happy camper on this end.
                      Awesome.

                      Yeah, I debated long and hard about the postback. I really wanted it to work, but Travis uncovered a serious flaw and I had to revert on a full page postback. The good news is that you only have to do it once
                      HS4Pro on a Raspberry Pi4
                      54 Z-Wave Nodes / 21 Zigbee Devices / 108 Events / 767 Devices
                      Plugins: Z-Wave / Zigbee Plus / EasyTrigger / AK Weather / OMNI

                      HSTouch Clients: 1 Android

                      Comment


                        #12
                        Originally posted by Pete View Post
                        Here are the thermostat debug logs.

                        From the HS3 GUI (showed unholding where as it was holding) put a hold. Waited a bit then put an unhold. Worked fine. Status showed on PCA fine when changing it.

                        Then I put a hold via PCA and saw the hold on HS3 GUI. I then did an unhold from PCA but it did not change the HS3 GUI.


                        1/19/2016 1:17:46 PM [2] [UNSOLICITED: SystemEvents]
                        1/19/2016 1:19:47 PM [2] [SetIOMulti: CC.Ref=[740] CC.ControlValue=[1]]
                        1/19/2016 1:19:47 PM [2] [-->name=[holdmode] val=[1] tstat=[1]]
                        1/19/2016 1:19:47 PM [2] [SetHoldMode: 1 1]
                        1/19/2016 1:19:49 PM [2] [UNSOLICITED: ExtendedStatus]
                        1/19/2016 1:19:49 PM [2] [---->Thermostat]
                        1/19/2016 1:19:49 PM [2] [coolsetpointtext=[78] temptext=[72] fanmode=[1] heatsetpointtext=[72] holdstatus=[1] mode=[1] protocol=[HAI Omnistat
                        1] HorC_Status=[0] outdoortemp=[20] type=[Auto Heat/Cool] zigbeeaddr=[0000] zwavenode=[0]]
                        1/19/2016 1:19:59 PM [2] [SetIOMulti: CC.Ref=[740] CC.ControlValue=[0]]
                        1/19/2016 1:19:59 PM [2] [-->name=[holdmode] val=[0] tstat=[1]]
                        1/19/2016 1:19:59 PM [2] [SetHoldMode: 1 0]
                        1/19/2016 1:20:00 PM [2] [UNSOLICITED: ExtendedStatus]
                        1/19/2016 1:20:00 PM [2] [---->Thermostat]
                        1/19/2016 1:20:00 PM [2] [coolsetpointtext=[78] temptext=[72] fanmode=[1] heatsetpointtext=[72] holdstatus=[0] mode=[1] protocol=[HAI Omnistat
                        1] HorC_Status=[0] outdoortemp=[20] type=[Auto Heat/Cool] zigbeeaddr=[0000] zwavenode=[0]]
                        1/19/2016 1:20:02 PM [2] [UNSOLICITED: ExtendedStatus]
                        1/19/2016 1:20:02 PM [2] [---->Thermostat]
                        1/19/2016 1:20:02 PM [2] [coolsetpointtext=[85] temptext=[72] fanmode=[1] heatsetpointtext=[62] holdstatus=[0] mode=[1] protocol=[HAI Omnistat
                        1] HorC_Status=[0] outdoortemp=[20] type=[Auto Heat/Cool] zigbeeaddr=[0000] zwavenode=[0]]
                        1/19/2016 1:20:14 PM [2] [UNSOLICITED: ExtendedStatus]
                        1/19/2016 1:20:14 PM [2] [---->Thermostat]
                        1/19/2016 1:20:14 PM [2] [coolsetpointtext=[85] temptext=[72] fanmode=[1] heatsetpointtext=[62] holdstatus=[0] mode=[1] protocol=[HAI Omnistat
                        1] HorC_Status=[0] outdoortemp=[20] type=[Auto Heat/Cool] zigbeeaddr=[0000] zwavenode=[0]]
                        1/19/2016 1:20:49 PM [2] [UNSOLICITED: ExtendedStatus]
                        1/19/2016 1:20:50 PM [2] [---->Thermostat]
                        1/19/2016 1:20:50 PM [2] [coolsetpointtext=[85] temptext=[72] fanmode=[1] heatsetpointtext=[62] holdstatus=[255] mode=[1] protocol=[HAI Omnistat
                        1] HorC_Status=[0] outdoortemp=[20] type=[Auto Heat/Cool] zigbeeaddr=[0000] zwavenode=[0]]
                        Whew - I'm glad I added this debug. I see the last line has a holdstatus of 255 - let me check the protocol docs and see what I can find out.
                        HS4Pro on a Raspberry Pi4
                        54 Z-Wave Nodes / 21 Zigbee Devices / 108 Events / 767 Devices
                        Plugins: Z-Wave / Zigbee Plus / EasyTrigger / AK Weather / OMNI

                        HSTouch Clients: 1 Android

                        Comment


                          #13
                          Thank you Rob.

                          Note that I only see that 255 when making a change to the hold from PCA (and HS2); the HS3 GUI makes it a one (1) instead of a 255.

                          Looked at the protocol document and it is 255.

                          IE:

                          70 0/255 0-n set thermostat P2 hold mode to P1

                          0 = off
                          255 = hold
                          Attached Files
                          Last edited by Pete; January 19, 2016, 03:04 PM.
                          - Pete

                          Auto mator
                          Homeseer 3 Pro - 3.0.0.548 (Linux) - Ubuntu 18.04/W7e 64 bit Intel Haswell CPU 16Gb
                          Homeseer Zee2 (Lite) - 3.0.0.548 (Linux) - Ubuntu 18.04/W7e - CherryTrail x5-Z8350 BeeLink 4Gb BT3 Pro
                          HS4 Lite - Ubuntu 22.04 / Lenovo Tiny M900 / 32Gb Ram

                          HS4 Pro - V4.1.18.1 - Ubuntu 22.04 / Lenova Tiny M900 / 32Gb Ram
                          HSTouch on Intel tabletop tablets (Jogglers) - Asus AIO - Windows 11

                          X10, UPB, Zigbee, ZWave and Wifi MQTT automation-Tasmota-Espurna. OmniPro 2, Russound zoned audio, Alexa, Cheaper RFID, W800 and Home Assistant

                          Comment


                            #14
                            Yeah, that is what's frustrating about HAI's protocol docs. I coded as listed on pages 26-27. Now, I see that section you have as just being on/off (0/255). My version of PCAccess only has OFF/ON. I'll get you something to test that has 0/255
                            Attached Files
                            HS4Pro on a Raspberry Pi4
                            54 Z-Wave Nodes / 21 Zigbee Devices / 108 Events / 767 Devices
                            Plugins: Z-Wave / Zigbee Plus / EasyTrigger / AK Weather / OMNI

                            HSTouch Clients: 1 Android

                            Comment


                              #15
                              Yeah in PC Access it just said on or off for hold.

                              IE: mode/fan/hold settings

                              hold on or hold off

                              So I went looking at the only HAI Omnipro keypad I have on line and I do enter a 0 or 1 for hold there for the thermostat stuff.

                              Well same for the other thermostat functions. Typically on the keypad I only if anything look at the thermostat temps or aux temperatures / humidity stuff.

                              Wondering why they would put in the Keypad commands in the SDK stuff?

                              Well as you have mentioned before about the SDK being a bit cryptic; could be that or just a laissez faire thing from HAI?

                              Ahhh....now I see it...system mode is 0,1,2,3. fan mode is 0,1 and hold mode is 0,255 which breaks the mode of the HAI logic...or it might have been Friday of a long week when HAI was doing this? I am not going to try to make sense of this stuff as it defies logic.

                              Well too noticed that I do not have a vacation hold function on the Omnistat. Hold is only on or off. (I take that back and looked again).

                              I do have a vacation function somewhere on the omnistat.

                              OK so looked at the Keypad. There is no vacation mode on it for hold or anywhere else relating to thermostat functions.

                              BUT when I looked at the Omnistat 2 there is a drop down for hold that shows: (stuff above saids other instead of override).

                              off, on, vacation, override.

                              BTW all of the Zigbee radio functions are there on the Omnitstat 2 menus sans the meat of the RF module (just an empty socket on the omnistat motherboard).

                              Going back now to PCA....for HOLD it only shows on or off; no vacation stuff or override stuff ...IE: thermostat==> hold ==> on or off.

                              I personally have never used vacation or override here with my Omnistat 2. That said I do not pay that much attention to the Omnistat and just use the Omnitouch screens mostly (and HS2 plugin stuff).

                              Now I am discombobulated. I am now a HAI plugin figment of my own newton. (I think)

                              Sorry to bug you about this Rob.
                              Last edited by Pete; January 19, 2016, 04:04 PM.
                              - Pete

                              Auto mator
                              Homeseer 3 Pro - 3.0.0.548 (Linux) - Ubuntu 18.04/W7e 64 bit Intel Haswell CPU 16Gb
                              Homeseer Zee2 (Lite) - 3.0.0.548 (Linux) - Ubuntu 18.04/W7e - CherryTrail x5-Z8350 BeeLink 4Gb BT3 Pro
                              HS4 Lite - Ubuntu 22.04 / Lenovo Tiny M900 / 32Gb Ram

                              HS4 Pro - V4.1.18.1 - Ubuntu 22.04 / Lenova Tiny M900 / 32Gb Ram
                              HSTouch on Intel tabletop tablets (Jogglers) - Asus AIO - Windows 11

                              X10, UPB, Zigbee, ZWave and Wifi MQTT automation-Tasmota-Espurna. OmniPro 2, Russound zoned audio, Alexa, Cheaper RFID, W800 and Home Assistant

                              Comment

                              Working...
                              X