MMM-MplayerRadio

[wishmaster270]

Hi,

as i wrote in the documentation you need to make sure that your script runs as long as the station is active and needs to stop the playback if it gets a kill signal.
Maybe i will find a short tutorial about catching the kill signal.

[wishmaster270]

If you change your script to (playRadio.bash):

#!/bin/bash
URL=$1
RUN=1
exit_script() {
        echo "Stopping playback"
        xmms2 stop
        xmms2 clear
        RUN=0
}

trap exit_script SIGINT SIGTERM

xmms2 stop
xmms2 clear
xmms2 add $URL
xmms2 play

while [ $RUN -gt 0 ]; do
        echo "Still running"
        sleep 1
done

and the config to

		{
			module: "MMM-MplayerRadio",
			header: "Radio",
			position: "top_center",
			config: {
				stations: [
					{
						title: "KissFM",
						url: "https://live.kissfm.ro/kissfm.aacp",
						logo: "https://upload.wikimedia.org/wikipedia/ro/8/86/Logo_Kiss_FM.png",
						customCommand: "/home/pi/MagicMirror/modules/MMM-MplayerRadio/scripts/playRadio.bash",
						customCommandArgs: ["###URL###"],
					},
				],
			},
		},

You can then reuse the same script for different stations only by adding the url as first parameter in the config

Edit: Added url back to the config

[electros]

@wishmaster270 it’s working now thanks.

[wishmaster270]

@electros Perfect.
I think I will check in the script into the repository so you can easy update to upcoming versions

[electros]

@wishmaster270 Thank you

[bryan_1]

@wishmaster270 Hi, I’m newbie and know almost nothing about coding. I have installed your module successfully, but what should I do to start it (without touchscreen)? It is shown on my mirror but not played. I put only one Station.
I want to start it automatically if I start my mirror.
Thanks.

[wishmaster270]

@bryan_1 Hi, currently there is no autoplay feature implemented. But I will check it the next days. Maybe it is not a big deal

[wishmaster270]

Hi,

just published an new version (0.0.3) which provides an autoplay feature. Simply add the station index you want to play to the config option “autoplay”. If you only configured one station it is 0. The station will start to play after about 1 second after the mirror started.

[A Former User]

hi @wishmaster270 ,

if you want me to create a vocal control with MMM-GoogleAssistant, just tell me.
I can create a special sub-code for your module

can do:

• volume control (no api found)
• change stations (next/previous/play/toogle,etc) from your api

[wishmaster270]

@Bugsounet Hi, great idea. At the moment my mirror is only controlled by sensors and touch.
The volume control buttons of my module only send an notification to MMM-Volume that’s way there isn’t any api in this module.
Everything else can be controlled by notifications. There is a small section about the notifications in the readme.

[bryan_1]

@wishmaster270 wow, vielen Dank :folded_hands:

[A Former User]

@wishmaster270 said in MMM-MplayerRadio:

The volume control buttons of my module only send an notification to MMM-Volume that’s way there isn’t any api in this module

ok so not needed because GA/A2D have native this function (volume control in vocal)
I can create quiclky an sample by I don’t know if you use my module

Edit:

the problem is I can’t send real name of the radio (it’s different with the google Server response)
so i will code :

SAY To GoogleAssistant	NOTIFICATION Sended to MMM-MplayerRadio	Function
Radio play	RADIO_PLAY	Playing first station
Radio stop	RADIO_STOP	Stop radio
Radio Next	RADIO_NEXT	Next Station
Radio Previous	RADIO_PREVIOUS	Previous Station

Of course all user can change you prefered ‘sentence’ for activate each wanted control

Edit 2:

[ASSISTANT] Command RADIO_PLAY is executed (notificationExec).
MMM-NotificationReceived.js:20 [Notification Sended From][MMM-GoogleAssistant] RADIO_PLAY {}

[ASSISTANT] Command RADIO_STOP is executed (notificationExec).
MMM-NotificationReceived.js:20 [Notification Sended From][MMM-GoogleAssistant] RADIO_STOP {}

[ASSISTANT] Command RADIO_PREVIOUS is executed (notificationExec).
MMM-NotificationReceived.js:20 [Notification Sended From][MMM-GoogleAssistant] RADIO_PREVIOUS {}

[ASSISTANT] Command RADIO_NEXT is executed (notificationExec).
MMM-NotificationReceived.js:20 [Notification Sended From][MMM-GoogleAssistant] RADIO_NEXT {}

Tell me if ok, in all case notification are sended.
sample of syntax used for send : this.sendNotification("RADIO_STOP")

For volume:
Vocal Control already coded with GA/A2D : volume 100% for exemple
make RPI volume to 100%
So don’t worry about this :)

Notes:
GA: MMM-GoogleAssistant
A2D: MMM-Assistant2Display
too long to write lol !

Sub-Code (recipe) is coded and commit in my dev branch

if some users want to test it

@bugsounet

[wishmaster270]

@Bugsounet Hi, thank you for your work. I checked the code, your notifications should work as planned. Play will start with the last station played or with the first one initially.

[robfer]

Hi!

my second post :)
I’ve lost my first one somewhere , sorry if you read twice :) :)

I’ve raspberry with AIY voice module , magic mirror software and a little touchscreen

the touchscreen works good ( in the lego cabinet) with touch software like MMM-ModuleBar
but I can’t use the buttons below the MMM-MplayerRadio , they seems dosn’t work or send notification

the MplayerRadio module is working , and I really like hear the music from the module but i want to use the touch buttons too 😃

i’ve used the “/etc/asound.conf” of your hints and the radio plays ok (with the “Pulse” configuration) but only if the trick below:

I put the option DisplayStatioOnStartup: true and I click on the suggested radio

(with this option = false, the radio dosn’t start or I cannot go in the menu with the radio display list)

I’ve also installed MMM-Volume module too, but the volume button I suppose have the same problem of previous , play and next buttons

Do you have any advice or hints or config example ?

thanks for reading
Roberto

[wishmaster270]

@robfer Hi, normally there is some other module covering the buttons in such cases.
You can solve this by setting z-index in your custom.css.
The higher the index the more in the foreground the module will be.

The following config is part of my custom.css file:

.MMM-ImagesPhotos, .MMM-ImageSlideshow, .MMM-COVID19, .MMM-Spotify, .MMM-Temperature, .MMM-LEDStripControl {
    z-index: -1;
}

.MMM-MplayerRadio {
    z-index: 999;
}

[robfer]

@wishmaster270
thanks,
you was right, the module newsfeed cover the buttons on my little screen

hiding and showing it solve my problem, now i can use the radio and the volume buttons too :)

maybe without use the custom.css
but in this case a little extra question, if you know: can I put standard module newsfeed in the custom.css file? (I tryed but seems not work)

[wishmaster270]

@robfer Hi, sure you can. The right class will be “.module.newsfeed”

[totofar]

Hi,

@bugsounet created notifications/patterns in his module MMM-GoogleAssistant to drive this module MMM-MplayerRadio.
Did anyone manage to implement these commands in GoogleAssistant ? How does it work ?

Thanks in advance

[totofar]

Found the solution…

FYI, for newbies like me…
If you want to use MMM-GoogleAssistant to command MMM-MplayerRadio, just use the recipe installed by default with GA.
To setup this function, just setup that way in config.js

	{
		  module: "MMM-GoogleAssistant",
		  position: "fullscreen_above",
		  config: {
			recipes: [
			  "Reboot-Restart-Shutdown.js", "MMM-MplayerRadio.js", 
			],
			debug: true,
			assistantConfig: {...

Then MPlayerRadio will be driven with the voice “Jarvis radio play”, “Jarvis radio next”, …

++