@plainbroke
sorry it took so long to reply back I’ve been kinda busy
and I did contact the owner and he said just that I did try it and it worked perfectly

Hi,
First: everything works well, on my installation about MMM-FRITZ-Box-Callmonitor-py3 on my Raspi 4 with Bullseye.

But i have some question about the devicefilter:

What do I have to register exactly there?

The Telephonnumber? The name of the “device”? The “intern number” The IPEI?

I know that this works like:
the “devicefilter entry” filters, the incoming calls for this phonenumber, out?

In my case we have 3 DECT-Phones and i want display only one from this devices on the MM-Screen when the call comes in.

Thank you all for your Support.

Greetings from Germany
Foxy25

I tried this module from https://github.com/ban9975/HPS-FaceID but after successfully installing everything and rebooting and putting in the config. it doesn’t work.
config.js base with only this, I get the default logo coming out.
I tried creating a datasheet with my face photos and then I created a photo as a profile but it doesn’t work. while running mm I tried mashing the FaceID and AddProfile buttons but nothing. I wanted to write directly to whoever created this fork but it is not possible to point out the problem there.

@sdetweil it is the MMM-RNV module but now it is going thank you

@jubbles
To show 3 sequenced month-instances of the CX3 modules;

{ module: "calendar", header: "US Holidays", position: "top_left", config: { maximumEntries: 100, maximumNumberOfDays: 365, calendars: [ { symbol: "calendar-check", url: "https://ics.calendarlabs.com/76/mm3137/US_Holidays.ics" } ] } }, { module: "MMM-CalendarExt3", position: "bottom_bar", config: { instanceId: "THISMONTH", mode: "month", } }, { module: "MMM-CalendarExt3", position: "bottom_bar", config: { instanceId: "NEXTMONTH", mode: "month", monthIndex: 1, } }, { module: "MMM-CalendarExt3", position: "bottom_bar", config: { instanceId: "NEXTNEXTMONTH", mode: "month", monthIndex: 2, } },

I don’t use MMM-Carousel, so get a help from others.

If this happens try to set useCorsProxy to false in your feed config. Like this:

modules: [ { module: "newsfeed", position: "top_right", config: { feeds: [ { title: "tagesschau.de", url: "https://www.tagesschau.de/xml/rss2/", useCorsProxy: false } ] } }, { module: "MMM-News-QR", position: "top_right", config: { updateType: "push", interval: 2000, animationSpeed: 2500, colorDark: "#fff", colorLight: "#000", imageSize: 150 } } ]

@MMRIZE thank you I am still failing miserably at getting the gkeepapi to work with the mmm google keep module. It’s been 10 days of Me working on it no luck

@bdeelman said in Default module: Compliments is day_sunny working?:

MMM-OpenWeatherForecast

it uses
//broadcast weather update
this.sendNotification(“OPENWEATHER_FORECAST_WEATHER_UPDATE”, payload);

that module is not the default/weather module

@JMac said in MMM-PIR:

(you) think the mode 4 for HDMI in this module

I do not know the details of this module modes

@Socrates
Ah that makes sense. Yes i did use sudo. You are right. Will follow the guidelines now.

@sunilstark one of my modules, MMM-SleepWake, uses a camera for motion detection… well, it uses a system library (the motion project) to report motion events, but does not have a windows version…

@moosespectacles this module uses the default calendar module to read the ics data , and then broadcast it to other modules.

so move the url to the default calendar, make sure it works, then comment out the default calendar position

// position: …

and use monthly calendar as you expect

@foggy the ‘logs’ are the stdout from the magicmirror app (npm run server)

I don’t know where those are in a container

@Peter awesome, can you mark this resolved

@MikeBishop can you mark this resolved?

click the 3dots beside the post that best articulates the answer

@BKeyport said in Not updating at midnight...:

start: function () {
function scheduleMidnightUpdate() {
const now = new Date();
const nextMidnight = new Date(now);

// Set the time to midnight nextMidnight.setHours(24, 0, 0, 0); // Calculate the time remaining until the next midnight const timeUntilMidnight = nextMidnight - now; // Schedule the updateDom method to be called at midnight setTimeout(() => { this.updateDom(); // Reschedule the update for the next midnight scheduleMidnightUpdate.call(this); }, timeUntilMidnight); }

},

I would do it like this , much more straight forward

function scheduleMidnightUpdate() { const now = new Date(); const nextMidnight = new Date(now); // Set the time to midnight nextMidnight.setHours(24, 0, 0, 0); // Calculate the time remaining until the next midnight const timeUntilMidnight = nextMidnight - now; // Schedule the updateDom method to be called at midnight setTimeout(() => { // trigger first update on next midnight change this.updateDom(); // start Recurring midnight change setInterval(()=>{ this.updateDom() }, 24*60*60*1000 ) // 24 hours * 60 minutes * 60 seconds * 1000 milliseconds (1 day elapsed in ms) setInterval delay }, timeUntilMidnight); // setTimeout delay } },

then the system triggers every midnight… not your code

@DIY_556 said in MMM-transitfeed https error:

"realtimeUrls: [“https://api-endpoint.mta.info/Dataservice/mtagtfsfeeds/nyct%2Fgtfs-l”],

well you have a misplaced " in front of realtimeUrls
which with the one in front of https makes the start and end of a string and then
https is an unknown JS token

@mlm198 This error is usually caused by not deploying the google apps script correctly. I have updated the README with pictures to hopefully make the deployment easier. Feel free to add an issue to the repo if you are still having problems.

@sdetweil In case anyone finds this post in the future.

This problem is usually one of two causes:

The google apps script was not deployed correctly and the request runs into a permission error page There is an error in the request due to bad script URL or other parameter

I have updated the module to fail gracefully in these cases and hopefully provide a better error message. If you are still having problems feel free to add an issue to the repo. (https://github.com/ryan-d-williams/MMM-GoogleSheets/issues).

@adamambarus yes, have to use the right info