Replies: 16 comments 68 replies
-
|
You can already use the |
Beta Was this translation helpful? Give feedback.
-
I might give it a go and see what happens Found everything I need I think. I will report back |
Beta Was this translation helpful? Give feedback.
-
|
Is it possible to use "enable" and "enabled" on a custom vehicle? |
Beta Was this translation helpful? Give feedback.
-
rather in the charger, like this (state, enabled -> read, enable, current -> write) |
Beta Was this translation helpful? Give feedback.
-
Not on the vehicle by the looks so you have to create a custom charger (so you cant use the twc3 template). For the Status, Enable and Enabled (which is beyond me) you need to create a script to pull these values from a json or rest call to the twc3, from Andy's template you can see, Status Status A = disconnected, Status C = contractor closed, Status B vehicle connected. Enable and Enabled @andig is it possible to add the custom charger "maxcurrent: # set charger max current (A)" and "enable: # set charger enabled state (true/false or 0/1)" (I think thats all we need?) to the custom vehicle template? I think Status and Enabled comes from the twc3 template? Then we can keep the TWC3 charger template. Or would it be hard to create a tesla-ble module as mentioned above? I know that the dev on TeslaMate was talking about relying more on the streaming api rather than the fleet api. Would it be possible to use the streaming api to get SoC, charge limit etc (all just read values) and then the Bluetooth Tesla-control to wake and adjust the max charge amps? Sorry I wish I could be more helpful, I am no dev so I could be way off. |
Beta Was this translation helpful? Give feedback.
-
|
Looking at tesla.go we'll need: // CurrentController provides settings charging maximum charging current
type CurrentController interface {
MaxCurrent(current int64) error
}
// ChargeController allows to start/stop the charging session on the vehicle side
type ChargeController interface {
ChargeEnable(bool) error
}
// CurrentGetter provides getting charging maximum charging current for validation
type CurrentGetter interface {
GetMaxCurrent() (float64, error)
}
|
Beta Was this translation helpful? Give feedback.
-
|
I have a working solution. I have created an HttpProxy that forwards HTTP requests via BLE to the vehicle. (You can find it here: https://github.com/wimaha/TeslaBleHttpProxy. I have a question about this: Sometimes (rarely) bluetooth forwarding fails. How can I inform the custom charger about this? @andig Also the HttpBleProxy uses the same rest api like Tesla. So it could be possible to add this to the twc3 charger. |
Beta Was this translation helpful? Give feedback.
-
|
The repository is now updated and fully functional. Furthermore, I have updated the documentation. |
Beta Was this translation helpful? Give feedback.
-
|
Nice. This should make it rather easy to include into the Tesla template. Just the IP would have to be added to the config. |
Beta Was this translation helpful? Give feedback.
-
|
Hi @wimaha, |
Beta Was this translation helpful? Give feedback.
-
|
@evilmon This seems to be caused by a bug introduced with v0.127.0. It works with v0.126.6… |
Beta Was this translation helpful? Give feedback.
-
Could you please expand the documentation for dummies? I´m not really firm with GO and Docker, so it would be nice to get the instructions to install and set the required components for using BLE-Proxy on a Raspberry Pi. |
Beta Was this translation helpful? Give feedback.
-
|
Hey all, I got my very noob version working tonight (kind of) running EVCC locally on my raspberry pi zero 2 w. Couple of issues, this doesnt work "{{if .enable}}charging-start{{else}}charging-stop{{end}}" it always goes to else, any idea what I am doing wrong there? I swapped the variables around just for testing to get it to start charging. Also I get this error below alot No idea what it mean, it retries a couple of times and then works so not sure. Manually inputting the commands into the shell I never get the error. EDIT: My plan is to put the commands into scripts that have a certain number of retries to try and prevent this error. Then once the scripts are working I will create a websever on the raspberry pi zero can call webhooks from my HA evcc to run the scripts. There is probably a way better way of doing this but this is within my capabilities. |
Beta Was this translation helpful? Give feedback.
-
|
Hey, I would say ATT errors are BLE errors, I would say in my case it's because of distance between RasPi and tesla. My Idea is also to write a script an hide *.pem and VIN stuff. also to diffirentiate between charging-start and stop But in general it works OK: |
Beta Was this translation helpful? Give feedback.
-
|
You don't have to use the vin and key every time. |
Beta Was this translation helpful? Give feedback.
-
|
Updated config below, see what you guys think. It handles the errors but the log fills up with crap (#14252 (comment)) |
Beta Was this translation helpful? Give feedback.
-
|
Here my BLE solution for now: wake.sh current.sh evcc.yaml (I'm using TeslaLogger to get status and SoC and so on) feel free to do it better! :) P.S. based on this examples: |
Beta Was this translation helpful? Give feedback.
-
So I understand, you are running evcc on the same raspberry that you use for the BLE, right? |
Beta Was this translation helpful? Give feedback.
-
|
yes, it's the easiest way. more complex way: |
Beta Was this translation helpful? Give feedback.
-
I like this idea, I might combine my scripts into a single mqtt listener as I need the error handling/wake up at the moment. I might skip the docker just to save complexity for myself. Then I can keep EVCC on my HA which I prefer. I am also trying an external usb bluetooth adapter. If anyone is interested I can post it here once I get it working but the above solution in probably going to be better with discovery etc. |
Beta Was this translation helpful? Give feedback.
-
|
I have done something similar but i built in error retries and also my evcc never tries to wake the vehicle because I think it doesn't know its asleep. So I built the wake command into enable and charge. It works but I get a ton of ble errors, not sure if it is my raspberry or distance (less than 5m). evcc.yaml enable.sh charge.sh wake.sh (not used?) |
Beta Was this translation helpful? Give feedback.
-
|
@wimaha since you‘re also using Go: wanna try adding a tesla-ble native vehicle implementation? |
Beta Was this translation helpful? Give feedback.
-
|
Those are bot the issue. Charge control is the problem. |
Beta Was this translation helpful? Give feedback.
-
|
Maybe next 2 weeks until Tesla shuts it down... |
Beta Was this translation helpful? Give feedback.
-
Hey @andig with my current custom vehicle config EVCC doesn’t know the vehicle is asleep. Is there a custom vehicle config entry to tell Evcc the vehicle is asleep? It doesn’t seem to try and wake the vehicle when I enable charging even if the command fails to change the max current |
Beta Was this translation helpful? Give feedback.
-
|
Not currently. Assleep is a special kind of error and we‘re missing a side channel to return errors. Right now, the implementation would need to handle the wakeup internally. |
Beta Was this translation helpful? Give feedback.
-
Yeah no worries, that’s what I am doing. My script does 3 retries then attempts to wake the vehicle if they fail. I also put a rant on the tesla github, probably not constructive but they need to give us more options besides cloud api calls instead of enforcing the rate limit with no option to buy more calls or use LAN. |
Beta Was this translation helpful? Give feedback.
-
|
So is an official Tesla Ble feature coming?. This would be pretty good actually. I can put my Pi with the charger and be done with this troublesome fleet api |
Beta Was this translation helpful? Give feedback.
-
I don't think so because an official version would have to be part of evcc which would mean running it on the Raspberry which is possible hoever, if you wanted a remote system (pi) running just the BLE side I would use one of the solutions above. They already work well |
Beta Was this translation helpful? Give feedback.
-
|
It would be great to indicate in the documentation that there is currently an issue for Tesla car if you cannot control your charger... it would also be interesting to know what direction evcc will take to improve the common scenario: Tesla Charger + Tesla Car. Right now my evcc instance run as an add-on in HA, but if I need a Pi anyway for the BLE communication, then I could run a dedicated Pi for that. I made the installation this week, saw it working for a few hours then the issue started. I would have noticed if that was somehow hinted in the documentation, even if this is a breaking news. PS: The fact that this ticket is in English and all the work done is greatly appreciated. I invested in the hardware Shelly + P1 reader for the initial setup, now I might just need to add a Pi in the vicinity of the charging port. If anybody write a tutorial or more end-user oriented documentation... please indicate it, but the technical work seems to be done, I just need to experiment. |
Beta Was this translation helpful? Give feedback.
-
|
That's exactly how I feel, I'm a bit disappointed that a system that was so good in the past no longer works. If Bluetooth is the future with this installation, then this must be described in the documentation. The documentation should also somehow include the setup from the Raspi (which Raspi etc. etc.). Not everyone is a Raspi professional. Perhaps this can also be set via the GUI, but I am not enough of an IT professional. |
Beta Was this translation helpful? Give feedback.
-
|
I agree. But I imagine the biggest problem is the missing communication etc. from Tesla. The easiest solution for EVCC would be to be able to use the API as they did in the past. But currently Tesla isn't offering any usable plans. They don't even communicate when and what they are going to offer. So EVCC can't really plan ahead. |
Beta Was this translation helpful? Give feedback.
-
|
Just as a feedback, I can say, that I have the setup with 2x TWC V1 and 2 Tesla running. vehicles:
site: chargers:
loadpoints:
|
Beta Was this translation helpful? Give feedback.
-
|
|
Beta Was this translation helpful? Give feedback.
-
|
Wie ist der Poll Mode in der evcc.yaml eingestellt? |
Beta Was this translation helpful? Give feedback.
-
|
Den hatte ich bis jetzt gar nicht eingestellt, nun aber so wie von dir hier angegeben. Ich habe nun im Debug-Log auch folgenden Eintrag gefunden: Das würde ja bedeuten, dass EVCC den Wert sehr wohl bekommt, aber dann halt nix damit macht? |
Beta Was this translation helpful? Give feedback.
-
|
Was ist denn jetzt noch die konkrete Problemstellung? Was funktioniert nicht? |
Beta Was this translation helpful? Give feedback.
-
|
Die Problemstellung ist, dass EVCC den SOC nicht anzeigt. EDIT: Es hat sich erledigt. Heute morgen zeigt es plötzlich den Ladestand an. Danke für die Hilfe! |
Beta Was this translation helpful? Give feedback.
-
|
I successfully managed to control via BLE my Tesla plugged on my Tesla Wall Connector 3, using a remote raspberry pi. It works either with TeslaBleHttpProxy or with tesla_ble_mqtt_docker. However, I cannot find a way to avoid using a « custom » vehicle in evcc, which requires installing a data logger like TeslaMate in order to feed the soc, range and status. I do not need to gather and store all these data, so this is bothering me (and using uselessly resources). Would it be possible to allow combining the official tesla template using the FleetAPI for all « read » operations and custom (mqtt or http) for all « write » operation (chargeenable, maxcurrent, wakeup) ? Is there another possible setup without Teslamate/TeslaLogger ? Note that I already tried to use a customer charger instead of the official twc3 template, but things turn bad when my other car (a Fiat 500e) is charging and not my tesla. For reference, here is my current evcc config, using tesla_ble_mqtt_docker. |
Beta Was this translation helpful? Give feedback.
-
|
As a workaround: Why do we need the these states? EDIT: Ignore the above, I´m wrong. But someone is already working on a solution for BLE status requests for tesla-command: teslamotors/vehicle-command#229 |
Beta Was this translation helpful? Give feedback.
-
|
I still think the best way would be to add support for a custom url for the proxy used in the controller. Like that we could have a vehicle using fleet api to read the data and TeslaBleHttpProxy (as it’s using the same syntax) to execute the commands instead of evcc proxy. |
Beta Was this translation helpful? Give feedback.
-
|
Today I'm getting a smart charger installed instead of the TWC3 :) I'm a bit over the Tesla API |
Beta Was this translation helpful? Give feedback.
-
|
Just discovered evcc. |
Beta Was this translation helpful? Give feedback.
-
|
I really won't get the TWC. Either get a go-E Gemini or Easee Home as both of them are capable of switching the phases and can work with any car in the future. |
Beta Was this translation helpful? Give feedback.
-
|
Halo an alle hier. Manchmal komme ich mir vor als wäre ich in einem falschen Film. Diese BLE-Installation habe ich nun den ganzen Nachmittag versucht auf zwei verschiedenen Raspberry's zu installieren. Ich komme bis zur Zeile cd vehicle-command Danach wirft mir Ich bin bestimmt kein Anfänger aber langsam zweifle ich doch daran. Ich habe Perplexity AI befragt. Rauf und runter. Keine Chance. Reboot u.s.w ebenfalls. Any hints? |
Beta Was this translation helpful? Give feedback.
-
|
Welcher RaspberryPi Typ wird verwendet? |
Beta Was this translation helpful? Give feedback.
-
|
Ich habe es auf einem Pi 4 und einem Pi Zero W2 installiert. Auf dem Pi 4 mit Pi OS 64 und auf dem Zero mit Pi OS lite 64 |
Beta Was this translation helpful? Give feedback.
-
|
32 bit OS verwenden |
Beta Was this translation helpful? Give feedback.
-
|
oder das Go x86-64 verwenden (z.B. go1.21.7.linux-amd64.tar.gz) |
Beta Was this translation helpful? Give feedback.
-
|
Woran ich persönlich scheitere sind die Sensoren für die Abfragen. |
Beta Was this translation helpful? Give feedback.
-
|
So ich taste mich langsam heran. Habe jetzt Damit habe ich schon einige Angaben. Diese Shell Befehle funktionieren auf der Konsole unter meinem user genau so wie sie hier stehen -allerdings wirft mir EVCC: raus. |
Beta Was this translation helpful? Give feedback.
-
|
Sorry, I am lost and I feel I need some advise... I made many steps, but I lost track of the (moving?) target:
My evcc config: So now I wonder how do I stop using the cloud API, and what of all the tools I have accumulated I should use to have a working and stable solution. HELP. ;-) |
Beta Was this translation helpful? Give feedback.
-
|
Maybe consider testing the the :tesla docker image with this PR #14616. |
Beta Was this translation helpful? Give feedback.
-
|
Bad idee. Couse of the API limits by tesla. This is my reason to use BLE. |
Beta Was this translation helpful? Give feedback.
-
Since Tesla introduced severe limits for their cloud API calls, it's not really usable for solar charging anymore. The same API can however be used over BLE (Bluetooth Low Energy). I have tried it successfully with a Raspberry Pi Zero W. Other Raspberry Pi models with wireless connectivity or any generic Linux device with a BLE chip or USB dongle should work as well.
This are the installation steps I took on a fresh Raspberry Pi OS lite install:
After initiating the last command you have to tap the key card in the center console (no message will be shown on the Tesla prior to tapping the card) and confirm adding the key.
Afterward you can run commands locally. For example:
tesla-control -ble -vin YOUR_VIN -key-file private.pem charging-startNow we just need to integrate it into EVCC. Sadly I'm no developer. I could probably cobble something together, but it probably wouldn't be upstreameable.
Beta Was this translation helpful? Give feedback.
All reactions