@BKeyport
Depends on what you want to stream and with what you want to stream it with.
I, for example, am streaming a single Axis IP cam (supposing it is h.264) using omxplayer. Standalone, controlled by pm2.
The MMM-RTSPStream does work, but I was having problems placing the stream on the screen to my likings.
You may need to check this list if there is a module that suites your needs:
https://github.com/MichMich/MagicMirror/wiki/3rd-party-modules#utility--iot--3rd-party--integration

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

old? I updated the dropbox file so, it should have been fixed…

I mean before you said “give it another try please…”.
Old is always relative :-)

The upgrade log did say```
upgrading from version 2.8.0 to 2.10.0

The upgrade that I still running says```
upgrading from version 2.9.0 to 2.10.0

The test run on the 2.8.0 install currently outputs this:

pi@MagicPi:~ $ date; bash -c  "$(curl -sL https://www.dropbox.com/s/lxzwyzohg61sppu/upgrade-script.sh?dl=0)"
Fri Jan  3 15:34:42 CET 2020
the log will be /home/pi/MagicMirror/installers/upgrade.log
No LSB modules are available.
doing test run = true
update log will be in /home/pi/MagicMirror/installers/upgrade.log

saving custom.css
upgrading from version 2.8.0 to 2.10.0
fetching latest revisions
there are 1 local files that are different than the master repo

   css/custom.css

do you want to save these files for later   (Y/n)?Y
processing dependency changes for active modules with package.json files

processing for module MMM-PublicTransportHafas please wait
----------------------------------
skipped processing for MMM-PublicTransportHafas, doing test run
processing complete for module MMM-PublicTransportHafas

processing for module MMM-soccer please wait
----------------------------------
skipped processing for MMM-soccer, doing test run
processing complete for module MMM-soccer

restoring custom.css
test run, restoring files stashed
error: Your local changes to the following files would be overwritten by merge:
	css/custom.css
Please commit your changes or stash them before you merge.
Aborting

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

grep version ~/MagicMirror/package.json

This MM install has

pi@MagicPi:~ $ grep version ~/MagicMirror/package.json
  "version": "2.8.0",

Apparently I did not upgrade to 2.9.0. :-)

In parallel I am upgrading an 2.9.0 install (using the ‘old’ apply script). I got the same git: 'git_user_name' is not a git command.error there, but decided to do the apply anyway.
Currently Downloading tmp-27972-0-electron-v3.1.13-linux-armv7l.zip which takes forever for some reason (approx. 700 B/s).

Btw, I know it can be solved by other means, but I would like you to be able to tweak your script.

@sdetweil

Latest run:

:
:
here are 1 local files that are different than the master repo

   css/custom.css

do you want to save these files for later   (Y/n)?Y
:
:
restoring custom.css
test run, restoring files stashed
error: Your local changes to the following files would be overwritten by merge:
	css/custom.css
Please commit your changes or stash them before you merge.
Aborting

I can of course save and restore during the apply, but I do not know if this is what you want /expect.

@sdetweil

Hi Sam, updating MM to 2.10.0 using your script. At the end the test run says:

any *-lock.json files do not need to be saved
do you want to save these files for later   (Y/n)?Y
git: 'git_user_name' is not a git command. See 'git --help'.
no modules found needing npm refresh
restoring custom.css
test run, restoring files stashed
git: 'git_user_name' is not a git command. See 'git --help'.

The upgrade.log file does not give a clue as to what exact command was used.
I am not into git, so cannot give you anything more than the git version

pi@MagicPi:~ $ git --version
git version 2.11.0

Any ideas ?

Best regards,
E.J.

@kris1208

Okay, this looks like a bit more than a “truncated stream” issue.
That you see something at all is a miracle, I would say :-)

First of all, please use the </> button when providing output or pieces of config.
Select the text and press on the </> button.
Makes it a bit easier to read.

You can disable the module by putting ‘disabled: true’ in the config.js.
With the value false you can enable it again later.

module: "MMM-RTSPStream",
    disabled: true,

Or remove the whole module entry, but this is not necessary when there are no syntax errors.

Then restart mm.
I always use

pm2 restart mm

provided mm is the pm2 app name.
See

pm2 status

To remove the module completely you can simply remove or disable it from the config.js and then delete the structure

rm -rf ~/MagicMirror/modules/MMM-RTSPStream

Or move it out of the way when you want to attempt a second try:
mv ~/MagicMirror/modules/MMM-RTSPStream ~/MagicMirror/modules/MMM-RTSPStream.old

@kris1208

Hi, bonjour, to be honest I do not see the problem right away. With truncated you mean you expect to see more? Of the top stream or the bottom stream, or both? What resolution(s) do you expect to see?

I suppose you followed the instructions from this repository:
https://github.com/shbatm/MMM-RTSPStream
Including the “To use this module, use the configuration builder tool included.” part to produce a recommended config for your stream(s).

I think your config defaults to the vlc player. Could you please do:

ps -eaf | grep -v grep | egrep 'omxplayer|vlc'

If you (re)start MagicMirror (or mm), then you will find some MMM-RTSPStream module related info.

pm2 logs --lines 200

It will start with something like this:

Starting stream stream1 with args:

I personally use omxplayer, but standalone, without using MMM-RTSPStream. Since it is an overlay anyway, I feel I can control it more.

Good luck gathering the information.

@kris1208

Perhaps you can share the config.js part for MMM-RTSPStream with us?

The pm2 log output for this module is useful too.
The part where it shows the applied coordinates.

@Thgj0842

There is a thread somewhere that discusses rotation via css.
I have my monitor rotated 90 degrees, clockwise, using these settings:

~/MagicMirror/css/custom.css

body {
  margin: 0;
  position: absolute;
  transform: rotate(-90deg);
  transform-origin: top left;
  width: 100vh;
  height: 100vw;

  object-fit: cover;
  top: 100vh;
        visibility: visible;
 }

/boot/config.txt

display_hdmi_rotate=0

Here are all settings from my current config.txt:

$ cat /boot/config.txt | egrep -v '^$|#'
decode_MPG2=0xYYYYYYYY
dtparam=audio=on
hdmi_group=2
hdmi_mode=83
display_hdmi_rotate=0
framebuffer_width=1600
framebuffer_height=900
gpu_mem=128

Give it a try.

@fribse said in Hmm, a lot of modules are putting up a fight for me :-(:

But now the MM is not showing anything

Hi,

Due to questions in another threat I installed that module myself.
I found out that this repository works (not the paphko version):
git clone https://github.com/szech/mmm-weatherchart.git

Try this:

$ cd ~/MagicMirror/modules/
$ mv mmm-weatherchart mmm-weatherchart.saved
$ git clone https://github.com/szech/mmm-weatherchart.git
$ cd ~/MagicMirror/modules/mmm-weatherchart
$ npm install

When it works:

$ cd ~/MagicMirror/modules/
$ rm -rf mmm-weatherchart.saved

@sdetweil said in Blank mm after update:

it is not positional

Okay, then it makes sense.
I have module: always first and then disabled:.
So you see that you never can assume something :-)

Using your script now :thumbs_up:

@kvicksson

If these are the only ‘errors’ you see in the pm2 log, then it looks you are quite okay.

As said, I personally would like to ged rid of npm audit errors, but if other board-members think it imposes a hazard to a good running system, then I would leave it. I remember that sometimes some dependencies just did not want to go away and I left it that way.

The only thing to consider, is that you are still running on Debian jessie, where the majority probably runs using stretch and fast adopters on buster.
I would leave this until you setup a new system.

So, when it runs as you expect it to run, then you can close this topic and enjoy your mirror. Otherwise we will hear from you.

@sdetweil said in Blank mm after update:

module: “newsfeed”,
disabled: false,
disabled: false,

I see now, that this is rather odd, not correct, without thinking too much about it.
Does my modified command give the same result ?
It sort of contradicts my statement on being sequential, etc.
Or do you really have ?

module: "newsfeed",
disabled: false,
disabled: false,

module: "MMM-Hotword",
disabled: false,
disabled: true,

@sdetweil said in Blank mm after update:

how can u tell which module ‘disabled’ applies to?

I am assuming it is sequential and that disabled: comes after module:, when present. Don’t think a ‘runaway’ disabled could exist.
And for the purpose it serves, it does its job, IMHO.

Perhaps it is better to first remove the leading blank space and then do the grep (and to ignore the comment parts):

$ cat ~/MagicMirror/config/config.js | sed -e 's/^[ \t]*//' | egrep -w '^module:|^disabled:'

Your piece of node.js looks nice, but how to run it standalone ?
If used as part of a script, it makes more sense to do it this way (more control, more flexible).

This is a command to list all your modules that are in the config.js and which ones are enabled/disabled:

$ cat ~/MagicMirror/config/config.js | egrep 'module:|disabled' | sed -e 's/^[ \t]*//'

@kvicksson said in Blank mm after update:

(node:2465) [DEP0025] DeprecationWarning: sys is deprecated. Use util instead.

I saw this error once for a specific module.
Needed a small code change.
Will try to find what is was.

@lavolp3 said in Blank mm after update:

Fixing” these npm warnings on the root MM install could break the whole mirror

The npm audit itself suggests to fix it using the fix option.
I personally never had any issues with this command, but perhaps I was lucky till now.
Sometimes it cannot resolve an issue, but it never broke anything.

But, if it appears to be that dangerous, then indeed it is perhaps to refrain from it when not really necessary.

@kvicksson said in Blank mm after update:

got an error on the egrep command

Forgot to escape the [, try this:

cat /boot/config.txt | egrep -v '^$|^#|^\['

EDIT: Did not forget to escape it, it is this shitty forum that removes it.

There needs to a backslash \ before the last [

@kvicksson

Doesn’t look too bad.
Probably you saw the previous errors in your log output, that it is why flushing (pm2 flush) sometimes cannot hurt.

In order to know a bit about your environment, can you post the output of the following commands ?
I am assuming you are using a Raspberry Pi

$ cat /proc/device-tree/model
$ lsb_release -a
$ npm --version
$ node --version
$ pm2 --version
$ cat /boot/config.txt | egrep -v '^$|^#|^\['

I also would suggest to see if npm shows any errors:

$ cd ~/MagicMirror
$ npm audit

In my case a

$ npm audit fix

solved the dependency issues it found.

Perhaps others have different ideas, but as a hobbyist, I would take these steps first myself.

@kvicksson said in Blank mm after update:

so don’t have to bother right now?

As long as the errors are no fatal errors that do not prevent the MagicMirror from starting or prevent a certain module from working right, you might chose to ignore them.
But the problem is, that when you add something new or update something existing, it becomes more and more difficult to debug and/or correct in case of problems.

When you do this:

$ pm2 flush
$ pm2 restart mm
$ pm2 logs --lines 100

what is the first error you see ?
Perhaps you post the first 50 to 100 lines of the log.

But only if you want to spend some time on it, when not that’s fine too.