node_helper.js is not working?

sdetweil

@vandy2424 said in node_helper.js is not working?:

To simplify this output, I am just enabling the default clock and weather module and MMM-DynamicWeather for these outputs

nothing matches that. please show the config.js and the logs from both backend and front end

vandy2424

@sdetweil Hi Sam, I am not sure what you mean by showing the logs from the backend and front end. I thought that is what I just showed you. (Terminal & dev console). You can see in the dev console, it loading clock, weather and MMM-DynamicWeather modules.

Please let me know what I am not understanding here and I will get you those logs. Thanks!

Here is the config.js file:

let config = {
  address: "0.0.0.0",	// default is "localhost",
  port: 8080,		// default,
  ipWhitelist: [], // default -- need to add your IP here,
  modules: [
    {
      module: "clock",
      position: "top_left",
      config: {
            timeFormat:12,
            timezone:"America/Chicago",
            displaySeconds:"true",
            showPeriod:"true",
            showDate:"true",
            displayType:"both",
        },
    },
    {
      module: "weather",
      position: "top_right",
      config: {
        type: "current",
        units: "imperial",
        tempUnits: "imperial",
        windUnits: "imperial",
        apiVersion: "3.0",
        weatherEndpoint: "/onecall",
        apiKey: "KEY",
        lat:"50.75",
        lon:"-88.16",
        showUVindex:"true",
      },
    },
    {
      module: "weather",
      position: "top_right",
      config: {
        type: "daily",
        units: "imperial",
        tempUnits: "imperial",
        windUnits: "imperial",
        apiVersion: "3.0",
        weatherEndpoint: "/onecall",
        apiKey: "KEY",
        lat:"50.75",
        lon:"-88.16",
      },
    },
    {
     module: 'MMM-DynamicWeather',
     position: 'fullscreen_above',
     config: { // See https://github.com/scottcl88/MMM-DynamicWeather for more information.
      api_key: "KEY",
      lat:"50",
      lon:"-88.16",
      },
    },
  ],
};

Again this is just with the DynamicWeather module. I can add others but this simplifies.

sdetweil

@vandy2424 backend , console output from npm start

front end, in the developers window

this config does not match the messages

vandy2424

@sdetweil Hi Sam,

I am unsure how else I am supposed to respond other than to say, this is the exact config that produced those backend/front end logs. If this is unusual, maybe something is broken here? I am not sure what “working” logs are supposed to look like, since it sounds like mine may be broken.

To show proof, here are screenshots as I am unsure how else to provide feedback here.
(I pulled up the dev window as far as I could while still exposing working default modules). This output is the same as listed above:

I also did a CTRL-ALT-DELETE to allow me to access my text editor and pull up the MagicMirror/config.js file live while the magic mirror is still running. This is the exact config I posted previously:

The front & backend logs remain completely the same as posted earlier. Hopefully I am not completely misunderstanding you here. Thanks for the help!

MMRIZE

@vandy2424
I think websocket issue would be the reason. Can you confirm whether other node_helper dependent module(e.g. default calendar module) works other than MMM-DynamicWeather?

Usually, websocket could be broken by firewall setting, port problem, network quality or by old library, oand many various reasons. Anyway when websocket is broken once, socketNotification will not work.

sdetweil

@vandy2424 can you please show the contents of the config folder

vandy2424

@MMRIZE Hey MMRize,

Yeah I went ahead and setup the calendar module. The first thing I tried was running this module with the default config:

    module: "calendar",
    position: "top_left", // This can be any of the regions. Best results in left or right regions.
    config: {
      // The config property is optional.
      // If no config is set, an example calendar is shown.
      // See 'Configuration options' for more information.
    },
  },

This returned loading… on the magic mirror. (I assumed based on the documentation it would at least show an example calendar).

I then tried to add a very basic calendar in the config.js just to see if the result would change:

module: "calendar",
      position: "top_left", // This can be any of the regions. Best results in left or right regions.
      config: {
        // The config property is optional.
        // If no config is set, an example calendar is shown.
        // See 'Configuration options' for more information.
        calendars: [
					{
						symbol: "calendar-check",
						url: "https://www.calendarlabs.com/ical-calendar/ics/39/Canada_Holidays.ics"									
          },
        ],
      },

And i still got the same result (Loading…).

sdetweil

@vandy2424

when you start mm,do

 npm start >somefile.txt 2>&1

that will capture all the backend output

the front end said it started the modules listed in that config.js

vandy2424

@sdetweil yes here are the contents of the config folder:

vandy2424

@sdetweil I did this and exported a file out. I then went ahead and ran the MagicMirror for 2 minutes.

Here is the output (same as before):

[09.02.2024 17:44.28.817] [LOG]   Starting MagicMirror: v2.26.0
[09.02.2024 17:44.28.835] [LOG]   Loading config ...
[09.02.2024 17:44.28.841] [DEBUG] config template file not exists, no envsubst
[09.02.2024 17:44.28.848] [LOG]   Loading module helpers ...
[09.02.2024 17:44.28.905] [LOG]   Initializing new module helper ...
[09.02.2024 17:44.28.907] [LOG]   Module helper loaded: updatenotification
[09.02.2024 17:44.28.909] [LOG]   No helper found for module: helloworld.
[09.02.2024 17:44.28.910] [LOG]   All module helpers loaded.
[09.02.2024 17:44.28.928] [LOG]   Starting server on port 8080 ... 
[09.02.2024 17:44.29.399] [LOG]   Server started ...
[09.02.2024 17:44.29.402] [LOG]   Connecting socket for: updatenotification
[09.02.2024 17:44.29.404] [LOG]   Starting module helper: updatenotification
[09.02.2024 17:44.29.405] [LOG]   Sockets connected & modules started ...
[09.02.2024 17:44.29.429] [LOG]   Launching application.
Warning: vkCreateInstance: Found no drivers!
Warning: vkCreateInstance failed with VK_ERROR_INCOMPATIBLE_DRIVER
    at CheckVkSuccessImpl (../../third_party/dawn/src/dawn/native/vulkan/VulkanError.cpp:88)
    at CreateVkInstance (../../third_party/dawn/src/dawn/native/vulkan/BackendVk.cpp:458)
    at Initialize (../../third_party/dawn/src/dawn/native/vulkan/BackendVk.cpp:344)
    at Create (../../third_party/dawn/src/dawn/native/vulkan/BackendVk.cpp:266)
    at operator() (../../third_party/dawn/src/dawn/native/vulkan/BackendVk.cpp:521)

[09.02.2024 17:46.45.217] [LOG]   Shutting down server...
[09.02.2024 17:46.45.219] [LOG]   Stopping module helper: updatenotification
[09.02.2024 17:46.45.221] [LOG]   Node_helpers stopped ...