@dcarls91
I understand that in the beginning the amount information can be overwhelming, but how are you going to find out what you are doing when you scrape your project?
Especially when you are so close in getting the ‘Mirror’ started; just a few characters are missing in the config file.
The community here is very active and very helpful and can step down a nodge when it is getting too technical.
Of course it is expected that you have a certain level of knowledge or that you are willing to obtain that level.

Besides spending several hours, did you spend any money on equipment, etc?

If you decide to give it a last effort, then it would help to tell us on what platform your Mirror is running (Raspberry, PC, Ubuntu, etc) and it would help to report back with a bit more details (other than I tried and it did not work).
And if someone tells you to perform action XYZ and you have no idea what the heck XYZ is or how to execute, then don’t be afraid to say so.

The suggestions given, like try it module by module and the config check are very useful (I guess everyone was in this position, I know I was) and will solve your issues.

If you decide to move away from Magic Mirror, then I respect that, but perhaps you will reconsider.

Disclaimer: I do not have any shares in the project and am by no means an expert. Just reaching out. :-)

@myfingersarecold said in MMM-MPlayer:

I don’t feel like actually uploading it to github, but here is the source code, and an example config.

I took the liberty to take the provided code, make changes to it and make it available as a public repository:

https://github.com/evroom/MMM-MPlayer

My own main purpose for using it, is to setup a new Raspberry Pi (Raspberry Pi 4 Model B), with Debian 12 (bookworm) and the latest MM version (2.30.0).
Replacing a Pi 3b 32-bit Debian 10 buster setup where OMXPlayer is still working.
I will be using a single window with a single RTSP stream (for an Axis Network Camera).
Nothing fancy.

Best regards,

E.J.

@KristjanESPERANTO

I did the update and it is looking much better now.
I reverted back to db (npm run query dbis working again).
Only one thing I noticed:

On display (last update 11:15)
11:08 +1.0333333333333334
11:28 +0

The 11:08 entry is in the past (maxUnreachableDepartures: 2,).
The +1.0333333333333334 is a bit too much :-)

Hi,

For beginners, the catchphrase is “JSON syntax”.
There are many articles to be found, both short and lengthy.
A small article would be:
https://restfulapi.net/json-syntax/

The main things to look for in your config.js file are:

• does every [ have a matching ]
• are all arrays separated by a , (the last array does not need a ,)
• does every { have a matching }
• are all objects separated by a , (the last object does not need a ,)
• is every name value pair separated by a ,

The syntax checker will try to find out if this syntax is correct and tries to predict where the error could be.
So, when it says it saw a [ and it cannot find a matching ] it tells you what was expected and what it saw.

Try to format you config.js to make it more visible.
For example this:

[{},{}],[{},{[]}]

is better written like this:

[
  {},
  {}
],
[
  {
  },
  {
    [
    ]
  }
]

Pairs of [ ]and { } are better visible like this.

Good luck :-)

@KristjanESPERANTO said in MMM-MPlayer:

@evroom Nice! 🚀 Please add it to the module list 🙂

Done.

@CyruS1337 said in Cronjob:

I have always used the command sudo crontab -e and with this it did not work.

Just to clarify.

Normally you are user pi: $ who am I

So crontab -e will work for the pi user.
Using sudo crontab -e will change the crontab for the root user.

Now how can you tell what is what ?

For the user pi:
$ sudo crontab -l -u pi
which is the same as
$ crontab -l
For the user root:
$ sudo crontab -l -u root

Furthermore, when you have activated the root crontab, then the command will run as root, in the root (/) directory.
In this case pm2 reload command will search for the mm.sh script under / and will not find it.
Whereas when activated the pi crontab, the mm.sh script will be searched in the /home/pi directory, where it should be, and it will work.

Use pm2 show mmto show the details on mm under pm2.
Then you will understand it better.

Cron messages normally are directed to /var/log/cron.log, but on my system it is not directed:

$ grep cron /etc/rsyslog.conf
#cron.*				/var/log/cron.log

To see the cron messages, when not in cron.log:

$ tail -F /var/log/syslog | grep CRON

[ On my system I see CRON messages for root, although I do not have root crontab entries. There is a crond running that runs alongside $ systemctl status cron.]

Have fun :-)

Okay, found it.

In my /boot/config.txt I had the width and height set to 900 and 1600 and this has to be now 1600 and 900.
This is working:

display_hdmi_rotate=0
framebuffer_width=1600
framebuffer_height=900

Works now.

Only need to modify the omxplayer lines to have those streams rotated too.

I got streaming from a Linux SAT receiver with enigma2 working, using the module MMM-RTSPStream-
But you will need to supply a bit more information than rather ‘a TV tuner’.

Hi,

Quite happy with MMM-RTSPStream so far; thx to those that contributed to it.

Next thing I am trying to use MMM-RTSPStream for, is streaming sat-tv from a Dreambox & VU+ receivers.
I am able to stream a channel using:

omxplayer --vol -3000 --win “0 0 480 320” --live http://192.168.178.28:8001/1:0:19:283D:3FB:1:C00000:0:0:0:

It is not a rtsp stream, but it can use omxplayer for streaming.
When I try to use MMM-iFrame, I can add the URL, but then it tries to open a program that can play mpg (and MagicMirror won’t start).
When I use it to stream using my browser (on my PC), I have it open VLC player, but installing VLC on Raspberry (using HW acceleration) is quite an act, so I would prefer to use omxplayer.

Could this be done ?

I am not so familiar with JavaScript and CCS (yet), more a Perl guy, but am willing to assist and test-drive.

Probably there are better and possible simpler ways to get it done, but I do something similar using a Perl script and this module:
https://github.com/eouia/MMM-HTMLBox
The Perl script reads values and builds a HTML page.
The module displays it on the Magic Mirror.
A cron job makes it semi-static as it runs the script regularly.

@Jose1701

No, sorry, no idea.
What Sam says, but that needs knowledge.
But I opened an issue/request, so let’s see if it will be granted:
https://github.com/CuddlyCow/MMM-HoymilesPVMonitor/issues

@Jose1701

Remove the old module from the config:

$ vi ~/MagicMirror/config/config.js

Remove the "MMM-Hoymiles-Wifi" config, or set:

    module: "MMM-Hoymiles-Wifi"
    disabled: true,

Delete HoymilesWifi from pm2:

$ pm2 stop HoymilesWifi
$ pm2 delete HoymilesWifi
$ pm2 save

If desired, completely remove the old module:

$ cd ~/MagicMirror/modules/
$ rm -rf MMM-Hoymiles-Wifi

Install MMM-HoymilesPVMonitor:

$ cd ~/MagicMirror/modules

$ git clone https://github.com/CuddlyCow/MMM-HoymilesPVMonitor.git

$ cd MMM-HoymilesPVMonitor

$ git branch
* main

$ git remote -v
origin	https://github.com/CuddlyCow/MMM-HoymilesPVMonitor.git (fetch)
origin	https://github.com/CuddlyCow/MMM-HoymilesPVMonitor.git (push)

$ which hoymiles-wifi
/home/admin/.local/bin/hoymiles-wifi

$ echo $PATH
/home/admin/.local/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/local/games:/usr/games

$ vi ~/MagicMirror/config/config.js

  {
    module: "MMM-HoymilesPVMonitor",
    disabled: false,
    header: "PV Monitor",
    position: "top_left",
    config: {
      dtuIp: "192.168.178.50",        // IP address of your Hoymiles DTU
      maxPower: 800,                  // Maximum system power in watts
      updateInterval: 5 * 60 * 1000   // Update interval in milliseconds (default: 5 minutes)
    }
  }


$ grep 'dtuIp' ~/MagicMirror/config/config.js
      dtuIp: "192.168.178.50",        // IP address of your Hoymiles DTU


$ ls -als public/history_daily.json
4 -rw-r--r-- 1 admin admin 115 Nov  6 08:47 public/history_daily.json

$ cat public/history_daily.json
[
  {
    "timestamp": "2025-11-06 08:47",
    "power": 40,
    "energy_daily": 0.03,
    "energy_total": 0.8
  }

$ pm2 flush

$ pm2 restart MagicMirror

$ pm2 status MagicMirror
┌────┬────────────────┬─────────────┬─────────┬─────────┬──────────┬────────┬──────┬───────────┬──────────┬──────────┬──────────┬──────────┐
│ id │ name           │ namespace   │ version │ mode    │ pid      │ uptime │ ↺    │ status    │ cpu      │ mem      │ user     │ watching │
├────┼────────────────┼─────────────┼─────────┼─────────┼──────────┼────────┼──────┼───────────┼──────────┼──────────┼──────────┼──────────┤
│ 0  │ MagicMirror    │ default     │ 2.33.0  │ fork    │ 26202    │ 4m     │ 3    │ online    │ 0%       │ 2.1mb    │ admin    │ enabled  │
└────┴────────────────┴─────────────┴─────────┴─────────┴──────────┴────────┴──────┴───────────┴──────────┴──────────┴──────────┴──────────┘

$ pm2 logs MagicMirror --lines 100

0|MagicMir | [2025-11-06 08:47:43.474] [INFO]  [MMM-HoymilesPVMonitor.js:17:9] MMM-HoymilesPVMonitor started with DTU-IP: 192.168.178.50
:
:
0|MagicMir | [2025-11-06 08:47:49.226] [LOG]   [MMM-HoymilesPVMonitor] Running Python script: python3 /home/admin/MagicMirror/modules/MMM-HoymilesPVMonitor/dtu_data.py --ip 192.168.178.50 --max 800 --out /home/admin/MagicMirror/modules/MMM-HoymilesPVMonitor/public/history_daily.json
0|MagicMir | [2025-11-06 08:47:51.682] [LOG]   [MMM-HoymilesPVMonitor] Python script output: [WARNING] Could not load history: Expecting value: line 2 column 1 (char 1)
0|MagicMir | [2025-11-06 08:47] [INFO] Live DTU data appended: {'timestamp': '2025-11-06 08:47', 'power': 40, 'energy_daily': 0.03, 'energy_total': 0.8}
:
:
0|MagicMir | [2025-11-06 08:52:42.141] [LOG]   [MMM-HoymilesPVMonitor] Running Python script: python3 /home/admin/MagicMirror/modules/MMM-HoymilesPVMonitor/dtu_data.py --ip 192.168.178.50 --max 800 --out /home/admin/MagicMirror/modules/MMM-HoymilesPVMonitor/public/history_daily.json
0|MagicMir | [2025-11-06 08:52:43.287] [LOG]   [MMM-HoymilesPVMonitor] Python script output: [2025-11-06 08:52] [INFO] Live DTU data appended: {'timestamp': '2025-11-06 08:52', 'power': 41, 'energy_daily': 0.03, 'energy_total': 0.8}

$ cat public/history_daily.json
[
  {
    "timestamp": "2025-11-06 08:47",
    "power": 40,
    "energy_daily": 0.03,
    "energy_total": 0.8
  },
  {
    "timestamp": "2025-11-06 08:52",
    "power": 41,
    "energy_daily": 0.03,
    "energy_total": 0.8
  }

Tested on:

$ cat /proc/device-tree/model; echo
Raspberry Pi 3 Model B Plus Rev 1.3

$ vcgencmd get_config total_mem
total_mem=1024

$ grep version ~/MagicMirror/package.json
	"version": "2.33.0",

@Jose1701

Yeah, stopped is not good.
I will need to get it working myself before I can give more useful information on what to check.
Will keep you posted.

@Jose1701

>> You installed that already, so no need to install it again.
>>The schris88 requirements.txt contains the hoymiles-wifi package.

If you want to repeat it under the new module name, then you will need to copy the requirements.txt file from the previous module.
But again, since you already did this, no need to repeat.

@Jose1701

You installed that already, so no need to install it again.
Probably using:

python -m pip install -r requirements.txt --break-system-packages

The schris88 requirements.txt contains the hoymiles-wifi package.

@Jose1701

You also might try this module:

https://github.com/CuddlyCow/MMM-HoymilesPVMonitor

I may give it a try myself.

@Jose1701

First of all, where I write

/home/admin/

please use

~/

(tilde sign)

And can you please send me:

cd ~/MagicMirror/modules/MMM-Hoymiles-Wifi
git branch
git remote -v

Every time you get that port in use error, run the long command to see what programs are using the port.
And of course do not use HoymilesWifi.sh when it is also active under pm2.

I am starting to wonder if the module works at all.
I finally got a picture, but it showed an error in it.

To be honest, for me the MM does not display anything.
Although it is dark, I still expected the graphic with 0 or so.
Or I have to wait a bit longer.

I used
https://github.com/schris88/MMM-Hoymiles-Wifi/
and all the above is correct and running.

A year ago I made a fork and made some changes, of which I think are present in the schris88 version as well.

https://github.com/evroom/MMM-Hoymiles-Wifi/
I will give this one a try when I have time.

PS: it seems that when the microinverter is off-line, you will not see anything. Need to wait for it to be active again.

@Jose1701

First I would disable the module:

$ vi ~/MagicMirror/config/config.js

    module: "MMM-Hoymiles-Wifi",
    disabled: true,

$ pm2 restart MagicMirror

I build this command to try to get more info on port 5000:

$ for pid in `lsof -i :5000 | grep -v 'PID' | awk '{print $2}' | sort -u`; do echo $pid; ps -Flww -p  $pid; done

Hopefully the Forum tool does not change it.

Furthermore please verify and supply the following data:

$ cd /home/admin/MagicMirror/modules/MMM-Hoymiles-Wifi

Check path:

$ which hoymiles-wifi
$ echo $PATH

Check if the path is in the PATH.
If not, do (using the path from ‘which’):

$ export PATH=$PATH:/home/admin/.local/bin

Check config.js:

$ grep ':5000' ~/MagicMirror/config/config.js

Expected is:

{ src: 'http://127.0.0.1:5000' },

Check HoymilesWifi.sh:

$ grep 'dtu_ip_address' HoymilesWifi.sh

Expected is your DTU IP address, for example:

python hoymiles_data.py --dtu_ip_address 192.168.178.50 --max 800

Test run (hoymiles-wifi):

$ hoymiles-wifi --host 192.168.178.50  identify-inverters

Expected is a response.

Test run (HoymilesWifi.sh)

$ ./HoymilesWifi.sh

Expected is:

* Serving Flask app 'hoymiles_data'
* Debug mode: off
INFO:werkzeug:WARNING: This is a development server. Do not use it in a production deployment. Use a production WSGI server instead.
* Running on http://127.0.0.1:5000
INFO:werkzeug:Press CTRL+C to quit

If you wait a bit some more output is shown.

If it works, then I would suggest to stop the ./HoymilesWifi.sh command and do:

$ cd /home/admin/MagicMirror/modules/MMM-Hoymiles-Wifi
$ pm2 start HoymilesWifi.sh
$ pm2 save

$ pm2 status HoymilesWifi

$ pm2 logs HoymilesWifi --lines 10

If everything is okay, the enable the module again:

$ vi ~/MagicMirror/config/config.js

    module: "MMM-Hoymiles-Wifi",
    disabled: false,

$ pm2 restart MagicMirror

@Jose1701

Yes, so an instance is already running.
You added it to pm2 too?

pm2 status

If yes, then you do not need to run it manually.
If no, then kill the (p)pid.

sudo kill -9 [ppid]