Originally posted by MNB
View Post
Announcement
Collapse
No announcement yet.
PI Enhancement
Collapse
X
-
HS4 Pro, 4.2.19.0 Windows 10 pro, Supermicro LP Xeon
-
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 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. MikeComputer: CUK Intel NUC7i7BNH
Op System: Windows10 Pro - Work Station
HS Version: HS4 Pro Edition 4.2.19.0
Plug-Ins: AK Weather 4.0.5.25,APCUPSD 3.3.2.3,BLBackup 2.0.63.0,BLEditor 2.0.11.0,BLGData 3.0.55.0,BLOccupied 2.0.28.0,BLShutdown 1.0.6.0,Blue-Iris 3.1.3.33206,Device History 3.2.0.2,EasyTrigger 3.0.0.76,Harmony Hub 4.0.14.0,iRobot 5.22.41.1,JowiHue 4.0.8.7,Nest 3.0.0.34,NetCam Plugin 1.0.0.5,PHLocation2 3.0.0.64,Pushover 4.0.10.0,Random 3.0.0.2,Restart 1.0.0.7,Ring 1.0.0.9,SDJ-Health 3.1.1.3,Sonos 3.1.0.59,Sonos4 4.0.1.12,UltraCID3 3.0.6681.34300,UltraMon3 3.0.6554.33094,UltraNetCam3 3.0.6413.20219,Unifi 4.0.32.0,Zigbee 4.0.11.0,Z-Wave 4.0.3.0, and Jon00 scripts.
Comment
-
Originally posted by MNB View PostRandy, I decided to read your post in detail.. If I understand you correctly
Code:(simple example) If and If Or If and If
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
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
The triggers are associated with the conditions as shown by the event being broken into blocks
If you delete the secondary trigger
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.
The only cure is to delete the remaining elements of the secondary block
After deleting it all, you can add a secondary trigger if you want
The lessons are:- Never delete a primary trigger. If you do, delete the event and start over. If you need a different trigger, change it.
- 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
HS4 Pro, 4.2.19.0 Windows 10 pro, Supermicro LP Xeon
Comment
-
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. MikeComputer: CUK Intel NUC7i7BNH
Op System: Windows10 Pro - Work Station
HS Version: HS4 Pro Edition 4.2.19.0
Plug-Ins: AK Weather 4.0.5.25,APCUPSD 3.3.2.3,BLBackup 2.0.63.0,BLEditor 2.0.11.0,BLGData 3.0.55.0,BLOccupied 2.0.28.0,BLShutdown 1.0.6.0,Blue-Iris 3.1.3.33206,Device History 3.2.0.2,EasyTrigger 3.0.0.76,Harmony Hub 4.0.14.0,iRobot 5.22.41.1,JowiHue 4.0.8.7,Nest 3.0.0.34,NetCam Plugin 1.0.0.5,PHLocation2 3.0.0.64,Pushover 4.0.10.0,Random 3.0.0.2,Restart 1.0.0.7,Ring 1.0.0.9,SDJ-Health 3.1.1.3,Sonos 3.1.0.59,Sonos4 4.0.1.12,UltraCID3 3.0.6681.34300,UltraMon3 3.0.6554.33094,UltraNetCam3 3.0.6413.20219,Unifi 4.0.32.0,Zigbee 4.0.11.0,Z-Wave 4.0.3.0, and Jon00 scripts.
Comment
-
Originally posted by MNB View PostRandy, 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. Mikecheeryfool
Comment
-
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 MikeComputer: CUK Intel NUC7i7BNH
Op System: Windows10 Pro - Work Station
HS Version: HS4 Pro Edition 4.2.19.0
Plug-Ins: AK Weather 4.0.5.25,APCUPSD 3.3.2.3,BLBackup 2.0.63.0,BLEditor 2.0.11.0,BLGData 3.0.55.0,BLOccupied 2.0.28.0,BLShutdown 1.0.6.0,Blue-Iris 3.1.3.33206,Device History 3.2.0.2,EasyTrigger 3.0.0.76,Harmony Hub 4.0.14.0,iRobot 5.22.41.1,JowiHue 4.0.8.7,Nest 3.0.0.34,NetCam Plugin 1.0.0.5,PHLocation2 3.0.0.64,Pushover 4.0.10.0,Random 3.0.0.2,Restart 1.0.0.7,Ring 1.0.0.9,SDJ-Health 3.1.1.3,Sonos 3.1.0.59,Sonos4 4.0.1.12,UltraCID3 3.0.6681.34300,UltraMon3 3.0.6554.33094,UltraNetCam3 3.0.6413.20219,Unifi 4.0.32.0,Zigbee 4.0.11.0,Z-Wave 4.0.3.0, and Jon00 scripts.
Comment
-
Originally posted by MNB View PostRandy, 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. MikeHS 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
-
Originally posted by reidfo View PostIMO 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.Computer: CUK Intel NUC7i7BNH
Op System: Windows10 Pro - Work Station
HS Version: HS4 Pro Edition 4.2.19.0
Plug-Ins: AK Weather 4.0.5.25,APCUPSD 3.3.2.3,BLBackup 2.0.63.0,BLEditor 2.0.11.0,BLGData 3.0.55.0,BLOccupied 2.0.28.0,BLShutdown 1.0.6.0,Blue-Iris 3.1.3.33206,Device History 3.2.0.2,EasyTrigger 3.0.0.76,Harmony Hub 4.0.14.0,iRobot 5.22.41.1,JowiHue 4.0.8.7,Nest 3.0.0.34,NetCam Plugin 1.0.0.5,PHLocation2 3.0.0.64,Pushover 4.0.10.0,Random 3.0.0.2,Restart 1.0.0.7,Ring 1.0.0.9,SDJ-Health 3.1.1.3,Sonos 3.1.0.59,Sonos4 4.0.1.12,UltraCID3 3.0.6681.34300,UltraMon3 3.0.6554.33094,UltraNetCam3 3.0.6413.20219,Unifi 4.0.32.0,Zigbee 4.0.11.0,Z-Wave 4.0.3.0, and Jon00 scripts.
Comment
-
Originally posted by reidfo View PostIMO 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.
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.HS4 Pro, 4.2.19.0 Windows 10 pro, Supermicro LP Xeon
Comment
-
Originally posted by MNB View PostRandy, 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
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.HS4 Pro, 4.2.19.0 Windows 10 pro, Supermicro LP Xeon
Comment
-
Originally posted by rprade View PostJust 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 iterationscheeryfool
Comment
-
Originally posted by cheeryfool View PostRandy
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 iterationsHS4 Pro, 4.2.19.0 Windows 10 pro, Supermicro LP Xeon
Comment
-
Originally posted by MNB View PostJames, 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
-
Originally posted by cheeryfool View PostAs 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.Computer: CUK Intel NUC7i7BNH
Op System: Windows10 Pro - Work Station
HS Version: HS4 Pro Edition 4.2.19.0
Plug-Ins: AK Weather 4.0.5.25,APCUPSD 3.3.2.3,BLBackup 2.0.63.0,BLEditor 2.0.11.0,BLGData 3.0.55.0,BLOccupied 2.0.28.0,BLShutdown 1.0.6.0,Blue-Iris 3.1.3.33206,Device History 3.2.0.2,EasyTrigger 3.0.0.76,Harmony Hub 4.0.14.0,iRobot 5.22.41.1,JowiHue 4.0.8.7,Nest 3.0.0.34,NetCam Plugin 1.0.0.5,PHLocation2 3.0.0.64,Pushover 4.0.10.0,Random 3.0.0.2,Restart 1.0.0.7,Ring 1.0.0.9,SDJ-Health 3.1.1.3,Sonos 3.1.0.59,Sonos4 4.0.1.12,UltraCID3 3.0.6681.34300,UltraMon3 3.0.6554.33094,UltraNetCam3 3.0.6413.20219,Unifi 4.0.32.0,Zigbee 4.0.11.0,Z-Wave 4.0.3.0, and Jon00 scripts.
Comment
Comment