Announcement

Collapse
No announcement yet.

HAI 2.0.0.19 or 2.1.2546.18811 version?

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

    HAI 2.0.0.19 or 2.1.2546.18811 version?

    Just started testing my upgrade from 1.7 to 2.x. This is new PC hardware etc and I'm lucky enough to be able to just about run the two systems at the same time while I debug HS 2.x.

    I'm running the release plug 2.0.0.19 and have found some issues.
    The release info for the 2.1.2546.18811 version doesn't have the differences between the release and the beta (it only talks about version 2.0.0.5).

    Here's some issues I have. Anyone know if these are fixes in the beta?
    I'll log helpdesk requests if required but I thought someone might know already.

    - Setup's always an issue with the panel code. The plugin shouldn't re-try to login over and over again with an incorrect code, it justs locks the panel out. Try once only then fail. Caused me to wait 1 hour TWICE while I got the code right... - Enhancement

    - I let the plugin create the devices before I imported the name, so I presed the "Delete All Plugin-Devices" to get it to recreate them. Big mistake, the devices didn't delete and I had this in the my logs forever:
    31/12/2006 7:54:24 PM ~!~HAI System~!~Delete Devices Button Pressed - Deleting all devices. Restart HomeSeer to recreate the devices.
    31/12/2006 7:54:33 PM ~!~HAI System~!~Error: Failed to initialize panel on COM 1. (Resume On-Line Init-1)
    31/12/2006 7:54:34 PM ~!~HAI System~!~Error: Failed to initialize panel on COM 1. (Resume On-Line Init-2)
    31/12/2006 7:54:45 PM ~!~HAI System~!~Error: Failed to initialize panel on COM 1. (Resume On-Line Init-1)
    31/12/2006 7:54:45 PM ~!~HAI System~!~Error: Failed to initialize panel on COM 1. (Resume On-Line Init-2)
    31/12/2006 7:55:06 PM ~!~HAI System~!~Error: Failed to initialize panel on COM 1. (Resume On-Line Init-1)
    31/12/2006 7:55:06 PM ~!~HAI System~!~Error: Failed to initialize panel on COM 1. (Resume On-Line Init-2)
    .....
    Had to manually delete all the devices.

    - Thermostats
    + Heat/Cool Setpoints Devices are created in F not C (even when the devices were created with TemperatureUnit=C command. So I have setpoints from 50 to 80 something.. Hummm.. If it's 80 C, then the world is coming to an end! HAVC page is ok. Just the devices that are created have this issue.

    + Heat Only Thermostat still lists a "Cool" setting. Plugin correct detects heat only at startup.
    31/12/2006 9:03:50 PM HAI System Thermostat (1): Heat Only


    - Zone Devices have Zone Number in them (Outside Side (18)) do we really need the zone number (optional maybe? Can we turn it off?)
    Thermo's have the same, thermo number in ().. Eg Main Stat Mode (1)

    - Shows Thermostat Zone (Zone 16) as a Zone, if there are thermostats then this really isn't a "Zone" as such.

    - One other thing. The test system I have HS2.x and the HAI plugin on is pretty crappy but the HAI plugin is taking %50 of CPU, all the time. Anyone else seeing high CPU usage for this plugin?

    And a side question: Can you delete Plugin Created devices without causing the plugin "issues". Eg can I just delete the Zone 16 without causing the plugin problem with it trying to update a device that doesn't exist? What about renaming a Zone Device after it's created Eg say I wanted to remove the numbers manually?

    Please forgive the typos above, been a long HS 2.x day!

    Ross.
    Last edited by rirvine; December 31, 2006, 08:06 AM.

    #2
    Hello Ross,
    Been running most currently posted beta HAI plugin on currently posted HS2 beta now for about a month. I had the same issues with initialization/communications. Once connected (started off with posted stable version then moved to beta) its not skipped a beat. Response times are much faster than HS1. I don't mind seeing the zone numbers as I sometimes lose track of the associations. (just moved my sprinkler names back to zone names also). I am not seeing high CPU utilization. When initially configuring/reading panel names only got the first one so I manually edited INI file. I have renamed and removed zones with no issues. I currently have migrated most of my serial connections over to HS2 (IE: Insteon, CID, W800, AB8SS, Temp05, Temp08 and HAI) and have been rebuilding events. Still testing Rain8Net/MCS Sprinkler Beta though on HS1 box. I did blow up my HS2 server yesterday (windows 2003) For some odd reason Microsoft media player (and HS2) quit playing WAV & MP3 files. In trying to repair it I blue screened it and it never came back. I did a repair (upgrade) and all is well again. I am actually getting ready to shut down my HS1 server after finishing testing mcs Sprinklers.
    - 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
      Hi Pete, thanks for the reassuring words. The HAI Plugin is almost the centre of my universe when it comes to Home Automation. Alarm state and motion around the house is part of almost everything HS does. I need that to be as stable as "ol' faithful 1.1.30".

      How many Zones do you track? I wonder if the CPU utilization I'm seen is due to 40 Zones. From memory anogee has more zones than me, so it would good to hear from him to see how he's going.

      Thanks,

      Ross.

      Comment


        #4
        I think I might understand the high CPU now. It's doing a re-login to the panel due to:
        ~Entering Quick_Recovery (that's a bad thing)
        About 3-4 times a minute.

        It seems when there are a few events to process it just goes nuts.

        I'll upgrade to the latest and see what happens.

        Comment


          #5
          Latest plugin not working well..
          1/01/2007 1:37:18 PM ~!~HAI System~!~Get_Multi_Zone_Status experienced error getting zones 28 thru 258 : 6, Arithmetic operation resulted in an overflow.

          I only configured the plugin for Zero Units, so I don't know why it's asking for 28 to 258. As it's using 258 it's using the extended unit status call causing read errors and all sorts of issues. I have configured it for 28 Zones, so it might be confusing the Zero X10 Units but 4 Flags.


          1/01/2007 1:36:33 PM:048993.41 ~Entering Send_Receive
          1/01/2007 1:36:33 PM:048993.54 ~Sending (Serial): 5A-5-17(UNIT STATUS)-0-13-1-2-5-C2
          1/01/2007 1:36:33 PM:048993.92 ~Received (Serial): 5A-D1-18(UNIT STATUS)-1-0-0-1-0-0-1-0-0-1-0-0-1-0-0-1-0-0-1-0-0-1-0-0-1-0-0-1-0-0-1-0-0-1-0-0-1-0-0-1-0-0-0-0-0-1-0-0-0-0-0-1-0-0-0-0-0-1-0-0-0-0-0-1-0-0-0-0-0-1-0-0-0-0-0-1-0-0-1-0-0-1-0-0-1-0-0-1-0-0-0-0-0-1-0-0-0-0-0-1-0-0-0-0-0-1-0-0-0-0-0-1-0-0-0-0-0-1-0-0-0-0-0-1-0-0-1-0-0-1-0-0-1-0-0-1-0-0-0-0-0-1-0-0-1-0-0-1-0-0-0-0-0-1-0-0-1-0-0-1-0-0-1-0-0-1-0-0-1-0-0-1-0-0-1-0-0-1-0-0-1-0-0-1-0-0-0-0-0-1-0-0-1-0-0-1-0-0-1-0-0-1-0-0-0-0-0-1-0-0
          1/01/2007 1:36:33 PM:048993.94 ~Returning FALSE from ReadFromPanel due to CheckSum Error

          Humm.. Not going well...

          Can't use this plugin, the unit status call is killing everything and takes the plugin about a minute to recover, then, the next Unit Status call like this just kills it again.

          Comment


            #6
            Hello Ross,

            Happy New Year to you!

            I have one expansion board and am using 12 on the main board (plus 4 for thermostat and temperature sensors) and 10 on the expansion board. I keep adding more sensors though. I prefer to have be hard wired versus wireless on the motion sensors. I have migrated to Insteon but still use Omni Pro II to turn on my lights. For exterior motion I use the external IR sensors to turn on exterior lights and utilize Omni Pro II programming command lines.
            - 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
              New error log

              I just updated my HAI plugin to Version 2.1.2546.18811 and received the below error log:


              1/1/2007 11:04:39 PM - HAI System - CreateDevices_SetValues Experienced Error 9 which is Index was outside the bounds of the array. on line 0
              1/1/2007 11:04:39 PM - HAI System - CreateDevices_SetValues returned False - Please report this to the plug-in author.

              Has anyone else seen this?

              cheers,

              Craig

              Comment


                #8
                I have not with Version 2.1.2546.18811.
                - 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


                  #9
                  Craig,

                  I can't find the log entry at the moment, but I'm sure that's one of the error I've seen as well.

                  Ross.

                  Comment


                    #10
                    I've used the plug-in for a long time, and like the others, I really could not live without it. Recently I worked with Rick to remove an error that was occuring with the latest panels, basically the ones released in the last year.

                    I upgraded from HS1.7 to HS2.1 about 3 months ago, and at the time I also upgraded the plug-in. Let me say there are some quirks with this plug-in, even the last one, but with some tweaking, it does seem to work well. The only errors I get are some errors on shutdown, and I think this is more a HS shutdown issue than a HAI plug-in issue. I have an OmniPro II with 48 zones and 2 expansion boards.

                    One error that I did see, that I think I saw that you were getting is an error caused on install. I recommend you install the "offical" HAI plug-in 2.0.0.19 first, get it running, THEN upgrade to the latest beta but ONLY when 2.0.0.19 is up and running. If that doesn't work, post here, and we should be able to get you running. As I said, this plug-in does have quirks, but it runs very well once you get by those.

                    Comment


                      #11
                      I've never been able to get the beta version running, so I stuck with the production version.

                      production version -> works good -> upgrade to beta -> no communications -> spend 4 miserable hours swearing and trying to get the beta to work -> major headache -> go back to production version -> everything works again.

                      I'm slow, but not completely stupid. After 4-5 iterations of the above, I learned my lesson and stay with the production version.
                      My system is described in my profile.

                      Comment

                      Working...
                      X