@evroom said in [MMM-Dreambox] to connect a Dreambox or a Enigma2 Receiver (like VU or VU+) to MagicMirror and stream stations via omxplayer:
Error: null in http://192.168.178.47/web/about
I checked with some of the files you send me (all different 3 VU+ about xmls), the work in my environment. Is your VU+ maybe also in standby mode?
AxLED
@evroom
I never tried my module in dreambox standby, as i dont use it. My dreambox is on or in deep standby.
Can you please try with your receivers (Dreambox or VU) on?
AxLED
I did some furter bugfixing:
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.git in your modules folder
Now the module should work with dreambox, no matter if the dreambox uses a separat port or not.
Regards
AxLED
@filmschooljefe
If you pc is windows, you can also activate SMB on the Pi ans Edit files in you Windows Machine.
AxLED
I did some modification to the dev branch.
Modified/fixed:
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
@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 a update.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
@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
Answer to the 5 errors in node_helper.js:
I comment the lines out, please try again with the dev branch.
AxLED
I did some bugfixing:
Please check the dev branch of my module:
git clone --branch dev https://github.com/Ax-LED/MMM-Dreambox.git in your modules folderTell me what happens now, if you try to connect to VU+ receiver.
Regards
AxLED
@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
@evroom
So i can fix the handling of an “empty” timerlist meanwhile, but this will take until the end of the week.
I am looking forward to hear from you if your DLAN adoptor is back online.
AxLED
@evroom
Thanks for the files, i tested with your files, but i am getting a different error:
Your error (some topics above): Problem at servicelistplayable
My error (with your VU xml files): Problem in MMM-Dreambox.js at line 387, where the timerlist expects a value. I can fix this error, somehow my code expects at least one timer.
Can you please tell me, at which point/line of code you get an error?
If your error is in MMM-Dreambox.js at line 387 can you try to add one timer in the future an test again?
AxLED
@evroom
To answer your questions:
I have some questions too:
So i can check what is going wrong.
AxLED
Can you please post your config for MMM-Dreambox (as i guess there are two problems):
apiBase:
omxargs:
refreshInterval:
apiabout:
apiservices:
apiepgnow:
apizap:
apiTimerlist:
apiServicelistplayable:
apibouquet: 0, //bouquet, if there is more than one under apiservices (/web/getallservices), important apiepgnow and apiServicelistplayable have to match to the selected bouquet
listmax:
AxLED
Some ideas:
Start streaming takes up to 15 seconds, did you wait long enough?
Are you streaming SD or HD channels? HD needs mpg license.
Is the play symbol (triangle) shown after sending the command DB-PLAY?
AxLED
Not every URL is displayable as iframe, Google is one of them. Try another URL.
AxLED
@Skorpionbird
I am not sure if the code mentioned above works, i just saw you have an node problem, my problem was a electron problem.
AxLED
I had a similar problem once with anoter module, this helped
#Change into the modules directory
cd modules/MMM-Hover
# Rebuild module for the correct elecron version
npm rebuild --runtime=electron --target=$(../../node_modules/electron/cli.js --version) --disturl=https://atom.io/download/atom-shell --build-from-source
AxLED
@robiv8
I guess i found the solution of your problem, it is the combination of MMM-Page-Selector and MMM-Podcast2 the way you used it in your config.js
Details see MMM-Podcast2/issues
AxLED