Announcement

Collapse
No announcement yet.

Did we pay to loose features?

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

    Did we pay to loose features?

    Is it just me? I paid money to "upgrade" to HS4Pro, but apart from the GUI has changed not much else has.

    If anything ive lost features which is annoying me.

    1) I can no longer Duplicate an event, so for similar events I have to create them all as new.

    2) I can no longer filter events in anyway. I need to be able to see all events relating to a particular device.

    3) I had rules where the first line was "device has been for at least", this is no longer supported as the first if statement.

    I was hoping to get more features (maybe "device has been for less than")

    Am i missing something? I paid good money to upgrade and waited a long time for it to be released?

    #2
    I hope your complaints are being addressed in the list of "things to fix in the next version." Otherwise, I'm not going to be a happy camper, either. I was an "early adopter" of HS3 and that experience taught me what an essential virtue patience was.

    I'm not impressed with what I've seen in the interface change, but we'll see.

    There are some major additions that I look forward to, but alas, from reading posts made in this forum, they appear not to be "ready" yet, either.

    I'm trying to stay positive.
    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


      #3
      Originally posted by barto View Post
      Is it just me? I paid money to "upgrade" to HS4Pro, but apart from the GUI has changed not much else has.

      If anything ive lost features which is annoying me.

      1) I can no longer Duplicate an event, so for similar events I have to create them all as new.

      2) I can no longer filter events in anyway. I need to be able to see all events relating to a particular device.

      3) I had rules where the first line was "device has been for at least", this is no longer supported as the first if statement.

      I was hoping to get more features (maybe "device has been for less than")

      Am i missing something? I paid good money to upgrade and waited a long time for it to be released?
      While i'm not trying to sell you on HS4... a couple of things.

      Remember you can access the old UI if you need it. I've found this useful (especially when working with events) as i get used to the new UI.

      on #1, there is a copy button for your event, so this feature is still there.
      #2 ... search is now universal. type the device you want in the search button, and all device names and events that match will show up.
      #3 ... see if that still works pulling old UI (/events in browser).

      Comment


        #4
        Originally posted by barto View Post
        Is it just me? I paid money to "upgrade" to HS4Pro, but apart from the GUI has changed not much else has.
        If anything ive lost features which is annoying me.
        1) I can no longer Duplicate an event, so for similar events I have to create them all as new.
        2) I can no longer filter events in anyway. I need to be able to see all events relating to a particular device.
        3) I had rules where the first line was "device has been for at least", this is no longer supported as the first if statement.
        I was hoping to get more features (maybe "device has been for less than")
        Am i missing something? I paid good money to upgrade and waited a long time for it to be released?
        In my experience, it takes a while for a new version of HS to become fully developed. I plan to wait a while longer before switching from HS3.

        The primary driver for HS4 seemed to be a UI that was accessible from hand-held devices. "Under the covers" I expect there have been some fundamental improvements and I would also expect that over time HS4 will add functionality that will be unique and unavailable in HS3 (with emphasis on over time).

        1) I believe it is possible to duplicate an event using the copy icon to the right of the event in the event list.
        2) This may be available, but I don't use HS4 yet.
        3) The capability is not lost, but the operation of the event has been made more explicit. (This "trigger", which is actually a condition, was causing serious problems for some users.) To implement the function, you can use a recurring trigger and the And If condition. (A recurring trigger of approximately every second, was hidden in the HS3 trigger. HS4 gives you control over how frequently you want the condition to be checked.)
        Mike____________________________________________________________ __________________
        HS3 Pro Edition 3.0.0.548

        HW: Stargate | NX8e | CAV6.6 | Squeezebox | PCS | WGL 800RF, Rain8Net+ | RFXCOM | QSE100D | Vantage Pro | Green-Eye | X10: XTB-232, -IIR | Edgeport/8 | Way2Call | Ecobee3

        Comment


          #5
          I think I must of been blind on the copy feature! Right under my nose!

          Comment


            #6
            I find the search feature finds devices and events etc containing the work you search for in its title

            But I miss that I can’t just find all events based on a particular device. If I want to remove a device I need a quick way to see all events using it.

            (HS3 was always annoying that you couldn’t filter on events using a particular timer or counter)

            How do you get the old ui please?

            Comment


              #7
              I just tried search again... works for me without device name in title. For example, i have a device/light in my office called "aiport". It's part of two events (lights on and off). When i search on the word "airport", this is what i see:

              Click image for larger version

Name:	Annotation 2020-07-18 094544.jpg
Views:	912
Size:	15.8 KB
ID:	1403743

              As for the old UI,... you can add /events to the end of your HS IP address in the browser (also works with /devices) to see the old UI.

              http://xxx.xxx.x.xxx/events

              Comment


                #8
                I have to agree that HS4 is a bit underwhelming for my needs. A big emphasize was put on making the GUI better for small devices. That's for people who want to do everything via their mobile device and are happy with relatively simple home automation. That's really where the big market is. For that reason I am not complaining too much because I want HS to survive. Having said that, I see HS more like on the level of Control4 and similar high level automation and in that regard HS4 didn't deliver much (also no HS4Touch....!!!!). I hope they don't neglect that market but the signs aren't good. In any case, check the website below. Around the middle they tell you what is available now in HS4 and what they are still planning to introduce.

                https://homeseer.com/hs4-smart-home-...tion-software/

                Comment


                  #9
                  Originally posted by barto View Post
                  3) I had rules where the first line was "device has been for at least", this is no longer supported as the first if statement.
                  When I first moved to HS I used that trigger quite extensively, but quickly realised it actually puts a lot of strain on the system. If you had "at least 5 seconds" for example then every single moment thereafter (5.15375 seconds, 5.251436 seconds, 5.27315 seconds, etc) is making HomeSeer re-evaluate your event.

                  If you rework your events to be more specific, say "exactly 5 seconds" or perhaps using EasyTrigger which can do timings for you, it'll take immense load off your system 👍

                  I'm presuming they therefore took this trigger away intentionally?

                  What the actual?!? When I make a sarcastic remark or joke it is moderated/deleted.
                  But you specifically go out of your way to label multiple HS4 issues that cause data loss/crash of HS4 to be "grumbles".
                  I can't even begin to put into words how offensive this is.

                  Comment


                    #10
                    I have to admit I found HS4 disappointing. I finally got HS4 up and running and really hate the new GUI. At least for me it's very slow and cumbersome. I know it takes time to get used to new things, but it just feels like it went ten steps backwards. Fortunately, I backed everything up before the upgrade, so after letting it run for a week, I restored HS3 and am happily running again. Guess I'll wait for a while before trying again.

                    Comment


                      #11
                      Originally posted by Tillsy View Post

                      When I first moved to HS I used that trigger quite extensively, but quickly realised it actually puts a lot of strain on the system. If you had "at least 5 seconds" for example then every single moment thereafter (5.15375 seconds, 5.251436 seconds, 5.27315 seconds, etc) is making HomeSeer re-evaluate your event.

                      If you rework your events to be more specific, say "exactly 5 seconds" or perhaps using EasyTrigger which can do timings for you, it'll take immense load off your system 👍

                      I'm presuming they therefore took this trigger away intentionally?
                      What’s easy trigger?

                      Comment


                        #12
                        Originally posted by Tillsy View Post

                        When I first moved to HS I used that trigger quite extensively, but quickly realised it actually puts a lot of strain on the system. If you had "at least 5 seconds" for example then every single moment thereafter (5.15375 seconds, 5.251436 seconds, 5.27315 seconds, etc) is making HomeSeer re-evaluate your event.

                        If you rework your events to be more specific, say "exactly 5 seconds" or perhaps using EasyTrigger which can do timings for you, it'll take immense load off your system 👍

                        I'm presuming they therefore took this trigger away intentionally?
                        I used that 'trigger' for a remote zwave plug that sometimes had connection issues. If I used the "exactly" trigger, it would fire once. If that command failed, the device would be left on for the whole night. With the At least, it would auto retry (I had not retrigger set to 15 seconds).

                        Comment


                          #13
                          Originally posted by barto View Post

                          What’s easy trigger?
                          EasyTrigger is a plugin that helps you build HS events: https://shop.homeseer.com/collection...re-plug-in-hs3

                          Comment


                            #14
                            Originally posted by Tillsy View Post

                            When I first moved to HS I used that trigger quite extensively, but quickly realised it actually puts a lot of strain on the system. If you had "at least 5 seconds" for example then every single moment thereafter (5.15375 seconds, 5.251436 seconds, 5.27315 seconds, etc) is making HomeSeer re-evaluate your event.

                            If you rework your events to be more specific, say "exactly 5 seconds" or perhaps using EasyTrigger which can do timings for you, it'll take immense load off your system 👍

                            I'm presuming they therefore took this trigger away intentionally?
                            Yes that trigger has been removed in HS4 because, most users didn't realize that it would re-trigger indefinitely when using it.
                            You can achieve the same behavior in HS4 by using a recurring trigger and a "device has been for at least condition"



                            Comment


                              #15
                              Originally posted by spud View Post

                              Yes that trigger has been removed in HS4 because, most users didn't realize that it would re-trigger indefinitely when using it.
                              You can achieve the same behavior in HS4 by using a recurring trigger and a "device has been for at least condition"


                              I use this trigger to shut down source components when all of the amplifiers in my multi-room system have been turned off. It did run repeatedly once triggered until I added an "and if" statement regarding the status of the sources. No problem here as far as I can see, this is just basic PLC programming.

                              Comment

                              Working...
                              X