teslaSeer, plugin using tesla motors "API"

[Overst]

Current (amps) settings (all of them) need to have their range changed. 220 v wall charger uses 72Amp. I changed settings to 1-100 and it worked great.

[NetworkGuy]

Current (amps) settings (all of them) need to have their range changed. 220 v wall charger uses 72Amp. I changed settings to 1-100 and it worked great.

Wow, 72 amp - really? That's super high. I would expect 40 or 50 amp max. That's a lot more than I would expect.

[salvesen]

Version on first page appears to be the same version I loaded last weekend?

I tried it anyway and grew another set of devices again. Plugin reports as same version 1.0.0.1

Thats strange, I thought I updated it. Anyways, put out the latest that I have running at my place now with some changes. Try that one.

By the way, if you did not delete the old devices from previous versions a new set will be added, after that no new sets will be made.

[salvesen]

Current (amps) settings (all of them) need to have their range changed. 220 v wall charger uses 72Amp. I changed settings to 1-100 and it worked great.

Thanks for the heads up! I am at a slow 10A myself :P But you are right, I guess that is about max for home charging. I will edit the device in next version.

[NotYetRated]

Updated to latest posted version and am getting the following error in logs along with no updates to my teslaseer items:

r

Posting back to plugin web page teslaSeerConfig: Index was outside the bounds of the array.-> Server stack trace: Exception rethrown at [0]: at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessag e(IMessage reqMsg, IMessage retMsg) at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(Mess ageData& msgData, Int32 type) at HomeSeerAPI.IPlugInAPI.PostBackProc(String page, String data, String user, Int32 userRights) at Scheduler.proxyPage.postBackProc(StateObject& state, String Data)

Oct-12 11:40:47 AM

tesla debug

Response from getAccessToken: failed to get response, contact plugin developer

Oct-12 11:40:47 AM

error

Error: The remote server returned an error: (500) Internal Server Error.

[salvesen]

Updated to latest posted version and am getting the following error in logs along with no updates to my teslaseer items:

r

Posting back to plugin web page teslaSeerConfig: Index was outside the bounds of the array.-> Server stack trace: Exception rethrown at [0]: at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessag e(IMessage reqMsg, IMessage retMsg) at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(Mess ageData& msgData, Int32 type) at HomeSeerAPI.IPlugInAPI.PostBackProc(String page, String data, String user, Int32 userRights) at Scheduler.proxyPage.postBackProc(StateObject& state, String Data)

Oct-12 11:40:47 AM

tesla debug

Response from getAccessToken: failed to get response, contact plugin developer

Oct-12 11:40:47 AM

error

Error: The remote server returned an error: (500) Internal Server Error.

Hm, the 500 is normal. Can just be no access to the servers. But that stack trace there is not good. Can you turn on debug and try again, if possible

And please, remove all old devices before installing new version.

[bsobel]

Thanks for the heads up! I am at a slow 10A myself :P But you are right, I guess that is about max for home charging. I will edit the device in next version.

80 amps is the current home max for cars with the high amperage charger. I actually have one 100amp charger (so at 80% its 80 amps), the rest are 60amp ones.
FYI

[will40]

It is fixed yes, new version on first page.

Could you go to config and enable debug information and send me the dumps that comes directly from tesla? it will be vehicleresponse if i remember correctly.

Is this the dump you wanted regarding the GPS coordinates not getting updated in my devices? I am scraping the teslavariables.ini file for the coordinates and pasting as devicestring in my virtual devices for the time being. If it can work with your plugin to report as values instead would be much more elegant and useful for me. Thanks

Oct-12 4:43:01 PM tesla debug Response from driveState: {"response":"shift_state":"D","speed":24,"power":35,"lati tud e":42.803144,"longitude":-71.995996,"heading":113,"gps_as_of":1539376984,"native_locat ion_supported":1,"native_latitude":42.803144,"native_longitu de":-71.995996,"native_type":"wgs","timestamp":1539376986349}}

and P.S. the duplicate devices is now thing of the past, thanks

[salvesen]

Is this the dump you wanted regarding the GPS coordinates not getting updated in my devices? I am scraping the teslavariables.ini file for the coordinates and pasting as devicestring in my virtual devices for the time being. If it can work with your plugin to report as values instead would be much more elegant and useful for me. Thanks

Oct-12 4:43:01 PM tesla debug Response from driveState: {"response":"shift_state":"D","speed":24,"power":35,"lati tud e":42.803144,"longitude":-71.995996,"heading":113,"gps_as_of":1539376984,"native_locat ion_supported":1,"native_latitude":42.803144,"native_longitu de":-71.995996,"native_type":"wgs","timestamp":1539376986349}}

and P.S. the duplicate devices is now thing of the past, thanks

thank you for the information, unfortunally everything looks normal so I am not sure what is going on. I will check some more later on. Both of your long/lat is displaying 0 in the device information right?

[will40]

thank you for the information, unfortunally everything looks normal so I am not sure what is going on. I will check some more later on. Both of your long/lat is displaying 0 in the device information right?

yes both are reporting 0

[shill]

Never mind, I found it hidden under the image Doh!

[NotYetRated]

I am still getting the following issue, and nothing is updating.

Nov-20 10:59:53 AM

tesla debug

Response from chargeState: failed to get response, contact plugin developer

Nov-20 10:59:53 AM

error

Error: The remote server returned an error: (408) Request Timeout.

Nov-20 10:59:53 AM

tesla debug

Response from climateSettings: failed to get response, contact plugin developer

Nov-20 10:59:53 AM

error

Error: The remote server returned an error: (408) Request Timeout.

Nov-20 10:59:53 AM

tesla debug

Response from driveState: failed to get response, contact plugin developer

Nov-20 10:59:53 AM

error

Error: The remote server returned an error: (408) Request Timeout.

Nov-20 10:59:53 AM

tesla debug

Response from guiSettings: failed to get response, contact plugin developer

Nov-20 10:59:53 AM

error

Error: The remote server returned an error: (408) Request Timeout.

Nov-20 10:59:53 AM

tesla debug

Response from vehicleState: failed to get response, contact plugin developer

Nov-20 10:59:53 AM

error

Error: The remote server returned an error: (408) Request Timeout.

Nov-20 10:59:53 AM

tesla debug

Response from chargeState: failed to get response, contact plugin developer

Nov-20 10:59:53 AM

error

Error: The remote server returned an error: (408) Request Timeout.

Nov-20 10:59:52 AM

tesla debug

Response from climateSettings: failed to get response, contact plugin developer

Nov-20 10:59:52 AM

error

Error: The remote server returned an error: (408) Request Timeout.

Nov-20 10:59:52 AM

tesla debug

Response from driveState: failed to get response, contact plugin developer

Nov-20 10:59:52 AM

error

Error: The remote server returned an error: (408) Request Timeout.

Nov-20 10:59:52 AM

tesla debug

Response from guiSettings: failed to get response, contact plugin developer

Nov-20 10:59:52 AM

error

Error: The remote server returned an error: (408) Request Timeout.

Nov-20 10:59:52 AM

tesla debug

Response from vehicleState: failed to get response, contact plugin developer

Nov-20 10:59:52 AM

error

Error: The remote server returned an error: (408) Request Timeout.

I have tried uninstalling plugin by deleting everything in the folder, deleting the created devices and readding the files. I did successfully get my token when i input the name and password.

[will40]

I saw the same as you. I got that error as the car was sleeping. I don't use the PI settings interval to ping the car.

I created an event to wake up then update and it works fine. Try this out and see if it works for you.

I get this HS log error on wake up command but it works fine. Maybe the author can silence this error? "Calling SetIOMulti in plugin teslaSeer:Index was outside the bounds of the array"

[NotYetRated]

I saw the same as you. I got that error as the car was sleeping. I don't use the PI settings interval to ping the car.

I created an event to wake up then update and it works fine. Try this out and see if it works for you.

I get this HS log error on wake up command but it works fine. Maybe the author can silence this error? "Calling SetIOMulti in plugin teslaSeer:Index was outside the bounds of the array"

Thanks for the comment! However that doesn't seem to have fixed it for me. I tried removing plugin. Deleting devices/ Deleting tesla.ini files. Restarting Homeseer. Readding plugin files, starting plugin, adding my credentials. Still get no updates. It does however successfully see my car when i get a token, as it pulls my VIN into the log. I am seeing this error now on my plugins page

"WARNING: Failed getting InterfaceStatus from teslaSeer - the interface was not found in the list of active interfaces, the list may need to be refreshed."

And the following in my log when restarting the plugin:

Nov-21 2:40:39 PM

Error

Initializing plug-in(2): teslaSeer Instance::Index was outside the bounds of the array.STACK: Server stack trace: Exception rethrown at [0]: at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessag e(IMessage reqMsg, IMessage retMsg) at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(Mess ageData& msgData, Int32 type) at HomeSeerAPI.IPlugInAPI.InitIO(String port) at Scheduler.clsHSPI.CheckInterfaces()

Nov-21 2:40:39 PM

tesla debug

Response from vehicleState: {"response":{"api_version":4,"autopark_state_v3":"ready","au topark_style":"dead_man","calendar_supported":true,"car_vers ion":"2018.42.3 eb373a0","center_display_state":0,"df":0,"dr":0,"ft":0,"home link_nearby":false,"is_user_present":false,"last_autopark_er ror":"no_error","locked":true,"media_state":{"remote_control _enabled":true},"notifications_supported":true,"odometer":10 47.667919,"parsed_calendar_supported":true,"pf":0,"pr":0,"re mote_start":false,"remote_start_supported":true,"rt":0,"soft ware_update":{"expected_duration_sec":2700,"status":""},"spe ed_limit_mode":{"active":false,"current_limit_mph":90.0,"max _limit_mph":90,"min_limit_mph":50,"pin_code_set":false},"sun _roof_percent_open":null,"sun_roof_state":"unknown","timesta mp":1542829237936,"valet_mode":false,"valet_pin_needed":true ,"vehicle_name":"Life, the Universe, and Everything"}}

Nov-21 2:40:39 PM

tesla debug

Response from getVehicleList: {"response":[{"id":XX,"vehicle_id":XX,"vin":"XX","display_name":"Life, the Universe, and Everything","option_codes":"AD15,MDL3,PBSB,RENA,BT37,ID3W,RF 3G,S3PB,DRLH,DV2W,W39B,APF0,COUS,BC3B,CH07,PC30,FC3P,FG31,GL FR,HL31,HM31,IL31,LTPB,MR31,FM3B,RS3H,SA3P,STCP,SC04,SU3C,T3 CA,TW00,TM00,UT3P,WR00,AU3P,APH3,AF00,ZCST,MI00,CDM0","color ":null,"tokens":["faf978de3410d02b","fe21bad4c7303f8b"],"state":"online","in_service":false,"id_s":"431761609616405 79","calendar_enabled":true,"api_version":4,"backseat_token" :null,"backseat_token_updated_at":null}],"count":1}

Nov-21 2:40:38 PM

tesla debug

Response from getAccessToken: {"access_token":"XX","token_type":"bearer","expires_in":3888 000,"refresh_token":"XX","created_at":1542829239}

Nov-21 2:40:36 PM

Warning

Attempt by plugin to register a duplicate link of teslaSeerConfig. Plugin: teslaSeer Instance:

[will40]

Sorry I can't help you beyond that nasty looking error you are getting. Just curious when you mention it sees your car. Is your teslaSeerVariables.ini file logging your car's current variables, such as-now car temp, mileage, LAT-LON, etc? Maybe you can narrow this down to an issue with the plug-in not populating your Homeseer devices?

I could never get the PI to populate LAT, LON, and Mileage on my HS3 device page so I execute a simple parsing script to scrape the teslaSeerVariables.ini file for those particular line items and push them to the Teslaseer Homeseer devices.

I attached if it helps you troubleshoot until the author chimes in.

Will

HS3parse teslaVAR file.txt