sorry to use the same topic. I have also trouble with the update to 2.10.0. The update script works, but I still have the notification that there is an update for MM. But the update log ends with “Upgrade ended - Do Jan 2 20:24:45 CET 2020”.

damn - 2nd try without a virtual environment.

@nischi: Is there a chance that you merge your module also with MMM-MotionDetector? Currently I use the camera to activate and deactive my screen and Google told me that it isn’t possible that 2 processes use the same camera. The suggested solution was to use a 2nd camera, merge both processes or stream the camera picture.

@chrizzz said in MagicMirror² v2.15.0 is available don't work.:

I do have some strange things after the update.

At first, the new weather module is just “loading” without displaying content. Even after 30+ minutes. Is there something wrong with the config? I saw that there is a minor issue with the data request which will cause it to load for ~10min (or to reduce the update interval).

{
			module: "weather",
			position: "top_right",
			classes: "always",
			config: {
				// See 'Configuration options' for more information.
				type: "current",
				locationID: "YYY",
				appid: "XXX"
			}
		},

I checked this again with switching back to the old module and the old module works. The forcasting takes 10min (as expected) but the module itself works. I thought this might be something with the connection to the API. Any ideas?

@sdetweil yes I did and both worked.

I did npm install in all module folders too and did the npm install of MM multiple times just to check if something is wrong

I do have some strange things after the update.

At first, the new weather module is just “loading” without displaying content. Even after 30+ minutes. Is there something wrong with the config? I saw that there is a minor issue with the data request which will cause it to load for ~10min (or to reduce the update interval).

{
			module: "weather",
			position: "top_right",
			classes: "always",
			config: {
				// See 'Configuration options' for more information.
				type: "current",
				locationID: "YYY",
				appid: "XXX"
			}
		},

And I have new lines of errors in the log, I don’t understand why these syntax errors appear. I checked my config file and everything looks fine. Regarding git, does this mean it couldn’t connect to github?

[03.04.2021 23:22.22.900] [ERROR] Failed to parse data , error SyntaxError: Unexpected end of JSON input
[03.04.2021 23:22.24.037] [ERROR] Failed to parse data , error SyntaxError: Unexpected end of JSON input
[03.04.2021 23:22.25.987] [ERROR] Failed to fetch git data for MMM-CountEvents: Error: block timeout reached
[03.04.2021 23:22.27.080] [ERROR] Failed to fetch git data for MMM-Parcel: Error: block timeout reached
[03.04.2021 23:22.35.518] [ERROR] Failed to fetch git data for MMM-Face-Reco-DNN: Error: block timeout reached
[03.04.2021 23:22.39.290] [ERROR] Failed to fetch git data for MMM-PIR-Sensor: Error: block timeout reached
[03.04.2021 23:32.42.638] [ERROR] Failed to fetch git data for MMM-CountEvents: Error: block timeout reached
[03.04.2021 23:37.14.466] [ERROR] Failed to parse data , error SyntaxError: Unexpected end of JSON input
[03.04.2021 23:37.14.577] [ERROR] Failed to parse data , error SyntaxError: Unexpected end of JSON input
[03.04.2021 23:52.14.126] [ERROR] Failed to parse data , error SyntaxError: Unexpected end of JSON input
[03.04.2021 23:52.14.377] [ERROR] Failed to parse data , error SyntaxError: Unexpected end of JSON input

It works again. I think it was my mistake in the config based on the classes setting or compared with the carousel module.

@sdetweil

git version 2.20.1

@sdetweil but I have modules with available updates and the update notification module doesn’t work for a few months. I did my last MM update without been notified. I did it just because it was weird to have such a long time without the update notification

@sdetweil sorry Sam, I think I don’t get your answer.

Hey guys,

I am struggling with the default module “updatenotification”. It doesn’t show the notification bar if there is an update for MM or one of the modules.

The mm-out.log shows:

[08.02.2021 18:55.19.771] [LOG]   Initializing new module helper ...
[08.02.2021 18:55.19.773] [LOG]   Module helper loaded: updatenotification
[08.02.2021 18:55.24.000] [LOG]   Connecting socket for: updatenotification

There aren’t any log entries in mm-error.log

My config has these lines for the module:

{
			module: "updatenotification",
			position: "top_bar",
			classes: "always"
},

I tried it without the classes line too.

My MM version is 2.14.0

//e: I used the “Troubleshooting” space and not the one in modules because I thought default modules would fit to this space better.

@evroom said in new update/upgrade script, ready for testing:

@ChrizZz said in new update/upgrade script, ready for testing:

Now my Pi is downloading the electron v3.1.13 version with 3.01 kB/s.

It looks like github has problems. I also cannot download other stuff from it with proper speed or without running into a timeout. Perhaps local or depends on your ISP region.

I started installing electron in a new terminal session and it is downloading now with 16 kB/s. Maybe a stupid decission, maybe not.

Current status: 45% downloaded in the new terminal session, 18.5% downloaded as part of the MM update.

//edit: I stopped the inital installation, downloaded the right electron file from a mirror and placed the zip file in the /home/pi/.cache/electron folder. After that I updated electron manually. It worked well and after that I started npm install of the new MM version again. Now everything is updated without waiting years to download the zip from Github.

@sdetweil said in new update/upgrade script, ready for testing:

@surger13 ok, looks like we have to fight the manual way

do

cd ~/MagicMirror
git stash
git merge
npm install

took the manual way too because of the same probs. Now my Pi is downloading the electron v3.1.13 version with 3.01 kB/s. can I stop the installation process to update electron manually?