MystaraTheGreat

I'm having almost exactly the same issue with a display where backgrounds are stored on an internet share and internet connectivity is patchy. At some point, the image rotation simply...

The problem certainly still arises with 31cf1f50e9c6e208445c75e9c03bb7c57471cf22 (Merge pull request #89 from DanielHabenicht/master) Curiosuly, with 663ba5234a0343aee135e4436802777e27e2e450 (Merge pull request #88 from shmulyeng/master) I just get a black screen.

Well, I can't seem to confirm the cause precisely. I've rolled back all the way (one at a time) to 47b86aa551405e47261fb21ec321a41639816c01. Each version either replicates the 'stuck image' or I...

Okay, well here's where I got to, but I'm stuck.... The problem arises in updateImageList. It sends a notification (BACKGROUNDSLIDESHOW_REGISTER_CONFIG) to node_helper. Node_helper correctly determines the list of images and...

Right. The answer, as best as I can determine, is that the sockets in socket.io underlying MM are unreliable. This module is not particularly robust to the unreliable nature of...

I think the problem is that the sockets in magic mirror are unreliable and MMM-BackgroundSlideshow doesn't implement any kind of reliable transport mechanism on top of them. As a consequence,...

Good point :) skuethe/MMM-RandomPhoto is the one I'm using, which seems to be relatively up-to-date. I just sent a PR to it. I'm hosting the MM on the display itself.

I've also been having an issue with a share mounted set of files. Take a look at my comment here: https://github.com/darickc/MMM-BackgroundSlideshow/issues/90#issuecomment-790700519 It might explain the problem

That all sounds entirely reasonable and exactly how I would expect it to work.

Hmmm, I'll defer to your (obvious) expertise here. But I'm surprised it needs to be that complicated. Couldn't it be as simple as: - Join channels that the existing connection...