Received the following user report
This is typically when the plugin starts to shut down and some thread has requested output to a text file which has already closed down. In this case it is the text file that logs the IO activity to irrigation valves.
Another common scenario is when mcsSprinklers is not run with elevated privileges (i.e. "run as administrator") and direct IO is not allowed without these privileges. As a plugin this one should not be the case.
Prior history such as any other anomalies or if valve control was ever achieved would be useful information. The general situation is to have the Debug log enabled from the Other Page so lower level debug information can be viewed. The startup initialization is also important to observe for any failures there. It will be in the HS3 log.
Code:
i get this error Jul-22 12:43:33 AM mcsSprinklers tsoNet Writeline C:\Program Files (x86)\HomeSeer HS3\Data\mcsSprinklers\IOWindow.txt Line 0 Object reference not set to an instance of an object. Jul-22 12:43:33 AM mcsSprinklers tsoNet Writeline C:\Program Files (x86)\HomeSeer HS3\Data\mcsSprinklers\IOWindow.txt Line 0 Object reference not set to an instance of an object. Jul-22 12:43:33 AM mcsSprinklers tsoNet Writeline C:\Program Files (x86)\HomeSeer HS3\Data\mcsSprinklers\IOWindow.txt Line 0 Object reference not set to an instance of an object. Jul-22 12:43:33 AM mcsSprinklers tsoNet Writeline C:\Program Files (x86)\HomeSeer HS3\Data\mcsSprinklers\IOWindow.txt Line 0 Object reference not set to an instance of an object. Jul-22 12:43:33 AM mcsSprinklers tsoNet Writeline C:\Program Files (x86)\HomeSeer HS3\Data\mcsSprinklers\IOWindow.txt Line 0 Object reference not set to an instance of an object. Jul-22 12:43:33 AM mcsSprinklers tsoNet Writeline C:\Program Files (x86)\HomeSeer HS3\Data\mcsSprinklers\IOWindow.txt Line 0 Object reference not set to an instance of an object.
Another common scenario is when mcsSprinklers is not run with elevated privileges (i.e. "run as administrator") and direct IO is not allowed without these privileges. As a plugin this one should not be the case.
Prior history such as any other anomalies or if valve control was ever achieved would be useful information. The general situation is to have the Debug log enabled from the Other Page so lower level debug information can be viewed. The startup initialization is also important to observe for any failures there. It will be in the HS3 log.