Module developer fewieden kindly picked this up. Apparently changes in MMM over time caused some incompatibility.
He has now released version 2.0.2 ; I can confirm that the problem is solved.
@brindlednearly I don’t understand your message
i consider this api one of the lazy/sloppy kind
there is a documented error code that can be used
but they return 200 (good), but have bad data…
The install was successful :)
I still get a bunch of these waning’s though that’s probably not your issue.
Thanks for all the effort you put into this project.
(node:2431) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 close listeners added to [TLSSocket]. Use emitter.setMaxListeners() to increase limit
@sdetweil I did change weather module and first it did’nt work. But after a while it did. Think it was the 3.0 onecall api take some time after I did sign up. Thanks for the tip!
@sdetweil @MMRIZE Oh really! Thank you Sam for letting me know the real problem. And you 2 guys have learned me so much these days, I really appreciate you took your time helping me.
I have now reinstall MM and begin from start. And then i did install CalendarEXT3 the correct way.
@misha2257 if you search on that error you should find instructions on how to compile the DTCs into the proper overlay format on the OS that you’re using. there are OS commands
it’s not a magic mirror problem it’s an OS I2C bus interface issue