Hello @GmdSaanen,
That json you posted double quotes are not ASCII (decimal 32) double quotes, but alternative UTF-8 variations of double quotes and therefore that is not valid json format.
Quick way to check with pythion3 command that your json is fine is below. I should not show any errors and show a pretty printed your json.
$ python3 -mjson.tool < GmdSaanen.json
Expecting value: line 1 column 1 (char 0)
$
But unfortunately it just reveals first error location and doesn’t show you clearly what to fix. So when I had years ago this kind of issue, I found SO post which had nifty check and which I then used bit later wrote tiny script so that it’s bit easier to use and remember by name. I’ll attach it here below, but first I attach as an image.
So there is what you need to fix at source where you get that json. You need to change right leaning “ to " which are more straight standing ASCII 32 original double quotes.
You may find using Google “utf-8 alternative doube quotes” more variants and info if you like to know about what this double quote mess is all about.
I have no way to know where from your json data got those wrong UTF-8 alternative double quotes, but you are not first to encounter same issue. I suspect that some general text editors and perhaps browsers too prefer UTF-8 variants certain locale (language, country) setting by default. Developement IDE’s and editors specifically for programming AFAIK not.
OK, so here is the script promised, it works both recent modern Linux and macOS, but cannot work under RutOS cli mode, as there grep command is a busybox stripped down version which do not support colors.
show-nonascii.zip (381 Bytes)
riku
ps.. I replied last February similar kind of issues where you can perhaps find bit more about json debugging if that interests you.