Hey The “old” weatherBackground did not always work for me, and given the new possibilities with AI I created a new module that can generate new background images on the fly using AI. You can add additional parameters to modify it. Parameters are based on time, month and general parameters… See code here: https://github.com/AJOCHAM/MMM-AIWallpaper Any feedback?

I had to insert in css body with 75% zoom, and that did it. I don’t know why, but everything looks correct. I also had to make changes to the code of MMM-Pir-Sensor-Lite, and now that works to. I also made some modifications to MMM-MyGarbage, so it support 11 diffrents wastebin with custom pictures of the correct pictograme. Everything is up to date now with Raspberry PI Trixie OS Thanks for the help 🤟

Published update to V3.1.1 list itemFix weeksToDisplay For example: 2 weeks are 14 days so this could end up showing 3 weeks. Now fixed to ISO weeks. list itemNormalized all dates to ISO strings list itemImprove CSV bin filtering (avoid garbage data)

I’ve just published MMM-SolarGenerationCalendar, a MagicMirror² module that displays a live solar generation dashboard by bridging directly with Home Assistant. No API keys or internet dependency required. Since I have a Soliscloud integration this module is tailored for that. However, you need to have integrated your Solar Plant with the relevant HA integration( Which requires, API Key & Secret). It features a live power gauge, six stat cards (Power, Today, Month, Peak, Year, Lifetime), a today’s generation curve, and a 30-day bar chart with a daily average line, all pulled from HA’s REST and WebSocket APIs. If you are using any other Solar Integration, you can still use this module. Check out the FAQ’s. for how to do that. Checkout the Module at; github.com/CyberRagz/MMM-SolarGenerationCalendar

@wswenson Post when you get it ready for use. Looks Like something fun for the grandkids.

@jpiatt ok, let us know. Big calendar rewrite coming next Wednesday My cal is 12 yrs old, oops actually 17 yrs.

@anagallis yes, custom.css is in the MagicMirror/css folder next release (April 1 it will move to the config folder (user files will all be in one place)

@evroom Nice. Thanks for the feedback! 🙂 The only thing that I would like to additionally see, is the last 2 departures/arrivals in the past Like the Hafas module it’s currently not possible to display past departures, sorry.

@Cybex999 can you show the module config? Use the code block wrapper please

Formated configuration: { module: "MMM-StreamerStatus", position: "top_right", header: "Live Now", config: { twitchClientId: "your_client_id", twitchClientSecret: "your_client_secret", kickClientId: "your_client_id", kickClientSecret: "your_client_secret", youtubeApiKey: "your_api_key", displayStyle: "list", // or "card" showOffline: false, streamers: [ { name: "your_streamer", platform: "twitch" }, { name: "your_streamer", platform: "kick" }, { name: "Channel Name", platform: "youtube", channelId: "UCxxxxxxx" }, ], }, },

Hey everyone! I’ve been working on a module to display a live Google Nest camera feed on MagicMirror² using WebRTC, and wanted to share it with the community. MMM-Nest-Camera-WebRTC https://github.com/brandaorafael/MMM-Nest-Camera-WebRTC [image: preview.png] What it does: Streams live video from a Google Nest camera directly on your mirror via WebRTC Automatically refreshes OAuth tokens — no manual intervention needed after initial setup Keeps the stream alive beyond Nest’s 5-minute session limit via periodic extension Includes an audio frequency visualizer — a bar equalizer that reacts to the camera’s audio track (without playing any sound through the mirror) Auto-reconnects on connection failure with configurable delay Integrates with USER_PRESENCE (e.g. MMM-PIR-Sensor) to suspend/resume the stream when you leave/return Supports hiddenOnStartup to defer the WebRTC connection until the module is shown Requirements: A Google Cloud project with the Smart Device Management API enabled A Device Access Console project (~$5 one-time fee to Google) OAuth 2.0 credentials (Client ID + Secret) The README has step-by-step instructions for getting all credentials and completing the initial OAuth setup with the included exchange-nest-code.js CLI tool. This is a fork originally based on work by @shbatm — I rewrote the streaming and token logic, added the audio visualizer, and hardened the reconnection/session extension flow. Feedback and issues welcome!

So I think the “Suspended” thing is a red herring. I booted up my dev system and watched the console messages there. I saw the same behaviour of BackgroundSlideshow being suspended but it does show the images. I’ll update just MMM-BackgroundSlideshow on that system and see what happens.

@barnosch I have not tested it with Jelly, but in theory it should. I’m happy to take a look and expand functionality if I have someone to test with :) Sorry for the delay in responding!

@sdetweil Thank you! I think that fixed it.

@PGP_Protector nice!

@videogame95 no, sorry. You are on developer.spotify.com Right?

@daportelli if you change the module name for a test, does it work? What do you get from MMM-GoogleCalendar that the default does not provide? never mind, it won’t work with the google side config… as for the purpose of this configuration. the content is protected by https encryption and no user will see it, its only exposed ON the system where MagicMirror runs, same for both modules. you can get the secret URL from the calendar.google.com settings,

@sdetweil said: @darlacollado calendarExt3 gets its events from the default calendar module Yes, for skylight you will have to adjust css for everything All changes go into custom.css to override those specified by MagicMirror and modules. Remember that modules are see thru to view the background Thanks for your suggestion. I got it.

@sdetweil Today I notice something. I had to turning off my router for a while, so no internet connection were available for nearly 10 minutes. In that time MM goes black with cursor… so the issue could be internet connection related

Hi, glad you like the module. If you want more teams on view and you have the screen space to accommodate it, the best bet would be to set it top-left or top-right with no other module above or below it. You can then increase the "maxTeams: 12 " and the "maxTableHeight: 520 " config.js values to accommodate more rows. You will also need to ensure that the " --mtlt-max-table-height: 520px; " value at line 20 of the MMM-MyTeams-LeagueTable.css is not less than what you set the "maxTableHeight: 520 " config.js value to be. I have my module positioned top_left but below another module and on my 22 inch monitor I can fit 16 teams displayed before scrolling . I recon I could get about 28 rows if i moved the other modules. regards