Hi,

I’m writing a module that changes the background colour dynamically. As a consequence of this, I’d like the text to be as readable as possible.

The difficulty is that although I’ve found a way to dynamically determine the optimal text colour for the current background colour, I have no way to push other modules to use it. Ideally I’d like to modify the --color-text variable dynamically. But I can’t see any way to do this.

Am I overlooking a simple answer?

@sdetweil Thanks for looking. Classic Microsoft behaviour :)

Hi there,

I’m getting the above error (Moment Timezone has no data for GMT+0100) for certain entries in my calendar. From a look, I think these are all iCal entries that relate to flights. From looking around, I understand that there’s some ‘need’ to create custom timezones for flights where a flight might take off in one timezone and land in another?

In any case, looking at my calendar file, there appear to be two relevant entries. The first:

BEGIN:VTIMEZONE
TZID:GMT+0100
BEGIN:STANDARD
TZOFFSETFROM:+0100
DTSTART:20010101T000000
TZNAME:GMT+1
TZOFFSETTO:+0100
END:STANDARD
END:VTIMEZONE

Seems to be creating a new time zone called “GMT+0100”.

The second entry then seems to use that time zone:

BEGIN:VEVENT
CREATED:20220426T192115Z
UID:20220426T192113Z--386008955@www.britishairways.com
DTEND;TZID=“GMT+0100”:20220526T072500
TRANSP:TRANSPARENT
X-APPLE-TRAVEL-ADVISORY-BEHAVIOR:AUTOMATIC
SUMMARY:Online Check-in opens for
LAST-MODIFIED:20220426T192115Z
DTSTAMP:20220426T192112Z
DTSTART;TZID=“GMT+0100”:20220526T072500
SEQUENCE:0
DESCRIPTION:
END:VEVENT

And I’m guessing it’s this latter entry that causes MM to raise the above error.

Any thoughts on how to fix this (besides removing the entry from my calendar)?

I’ve been trying to debug an error that I’ve been having with MMM-BackgroundSlideshow and my investigations have brought me to MM itself.

In short, the background on MMM-BackgroundSlideshow was sticking on my system. The cause of this is that a return notification from the node_helper doesn’t always arrive back at the module. Debugging indicates that it’s transmitted, but it doesn’t always arrive.

My pi occasionally loses internet connectivity briefly and it makes sense that this could be causing the problem. One possibility is that the socket dies whenever internet connectivity goes down. Another possibility is that the node_helper is transmitting data when the connection is down and so it never arrives.

I’m not sure which, and I’m not sure what the fix would be.

Firstly, is it possible for a socket to die in this way?
Secondly, is there any kind of built in ACK mechanism that can be applied to a sendSocketNotification?

Thanks!