Open HayderHekmat opened 2 months ago
I don't see anything fundamentally wrong in there. Error 133 could mean the car is out of range, or the MAC is not correct. You can use the ble tracker to check which BLE devices your ESP is able to see
Thanks for the fast response. May I know how to retrieve the MAC address?
I use this:
esp32_ble_tracker:
on_ble_advertise:
then:
- lambda: |-
ESP_LOGD("ble_adv", "New BLE device");
ESP_LOGD("ble_adv", " address: %s", x.address_str().c_str());
ESP_LOGD("ble_adv", " name: %s", x.get_name().c_str());
Thanks @robin-thoni . I found the MAC address and I can control the car through BLE. Then, I configured the evcc by adding commandProxy: Then, I got this error:
[lp-1 ] ERROR 2024/07/11 22:56:18 max charge current 3A: Post "http://192.168.xxx.xxx:8080/api/1/vehicles/VIN/command/set_charging_amps": dial tcp 192.168.xxx.xx:8080: connect: connection refused
Do you know what is the wrong? Or should I use MQTT instead of commandproxy configure
Hello,
first of all, thanks for your effort to create such feature.
Would you please summarize steps that I need to follow to install and connect the ble to the tesla.
I have already configured ESP32 and it look likes something is missing. I will attach log files just in case to analysis my configuration.
logs_mytesla-access_logs.txt logs_mytesla-access_run.txt
Thanks for your support.