Panda88 Posted October 21, 2022 Posted October 21, 2022 Just released 0.2.6 - some new functionality - A reboot of IoP is probably needed to enable all
garybixler Posted October 24, 2022 Posted October 24, 2022 @Panda88Hi, I installed the latest version 0.2.5. All looked good and I see the additional functionality without having to reboot iop. The only thing that I see that isn't correct is the 'Estimated Range'. For example it shows 222 miles but should only be 135. I did find what is received down from the Tesla Server. 'est_battery_range': 135.77, which would be correct. Also when I plugged in the charger the info was immediately feed into the NS without the need for any action like wake or update and continues to update without polling. Nice. I have the long poll set for 1 day as not to keep the car awake. The short poll is set for 300. Is it possible that the short poll just polls the Tesla server rather than the car itself? Great additions. Thanks Gary
Panda88 Posted October 24, 2022 Author Posted October 24, 2022 The range is a bug - I converted the miles to km for both miles and km - 0.2.7 is released The short poll currently supposed to check if car is on-line - if it is, it will poll car data - if not, it will use the cloud data without waking the car - Naturally this I what I believe the car is doing - There may be a bug. Naturally, I could use cloud data only - but then there is likely some delay - even when car is online (I have no way to check this as I do not have access to car) I would imagine plugging the charger in would wake the car - I am not sure
garybixler Posted October 24, 2022 Posted October 24, 2022 After starting charging it went online so short polling at that time is probably the case. Polling as is I think works the best. I didn't realize short poll worked that way. 0.2.7 corrected mileage. Thanks
garybixler Posted October 26, 2022 Posted October 26, 2022 @Panda88 I think the wrong parameter is showing for estimated range in miles. I found two parameters in the download from tesla. 'battery_range': 123.08 which is correct according to app and the car and 'est_battery_range': 167.12 which is displayed in the AC. I can't figure what the 'est_battery_range' is referring to. Thanks
Panda88 Posted October 26, 2022 Author Posted October 26, 2022 Thanks - I can update the app to use 'battery_range' Should not take long - look for 0.2.8 shortly 1 1
garybixler Posted October 27, 2022 Posted October 27, 2022 (edited) I finally noticed what happens when the tesla goes to sleep. I was wondering if this event could be shown as EV Online False on the AC. Would be a nice way to know if a wake command may be necessary or just generally knowing if the car is asleep.. Thanks so much. 2022-10-26 23:19:17,680 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING shortPoll 2022-10-26 23:19:17,681 Thread-92 udi_interface DEBUG TeslaEVController:systemPoll: systemPoll 2022-10-26 23:19:17,683 Thread-92 udi_interface INFO TeslaEVController:shortPoll: Tesla EV Controller shortPoll(HeartBeat) 2022-10-26 23:19:17,683 Thread-92 udi_interface DEBUG TeslaEVController:heartbeat: heartbeat: 1 2022-10-26 23:19:17,684 Thread-92 udi_interface.interface DEBUG interface:send: PUBLISHING {'command': [{'address': 'controller', 'cmd': 'DOF'}]} 2022-10-26 23:19:17,686 Thread-92 udi_interface DEBUG TeslaCloudEVapi:teslaEV_getLatestCloudInfo: teslaEV_getLatestCloudInfo: 1492932395099962 2022-10-26 23:19:17,739 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message command 2022-10-26 23:19:17,741 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING command 2022-10-26 23:19:18,388 Thread-92 udi_interface DEBUG TeslaCloudEVapi:teslaEV_getLatestCloudInfo: teslaEV_getLatestCloudInfo (car not online) RETURN: {'response': None, 'error': 'vehicle unavailable: {:error=>"vehicle unavailable:"}', 'error_description': ''} 2022-10-26 23:19:18,389 Thread-92 udi_interface DEBUG TeslaCloudEVapi:process_EV_data: process_EV_data 2022-10-26 23:19:18,390 Thread-92 udi_interface DEBUG TeslaCloudEVapi:teslaEV_getLatestCloudInfo: Exception teslaGetSiteInfo: argument of type 'NoneType' is not iterable 2022-10-26 23:19:18,391 Thread-92 udi_interface ERROR TeslaCloudEVapi:teslaEV_getLatestCloudInfo: Error getting data from vehicle id: 1492932395099962 2022-10-26 23:19:18,392 Thread-92 udi_interface ERROR TeslaCloudEVapi:teslaEV_getLatestCloudInfo: Trying to reconnect 2022-10-26 23:19:19,130 Thread-92 udi_interface DEBUG TeslaCloudApi:tesla_refresh_token: tesla_refresh_token RETURN: {'access_token': SiO9A9PJQcn1QqbRHnRYJmss9rOBywjrw', 'expires_in': 28800, 'token_type': 'Bearer'} 2022-10-26 23:19:19,140 Thread-92 udi_interface DEBUG TeslaEVController:shortPoll: Controller poll node controller 2022-10-26 23:19:19,142 Thread-92 udi_interface DEBUG TeslaEVController:updateISYdrivers: System updateISYdrivers - Controller 2022-10-26 23:19:19,142 Thread-92 udi_interface.node DEBUG node:setDriver: controller:Tesla EV Info Reporting set GV0 to True to Polyglot 2022-10-26 23:19:19,143 Thread-92 udi_interface.node DEBUG node:reportDriver: Updating value to 1 2022-10-26 23:19:19,144 Thread-92 udi_interface.interface DEBUG interface:send: PUBLISHING {'set': [{'address': 'controller', 'driver': 'GV0', 'value': '1', 'uom': 25}]} 2022-10-26 23:19:19,146 Thread-92 udi_interface.node DEBUG node:setDriver: controller:Tesla EV Info Reporting set GV1 to 1 to Polyglot 2022-10-26 23:19:19,147 Thread-92 udi_interface.node DEBUG node:reportDriver: Updating value to 1 2022-10-26 23:19:19,148 Thread-92 udi_interface.interface DEBUG interface:send: PUBLISHING {'set': [{'address': 'controller', 'driver': 'GV1', 'value': '1', 'uom': 107}]} 2022-10-26 23:19:19,150 Thread-92 udi_interface.node DEBUG node:setDriver: controller:Tesla EV Info Reporting set GV2 to 1 to Polyglot 2022-10-26 23:19:19,151 Thread-92 udi_interface.node DEBUG node:reportDriver: Updating value to 1 2022-10-26 23:19:19,152 Thread-92 udi_interface.interface DEBUG interface:send: PUBLISHING {'set': [{'address': 'controller', 'driver': 'GV2', 'value': '1', 'uom': 25}]} 2022-10-26 23:19:19,154 Thread-92 udi_interface.node DEBUG node:setDriver: controller:Tesla EV Info Reporting set GV Edited October 27, 2022 by garybixler
Panda88 Posted October 27, 2022 Author Posted October 27, 2022 Thanks It is a slightly different behavior than I would expect - I had expected the car to set online to False (and my code is working that way) - it almost looks like an issue connecting to getting data from the Tesla Cloud. The sleep feature is there indirectly with time since last update fields (assuming they work correctly) - but I can add a dedicated sleep state in the status node - with offline, sleep, online, and unknown states - does than make sense? I feel it is too much to say the node is not online - as it is after you wake the car - I see the connection as the indicator - not the car Do you have a little longer snippet of the log so I can see what happens next
garybixler Posted October 27, 2022 Posted October 27, 2022 (edited) I checked after waking the car and it shows car on line in the query. TeslaCloudEVapi:teslaEV_getLatestCloudInfo: teslaEV_getLatestCloudInfo (car is online) RETURN: {'response': {'id': 1 It may be the release that I am at. I can PM a snippet just before and after I woke the car up. The dedicated sleep state sounds good. Edited October 27, 2022 by garybixler
Recommended Posts