Read the statement by Michael Teeuw here.
MMM-euro2024
-
@0m4r i want to nudge you a little more, on the defaults.
my MMM-Config module presents a form for config customization, and it does this by discovering the parameters in the defaults section of the modulename.js. as it sits, your module would have no parameters for the user to configure
just move that one section to the modulename.js from the node helper and all will be good. no other change to your module is required because you did that change.
-
I get a black screen when I activate the module?
Original Config as in description and token available.
Does anyone know what this could be?Ich bekomme einen Schwarzen Schirm wenn ich das Modul Aktiviere?
Original Config wie in Beschreibung und Token vorhanden.
Weiß jemand was das sein könnte?Danke
Robert -
@robiv8 hey, I am sorry to hear that.
Are you able to provide some logs? -
@sdetweil this is done in version 1.0.4
-
@0m4r
das log sagt: Please correct syntax errors at or above this line: ReferenceError: b1e6…meinToken…67c8c5 is not defined -
@robiv8 I think your configuration is wrong.
Is the token wrapped into quotes?{ disabled: false, module: 'MMM-euro2024', position: 'center', header: 'Euro 2024', config: { updateInterval: 60 * 1000, token: "M4g1cM1rr0r" } },
-
@0m4r this is what your module config looks like in MMM-Config
-
@sdetweil this is good, isn’t it?
-
@0m4r yes… it works
-
@0m4r
Hallo.
This i my config, as described in GitHub{ disabled: false, module: "MMM-euro2024", position: "center", header: "Euro 2024", config: { updateInterval: 60 * 1000, token: [b1e67..myToken..67c8c5], } },
Ok Danke,
with superscripts it works.
Why isn’t that right in GitHub?