Trouble with config file, Error Create Config File

cowboysdude

Yes you must do a cp to have a config.js to start with BUT before you make changes ALWAYS have a backup that works… ALWAYS.

IF you’re not sure and you’re having config.js problems run it through here …

http://esprima.org/demo/validate.html

It will tell you where your errors are… I mean it’s nice of people to fix things but if you’re working on this at 2AM and nobody is here… you’re not getting your mirror to work until the next day ;)

twosix

@Mykle1 I did the same, I fired up the sample config and it worked fine, but then after I put my stuff in, it gave me the “WARNING? Could not validate config file. Please correct syntax errors. Starting with default configuration.”

And then when I loads up it says, “Please create config file.”

twosix

@cowboysdude Thank you, I ran that through my code and there appears to be no problems…I just can’t figure out what the problem is…I boot the mirror up normally by going:

cd Magic Mirror
npm start

and then I get the “WARNING? Could not validate config file. Please correct syntax errors. Starting with default configuration.”

and then when it loads the “Please create config file.”

twosix

@bhepler Thank you! I did this and it reset my config file, and that booted up fine, but when I put my information in, and started it:
cd MagicMirror
npm start

I got the "WARNING? Could not validate config file. Please correct syntax errors. Starting with default configuration.”

Then load it said “Please create config file.”

Mykle1

@twosix said in Trouble with config file, Error Create Config File:

it worked fine, but then after I put my stuff in
Please correct syntax errors.

If the default config works then this should be telling you that you are not making config entries correctly. Start again from the default config, making sure it runs, then add one module at a time, making sure it still works after each entry, then backing up your config each time you successfully add a module. I don’t know what else to offer you. I fixed your first config and tested it.

twosix

@Mykle1 Okay I did that, and figured out the problem is my calendar…is there anyway I can fix that?

strawberry 3.141

@twosix in all your examples you’re escaping the closing quote

{
  symbol: "calendar-check-o ",
  url: "webcal://p55-calendars.icloud.com/published/2/TDWYwJjbv2BpM3HLxxxxxxxxxxxxxxxxxvZM-3TNpXNgZXsi192SI7M6pxxxxxxxxxxxxxxxxxxxxxxxXZCkcApre7Kg\"
}

you can see there that the next line is green which indicates that the string isn’t closed there probably. This happen because of the \ right in front of the quote character.

If the backslash doesn’t belong to your string remove it, if you need the backslash you have to escape the backslash by adding a second. like this:

{
  symbol: "calendar-check-o ",
  url: "webcal://p55-calendars.icloud.com/published/2/TDWYwJjbv2BpM3HLxxxxxxxxxxxxxxxxxvZM-3TNpXNgZXsi192SI7M6pxxxxxxxxxxxxxxxxxxxxxxxXZCkcApre7Kg\\"
}

here you can see that the closing curly brace is no longer highlighted in green because the string is closed properly.