No, there are no predefined flows. It’s all very individual.
I think the post was moved because you want to adjust charging via your car. If you really meant Tessie app, then you are wrong here becaude Tessie only provides data. This app provides also actions to control the car.
As alternative, you can also control charging using your charger (if it’s smart). So there are many ways to do it.
If you have questions about this app, please ask. Your question was very general and not clear if or which app you want to use. Perhaps it’s better to ask again in Flow part of the forum and describe more clear your current state (which apps used) and where you need help.
Not a tesla flow, but I do have a flow that does that for my Amina Charger.
Just replace the Amina specific cards by Tesla cards and my youless P1 cards with your homewizzard P1 and you should be there…
There is a link to download the flow too.
Works like a charm!
As soon as the surplus power on my P1 (not homewizzard, but its all the same) is over 6A (my car does not allow 5A) it starts charging driving the surplus to zero. Adjustment is per 1A. I use the median over 1min but you can also change that to your liking)
@RonnyW I often get “Invalid enum capability (homey:app:com.tesla.car:climate_steering_wheel_heat_level) value: 2-auto. Expected: 0-auto,0,1-auto,1,3-auto,3” when the car preconditions.
Yeah. I make it a habit to catch any errors on action cards. I get it on the “refresh car data” card (sorry, I only know the Dutch name which is “Bijgewerkte voertuiggegevens”).
I’ve tried Telemetry, nice feature! I only see levels 0, 1 and 3 though. But that is by setting it by hand. This “2-auto” is only by pre-heating the car and it’s too warm now…
I just meant, using Telemetry you could turn off polling. It saves most of your API usage.
But I just saw that such combined values are not already fully functional for Telemetry. For steering wheel heating I have to add additional capabilities. In polling, I get all data at once and can check level+auto mode. In Telemetry I only get one value at a time…
And for yoru case I checked preheating (nor defrost) for my MY 2023 and I only got value 1 and 3.
I think I will just switch the 2 to a 3
The value “2” is now interpreted as “3” (high).
The status is now updated correctly based on level and auto state. There are also two new capabilities for (climate_steering_wheel_heat_level_auto, climate_steering_wheel_heat_level_number), but only visible as flow tag.
You mean to get the car navigation favorites via FleetAPI? I don’t think so.
But: Tesla itself just uses the navigation command where you can insert free text (address, POI etc.). I think so, because the API doesn’t offer the “work” or “home” location, but Tesla itself can use it from Grok. That’s why I think, they just send “home” or “work” as destination.
So you can try to use this card and insert the favorite name - just as a try.
No, I meant for audio. Navigation works, I’ve tested that. I can for example use flows to either navigate to my client or to my home office. What I would like to control too is the radio statiion that is playing. At home I let my Sonos play specific radio stations based on the time of day.
hi @RonnyW , it seems to me that the ‘destination address’ somewhat remembers the previous destination address when im not navigating.
So when i navigate home, the destination address is filled with my home address (expected). But when i later on (hours later) drive away from home (e.g. to the gym and there is no navigation turned on) - it still tells me that the destination address is my home address.
it seems that you fixed this issue a while ago (see the comment im replying to) - could it be that this ‘issue’ is returned?
The car still reports the destination coordinates, also after the navigation ended.
That’s why the destination address (bsed on coordinates) is still present in device details.
All other fields are cleared (destination name, distance, time to arrival).
Seems to be a bug in car software
For now you can use distance to arrival if you want to check it in flows.
