Souds a bit strange though since there should be enough memory inside the router to load OpenWRT.
It appears that the developer tried to keep OpenWRT as unmodified as possible, at least on the D-Link DIR-505. The slow green blink on the indicator light signifies OpenWRT is running, and all of the time after that until you get either a fast green blink (failed network load) or solid green (MeteoBridge software running) is the app download/startup code running from /root/start.sh. If you try to connect to the web server during the slow green blink, OpenWRT's web server will answer because MeteoBridge's web server code has't finished loading.
It bears mentioning that I have no intention of reverse-engineering the package. I'm just trying to figure out which sensor(s) it reports to WU in the case of an AcuRite Bridge interface with multiple sensors reporting. With the exception of the AcuRite support quirks that I wrote about above, I think that MeteoHub/Bridge are great packages and the developer deserves to be financially compensated for all of the great work that was done to create both of them.....