@Selph
It is not the translation’s problem.
This module (and agenda) depends on its internationalization to Intl internal Javascript object. (https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Intl). That is supposed to be a standard method for I18N/L10N in JavaScript world.
But unfortunately, Chromium(Electron of MagicMirror is using it) is known to have a bug in handling Icelandic locale ‘is’ or ‘is-IS’, and not been fixed yet.
https://support.google.com/chrome/thread/26467925/icelandic-locale-formating-wrong?hl=en

Sorry. At this moment, I cannot help about it.

@Ronald @plainbroke @BKeyport (or any others)
Do you guys still have an interest in this issue? (RTSP implements on MM).

I build up a simple module, and It looks to be working, but my Home IP cams don’t support long-live RTSP streaming (Because it is not wire-powered, thus to protect from battery draining, the feature has limited.), And at this moment, I don’t have any RPI to test. (I tested this module on Mac, VIM3(Ubuntu) but not on RPI.

So, I need the help of a real-world test. Anyone who has interests and has RTSP-streamable cams, Give me DM, please. (in this forum or eouia0819@ gmail. com)

@td

• This doesn’t work?

getScripts: function () {
  return [ 
    this.file('node_modules/preact/dist/preact.min.js'), //from this module's directory
  ]
}

• Or you can serve preinstall or postinstall scripts for your module to handle that kind of job (additional install, move/rename files, etc.)

I scratch up a very simple module to prove my theory;

It seems working.

But;

• There would be some delay. (even almost 2s on my M1MaxMBP. So in RPI, it would be more. not yet tested.)
  • Some old/weak SBCs might not have enough power to handle real-time converting.
  • multi cam’s streaming would be too burdensome, more tests be needed

Anyway after some adjustment, I’ll release the module in a few days.

Most browser doesn’t support RTSP protocol natively. There would be several plugins/extensions to enable that feature, but not for RPI (I have not found yet.)

One available approach would be real-time transcoding RTSP to affordable formats (for example, MJPEG) to be handled by the browser itself. Maybe ffmpeg could do that in the background. I think it could be done as MagicMirror module, but I believe as an independent background daemon, it will work better.

Hmmm. I have no RTSP device at this moment, so I cannot prove this by myself. Anyway, in my opinion, this method will work.

@almightyyoshi

If your calendar module has some configuration like this;

{
  module: "calendar",
  header: "Schedules",
  position: "top_left",
  config: {
    calendars: [
      {
        symbol: "calendar-check",
        url: "...",
        color: "red",
        name: "Music",
      },
...

Events on this calendar will be represented in MMM-CalendarExt3 as like this.

<div class="event calendar_Music PUBLIC fullday future useSymbol" data-calendar-seq="0" data-calendar-name="Music" data-color="red" ... > ... </div>

So you can use CSS Selector like this.

.CX3 .event.calendar_Music {
  ...
}

If you want, you can add more CSS Specifity to grab more specific target events.

But that is not the real cause of your issue.

Your real issue is;

.CX3 .event.calendar_Music {
        border: none; // <-- Here;
}

In the default CSS of this module, a single event has no border, and a full-day event has a regional background colour(and box-sizing model is border-box), so even though you remove the border, you cannot distinguish what changed, you probably have thought the CSS grammar might have been wrong because nothing looked changed. That was why you lost your way.

@hclaus
Anyway, this is a universal solution, because I don’t know your screen resolution, direction, background padding/margin, wanted photo size, etc.
With specific conditions, it would be deadly simpler.

@sdetweil
It would be rotated.

2560w x 1080h
that is horizontal resolution, so by media rule; below will be adopted;

left: calc((100vw - 90vh) / 2); /* (2560 - 972) / 2 = 794 */
transform: rotate(90deg);
width: 90vh; /* 972 */
height: (auto) /* 972, by aspect-ratio: 1 / 1; */
top: 0;

@sdetweil
Yes, It works. Guess it. :)

@hclaus
custom.css

#SELFIE .result {
  width: auto;
  height: auto;
  aspect-ratio: 1 / 1;
}

@media (min-aspect-ratio: 1 / 1) { /* Horizontal Screen */
  #SELFIE .result {
    left: calc((100vw - 90vh) / 2);
    transform: rotate(90deg);
    width: 90vh;
    top: 0;
  }
}
@media (max-aspect-ratio: 1 / 1) { /* Vertical Screen */
  #SELFIE .result {
    top: calc((100vh - 90vw) / 2);
    transform: rotate(90deg);
    height: 90vw;
    left: 0;
  }
}

You can adjust some values for your purpose.

@hclaus
So what you need is just displaying picture on mm screen with 90 CW/CCW rotation, I think it could be done with CSS only. I’ll test and show you how to do in a while. (I have dinner now ;) )

@EphraimB
You are referring a calendar which has the name of “personal” in your “calendarSet”, but there is no calendar in your “calendar” module’s config like that. That’s the reason.

@hclaus

This module’s features are dependent on node_webcam module, but that module is just a convenient wrapper of lower-level applications like fswebcam or ImageSnap. Anyway, node_webcam itself has no feature about it.

Frankly said, I’ve already requested that feature to the developer of that node module (https://github.com/chuckfairy/node-webcam/issues/38) for my own purpose, but he hadn’t yet.

There could be several solutions;

• Rotating the picture on display of MM (Just with CSS it could be done, but the file itself is not rotated, so if what you need is the picture itself, this is not a perfect solution)
• Rotating the picture file after shooting (Another post-process is needed. Fortunately, Just one picture’s rotating takes not so long time - Some SBC might not have enough power to process fast)
• Taking photo itself with rotation. (To achieve this, Independence from node_webcam module might be needed. But not a big deal.)

I’ll consider options and make a solution for this.

But you need to know one thing. At this moment, the module’s owner is in anotherone, not me. So I’ll make a PR but acceptance would be on his hands. (Maybe we could have other branch or special dedicated clone for you when the PR is not accepted.)

@hclaus
Sorry for not paying attention to this issue; I appreciate your confirmation it works again. Thanks.

@EphraimB
There were so many modules using openweather API(So I don’t know which module is what you mentioned), but since MM changed its default weather module, the default weather module could also handle openweather API natively. So, just use the default weather module.
Or, request the developer of your open-weather-using-module to support CURRENTWEATHER_TYPE notification to be compatible with the default weather module.

@sdmydbr9
I think it’s not so difficult to create the module, but what is different with the view which shows only one event upcoming on default calendar module?

@acdacd2
It’s normal. Why did u think it’s a problem?
Your MM mighe be rebooted or restarted at taht moment.

@luisestrada

• broadcastPastEvents : enable the feature
• maximumNumberOfDays : how old events would be gathered
• maximumEntries : give enough rooms otherwise your too old events would consume your default slots.

MMM-CalendarExt3Agenda

Daily agenda view module of MagicMirror

Screenshot

Concept

This is a sibling module of [MMM-CalendarExt3](https://github.com/MMRIZE/MMM-CalendarExt3). This module is made to be an alternative to my previous module MMM-CalendarExt2, especially daily, current and upcoming views.

Features

What’s different with CX2.

• Only focusing on how it shows; Parsing is delegated to the original MagicMirror module calendar. (It means the calendar module is REQUIRED to use this module.)
• Respect to original MM’s hide/show mechanism. Now you can hide/show this module easily with other scheduler or control modules. (By the way, Look at this module also. - MMM-Scenes)
• No dependency on the 3rd party modules (e.g. momentJS or Luxon, etc.). This is built with pure JS and CSS only.

Relation with CX3

• Nothing. It is independent from MMM-CalendarExt3. But of course, you can use them together.
  

DETAILS
https://github.com/MMRIZE/MMM-CalendarExt3Agenda

@alphanet
The symptom could happen from various reasons.

Where the URL of the calendar comes from? Directly from Google calendar? or another source? If the calendar would be imported from another source and the original event might lay in a different timezone, it could happen.

Or simply, your events have a wrong(or unparsable) timezone format.

Anyway, you can adjust the timezone of events by force with forceLocalTZ:true on calendar section (https://github.com/MMM-CalendarExt2/MMM-CalendarExt2/blob/main/docs/Configuration/Calendar.md). It will override timezone information to your local timezone by force.