Read the statement by Michael Teeuw here.
[MMM-Dreambox] to connect a Dreambox or a Enigma2 Receiver (like VU or VU+) to MagicMirror and stream stations via omxplayer
-
@axled sorry for replaying late again, but I always work at night. :winking_face:
Do you still need my config or are you already done?
-
@Cr4z33
I got some testfiles for VU+ from Evroom and i have to do some modification and testing to the module within the next days.
AxLED -
@axled alright. :thumbs_up_medium-light_skin_tone:
-
I did some bugfixing:
- bugfixing in error response (node_helper.js)
- bugfix in handling timerlist if empty (MMM-Dreambox.js)
Please check the dev branch of my module:
- Rename your MMM-Dreambox folder to _MMM-Dreambox (for example)
- do a
git clone --branch dev https://github.com/Ax-LED/MMM-Dreambox.gitin your modules folder
Tell me what happens now, if you try to connect to VU+ receiver.
RegardsAxLED
-
@axled said in [MMM-Dreambox] to connect a Dreambox or a Enigma2 Receiver (like VU or VU+) to MagicMirror and stream stations via omxplayer:
git clone --branch dev https://github.com/Ax-LED/MMM-Dreambox.git
Unfortunately still (the same?) errors:
0|mm | Starting node helper for: MMM-Dreambox 0|mm | Whoops! There was an uncaught exception... 0|mm | TypeError: Cannot read property 'statusCode' of undefined 0|mm | at Request._callback (/home/pi/MagicMirror/modules/MMM-Dreambox/node_helper.js:75:42) 0|mm | at self.callback (/home/pi/MagicMirror/node_modules/request/request.js:185:22) 0|mm | at emitOne (events.js:116:13) 0|mm | at Request.emit (events.js:211:7) 0|mm | at Request.onRequestError (/home/pi/MagicMirror/node_modules/request/request.js:877:8) 0|mm | at emitOne (events.js:116:13) 0|mm | at ClientRequest.emit (events.js:211:7) 0|mm | at Socket.socketErrorListener (_http_client.js:387:9) 0|mm | at emitOne (events.js:116:13) 0|mm | at Socket.emit (events.js:211:7)pi@MagicPi:~/MagicMirror/modules/MMM-Dreambox $ git status On branch dev Your branch is up-to-date with 'origin/dev'. nothing to commit, working tree clean0|mm | TypeError: Cannot read property 'statusCode' of undefined pi@MagicPi:~/MagicMirror/modules $ grep 'at Request._callback' /home/pi/.pm2/logs/mm-error.log | sort -u at Request._callback (/home/pi/MagicMirror/modules/MMM-Dreambox/node_helper.js:103:42) at Request._callback (/home/pi/MagicMirror/modules/MMM-Dreambox/node_helper.js:116:42) at Request._callback (/home/pi/MagicMirror/modules/MMM-Dreambox/node_helper.js:129:42) at Request._callback (/home/pi/MagicMirror/modules/MMM-Dreambox/node_helper.js:75:42) at Request._callback (/home/pi/MagicMirror/modules/MMM-Dreambox/node_helper.js:89:42) -
@AxLed
I also tried the Dreambox.
There are no errors and the play list is shown on the Mirror.
However, there is a problem when you put the port in the config.js:pi@MagicPi:~ $ ps -eaf | grep omxplayer | grep -v grep pi 20618 20445 1 22:07 ? 00:00:00 /bin/sh -c omxplayer --vol -6000 --win 0,625,590,957 --live http://192.168.178.28:80:8001/1:0:1:2EE3:441:1:C00000:0:0:0: pi 20619 20618 1 22:07 ? 00:00:00 /bin/bash /usr/bin/omxplayer --vol -6000 --win 0,625,590,957 --live http://192.168.178.28:80:8001/1:0:1:2EE3:441:1:C00000:0:0:0: pi 20642 20619 0 22:07 ? 00:00:00 /usr/bin/omxplayer.bin --vol -6000 --win 0,625,590,957 --live http://192.168.178.28:80:8001/1:0:1:2EE3:441:1:C00000:0:0:0:You see that streaming uses port 8001, so you get 80:8001 as port.
In my case, I use the standard port 80, so I can leave it out, but for example @Cr4z33 uses a different port, so he will not be able to stream.
So, my suggestion is to set the port as a separate variable in the config and only use it where necessary.
-
Other observations (tested with Dreambox dm7020hd).
1/
When I start the Mirror, I no channel is selected.
Then when you do DB-PLAY as first remote command, the list on the Mirror will have a grey background (as if everything is selected) and nothing is streamed.2/
When you do DB-PLAY, I get multiple streams.
I reported this before.pi@MagicPi:~ $ ps -eaf | grep omxplayer | grep -v grep pi 20862 20720 0 22:14 ? 00:00:00 /bin/sh -c omxplayer --vol -6000 --win 0,625,590,957 --live http://192.168.178.28:8001/1:0:1:2EE3:441:1:C00000:0:0:0: pi 20863 20862 0 22:14 ? 00:00:00 /bin/bash /usr/bin/omxplayer --vol -6000 --win 0,625,590,957 --live http://192.168.178.28:8001/1:0:1:2EE3:441:1:C00000:0:0:0: pi 20886 20863 7 22:14 ? 00:00:17 /usr/bin/omxplayer.bin --vol -6000 --win 0,625,590,957 --live http://192.168.178.28:8001/1:0:1:2EE3:441:1:C00000:0:0:0: pi 20894 20720 0 22:14 ? 00:00:00 /bin/sh -c omxplayer --vol -6000 --win 0,625,590,957 --live http://192.168.178.28:8001/1:0:1:2EE3:441:1:C00000:0:0:0: pi 20895 20894 0 22:14 ? 00:00:00 /bin/bash /usr/bin/omxplayer --vol -6000 --win 0,625,590,957 --live http://192.168.178.28:8001/1:0:1:2EE3:441:1:C00000:0:0:0: pi 20921 20895 7 22:14 ? 00:00:17 /usr/bin/omxplayer.bin --vol -6000 --win 0,625,590,957 --live http://192.168.178.28:8001/1:0:1:2EE3:441:1:C00000:0:0:0:3/ After a while the selection of a channel disappears.
The selection sometimes is just a grey background and sometimes a grey background with a play button.4/ My Dreambox has 2 tuners.
I probably see the “now playing” from tuner A, whilst tuner B is streaming.
As the selection disappears, I do not know which channel is streaming. -
@evroom
Answer to the 5 errors in node_helper.js:
I comment the lines out, please try again with the dev branch.AxLED
-
@evroom
About the error for following usage: Dreambox and Dreambox-IP with a port.
I will have to do some testing and come back to you if i have the solution.AxLED
-
@evroom said in [MMM-Dreambox] to connect a Dreambox or a Enigma2 Receiver (like VU or VU+) to MagicMirror and stream stations via omxplayer:
Other observations (tested with Dreambox dm7020hd).
1/
When I start the Mirror, I no channel is selected.
Then when you do DB-PLAY as first remote command, the list on the Mirror will have a grey background (as if everything is selected) and nothing is streamed.
2/
When you do DB-PLAY, I get multiple streams.
I reported this before.
3/ After a while the selection of a channel disappears.
The selection sometimes is just a grey background and sometimes a grey background with a play button.
4/ My Dreambox has 2 tuners.
I probably see the “now playing” from tuner A, whilst tuner B is streaming.
As the selection disappears, I do not know which channel is streaming.Here are some answers:
to 1: Thats true, if module is loaded no channel is selected. Normally you should select a channel first an then start streaming (by DB-PLAY)
to 2: I dont understand at which point you get multiple streams. If no channel was selected before?
to 3: Thats true, if a channel is selected, the background of the selection should be grey. The grey selection will be reseted (to black background), if a refresh of datas is done (duration depends on your refresh interval in config.js). The refresh is hardly to see on the mirror, as i dont do aupdate.dom, i am updating the relevant dom datas directly. The play symbol is shown if you send a DB-PLAY after selection, so you can see that streaming will start within the next seconds. Because after start of streaming the datas are updatet, the grey selection and the play symbols dissapear.
to 4: On my dreambox, if a start a stream on MM, the first line of the module now playing shows the channel i am streaming (if you dont defined the size of stream to full screen). I have no idea, what would be shown on now playing on a 2 tuner box.Most of the issues can be fixed, but i would like to get the some other issues (see this thread) fixed first.
AxLED
-
Did git pull.
0|mm | Starting node helper for: MMM-Dreamboxpi@MagicPi:~/MagicMirror/modules/MMM-Dreambox $ git status On branch dev Your branch is up-to-date with 'origin/dev'. nothing to commit, working tree cleanpi@MagicPi:~/MagicMirror/modules/MMM-Dreambox $ ls -alstr total 112 4 drwxr-xr-x 13 pi pi 4096 Jan 31 21:39 .. 4 drwxr-xr-x 2 pi pi 4096 Jan 31 21:39 translations 8 -rw-r--r-- 1 pi pi 7330 Jan 31 21:39 README.md 8 -rw-r--r-- 1 pi pi 7185 Jan 31 21:39 MMM-Dreambox-xml2json.js 48 -rw-r--r-- 1 pi pi 45771 Jan 31 21:39 MMM-Dreambox_screenshot1.jpg 20 -rw-r--r-- 1 pi pi 19015 Jan 31 21:39 MMM-Dreambox.js 4 -rw-r--r-- 1 pi pi 821 Jan 31 21:39 MMM-Dreambox.css 8 -rw-r--r-- 1 pi pi 5242 Feb 1 20:10 node_helper.js 4 drwxr-xr-x 4 pi pi 4096 Feb 1 20:10 . 4 drwxr-xr-x 8 pi pi 4096 Feb 1 20:19 .gitRestarted MM.
|mm | Starting node helper for: MMM-DreamboxNo errors in the pm2 logs.
On the Mirror I see
ErrorAnd a white line (in the MMM-Dreambox module area).
EDIT: Same behaviour for my Dreambox.
-
@axled said in [MMM-Dreambox] to connect a Dreambox or a Enigma2 Receiver (like VU or VU+) to MagicMirror and stream stations via omxplayer:
to 2: I dont understand at which point you get multiple streams. If no channel was selected before?
In fact I get 2 streams always.
When I send DB-PLAY immediately.
Or when I send DB-PLAY after selecting a service.When I send DB-STOP both streams are stopped.
Most probably due to my 2 tuner box.
I have a 1 tuner VU+ solo, but there we are still debugging to get the services visible at all. -
I did some modification to the dev branch.
Modified/fixed:
- error if used Dreambox-IP with a port
- errors showing up in node_helper.js
Now i can use my dreambox with a different port and the data requests (with defined port) and streaming (with port :8001) works correctly.
Can you please try with your tuners?
AxLED
-
@AxLed
With “apiBase: ‘http://192.168.178.28’”, I get “http:8001”.pi@MagicPi:~/MagicMirror/modules/MMM-Dreambox $ ps -eaf | grep omxplayer | grep -v grep pi 30691 30252 2 23:09 ? 00:00:00 /bin/sh -c omxplayer --vol -6000 --win 0,625,590,957 --live http:8001/1:0:1:2F08:441:1:C00000:0:0:0: pi 30692 30691 0 23:09 ? 00:00:00 /bin/bash /usr/bin/omxplayer --vol -6000 --win 0,625,590,957 --live http:8001/1:0:1:2F08:441:1:C00000:0:0:0:BUT …
With “apiBase: ‘http://192.168.178.28:80’”, I get “http://192.168.178.28:8001” and streaming works.pi@MagicPi:~/MagicMirror/modules/MMM-Dreambox $ ps -eaf | grep omxplayer | grep -v grep pi 31023 30795 0 23:14 ? 00:00:00 /bin/sh -c omxplayer --vol -6000 --win 0,625,590,957 --live http://192.168.178.28:8001/1:0:1:2EF4:441:1:C00000:0:0:0: pi 31024 31023 0 23:14 ? 00:00:00 /bin/bash /usr/bin/omxplayer --vol -6000 --win 0,625,590,957 --live http://192.168.178.28:8001/1:0:1:2EF4:441:1:C00000:0:0:0: pi 31047 31024 7 23:14 ? 00:00:00 /usr/bin/omxplayer.bin --vol -6000 --win 0,625,590,957 --live http://192.168.178.28:8001/1:0:1:2EF4:441:1:C00000:0:0:0:Observations:
Streaming is working.
The first time DB-PLAY: one service only.Changing services is not possible using DB-SERVICE-NEXT.
Stopping with DB-STOP, then DB-SERVICE-NEXT and then DB-PLAY: two streams again.
Got into a situation where DB-PLAY caused my second tuner (what I was seeing on my regular TV) changed channel to the selected service.
The “now playing” line still shows the service from the other tuner, but if you have a single tuner, then it will be difficult to change this.
Perhaps I will find something on this topic.So, I guess that for a single Dreambox tuner everything works fine, but that there are odd behaviours when you have a multiple tuner (a dual tuner in my case).
I would concentrate now on getting it to work for VU+ devices.
If I could, I would help you, but I still fail to see where and how the parsing of the xml data is done. -
- I can fix the “http:8001” problem, if i find some time, so the module works for single tuner dreamboxes again.
- If you use the module (dev branch) with VU+, what happens?
AxLED
-
@AxLed sorry for not being so much available lately, but apart from work and mirror assembly (the ‘baby’ is going to born into the next days if everything goes well… :crossed_fingers_medium-light_skin_tone: ) I see that @evroom is much more skilled and suitable for the debugging. :grimacing_face:
I hope that everything will be sorted soon and thanks @AxLed for taking care into it.
-
@axled said in [MMM-Dreambox] to connect a Dreambox or a Enigma2 Receiver (like VU or VU+) to MagicMirror and stream stations via omxplayer:
f you use the module (dev branch) with VU+, what happens?
I still see ‘Error’ on the Mirror.
No errors in the pm2 logs. -
@cr4z33 said in [MMM-Dreambox] to connect a Dreambox or a Enigma2 Receiver (like VU or VU+) to MagicMirror and stream stations via omxplayer:
I see that @evroom is much more skilled and suitable for the debugging.
Testing is no problem.
It is a pity I cannot help with real debugging.
Oddly enough I do programming for REST api’s on a professional level, but for that I use Perl.
Also puts me off a bit in going deeper into the MMM modules stuff, but I think that applies to more persons (8 hours a day behind the computer at work and sitting being that thing again in you spare time is sometimes too much :-) ).Hope that the ‘baby’ will be a real baby and I wish you and your partner all the best.
MagicMirror version: 2.33.0
Raspberry Pi 4 Model B Rev 1.5 (8 GB RAM)
Raspbian GNU/Linux 12 (bookworm)Test environment:
MagicMirror version: v2.33.0
Raspberry Pi 3 Model B Plus Rev 1.3 (1 GB RAM)
Raspbian GNU/Linux 12 (bookworm) -
I noticed that after ‘Error’ there was a short other message.
I had to set the refresh time to 1 second and to capture numerous time before I could capture 1 error message:Error: null in http://192.168.178.47/web/aboutIt can be that there are more errors or just this one.
I will send you some xml files by mail.
-
@evroom said in [MMM-Dreambox] to connect a Dreambox or a Enigma2 Receiver (like VU or VU+) to MagicMirror and stream stations via omxplayer:
Hope that the ‘baby’ will be a real baby and I wish you and your partner all the best.
Lol no it’s actually my first MM mirror. :face_with_stuck-out_tongue_winking_eye:
If there will be any improvement into getting Vu+ devices to work I will be trying it in a Duo² dual DVB-S / DVB-T tuner decoder.
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login