Read the statement by Michael Teeuw here.
MMM-GooglePhotos suddenly stopped working this morning
-
@Jabl0 are you using my fork of the module? there was a bug handling restarting if one of the images failed to load
when you have the black screen you might be able to open the developers window , ctrl-shift-i, select the console tab
also i think there is a
debug:true
config option which will show the whole flow of getting files and selecting a file to display in the output of npm startif you install MMM-Logging or MMM-LogExt it will capture the browser console and merge w the npm start console
-
@sdetweil apologies but i am not sure what you mean by fork :( however, i am using this one https://github.com/roramirez/MMM-ImagesPhotos and i see you are a contributor on there?
I will give the recommended debugging log methods you have suggested and see what i can find.
Thank you.
-
@Jabl0 fork, means i have a copy too
-
@sdetweil Ah, right! Learnt something new :) I am using the other one. One more thing, i did enable debugging yesterday and for some strange reason i have not seen the black screen since i have done this. Fingers crossed though.
I did see these errors:
Invalid SOS parameters for sequential JPEG
But the module kept running fine with no black screen.
I would like to use your version, will i have to completely remove the module and clone yours instead, or is there a quicker way to migrate?
Thanks.
-
@Jabl0 just rename the module folder out of the way
and install mine in its place. only change config for new parms if you want to use them -
@sdetweil Legend! Thanks :)
-
said in MMM-GooglePhotos suddenly stopped working this morning:
@sdetweil Legend! Thanks :)
@sdetweil its been a few days and that black screen keeps persisting. Using your fork and the original one.
I am not seeing much from the logs, im keeping an eye on temperature as well. I do have over 3000 photos though. Dont know if that is an issue.
I’d appreciate if you can help me with this.
Let me know what i need to provide in order to be able to get this resolved.
Thanks :)
-
@Jabl0 did you add
debug:true,
to the module config, and add MMM-Logext
you should see logging where npm start is done
-
@sdetweil yes I did. That’s where have been checking the past few days and all the images load just fine, even when it goes black which why im baffled. Is there anything else I should be looking for in the logs?
I use pm2 logs to see the logs btw.
I also check in dmesg
-
@Jabl0 ok, good. ill relook thru the code, i had a similar problem with a similar module on another mirror platform, was an out of memory problem.
wont be able to get to that til this afternoon.