Please only submit reproducible issues to GitHub.
If you’re not sure if it’s a real bug or if it’s just you, please open a topic on the forum: https://forum.magicmirror.builders/category/15/bug-hunt - Problems installing or configuring your MagicMirror? Check out: https://forum.magicmirror.builders/category/10/troubleshooting
When submitting a new issue, please supply the following information:
Platform [ Raspberry Pi 2/3, Windows, Mac OS X, Linux, Etc … ]:
Node Version [ 0.12.13 or later ]:
MagicMirror Version [ V1 / V2-Beta ]:
Description: Provide a detailed description about the issue and include specific details to help us understand the problem. Adding screenshots will help describing the problem.
Steps to Reproduce: List the step by step process to reproduce the issue.
Expected Results: Describe what you expected to see.
Actual Results: Describe what you actually saw.
Configuration: What does the used config.js file look like? (Don’t forget to remove any sensitive information.)
Additional Notes: Provide any other relevant notes not previously mentioned (optional)
@richland007 said in Spotify Play?:
First you have to have a premium Spotify account to play outside authorized Spotify devices
Re: Spotify Play?
you need to First have a premium Spotify account to play outside authorized Spotify devices !!
At first glance, I think you forgot to run the npm install in the proper directory during the upgrade. Try this:
pm2 stop all
The npm install command will take a while to run, so be patient. Let us know how it goes.
Sorry it’s in french but that can help you to test your sensor out of the magicmirror app directly in python
thanks for your reply.
This cache management header is only used for the local caching of any (wget) download. If you set the above header in the fetcher script it isn’t using any local caching mechanism and requests a fresh file download from the web server every time it’s triggered.
I’ve to investigate a bit more also to the fact that I’m using a caching proxy server inside my LAN. On the RPi I disabled proxy usage for local addresses, but it seems maybe something isn’t working correctly here.
The .ics file (calendar export from Lotus Domino client) has the same structure like other files (eg. from MS Outlook or Thunderbird). So, I guess this isn’t really a calendar file problem as more an OS related issue.
If I download this file from the web server with ‘wget’ on my RPi, I’m getting the same file version every time I try to download even if it has changed or not. If I manipulate the HTTP-header which wget is using, the download is working as expected. (see http://xmodulo.com/how-to-use-custom-http-headers-with-wget.html for example). Some about cache management can be found here: http://dev.mobify.com/blog/beginners-guide-to-http-cache-headers/
Currently I’m at work, but I’ll try to figure it out today evening. I’ll update this post with my findings.
I’ve noticed recently that the new weather module in the develop branch stops updating. I got this error in the developer console:
2cors-anywhere.herokuapp.com/https://api.darksky.net/forecast/mykey/mylatlong?units=us&lang=en Failed to load resource: the server responded with a status of 503 (Service Unavailable)
0.0.0.0/:1 Failed to load https://cors-anywhere.herokuapp.com/https://api.darksky.net/forecast/mykey/mylatlong?units=us&lang=en: No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'http://0.0.0.0:8080' is therefore not allowed access. The response had HTTP status code 503.
If the service is unavailable shouldn’t the weather module update once it is available?
If I restart MM, the module will update properly and work for about a day.
mi problem is that i changed the default port to 8089, but using the remote module, the displayed port is 8080, but in any way i can’t connect to the magic mirror on the 8089 port, neither on the 8080 port…so, what’s wrong? Thank for any response.
@soccer19 said in Location ID:
in the config.js or the weather.js>?
In the config.js for your weatherforecast entry. If you have a header set with a location you would have to change that as well
position: "top_right", // This can be any of the regions.
location: "New York, US", // Change this to your location
locationID: "Your location ID", // Your Location ID from http://openweathermap.org/help/city_list.txt
appid: "Your API Key" //openweathermap.org API key.
It is not recommended that you change anything in the module.js files
when i start with npm start dev.
I see the following error.
InvalidValueError: unknown property orgin js:51:110
Jc https://maps.googleapis.com/maps/api/js?key=API KEYc:51
Lc https://maps.googleapis.com/maps/api/js?key=API KEY:51
route https://maps.googleapis.com/maps/api/js?key=API KEY:196
The MM does show the correct part of the road map I have selected.
I also have MMM-Route enabled with the same API.
key: “API Key”,
key: “API KEY”,