Announcement

Collapse
No announcement yet.

How to Upgrade to HS4...?

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

    #16
    Originally posted by kenm View Post

    The link in this post returns "Not Found". Where'd the upgrade instructions go?
    All of the guides are on the HomeSeer support page:
    https://homeseer.com/support-home/
    -Rupp
    sigpic

    Comment


      #17
      Originally posted by wpiman View Post

      I was cautious and waited to upgrade. I did it maybe a month ago and it has been pretty smooth.... I recommend the alternate procedure because you can run both at separate times.
      You don't have to use the alternate route to be able to run both. Just make a copy of the HS3 folder before the upgrade, which should be done anyways. You can then just navigate to that folder and start HS3.

      Comment


        #18
        Thanks Rupp and mulu . Onward and upward.

        Comment


          #19
          Is it still true that you have to go in and edit any events that run scripts if you use the alternate method?

          Comment


            #20
            If you put HS4 into the old HS3 folder, no (that will happen if you follow the instructions). If you want HS4 in a folder called HS4, yes. IF you want to keep HS3 in the original folder and put HS4 in its own folder, yes.
            HomeSeer Version: HS3 Pro Edition 3.0.0.500
            Operating System: Microsoft Windows 10 Pro - Work Station

            Enabled Plug-Ins:
            2.1.0.119: AmbientWeather | 3.0.21.0: BLLock | 2.0.24.0: BLUPS | 1.3.6.0: Device History | 3.0.0.56: EasyTrigger | 3.1.0.7: MeiHarmonyHub | 3.0.6681.34300: UltraCID3 | 3.0.6644.26753: UltraLog3 | 3.0.6554.33094: UltraMon3 | 3.0.0.91: weatherXML | 3.0.1.245: Z-Wave | 3.0.51: HS Touch Designer | 3.0.0.40 Z-Seer+

            Comment


              #21
              ewkearns is right. Personally, I would rather edit the scripts than installing HS4 in the HS3 folder. It just a copy replace. Of course if you have a lot of scripts then it can be a pain to manually open each file but I am sure there are tools for it. In Linux I think you can do it with a simple one liner using sed but I am sure there is also something for Windows.

              Btw, I have put in a request that they introduce a global variable that can be used instead of having to use absolute paths. Hopefully, that way most people scripting will use that instead of hardcoding paths.

              Comment


                #22
                It is already possible to assign a relative path:

                https://forums.homeseer.com/forum/ho...49#post1415149

                However it should be the default behavior.
                Had to modify all my events and need to make sure I modify the path on each new event/script...

                thanks to zwolfpack for the hint.

                Comment


                  #23
                  An interesting observation... I decided to use the alternate method and install HS4 in "HomeSeer HS4" and was pleasantly surprised that all of the events that called scripts continued to work after the migration. As it turned out, the events were running the scripts from the HS3 scripts directory since it was on the same system. These have all been manually edited now to point to the scripts I copied over to the new installation.

                  I also noticed that HS4 does not store an absolute path for the script in events.json, but only the script name and extension.

                  Upgrade completed and besides a "few glitches" due to may own customizations, everything seems to be functioning.

                  Onward and Upward.

                  Ken

                  Comment

                  Working...
                  X