@sdetweil What’s the CORS service in MM?
I see I have been away for a while…

@bugsounet Hi thanks for the help.
Will consider reworking the code, but as said, it does work on an external browser, so the code itself should not be the issue, would it?
Rather the interpretation by the browser or any frontend behaviour when downloading the file.

@sdetweil that’s what I usually do, but here the error is not reproducible on any other browser. But I can try to use electron’s developers tab.

However, I strongly suspect the reason is @MMRIZE 's CORS issue.
But have no real idea how to solve that.

Anybody want to give me a hint?

HI,
I have an issue where an image is not loading on the browser of the mirror itself, while on Firefox on my laptop, it shows.

The image is loaded in MMM-Sonos:

                    if (item.track.albumArtURI !== null && item.track.albumArtURI !== undefined && item.track.albumArtURI.trim() !== "") {
                        albumCover.innerHTML = `<img src="${item.track.albumArtURI}" width="80" height="80">`;
                    } else {
                        albumCover.innerHTML = `<img src="SonosRadio.png" width="80" height="80">`;
                    }
                    container.append(albumCover);

It seems to be some browser problem, because as said, on a laptop browser the image is shown.

Any ideas?

Thanks,
Dirk

@sdetweil Sam, sorry for the confusion, everything is working. A said I had installed node 18 and then it all worked. I didn’t need help, just wanted to point out that node 20 seems to not be working with some systems. But as I see you got that covered in your script.

@sdetweil Sorry I have BUSTER installed. My mistake.

Here the lastlog

Upgrade started - Wed Nov  1 10:25:06 CET 2023
system is Linux magicmirror 5.10.103-v7+ #1529 SMP Tue Mar 8 12:21:37 GMT 2022 armv7l GNU/Linux
the os is Distributor ID: Raspbian Description: Raspbian GNU/Linux 10 (buster) Release: 10 Codename: buster
n (node version manager tool) not installed, doing test run, install skipped
doing test run = true, NO updates will be applied!
Check current Node installation ...
Node currently installed. Checking version number.
Minimum Node version: v18.18.0
Installed Node version: v16.20.2
Node should be upgraded.

Upgrade started - Wed Nov  1 10:45:19 CET 2023
system is Linux magicmirror 5.10.103-v7+ #1529 SMP Tue Mar 8 12:21:37 GMT 2022 armv7l GNU/Linux
user requested to force apply changes
the os is Distributor ID: Raspbian Description: Raspbian GNU/Linux 10 (buster) Release: 10 Codename: buster
node not installed, trying via apt-get
Reading package lists... Building dependency tree... Reading state information... nodejs is already the newest version (20.9.0-1nodesource1). 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
npm not installed, trying via apt-get
npm NOT installed now, install now
Reading package lists... Building dependency tree... Reading state information... Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: npm : Depends: nodejs (>= 6.11~) Depends: node-abbrev (>= 1.1.1~) but it is not going to be installed Depends: node-ansi-regex (>= 3.0~) but it is not going to be installed Depends: node-ansistyles (>= 0.1.3~) but it is not going to be installed Depends: node-aproba (>= 1.2~) but it is not going to be installed Depends: node-archy (>= 1.0~) but it is not going to be installed Depends: node-cacache (>= 10.0.4~) but it is not going to be installed Depends: node-bluebird (>= 3.5.1~) but it is not going to be installed Depends: node-call-limit (>= 1.1~) but it is not going to be installed Depends: node-chownr (>= 1.0.1~) but it is not going to be installed Depends: node-config-chain (>= 1.1.11~) but it is not going to be installed Depends: node-detect-indent (>= 5.0~) but it is not going to be installed Depends: node-detect-newline (>= 2.1~) but it is not going to be installed Depends: node-editor (>= 1.0~) but it is not going to be installed Depends: node-fs-vacuum (>= 1.2.10~) but it is not going to be installed Depends: node-fs-write-stream-atomic (>= 1.0.10~) but it is not going to be installed Depends: node-glob (>= 7.1.2~) but it is not going to be installed Depends: node-graceful-fs (>= 4.1.11~) but it is not going to be installed Depends: node-has-unicode (>= 2.0.1~) but it is not going to be installed Depends: node-hosted-git-info (>= 2.6~) but it is not going to be installed Depends: node-iferr (>= 0.1.5~) but it is not going to be installed Depends: node-inflight (>= 1.0.6~) but it is not going to be installed Depends: node-inherits (>= 2.0.3~) but it is not going to be installed Depends: node-ini (>= 1.3.5~) but it is not going to be installed Depends: node-npm-package-arg but it is not going to be installed Depends: node-promzard but it is not going to be installed Depends: node-jsonstream (>= 1.3.2~) but it is not going to be installed Depends: node-json-parse-better-errors (>= 1.0.1~) but it is not going to be installed Depends: node-lazy-property (>= 1.0~) but it is not going to be installed Depends: node-libnpx (>= 10.0.1~) but it is not going to be installed Depends: node-lockfile (>= 1.0.3~) but it is not going to be installed Depends: node-lru-cache (>= 4.1.1~) but it is not going to be installed Depends: node-mississippi (>= 3.0~) but it is not going to be installed Depends: node-mkdirp (>= 0.3.3) but it is not going to be installed Depends: node-move-concurrently (>= 1.0.1~) but it is not going to be installed Depends: node-nopt but it is not going to be installed Depends: node-normalize-package-data (>= 2.4~) but it is not going to be installed Depends: node-gyp (>= 3.6.2~) but it is not going to be installed Depends: node-resolve-from (>= 4.0~) but it is not going to be installed Depends: node-encoding but it is not going to be installed Depends: node-errno but it is not going to be installed Depends: node-npmlog (>= 4.1.2~) but it is not going to be installed Depends: node-once (>= 1.4~) but it is not going to be installed Depends: node-opener (>= 1.4.3~) but it is not going to be installed Depends: node-osenv (>= 0.1.5~) but it is not going to be installed Depends: node-path-is-inside (>= 1.0.2~) but it is not going to be installed Depends: node-promise-inflight (>= 1.0.1~) but it is not going to be installed Depends: node-ansi but it is not going to be installed Depends: node-qw (>= 1.0.1~) but it is not going to be installed Depends: node-read (>= 1.0.7~) but it is not going to be installed Depends: node-read-package-json (>= 2.0.13~) but it is not going to be installed Depends: node-request (>= 2.83~) but it is not going to be installed Depends: node-retry (>= 0.10.1~) but it is not going to be installed Depends: node-rimraf (>= 2.6.2~) but it is not going to be installed Depends: node-safe-buffer (>= 5.1.1~) but it is not going to be installed Depends: node-semver (>= 5.5~) but it is not going to be installed Depends: node-sha (>= 2.0.1~) but it is not going to be installed Depends: node-slide (>= 1.1.6~) but it is not going to be installed Depends: node-sorted-object (>= 2.0.1~) but it is not going to be installed Depends: node-from2 but it is not going to be installed Depends: node-stream-iterate but it is not going to be installed Depends: node-ssri (>= 5.2.4~) but it is not going to be installed Depends: node-strip-ansi (>= 4.0~) but it is not going to be installed Depends: node-tar (>= 4.4~) but it is not going to be installed Depends: node-text-table (>= 0.2~) but it is not going to be installed Depends: node-uid-number (>= 0.0.6~) but it is not going to be installed Depends: node-unique-filename (>= 1.1~) but it is not going to be installed Depends: node-unpipe (>= 1.0~) but it is not going to be installed Depends: node-boxen (>= 1.2.1~) but it is not going to be installed Depends: node-import-lazy but it is not going to be installed Depends: node-is-npm (>= 1.0~) but it is not going to be installed Depends: node-latest-version (>= 3.0~) but it is not going to be installed Depends: node-semver-diff (>= 2.0~) but it is not going to be installed Depends: node-xdg-basedir (>= 3.0~) but it is not going to be installed Depends: node-validate-npm-package-name (>= 3.0~) but it is not going to be installed Depends: node-which (>= 1.3~) but it is not going to be installed Depends: node-wrappy (>= 1.0.2~) but it is not going to be installed Depends: node-write-file-atomic (>= 2.3~) but it is not going to be installed E: Unable to correct problems, you have held broken packages.
doing test run = false
Check current Node installation ...
Node currently installed. Checking version number.
forcing low Node version
Minimum Node version: v18.18.0
Installed Node version: V1.0.0
Node should be upgraded.

That was the last failed upgrade. Node V1.0.0 lol. Node 20 was installed.
After that I manually purged Node, installed Node 18 and did the npm run install-mm

@sdetweil
Sam, I did an update yesterday and found Node 20.8 not working on my raspbian bullseye install.
I had an issue mentioned by someone else here before referring a missing GLIBCXX_3.4.26 file.
I needed to purge and install node 18.x. Then it worked.
Possible that this happens for more users with Raspbian
Bullseye.
I see your upgrade script requests Node 20.8.
Not sure if that may be an issue for other people as well?

@sil3ntstorm Looks like you need tio change the city to “hemau”.
If the link works, the module only needs the city name.

city: "hemau",

@sil3ntstorm That should be MMM-OpenWeatherForecast
https://github.com/jclarke0000/MMM-OpenWeatherForecast

@dawookie1979 You can try my module MMM-soccer.
See the link :backhand_index_pointing_down_light_skin_tone: in my signature.

Thanks!
I still need to work on the ticker and update the readme. Hope I can get this done in the next weeks.

@westpole said in Magic Mirror 2 Modul Anzeigeproblem:

Hi

Danke für deine Antwort. Da geht das Problem wohl schon los: Ich kann den MM per Browser nicht öffnen. Es wird immer ein DNS_PROBE_FINISHED_NXDOMAIN angezeigt. Die Werte habe ich entsprechend eingetragen.

Vielleicht ein Problem des DNS Servers? Ich kann z.B. oft nicht per browser magicmirror:8080 ansprechen sondern muss die IP-Adresse direkt ansprechen, also:

http://192.168.1.53:8080

Warum das so ist weiß ich auch nicht.
Denk dran den Port (:8080 ist bei MagicMirror Standard) immer mit an die Adresse zu setzen.

Wie kann ich denn ein Modul deaktivieren?

Indem du in der config.js in die Eigenschaften des Moduls

disabled: true;

schreibst.
Also z.B.

{
    module: "MMM-Somemodule",
    disabled: true,
    config: {
        ....
    }
}

@shalumov Usually these things are not related to the magicmirror software update itself, because MM updates have rarely any direct effect on third party modules.

Probably an issue with the module itself.
Can you open the MagicMirror on your laptop, show developer tools (F12) in the browser and look for any error this module sends out?

You can also find a troubleshooting guide in my signature.

Also, would be good to post the issue on github, so the module developer gets a notification.

@tjat

Hello tjat, that’s really cool.

Have you used ChatGPT to program the complete modules for you? Or did you just use it for help with Javascript?
I had provided a module called MMM-Keyboard a few years ago, which includes simplekeyboard and can interact with other modules. Just so you know if you need something else, I’m happy to work with you on including it in my module.

@westpole Hallo westpole,

entweder das Modul wird verdeckt (das würde ich testen, indem ich die anderen Module deaktiviere)
oder es gibt einen Fehler sodass das Modul nicht angezeigt wird.

Ich gehe davon aus, dass du bei latitude/longitude und apikey entsprechende Werte eingegeben hast?
Ich habe in meiner Signatur eine Beschreibung wie man Troubleshooting machen kann.
Vielleicht schaust du dir die mal an.

Kurzversion davon: Am besten den Mirror in einem Browser öffnen, Developer Tools aufmachen (F12), in der Console nach Fehlern schauen, hier posten.

@AnduriI Hi Andruil,
I have worked with this module for the past years and did a lot of changes, including the switch to a new API.
However, changes are not uploaded to github yet.
I can do that probably tomorrow so you can test it out if you like.

Also, have a look at @FlatPepsi s continuation of the module as MMM-WeatherGraph.
https://github.com/FlatPepsi17/MMM-WeatherGraph

The difference between his and mine is mainly the graph.

@Cliff365 Just so I understand correctly: You want a multi-day event, like a holiday, appear for every upcoming day?
You could consider using the daily view of the calendar, there your event would be split into days. Maybe it helps?

IIRC it is the timeFormat: 'dateheaders'option in the config

"timeFormat 	
Display event times as absolute dates, or relative time, or using absolute date headers with times for each event next to it

Possible values: absolute or relative or dateheaders
Default value: relative"

MMM-AVStock has been REANIMATED!

I have pushed a branch that uses the yahoo finance API and leaves Alphavantage behind for good.
Config should work as before, so anyone who wants to test, please let me know how it works!
You don’t need any new API Key!

@thymon for sure it is, but will need a few days probably

@thymon
please do a git pull and check out.
Hope it works!
Got a bit rusty on the programming after 3 years…