PI Enhancement

[MNB]

James, thanxs for the comeback.. I was wondering if you were using a specific time or had a means to look for a broken condition/trigger you choices the easier route . You also clarified ensuring that ones naming of events and within events to "Borked" vs "Broken". I named my event as "Events - Broken Report" and always see it in the Broken report.

[cheeryfool]

James, thanxs for the comeback.. I was wondering if you were using a specific time or had a means to look for a broken condition/trigger you choices the easier route . You also clarified ensuring that ones naming of events and within events to "Borked" vs "Broken". I named my event as "Events - Broken Report" and always see it in the Broken report.

Given where I came from (about 25 unknown broken events) before Jon built this, I figured a once a day check was more than adequate.

[MNB]

James, I took your two events and combined them into one. It would be neat to be able to run a script that would run the report, check for "Broken" and then either delete the file if there is only one "Broken" or save it to be emailed with more than One "Broken" your thoughts? Mike

[cheeryfool]

James, I took your two events and combined them into one. It would be neat to be able to run a script that would run the report, check for "Broken" and then either delete the file if there is only one "Broken" or save it to be emailed with more than One "Broken" your thoughts? Mike

[MNB]

I love the idea, but it’s beyond my capabilities. If someone can figure out a way to monitor for a new version of the file and parse out whether it includes just that one event, then it could be used as a condition to run the second event or not. That would need the 2 event structure though.

Are there any scripting experts out there that could offer a solution(s)? Requirement:
1. Parse a specific text file at located c:\Program Files (x86)\Homeseer3\html\eventlisting.txt and search for the text string "Broken" and count the number of "Broken" if the count of "Broken" is greater than X then execute an event otherwise don't do anything
2. The User will create two events;

• One to run the new parse script daily
• The other to send email with txt file to specific emails if the script detects a count of more than X "Broken" strings.