Launchd daemon not starting correctly on launch

Question

Hi All,
I have a script that I like to have run anytime my wireless network changes.  The script needs to be run under sudo, so I created a daemon inside of /Library/LaunchDaemons .
My plist file looks like this:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
          <key>Disabled</key>
               <false/>
          <key>Label</key>
               <string>my.plist.name</string>
          <key>ProgramArguments</key>
               <array>
                              <string>/path/to/script/to/run.sh</string>
               </array>
          <key>WatchPaths</key>
               <array>
                              <string>/Library/Preferences/SystemConfiguration/com.apple.airport.pr eferences.plist</string>
               </array>
</dict>
</plist>
So here's where the oddness starts happening.  When I start up my computer, launchctl tells me that this daemon is loaded.  (I run sudo launchctl list and it's there).  However, the script does not run when it should.
However, if I manually unload and then load the plist using the launchctl command then everything works completely fine.
So the question is, why does it work when I load it manually, but not work when the system loads it on startup?
Thanks,
Q

Answer 1

No suspicious message in the console.  When I sudo launchctl list it shows up with a 0 in the second field.
The only thing I can find in doing some google-ing is this:
https://managingosx.wordpress.com/2006/05/10/launchd-gotcha/
Which seems to imply that a launch daemon that is watching a file will fail to work if that file doesn't exist at all times.  However, I would think that /Library/Preferences/SystemConfiguration/com.apple.airport.preferences.plist should always exist.  So I'm still perplexed.
Right now I have a seomwhat convoluted system set up as the following:
My launch daemon (that needs to run as root) is set to watch a folder ~/random/
Then I have a launch agent which successfully watches for changes in /Library/Preferences/SystemConfiguration/com.apple.airport.preferences.plist and when it sees them touches a file in ~/random/.
The launch daemon then deletes that file and successfully runs the script I want it to run.
It seems weird/odd/annoying to have to set up a this double-headed process just to do something simple like this, so I'm open to suggestions as to what is going on.