You should probably fix that, but that doesn't seem to be it.
Then maybe the BASE URL in your config.json?
{
"username": "[email protected]",
"password": "SuPERS3cr3t",
"visualize": {
"baseUrl" : "",
"webusers": [
{ "id": 1, "username": "hans", "password": "hans" },
{ "id": 2, "username": "bob", "password": "bob" }
]
},
"awsiot" : {
"keyPath" : "/Users/hans/.teslams/somePrivateKey.pem",
"certPath" : "/Users/hans/.teslams/someCert.pem",
"caPath" : "/Users/hans/.teslams/someRootCA.pem",
"clientId" : "MYAWSCLIENTID",
"region" : "us-east-1"
}
}I'll double check when I can get back to the computer, but I don't think so because when I removed the / in the command line it no longer showed the double slash in the error message, but the rest of the error remained the same.
{
"_id" : ObjectId("568b23f6c147a4e4683cd01d"),
"ts" : 1451959286915,
"vehicles" : {
"color" : null,
"display_name" : "Tessie",
"id" : {
"s" : 1,
"e" : 16,
"c" : [
2,
0,
3,
6,
8,
9,
1,
8,
2,
x,
x,
x,
x,
x,
x,
x
]
},
"option_codes" : "MS01,RENA,TM02,DRLH,PF01,BT85,PPSR,RFPO,WT21,IDCF,IZMB,TR01,SU01,SC01,TP01,AU01,CH01,HP01,PA00,PS01,AD02,X001,X003,X007,X011,X013,X024,X019,COUS",
"vehicle_id" : 296xxxxxx,
"vin" : "5YJxxxxxxxxxxxxxx",
"tokens" : [
"ca9aba1fffxxxxxx",
"be738567a1xxxxxx"
],
"state" : "online",
"id_s" : "20368918261xxxxxx",
"remote_start_enabled" : true,
"calendar_enabled" : true,
"notifications_enabled" : true,
"backseat_token" : null,
"backseat_token_updated_at" : null
}
}The strange data in the 'id' field is just a workaround for the fact that Tesla made the new IDs larger than JavaScript can parse natively as JSON so I had to use a special encoding called bigInt. It's still valid javascript, just not as human readable. If you want the easy to read version see the id_s field which is the same number as a string.
I messed with the firmware stuff to make it display more versions correctly, maybe I messed something up on the unknown ones? (should still give the build number even if it doesn't know v7.0 or v7.1) (what build do you have?)
It displays this way if the REST request for the data fail at startup. Usually if you quit and try again it works. I can have the code check for failed requests and try again. Really wish Tesla's APIs were more reliable.
Are you saying it defaults to metric if unknown? if it fails that would be better as "unknown" then as the wrong one...
That's unfortunate... it confirms that Tesla has an incredibly annoyingly convoluted way of presenting such things in the options stream, and that there is quite a lot of variety in how they chose to label it.
module.js:340
throw err;
^
Error: Cannot find module 'mqtt'
at Function.Module._resolveFilename (module.js:338:15)
at Function.Module._load (module.js:280:25)
at Module.require (module.js:364:17)
at require (module.js:380:17)
at Object.<anonymous> (/usr/local/lib/node_modules/teslams/examples/streaming.js:12:12)
at Module._compile (module.js:456:26)
at Object.Module._extensions..js (module.js:474:10)
at Module.load (module.js:356:32)
at Function.Module._load (module.js:312:12)
at Function.Module.runMain (module.js:497:10)
