Announcement

Collapse
No announcement yet.

PI Enhancement

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

  • #16
    Originally posted by MNB View Post
    Dumb question... why do I define the backup; format, type, directories and destination folder both within the event action and within the BLbackup PI? seems counter intuitive, am I missing something? Mike
    The only crossover between BLBackup condfiguration and the Event is the destination directory, which can be overridden in an Event and is not required in the configuration. The backup format and type are only selectable in an Event. The backup directory as selected in an Event is not explained in the docs, but I always leave mine at None. I suppose if you had a number of backup jobs configured, this would allow you to choose among them.
    Randy Prade
    Aurora, CO
    Prades.net

    PHLocation - Pushover - EasyTrigger - UltraECM3 - Ultra1Wire3 - Arduino

    Comment


    • #17
      Randy, I decided to read your post in detail.. If I understand you correctly

      Code:
      (simple example)
      
      If
      and If
      
      Or If
      and If
      The primary trigger is the first "If" statement
      The secondary trigger is the first "Or If" statement
      The first condition is the first "If" statement
      The second condition is the first "and If" (after the first "If")
      The third condition is the first "Or If" statement and
      The fourth condition is the second "and If" (after the first "Or If")

      Trying to better understand your post. Mike
      Computer: CUK Intel NUC7i7BNH
      Op System: Windows 10 Pro - Work Station
      HS Version: HS3 Pro Edition 3.0.0.435

      Plug-Ins: BLBackup, BLGData, BLRoombaWifi, Device History, EasyTrigger, ImperiHome, Nest, PHLocation, Pushover 3P, Restart, Sonos, UltraCID3, UltraWeatherWU3, Z-Wave, and Jon00 scripts.

      Comment


      • #18
        Originally posted by MNB View Post
        Randy, I decided to read your post in detail.. If I understand you correctly

        Code:
        (simple example)
        
        If
        and If
        
        Or If
        and If
        The primary trigger is the first "If" statement
        The secondary trigger is the first "Or If" statement
        The first condition is the first "If" statement
        The second condition is the first "and If" (after the first "If")
        The third condition is the first "Or If" statement and
        The fourth condition is the second "and If" (after the first "Or If")

        Trying to better understand your post. Mike
        Conditions are ALWAYS preceded with AND IF, they are never preceded with IF or OR IF.

        IF and OR IF always precede triggers.

        Here are some screenshots. I built an vent with two triggers and a pair of conditions associated with each trigger

        Click image for larger version

Name:	trigger1b.png
Views:	1
Size:	56.9 KB
ID:	1196524

        The triggers are associated with the conditions as shown by the event being broken into blocks

        Click image for larger version

Name:	trigger1a.png
Views:	1
Size:	54.8 KB
ID:	1196523

        If you delete the secondary trigger

        Click image for larger version

Name:	trigger1c.png
Views:	1
Size:	48.6 KB
ID:	1196525

        you will end up with a corrupted event. What was the first secondary condition becomes the secondary trigger. Note that a weekend day is not a valid trigger since it is true for 48 hours each week.

        Click image for larger version

Name:	trigger2.PNG
Views:	1
Size:	55.9 KB
ID:	1196526

        The only cure is to delete the remaining elements of the secondary block

        Click image for larger version

Name:	trigger3.PNG
Views:	1
Size:	26.1 KB
ID:	1196527

        After deleting it all, you can add a secondary trigger if you want

        Click image for larger version

Name:	trigger4.PNG
Views:	1
Size:	29.9 KB
ID:	1196528

        The lessons are:
        1. Never delete a primary trigger. If you do, delete the event and start over. If you need a different trigger, change it.
        2. If you need to delete a secondary trigger, you must delete all of the conditions as well and it is better to delete them first
        Randy Prade
        Aurora, CO
        Prades.net

        PHLocation - Pushover - EasyTrigger - UltraECM3 - Ultra1Wire3 - Arduino

        Comment


        • #19
          Randy, many thanxs for taking the time.. to edumcate, your examples makes it clear. With you graphics and verbiage I can see that I've corrupted some of my events without not knowing any better.

          Now that Rich and company has formally released HS3 v.435 a practical new feature that would identify (visually or via a subroutine) those events that have; errors, devices with triggers/conditions that are no longer working either by deleting/inserting new devices ect. Today one has to open all of ones events to discover where or not I have conditions that are no longer functional and obviously where triggers are broken and cannot be easily seen other than looking within Logs and doing investigation to figure out where the problem. Mike
          Computer: CUK Intel NUC7i7BNH
          Op System: Windows 10 Pro - Work Station
          HS Version: HS3 Pro Edition 3.0.0.435

          Plug-Ins: BLBackup, BLGData, BLRoombaWifi, Device History, EasyTrigger, ImperiHome, Nest, PHLocation, Pushover 3P, Restart, Sonos, UltraCID3, UltraWeatherWU3, Z-Wave, and Jon00 scripts.

          Comment


          • #20
            Originally posted by MNB View Post
            Randy, many thanxs for taking the time.. to edumcate, your examples makes it clear. With you graphics and verbiage I can see that I've corrupted some of my events without not knowing any better.



            Now that Rich and company has formally released HS3 v.435 a practical new feature that would identify (visually or via a subroutine) those events that have; errors, devices with triggers/conditions that are no longer working either by deleting/inserting new devices ect. Today one has to open all of ones events to discover where or not I have conditions that are no longer functional and obviously where triggers are broken and cannot be easily seen other than looking within Logs and doing investigation to figure out where the problem. Mike
            cheeryfool

            Comment


            • #21
              James, thanxs for the suggestion, I currently use a number of Jon's Plug-ins but not this one, will have download and try it. I would have thought that HS3 would have a few basic tools to do the same....I'm just saying Mike
              Computer: CUK Intel NUC7i7BNH
              Op System: Windows 10 Pro - Work Station
              HS Version: HS3 Pro Edition 3.0.0.435

              Plug-Ins: BLBackup, BLGData, BLRoombaWifi, Device History, EasyTrigger, ImperiHome, Nest, PHLocation, Pushover 3P, Restart, Sonos, UltraCID3, UltraWeatherWU3, Z-Wave, and Jon00 scripts.

              Comment


              • #22
                Originally posted by MNB View Post
                Randy, many thanxs for taking the time.. to edumcate, your examples makes it clear. With you graphics and verbiage I can see that I've corrupted some of my events without not knowing any better.

                Now that Rich and company has formally released HS3 v.435 a practical new feature that would identify (visually or via a subroutine) those events that have; errors, devices with triggers/conditions that are no longer working either by deleting/inserting new devices ect. Today one has to open all of ones events to discover where or not I have conditions that are no longer functional and obviously where triggers are broken and cannot be easily seen other than looking within Logs and doing investigation to figure out where the problem. Mike
                IMO it would be better for HST to fix the events page so event corruption doesn't happen. I have used HomeSeer for many years and didn't know there was a specific procedure for editing events to avoid corrupting them. Could explain some of the problems I've had over the years.
                HS Pro 3.0 | Linux Ubuntu 16.04 x64 virtualized under Proxmox (KVM)
                Hardware: Z-NET - W800 Serial - Digi PortServer TS/8 and TS/16 serial to Ethernet - Insteon PLM - RFXCOM - X10 Wireless
                Plugins: HSTouch iOS and Android, RFXCOM, BlueIris, BLLock, BLDSC, BLRF, Insteon PLM (MNSandler), Device History, Ecobee, BLRing, Kodi, UltraWeatherWU3
                Second home: Zee S2 with Z-Wave, CT101 Z-Wave Thermostat, Aeotec Z-Wave microswitches, HSM200 occupancy sensor, Ecolink Z-Wave door sensors, STI Driveway Monitor interfaced to Zee S2 GPIO pins.

                Comment


                • #23
                  Originally posted by reidfo View Post
                  IMO it would be better for HST to fix the events page so event corruption doesn't happen. I have used HomeSeer for many years and didn't know there was a specific procedure for editing events to avoid corrupting them. Could explain some of the problems I've had over the years.
                  Reid, I agree with you, HST should either fix or provide monitoring tools/routines that easily identify issues much like the one I experienced this week while trying to get a simple event to work and oh by the way I did not delete anything within the events trigger only added the "OR IF". I was glad that Randy had the patience with me and explained the procedure.. I know I can be a little dense at times but I find that by having a simple dialogue can help other users less thicker than me. Mike
                  Computer: CUK Intel NUC7i7BNH
                  Op System: Windows 10 Pro - Work Station
                  HS Version: HS3 Pro Edition 3.0.0.435

                  Plug-Ins: BLBackup, BLGData, BLRoombaWifi, Device History, EasyTrigger, ImperiHome, Nest, PHLocation, Pushover 3P, Restart, Sonos, UltraCID3, UltraWeatherWU3, Z-Wave, and Jon00 scripts.

                  Comment


                  • #24
                    Originally posted by reidfo View Post
                    IMO it would be better for HST to fix the events page so event corruption doesn't happen. I have used HomeSeer for many years and didn't know there was a specific procedure for editing events to avoid corrupting them. Could explain some of the problems I've had over the years.
                    There would be no need for a procedure if there weren't a bug. This is a bug that I discovered as soon as I started with HomeSeer in 2014. I have filed a Bugzilla and communicated it directly via email more than once. It has never been addressed. My suggestion was not to put an "X" beside the primary trigger and when a secondary (or tertiary, etc.) trigger is deleted, automatically remove the conditions, instead of moving the first one up and having it become an invalid trigger. As I wrote above, there is never a need to delete the primary trigger in an event.

                    The only bug that was fixed of the several that were brought up at that time was corruption during Event copying. The deleting of a trigger was never addressed, nor was the issue where during a marathon Event editing session, the time picker for the Wait action will stop getting focus. The same problem can happen to time pickers on delayed actions or delayed Events.
                    Group conditions remain unpredictable and do not work with plug-in triggers.
                    Randy Prade
                    Aurora, CO
                    Prades.net

                    PHLocation - Pushover - EasyTrigger - UltraECM3 - Ultra1Wire3 - Arduino

                    Comment


                    • #25
                      Originally posted by MNB View Post
                      Randy, many thanxs for taking the time.. to edumcate, your examples makes it clear. With you graphics and verbiage I can see that I've corrupted some of my events without not knowing any better.

                      Now that Rich and company has formally released HS3 v.435 a practical new feature that would identify (visually or via a subroutine) those events that have; errors, devices with triggers/conditions that are no longer working either by deleting/inserting new devices ect. Today one has to open all of ones events to discover where or not I have conditions that are no longer functional and obviously where triggers are broken and cannot be easily seen other than looking within Logs and doing investigation to figure out where the problem. Mike
                      Just don't EVER delete a Trigger

                      It is a shame that this problem has never been addressed, because it is one that bites users frequently. I have helped a half dozen or more members who had broken events due to deleting Triggers. Until you know about the problem, it can be a silent killer, rendering Events that look correct completely broken. I was enthusiastic about the importance of fixing this particular bug, but it was never acknowledged of addressed.
                      Randy Prade
                      Aurora, CO
                      Prades.net

                      PHLocation - Pushover - EasyTrigger - UltraECM3 - Ultra1Wire3 - Arduino

                      Comment


                      • #26
                        Originally posted by rprade View Post
                        Just don't EVER delete a Trigger



                        It is a shame that this problem has never been addressed, because it is one that bites users frequently. I have helped a half dozen or more members who had broken events due to deleting Triggers. Until you know about the problem, it can be a silent killer, rendering Events that look correct completely broken. I was enthusiastic about the importance of fixing this particular bug, but it was never acknowledged of addressed.


                        Randy

                        Try adding it to the Quick Wins thread that I created the other week. Of course it may
                        go nowhere, but the everlasting Longitude bug was finally addressed, albeit after a couple of iterations
                        cheeryfool

                        Comment


                        • #27
                          Originally posted by cheeryfool View Post
                          Randy

                          Try adding it to the Quick Wins thread that I created the other week. Of course it may
                          go nowhere, but the everlasting Longitude bug was finally addressed, albeit after a couple of iterations
                          Done! We'll see what happens.
                          Randy Prade
                          Aurora, CO
                          Prades.net

                          PHLocation - Pushover - EasyTrigger - UltraECM3 - Ultra1Wire3 - Arduino

                          Comment


                          • #28
                            Originally posted by MNB View Post
                            James, thanxs for the suggestion, I currently use a number of Jon's Plug-ins but not this one, will have download and try it. I would have thought that HS3 would have a few basic tools to do the same....I'm just saying Mike


                            As an example - I replaced a Z-wave device last night with a different type. This morning, on my commute, I received the broken events report which showed 4 that needed fixing. Took a couple of mins on my iPhone to replace the device in the events and re-run the report to double check.
                            cheeryfool

                            Comment


                            • #29
                              Originally posted by cheeryfool View Post
                              As an example - I replaced a Z-wave device last night with a different type. This morning, on my commute, I received the broken events report which showed 4 that needed fixing. Took a couple of mins on my iPhone to replace the device in the events and re-run the report to double check.
                              James, out of curiosity what events have you set-up (trigger/periodicity) to run the Broken Report and how are you being notify (I'm assuming Pushover?) Mike
                              Computer: CUK Intel NUC7i7BNH
                              Op System: Windows 10 Pro - Work Station
                              HS Version: HS3 Pro Edition 3.0.0.435

                              Plug-Ins: BLBackup, BLGData, BLRoombaWifi, Device History, EasyTrigger, ImperiHome, Nest, PHLocation, Pushover 3P, Restart, Sonos, UltraCID3, UltraWeatherWU3, Z-Wave, and Jon00 scripts.

                              Comment


                              • #30
                                Originally posted by MNB View Post
                                James, out of curiosity what events have you set-up (trigger/periodicity) to run the Broken Report and how are you being notify (I'm assuming Pushover?) Mike
                                cheeryfool

                                Comment

                                Working...
                                X