Read the statement by Michael Teeuw here.
MMM-PilotWX
-
@Mykle1 Thanks for the info! I wouldn’t even know where to start with that!
Cheers -
Reviving an old thread, I just installed the module but it stays stuck on “loading PilotWX”, I have just one airport (LIBD) in the list and copy-paste the configuration from the example changing just the location to bottom_left.
Any hint on how to make it work? -
@on8cb this module suffers from this.
https://forum.magicmirror.builders/topic/15778/fix-for-black-screen-in-2-16-and-later
and it’s possible the API has changed in 3 years
the author is not available currently.
-
@sdetweil Thank you.
I noticed that several 3rd party modules are in the same conditions either for the broken/old libraries or for the expired certificates or because the API are no longer working (WUnderground, DarkSky) or a combination of the three.
I will try to understand how it work and eventually how to create my own modules.
-
@on8cb old libs problem
a module should identify all the libs it uses in it’s package.json file, as 'dependencies.
it worked and the authors didn’t know about this.
we deleted the libs as they were removed from distribution (deprecated)… and oops the module still needs them but didn’t say so.
if they had, and created a package.json file (npm init -y) the problem would not have occurred.
apis not working… well nobody wants to drag old stuff along anymore ‘too much work’… so they change whatever they want, too bad for developers or users.
when I worked for IBM my mentor reminded me often that, when u document an API, it lives like that forever. same input produces the same output. you want to ADD stuff ok, it’s a new API… stuff doesn’t break… customers can continue to depend on you…
anyhow…
certs… well they expire… app owners should plan for that… nah, too much work, we’ll deal w it then…
