@sdetweil I’m going to go ahead and start over on with a clean build on bullseye. This one is still running on buster which may be part of the issue. I’ve got another Pi I can use and I’ll just use the config from this one and rebuild it. Thanks for the quick reply.
Read the statement by Michael Teeuw here.
Posts made by gonzonia
-
RE: After update MMM-Buttons breaks, made things worse trying to fix it
-
After update MMM-Buttons breaks, made things worse trying to fix it
So after I ran the update script, magicmirror wouldn’t start.
This was in the log
[03.07.2023 08:40.46.643] [ERROR] 2023-07-03T08:40:46 <error> (node:17008) UnhandledPromiseRejectionWarning: Error: The module '/home/pi/MagicMirror/modules/MMM-Buttons/node_modules/epoll/build/Release/epoll.node' was compiled against a different Node.js version using NODE_MODULE_VERSION 93. This version of Node.js requires NODE_MODULE_VERSION 116. Please try re-compiling or re-installing the module (for instance, using `npm rebuild` or `npm install`). at process.func [as dlopen] (node:electron/js2c/asar_bundle:2:1822) at Module._extensions..node (node:internal/modules/cjs/loader:1354:18) at Object.func [as .node] (node:electron/js2c/asar_bundle:2:1822) at Module.load (node:internal/modules/cjs/loader:1124:32) at Module._load (node:internal/modules/cjs/loader:965:12) at f._load (node:electron/js2c/asar_bundle:2:13330) at Module.require (node:internal/modules/cjs/loader:1148:19) at require (node:internal/modules/cjs/helpers:110:18) at bindings (/home/pi/MagicMirror/modules/MMM-Buttons/node_modules/bindings/bindings.js:112:48) at /home/pi/MagicMirror/modules/MMM-Buttons/node_modules/epoll/epoll.js:7:31 at Object.<anonymous> (/home/pi/MagicMirror/modules/MMM-Buttons/node_modules/epoll/epoll.js:15:3) at Module._compile (node:internal/modules/cjs/loader:1269:14) at Module._extensions..js (node:internal/modules/cjs/loader:1324:10) at Module.load (node:internal/modules/cjs/loader:1124:32) at Module._load (node:internal/modules/cjs/loader:965:12) at f._load (node:electron/js2c/asar_bundle:2:13330) (Use `electron --trace-warnings ...` to show where the warning was created) (/home/pi/MagicMirror/node:internal/process/warning:60 writeOut) [03.07.2023 08:40.46.645] [ERROR] 2023-07-03T08:40:46 <error> (node:17008) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1) (/home/pi/MagicMirror/node:internal/process/warning:60 writeOut) MESA-LOADER: failed to retrieve device information MESA-LOADER: failed to retrieve device information MESA-LOADER: failed to retrieve device information MESA-LOADER: failed to open kms_swrast (search paths /usr/lib/arm-linux-gnueabihf/dri:\$${ORIGIN}/dri:/usr/lib/dri) failed to load driver: kms_swrast MESA-LOADER: failed to open swrast (search paths /usr/lib/arm-linux-gnueabihf/dri:\$${ORIGIN}/dri:/usr/lib/dri) failed to load swrast driver Gdk-Message: 08:40:55.667: electron: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.
I tried
npm rebuild
I tried
npm install
Wasn’t working.
An unhandled error occurred inside electron-rebuild Could not detect abi for version 25.2.0 and runtime electron. Updating "node-abi" might help solve this issue if it is a new release of electron
I saw a message
npm WARN EBADENGINE Unsupported engine { npm WARN EBADENGINE package: 'lru-cache@10.0.0', npm WARN EBADENGINE required: { node: '14 || >=16.14' }, npm WARN EBADENGINE current: { node: 'v16.13.1', npm: '9.7.1' } npm WARN EBADENGINE }
I thought it was saying that my node was just a bit out of date, so I made the mistake of running
nvm install node
and now I get this
node: /usr/lib/arm-linux-gnueabihf/libstdc++.so.6: version `GLIBCXX_3.4.26' not found (required by node)
help?
-
RE: MMM-BMW-DS (A different kind of weather module)
@Cr4z33 Yes, the data that us returned is in a different format. There may be some overlap, but overall it’s outside my skill set.
-
RE: MMM-BMW-DS (A different kind of weather module)
@Cr4z33 It doesn’t look like the data comes back the same. Sorry.
-
RE: MMM-BMW-DS (A different kind of weather module)
@Cr4z33 PirateWeather was easy because it uses the same format as DarkSky. If Tomorrow.io does as well then theoretically it could be easy to add a config setting for the URL along with the existing API key setting.
-
RE: MMM-BMW-DS (A different kind of weather module)
With the end of DarkSky API, I’ve forked this and updated it to use PirateWeather. https://github.com/gonzonia/MMM-BMW-PW
All coding credit goes to @Mykle1 . I pretty much just changed the name and a URL. Pirateweather does not support languages though and that was removed.
-
RE: electron-rebuild and MagicMirror v2.18 (and more)
@bugsounet THANK YOU! This saved me a lot of headaches. I went ahead and updated to 2.18 and got the exact error you reference in the exact same module. A quick search and I found your very helpful solution. Thank you for sharing.
-
RE: MMM-NewsFeed
I’m trying this out as a replacement for the default newsfeed. I’m having trouble styling it though. I’d like it to have a more transparent background and to make the font white. I can’t seem to make that happen.
For example- on the default newsfeed module I set the background with rgba(0, 0, 0, 0.2);I can’t get that to apply to this one.
-
RE: MMM-GooglePhotos
@sdetweil It’s interesting. I’m seeing this error now instead of the socket disconnected error. I’ve changed the DNS on the MM to not use the pihole (it’s using Google DNS).
I don’t know why I’m seeing this vs. the other error all of a sudden. I still think it’s hard to blame the network exclusively. I have other modules too that all run fine at the exact same time.
I’ve tried to figure out how to catch the error but I don’t think I can. From what I can tell it’s making the async call and then while waiting for a response it loses the connection for some reason. I’m not skilled enough to re-write try the async queue method referenced in the github post I linked to previously. I’m just hopeful someone who has the same problem might have the skills to fix it or at least catch it better so that the module doesn’t fail completely. (Meanwhile I’ll keep trying to identify what the problem is).
-
RE: MMM-GooglePhotos
@sdetweil I do but I thought I’d switched the DNS on there to not use it. Apparently not. This new error was likely the result of the update to pihole v5 (need to figure that out separately). Thanks for pointing me in the right direction!