@Cr4z33 Yes, the data that us returned is in a different format. There may be some overlap, but overall it’s outside my skill set.

@Cr4z33 It doesn’t look like the data comes back the same. Sorry.

@Cr4z33 PirateWeather was easy because it uses the same format as DarkSky. If Tomorrow.io does as well then theoretically it could be easy to add a config setting for the URL along with the existing API key setting.

With the end of DarkSky API, I’ve forked this and updated it to use PirateWeather. https://github.com/gonzonia/MMM-BMW-PW

All coding credit goes to @Mykle1 . I pretty much just changed the name and a URL. Pirateweather does not support languages though and that was removed.

@bugsounet THANK YOU! This saved me a lot of headaches. I went ahead and updated to 2.18 and got the exact error you reference in the exact same module. A quick search and I found your very helpful solution. Thank you for sharing.

I’m trying this out as a replacement for the default newsfeed. I’m having trouble styling it though. I’d like it to have a more transparent background and to make the font white. I can’t seem to make that happen.
For example- on the default newsfeed module I set the background with rgba(0, 0, 0, 0.2);

I can’t get that to apply to this one.

@sdetweil It’s interesting. I’m seeing this error now instead of the socket disconnected error. I’ve changed the DNS on the MM to not use the pihole (it’s using Google DNS).

I don’t know why I’m seeing this vs. the other error all of a sudden. I still think it’s hard to blame the network exclusively. I have other modules too that all run fine at the exact same time.

I’ve tried to figure out how to catch the error but I don’t think I can. From what I can tell it’s making the async call and then while waiting for a response it loses the connection for some reason. I’m not skilled enough to re-write try the async queue method referenced in the github post I linked to previously. I’m just hopeful someone who has the same problem might have the skills to fix it or at least catch it better so that the module doesn’t fail completely. (Meanwhile I’ll keep trying to identify what the problem is).

@sdetweil I do but I thought I’d switched the DNS on there to not use it. Apparently not. This new error was likely the result of the update to pihole v5 (need to figure that out separately). Thanks for pointing me in the right direction!

New error now that I’ve increased logging. Not sure it’s related but it does seem more specific.
Error: getaddrinfo EAI_AGAIN photoslibrary.googleapis.com
Which could be this. https://github.com/googleapis/google-api-nodejs-client/issues/761

Popping up at this line (I have a log entry directly before that shows up, and one after that doesn’t)

            		var response = await this.request(token, 'mediaItems:search', 'post', null, data)

@Sean thank you. As always I appreciate the efforts you’ve put in. Much of my posting has been throwing out ideas to see what might stick too. I’m not adept enough at js to tackle this myself but may try at some point. I’ve got it logging at almost a line by line level to see if there’s one call that has the problem. I actually got a whole new error today which was weird. I’ll keep posting as I discover anything but please don’t think I’m trying to get you to do something, it’s more for documentation of the problem in hopes that someone can fix it!