You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am developing with nodered a flow that sets automatically the scheduled charge and scheduled departure by reading my Google calendar.
I have noticed that the car gives a lot of information about such events placed in the future that will wake the car up by itself but Teslamate does not use them (yet).
Here is what I have identified (may probably be improved, this is the reason of this discussion thread).
A. Do not allow to go in 'suspended' state: (maybe already handled by the 'A/C is on' condition)
Keeper mode is set (dog mode, camp, ...): climate_state.climate_keeper_mode !== 'off'
Auto conditionning is on: climate_state.is_auto_conditionning_on
B. Automaticly resume Teslamate:
On a scheduled preconditionning is going to starting or is started: charge_state.is_preconditionning_enabled === true && now/1000 in (charge_state.scheduled_departure_time +/-25min*60)
Here, the 25 minutes are estimates and must be refined. Not sure it is a constant, it may depends on the inside/outside temperatures. now unit is milliseconds. Maybe the +25min is not a good idea and should be reduced to 1min to let the car actually start the A/C (which is already a condition to not go in suspended state)
On a scheduled charge starting: charge_state.scheduled_charging_start_time !== null && now/1000 >= charge_state.scheduled_charging_start_time
On a managed charge starting: charge_state.managed_charging_start_time !== null && charge_state.managed_charging_user_canceled !== true && now/1000 in (charge_state.managed_charging_start_time -0, +charge_state.minutes_to_full_charge*60)
Here, I have not tested the condition in details (mainly the user cancelation)
What do you think of all of those improvements?
It should hopefully let Teslamate log more events from their start.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Hi all,
I am developing with nodered a flow that sets automatically the scheduled charge and scheduled departure by reading my Google calendar.
I have noticed that the car gives a lot of information about such events placed in the future that will wake the car up by itself but Teslamate does not use them (yet).
Here is what I have identified (may probably be improved, this is the reason of this discussion thread).
A. Do not allow to go in 'suspended' state: (maybe already handled by the 'A/C is on' condition)
climate_state.climate_keeper_mode !== 'off'
climate_state.is_auto_conditionning_on
B. Automaticly resume Teslamate:
charge_state.is_preconditionning_enabled === true && now/1000 in (charge_state.scheduled_departure_time +/-25min*60)
Here, the 25 minutes are estimates and must be refined. Not sure it is a constant, it may depends on the inside/outside temperatures.
now
unit is milliseconds. Maybe the +25min is not a good idea and should be reduced to 1min to let the car actually start the A/C (which is already a condition to not go in suspended state)charge_state.scheduled_charging_start_time !== null && now/1000 >= charge_state.scheduled_charging_start_time
charge_state.managed_charging_start_time !== null && charge_state.managed_charging_user_canceled !== true && now/1000 in (charge_state.managed_charging_start_time -0, +charge_state.minutes_to_full_charge*60)
Here, I have not tested the condition in details (mainly the user cancelation)
What do you think of all of those improvements?
It should hopefully let Teslamate log more events from their start.
Thanks !
Beta Was this translation helpful? Give feedback.
All reactions