Hi,
What does pm2 log say?
And do you see omxplayer in the process list ?
$ ps -eaf | grep omxplayer | grep -v grep
Finally, can you see if omxplayer works standalone ?
$ omxplayer --vol -6000 --win "0 0 720 576" --live http://192.168.1.50:8001/1:0:19:2B66:3F3:1:C00000:0:0:0:
Can you try this ?
$ omxplayer --avdict rtsp_transport:tcp --live --video_queue 4 --fps 30 --win "0 0 480 320" rtsp://USER:PASSWORD@ADDRESS/live
To see if it works standalone.
I forgot if a license is needed for the camera stream, but to know if a license is present:
$ vcgencmd codec_enabled MPG2
Btw,
Not all leagues are for free:
https://www.football-data.org/coverage
So, for example DFB and BL2 will not work.
You might need to remove those or comment them (with //).
And you might need this entry:
show: 'GERMANY',
But I am not sure what the connection is between this and the leagues entries.
@mrSnatz said in MMM-Soccer - Soccer Standings:
Do you have any tip
Hi,
Try this:
{
module: 'MMM-soccer',
position: 'bottom_right',
config: {
api_key: 'XXXX129ce6f9XXXXXXXXXXXXXXXXX',
colored: true,
logos: true,
leagues: {
GERMANY: 'BL1',
GERMANY: 'DFB',
GERMANY: 'BL2',
EUROPE: 'CL',
WORLD: 'WC',
},
}
},Hi,
It is my understanding that for $200 you get 28.000 calls (hence monthly $200 credit equivalent free usage).
As you get a monthly free credit of $200, you get those for free.
There is a price calculator link on the site where you can calculate things.
You can put a quota to make sure you will not go over the ‘free’ amount.
The statistics provided are very detailed, so you can monitor your usage very easily.
Sorry, no idea.
You could disable all modules (disabled: true,) and then enable them one by one (disabled: false,) until the issue appears.
But also run cd ~/MagicMirror; npm run config:check to be sure you do not have a config issue.
Perhaps the ATTENTION is not related to the config.
I get the warning too, but MM does start.
There are several hits using google.
Seems to be a Chromium and HTML syntax issue.
Just FYI
Simple test if both API key and place ID are okay using curl.
This returns both name & opening_hours (as it should be):
$ curl "https://maps.googleapis.com/maps/api/place/details/json?fields=name,opening_hours&language=en&placeid=ChIJl7ycbxZYn0cRqZwkVTJ3Rzw&key="API_KEY"
In my case, it returned only the name:
$ curl "https://maps.googleapis.com/maps/api/place/details/json?fields=name,opening_hours&language=en&placeid=ChIJ9SpsbxZYn0cRhBEv4PE_Tvs&key="API_KEY"
Still confused why the place ID from Place Finder seems a bit off.
@htilly said in Opening hours for stores/places thru Google API:
Try this ID instead:
Thanks for spending time on it.
Strange, but it works.
The Place finder really says “ChIJ9SpsbxZYn0cRhBEv4PE_Tvs”, how did you find “ChIJl7ycbxZYn0cRqZwkVTJ3Rzw” ??
Rebooted.
No change.
I do get this error:
0|mm | [5:13:03 PM] - MMM-OpeningHours : Starting helper: MMM-OpeningHours
0|mm | Sockets connected & modules started ...
0|mm | Launching application.
0|mm | (node:2342) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 1): TypeError: Cannot read property 'refs' of undefined
0|mm | (node:2342) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
I suppose the API key is right, as it finds the (street)name.
And it increases the usage counter for Google Places for my account.
But no opening times.
On Google Maps opening times are visible for this ID.
0|mm | json:
0|mm | { html_attributions: [],
0|mm | result: { name: 'Laufamholzstraße 76' },
0|mm | status: 'OK' },
0|mm | requestUrl: 'https://maps.googleapis.com/maps/api/place/details/json?fields=name%2Copening_hours&language=en&placeid=ChIJ9SpsbxZYn0cRhBEv4PE_Tvs&key=',
0|mm | query:
0|mm | { fields: 'name,opening_hours',
0|mm | language: 'en',
0|mm | placeid: 'ChIJ9SpsbxZYn0cRhBEv4PE_Tvs',
0|mm | key: '' } }
And I do not see a mapping between place id, street name and the name of the place.