Hello everybody, I have the same problem. Because I’m not an IT professional, I’m having trouble solving the problem with your instructions.
The second workaround in particular is difficult:
…I completely removed the usage of the sync-fetch library in netatmo.js in favor of the default async version . That is, simply remove the line: const fetch = require(‘sync-fetch’), make the authenticate, loadData and socketNotificationReceived functions async, handle the promise object returned by fetch appropriately as well as the call to json().

• I can’t find the “const fetch” line in the netatmo.js file
• how can I make functions asynchronous
• the sentence “handle the promise object returned by fetch appropriately as well as the call to json().” I don’t really understand either

Is it possible to make the instructions a bit more detailed? Or what is the best way to ensure that the great module works for me again?

Thank you very much for your effort!

@sdetweil said in Error starting after upgrade:

@wwats said in Error starting after upgrade:

Can I something do for You

no… i just like to help…

thank you so much :folded_hands_light_skin_tone:

@sdetweil
Everything works :thumbs_up: :thumbs_up: ! Thank You very much - so the mirror is running again. Can I something do for You?

@sdetweil
ok i understand - output is
/usr/bin/node

maybe is this important: i work directly on my raspberry with ssh

@sdetweil i’m very sorry but i don’t understand this and what i have exactly to do… Can you explain it in a different way?

@sdetweil no… :
pi@raspberrypi:~ $ ls -laF /usr/local/bin/node
ls: Zugriff auf ‘/usr/local/bin/node’ nicht möglich: Datei oder Verzeichnis nicht gefunden

@sdetweil

pi@raspberrypi:~ $ node -v
-bash: /usr/local/bin/node: Datei oder Verzeichnis nicht gefunden

@sdetweil ok this was sucessfull… and what do I have to do now? reinstall? How?
Thank you very much and sorry, I’m not an IT specialist…

@sdetweil ok i did. I still have version 16.13.1 :-(
Am I perhaps in the wrong directory?
I have to run the script in the lowest directory directly at pi@raspberrypi:~ $, right?

No, unfortunately not. i see: