Announcement

Collapse
No announcement yet.

Feature Suggestions

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

    #31
    DEVICE DISPLAY FILTERS: How are these supposed to work?

    Having no filters on FLOOR, ROOM and CATEGORY filter options selected displays all Devices that were created.
    Selecting all floors in the FLOOR filter results in all devices being displayed. Likewise selecting all rooms in the ROOM filter has no effect on displayed devices. But now my display has a huge filter banner on the top which effectively did nothing to which devices are listed. Now the logic gets inverted and unchecking an floor or room removes devices in that floor or room from the display.

    I do not want to display any timers or counters on the device page so logically I check all items on the FLOOR filter and then X out the Counters-Times FLOOR. I now have what I need with a HHHUUUUUGGGGEE 7 line banner on my mobile device that leaves almost no room to look at the devices. If there is also one ROOM I wish to exclude the banner takes up my whole screen and no devices can be seen. I use a tablet with the web page display, not the mobile app.

    So that means items checked in the FLOOR filter includes those devices unless of course you have none checked and that also means all devices are displayed.

    I can check the filters by clicking on FLOOR, ROOM or CATEGORY, so why is the big banner required showing all checked items? If there a way to remove the filter list from the display?

    Also since the default display of devices is to include why don't the FLOOR and ROOM filter checked items cause those items not to be displayed​ if a single item is checked?

    Now I think I've got this understood as all of the items in the CATEGORY drop down are still unchecked and all those category's are are being displayed. So checking all items would logically work the same way. NOT So I do not understand the logic behind these filters. In electrical engineering there are band pass and band stop or notch filters.
    The FLOOR and ROOM filter act like an all pass filter with no items check or all items checked. Once all items are checked, the FILTER become a notch filter for any devices in the unchecked floor or room

    Logically if all categories are selected by the filters then it becomes an all pass filter. Now I'm trying to use the CATEGORY filter on devices display page and cannot figure out the logic for this filter. So, I checked fans category, and I have no devices in the fans category and no devices were visible, I thought maybe this is the reverse logic and checking one item creates a band pass or display filter and that will only allow fans to be displayed. Not so.
    So I checked all devices in categories and then uncheck fans but still have no devices.
    It seems to make no difference which CATEGORY item is checked, as when any one of them is checked or all of them are checked, no devices are displayed.

    How are these filters supposed to work?

    I could go without understanding the logic of it, it the big banner showing filter items was removed. When adding a new device to a new ROOM or FLOOR, I just click on the category and check it. The banner adds no information because the new ROOM or FLOOR is not shown and I can find out with one click that I must do anyway to add the missing FLOOR or ROOM.

    So the feature I'm looking for is a way to remove the checked filter items from the display banner at the top of the page and go back to the one line that lets me select FLOOR ROOM CATEGORY.

    Comment


      #32
      Yes, I don't much like all the filters either. In HS3 for those devices I didn't always want to see, I created a room called hidden and put the devices of concern in there. When I wanted to look at them, I would check the functional group to view them. The show all devices messed up my device list.

      To the point of the Op, showing and/or rather having the ability to hide the list of filters would be a nice addition.
      HS3PRO 3.0.0.500 as a Fire Daemon service, Windows 2016 Server Std Intel Core i5 PC HTPC Slim SFF 4GB, 120GB SSD drive, WLG800, RFXCom, TI103,NetCam, UltraNetcam3, BLBackup, CurrentCost 3P Rain8Net, MCsSprinker, HSTouch, Ademco Security plugin/AD2USB, JowiHue, various Oregon Scientific temp/humidity sensors, Z-Net, Zsmoke, Aeron Labs micro switches, Amazon Echo Dots, WS+, WD+ ... on and on.

      Comment


        #33
        I agree the HS4 device filtering could be made to be much more useful, especially as the number of devices, areas, rooms and categories grow. I've made full use of the area/room/category structure but find it difficult to view quickly what I need to see. Two things I like to suggest:

        1. Add Boolean logic functionality to the filtering with AND, OR, NOT operators. This way I can filter very easily for instance "NOT rnbWeather" where rnbWeather is a Room. This would return all devices except where Room=rnbWeather.
        2. Add ability to save filters. This would allow user to create a custom device filter logic for display, save the logic with a name, and recall that filter by name for reuse. The saved filter would be available across system restarts and new UI sessions by saving the filter logic on the server. Functions should be available to the user to manage the saved filters such as delete, rename, etc.

        Comment


          #34
          I would like to see a delay at boot time setup option for HS4, either in the O/S or in the startup.vb script prior to anything else happening. I have a rather complex local network based on a mesh router system and StarLink access to the internet. Due to the power on delays associated with these network devices, the Homeseer PI HS4 fails to boot properly upon a power failure and subsequent restoration of power restart. It fails to find the Insteon Hub (different mesh router due to location critical radio) and subsequently boots without its Insteon devices. It never makes the correct connection to the Insteon Hub. The only way it works is to manually reboot it after the entire local mesh network and StarLink modem system is up and running.

          I corrected this by adding a 2-minute delay to the Debian Linux startup script. It works now, but that has made my Homeseer factory PI O/S non-standard now. A setup parameter allowing a variable boot delay would solve this restart problem for a lot of cases where mesh systems or satellite internet is involved.

          Comment


            #35
            I was a long time HS3 user who finally upgraded to HS4 a few months ago. I have now had a chance to "digest" the new functionality that came with the HS4 upgrade and I am generally very pleased with the changes provided. Off the top of my head I will mention UI improvements, the ability to discover events referencing devices as well as the ability to easily locate broken devices. Also, the recently added device filter is fantastic as it replaces the (in my mind) less useful search listing. Ongoing system stability is solid and the upgrade process was fairly straightforward (although not without a few minor hiccups :-)).

            Here is my suggestion for an HS4 feature (apologies if this has been brought up before):

            It would be great if the "architecture" built in HS4 for devices was extended to events and other things like timers, counters etc. This would include:

            - normalize events, devices, counters, timers and variables using the current architecture used for devices
            (i.e. grid view/list view, drilldown to a tab display where events would have a tab for the logic, another for event settings etc.
            - going forward refer to all events, devices, timers, counters etc. as "Home Automation Objects"
            - add the Room and Floor attributes to events and all other "HAO" types
            - change the device view to be a global object view, depending on the search different object types can be listed together
            - add a selection dropdown at the top of the "object" listing allowing the selection of Object Types (devices, events etc.) similar to the selections for Room and Floor in the current device view.
            - following from the above, the filter functionality would apply to all "objects" = devices, events, counters, timers
            - expand the referencing functionality to apply to all objects (not just events referencing a given device)
            - sunset the old listing based search view.

            I realize this would be a significant undertaking but I believe it would contribute greatly to the user friendliness of the product and lead to a better more intuitive "Home Automation Management" experience.​

            Comment


              #36
              Originally posted by RFB View Post
              I would like to see a delay at boot time setup option for HS4, either in the O/S or in the startup.vb script prior to anything else happening. I have a rather complex local network based on a mesh router system and StarLink access to the internet. Due to the power on delays associated with these network devices, the Homeseer PI HS4 fails to boot properly upon a power failure and subsequent restoration of power restart. It fails to find the Insteon Hub (different mesh router due to location critical radio) and subsequently boots without its Insteon devices. It never makes the correct connection to the Insteon Hub. The only way it works is to manually reboot it after the entire local mesh network and StarLink modem system is up and running.

              I corrected this by adding a 2-minute delay to the Debian Linux startup script. It works now, but that has made my Homeseer factory PI O/S non-standard now. A setup parameter allowing a variable boot delay would solve this restart problem for a lot of cases where mesh systems or satellite internet is involved.
              Another option might be a time delay power strip such as is used in server farms and high end stereo systems to contol equipment power on sequences.

              Comment


                #37
                Minor item here: In the HS4 Log, suggest revising the "Type" category for Event Triggers to "Trigger" or something similar. These items are currently only classified as Info. Would be helpful to be able to Type Filter by Triggered events if needing to troubleshoot what caused an unexpected automation behavior.

                Comment


                  #38
                  Originally posted by goldriver View Post

                  Sorry hould have been more specific, multi language ... I tried phrases in french with this option once and it was catastrophic...
                  Ui translations in other languages. Right now it is only english. Would like it in french


                  ++1 for both


                  Visit zee e-maison : http://www.e-maison.com

                  Comment


                    #39
                    Add evaluation result display to Event conditions.
                    This one should be fairly simple to implement, and I'd find it very informative.
                    In my image below you can see I added a column for Status of each of the evaluations. In the case of time based it would be a live display of the current time.
                    The same should be applied to Action conditions so that every state being evaluated shows its current result at all times.

                    Click image for larger version

Name:	image.png
Views:	203
Size:	176.7 KB
ID:	1647983

                    Comment


                      #40
                      Originally posted by QuikDraw View Post
                      Add evaluation result display to Event conditions.
                      This one should be fairly simple to implement, and I'd find it very informative.
                      In my image below you can see I added a column for Status of each of the evaluations. In the case of time based it would be a live display of the current time.
                      The same should be applied to Action conditions so that every state being evaluated shows its current result at all times.

                      Click image for larger version

Name:	image.png
Views:	203
Size:	176.7 KB
ID:	1647983
                      I don't recall if I submitted a feature request for exactly that functionality or if I was just thinking of submitting such a request. In any case, I also would find that very useful.

                      Comment


                        #41
                        macromark and rjh I am going to link to my feature requests for HSTouch Designer. Having a better two-way communication between HSTouch and HS incl. HS knowing with which client it is dealing with (location awareness) would be VERY helpful and avoid cumbersome workarounds. I believe it should be fairly straightforward and provide a big improvement.

                        ttps://forums.homeseer.com/forum/homeseer-products-services/general-discussion-area/the-suggestion-box/1617236-feature-suggestions?p=1617253#post1617253

                        Comment


                          #42
                          Not a software suggestion here, but rather a hardware one.

                          I would really love to see the HSM200 multi-sensor available in a "decora style" hardwired version rather than plug-in style. This could be done as either a full sized decora or a half-sized one combined either with a half-switch or half-receptacle (white, and light almond too pretty please :-). You could also value-add these by making them usable as a night-light by brightening up the LEDs a bit, you already have the motion and light sensors built-in. There are a lot of manufacturers (Leviton, Legrand, etc) that are already doing both the full-sized and half-sized form factors as night-lights so it's not uncommon, you'd just be effectively pimping out the concept.

                          The HSM200 itself is great, I have several... but with the exception of the one plugged in to one of the kitchen counter outlets the rest of them are all plugged into extension cords and sitting on tables so they're visible. If you're only using them as sensors then having them at plug-height is ok, but if you're taking advantage of the indicators then having them plugged in near the floor makes them impractical.

                          Think of this hardwired device installed at light-switch level next to your exit doors warning you that you've left a window open, or in your bedroom indicating that you've got a door or window open/unlocked and the bonus of detecting motion if someone comes in the door. Alternately at plug-level in a kid's room as a color-changeable night-light, and a warning if there's movement when they're supposed to be sleeping.

                          Comment


                            #43
                            I wish the webserver and myhs was more efficient and forgiving on remote connections.
                            I used myhs for many years on HS3 and now 7 months on HS4. There are numerous instances where I've had connection drop outs and the spinning circle to only get timeouts trying to bring forth the devices page. On many occasions I would see the following:

                            (663075) Timeout from host, source IP: 151.124.104.72 TimeMS: 200

                            As well, in the hslog - not nessarily at the same time.

                            HomeSeer
                            Warning

                            Error serializing myhs data: Unable to write data to the transport connection: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host

                            I've even seen reported by myhs that stated my instance of homeseer was down. I've either had to wait, or login directly and restart "Enable Remote Access through MyHS Service".All the while accessing homeseer directly or my emails server on the same host instantaneously.

                            So yeah, please improve this.


                            HS3PRO 3.0.0.500 as a Fire Daemon service, Windows 2016 Server Std Intel Core i5 PC HTPC Slim SFF 4GB, 120GB SSD drive, WLG800, RFXCom, TI103,NetCam, UltraNetcam3, BLBackup, CurrentCost 3P Rain8Net, MCsSprinker, HSTouch, Ademco Security plugin/AD2USB, JowiHue, various Oregon Scientific temp/humidity sensors, Z-Net, Zsmoke, Aeron Labs micro switches, Amazon Echo Dots, WS+, WD+ ... on and on.

                            Comment


                              #44
                              For events with multiple OR IF triggers I would like the HS Log to indicate which of the triggers was hit.
                              For example, I have an event that's triggered at sunrise OR IF sunset OR IF device value changed.
                              The log looks like this no matter which of the triggers was hit:
                              Event Trigger "My Event Name"

                              I would like for it to say:
                              Event Trigger "My Event Name" Trigger: Sunrise (7:08:23 AM)
                              OR
                              Event Trigger "My Event Name" Trigger: Sunset (6:20:57 PM)
                              OR

                              Event Trigger "My Event Name" Trigger: "My Device Name" Changed Value

                              Now, obviously I can tell by the timestamp whether it was sunrise or sunset that triggered my event. But it's very possible for "My Device" value to change very close to sunrise or sunset. In those cases it would be nice to see in the log which trigger was actually hit.

                              I have workarounds using event conditions to determine which trigger was hit, but because time-based triggers work differently than time-based conditions, they can't be 100% reproduced.

                              And the reason I'm asking is because I have an event that's being double-triggered when it shouldn't.
                              The event runs a script that changes a device value if certain conditions are met.
                              Yes, the device it manipulates is the same one referenced in the trigger.
                              And yes, I realize that if the script actually changes the device value it will trigger the event.
                              I'm not concerned with that specific double-triggering which is expected.​
                              The script checks the current value, and does not set the device if the new calculated value is the same.
                              And yet, my event is always double triggered, implying that HS4 believes the device changed value even when it did not.

                              Comment


                                #45
                                New HS sensors to include builds for the wider market than just US. Sensors for UK, EU etc.

                                Comment

                                Working...
                                X