# \[APP\]\[Pro\] Tesla Car & Energy - Zero emissions. Zero compromises **URL:** \ **Category:** Apps\ **Tags:** app, homey-pro\ **Created:** [January 11, 2024, 5:15pm UTC](https://community.homey.app/t/app-pro-tesla-car-energy-zero-emissions-zero-compromises/100824 "2024-01-11T17:15:52Z")\ **Posts on this page:** 20\ **Page:** 67
**Author:** ![Koen\_van\_Daalen](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/koen_van_daalen/32/17092_2.png) [@Koen\_van\_Daalen](https://community.homey.app/u/Koen_van_Daalen)\ **Post date:** [September 2, 2026, 3:16pm UTC](https://community.homey.app/t/app-pro-tesla-car-energy-zero-emissions-zero-compromises/100824/1340 "2026-09-02T15:16:26Z")
Setup the telemetry as you suggested and it works as expected. Thanks for you guidance! ---
**Author:** ![Kikegf](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/kikegf/32/81265_2.png) [@Kikegf](https://community.homey.app/u/Kikegf)\ **Post date:** [September 5, 2026, 4:55pm UTC](https://community.homey.app/t/app-pro-tesla-car-energy-zero-emissions-zero-compromises/100824/1341 "2026-09-05T16:55:03Z")
Hello. I am trying to add my Energy Site and following all your instructions, i get stucked in the last step, Session initiate on the manufacturer website ![Captura 2026-09-05 a las 17.40.56](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/f/f/ff9408d8053071953faa7147a66ee0f1075502e3.png) ---
**Author:** ![RonnyW](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/ronnyw/32/10879_2.png) [@RonnyW](https://community.homey.app/u/RonnyW)\ **Post date:** [September 5, 2026, 6:55pm UTC](https://community.homey.app/t/app-pro-tesla-car-energy-zero-emissions-zero-compromises/100824/1342 "2026-09-05T18:55:56Z")
In this step, the Tesla oAuth popup should be shown. Can you try to hard-close the Homey app (Homey mobile app). This oAuth call is done by Homey/mobile app. Something stopped the GUI to open the html popup. ---
**Author:** ![Kikegf](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/kikegf/32/81265_2.png) [@Kikegf](https://community.homey.app/u/Kikegf)\ **Post date:** [September 5, 2026, 10:03pm UTC](https://community.homey.app/t/app-pro-tesla-car-energy-zero-emissions-zero-compromises/100824/1343 "2026-09-05T22:03:06Z")
Thanks for your answer. But I fixed it, opening a private web session and adding the devices. It worked! ---
**Author:** ![Mikrent](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/mikrent/32/17475_2.png) [@Mikrent](https://community.homey.app/u/Mikrent)\ **Post date:** [September 6, 2026, 5:08pm UTC](https://community.homey.app/t/app-pro-tesla-car-energy-zero-emissions-zero-compromises/100824/1344 "2026-09-06T17:08:55Z")
Hi Ronny, I’m trying to add a Tesla Energy Site / Powerwall using Tesla Car & Energy v4.4.8 on a Homey Pro Early 2019. I created the Tesla Fleet API application according to your instructions, with both allowed origins ([athom.com](http://athom.com) and [rwdevelopment.de](http://rwdevelopment.de)), the Athom OAuth callback, Authorization Code + Machine-to-Machine, and all requested scopes. Tesla OAuth completes successfully and redirects to [callback.athom.com](http://callback.athom.com) with “You can now close this window”. Immediately afterwards Homey returns: 412 Precondition Failed – Account … must be registered in the current region [https://fleet-api.prd.na.vn.cloud.tesla.com](https://fleet-api.prd.na.vn.cloud.tesla.com) Restarting the Homey app and repeating OAuth gives exactly the same result. My Tesla energy installation/account is in Switzerland. Could you please advise how the Partner Account should be registered for the NA region, or whether this is something the Homey app should perform automatically during pairing? Thanks! ---
**Author:** ![RonnyW](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/ronnyw/32/10879_2.png) [@RonnyW](https://community.homey.app/u/RonnyW)\ **Post date:** [September 6, 2026, 8:56pm UTC](https://community.homey.app/t/app-pro-tesla-car-energy-zero-emissions-zero-compromises/100824/1345 "2026-09-06T20:56:36Z")
Hi, can you please show me a screenshot, where exactly the error is shown? In pair view or in device details? Or just try agian, then send me a diagnostics report. Thanks. In the past, there have been user accounts in another reqion than the device region. But I’m not sure if that’s the case. ---
**Author:** ![Mikrent](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/mikrent/32/17475_2.png) [@Mikrent](https://community.homey.app/u/Mikrent)\ **Post date:** [September 7, 2026, 6:38am UTC](https://community.homey.app/t/app-pro-tesla-car-energy-zero-emissions-zero-compromises/100824/1347 "2026-09-07T06:38:21Z")
Hello, it is after the login Tesla (ok) and the “you can close this window” screen. Thank you! ![1000062530](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/7/8/784d7ff499f817f1c83ad67eb637fcca413e34de.jpeg) ![1000062555](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/b/c/bce139f71a8e7f45daa365f4b607f691dd903f33.jpeg) ---
**Author:** ![RonnyW](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/ronnyw/32/10879_2.png) [@RonnyW](https://community.homey.app/u/RonnyW)\ **Post date:** [September 7, 2026, 8:41pm UTC](https://community.homey.app/t/app-pro-tesla-car-energy-zero-emissions-zero-compromises/100824/1348 "2026-09-07T20:41:31Z")
I haven’t got a diagnostics report, but I think it won’t help as the error is shown in the html GUI. I think it occours by reading devices. The error looks like your device is registered is another region than your account. There was an old issue where this happened and the only way to solve it was to change the account region. Can you please look at your account region? > [@\[APP\]\[Pro\] Tesla Car & Energy - Zero emissions. Zero compromises](https://community.homey.app/t/app-pro-tesla-car-energy-zero-emissions-zero-compromises/100824/118): > > @Jacco_van_Eck Here is a step by step example. Open this page in your browser. [https://accounts.tesla.com/en\_us/account-settings/personal-information](https://accounts.tesla.com/en_us/account-settings/personal-information) If it’s showing a 404 error, just click on the icon in top right corner and open account settings. [grafik] [grafik] Then edit: I think this is nor matching the owner region. Hit STRG+Shift+K Open the tree: Right click. Then select “copy”. Then select “insert” and “after” [grafik] Double click on the v… Background: Your account is registered in a region and it also delivers the correct API url. The app is using this URL to access your devices via FleetAPI. So it seems as if either your device or your account is registred in a wrong region. (but that’s only a guess). ---
**Author:** ![Paul\_Nas](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/paul_nas/32/80581_2.png) [@Paul\_Nas](https://community.homey.app/u/Paul_Nas)\ **Post date:** [September 10, 2026, 10:52pm UTC](https://community.homey.app/t/app-pro-tesla-car-energy-zero-emissions-zero-compromises/100824/1349 "2026-09-10T22:52:03Z")
@RonnyW is it possible to add the FSD version? I log the software version but that doesn’t include FSD. Thanks! ---
**Author:** ![Tariq](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/tariq/32/122207_2.png) [@Tariq](https://community.homey.app/u/Tariq)\ **Post date:** [September 12, 2026, 3:11pm UTC](https://community.homey.app/t/app-pro-tesla-car-energy-zero-emissions-zero-compromises/100824/1350 "2026-09-12T15:11:47Z")
Hi Ronny, I have the same I think, I fail at the Fleet API partner/domain registration stage. Homey Pro 2023, Tesla Car & Energy v4.4.8, UK Tesla account, first-ever Tesla Developer application. The application is approved, OAuth succeeds, the app appears under Tesla Third Party Apps, and all 7 scopes are now granted including Profile Information. Energy Site pairing still fails with: `412 Precondition Failed: Account must be registered in the current region https://fleet-api.prd.na.vn.cloud.tesla.com` Reproducing Car pairing in Homey Developer Tools gives: `422 Validation failed: Domain has already been taken` for both NA and EU domain registration. Could the Homey-specific domain have been successfully/partially registered during the first attempt, with subsequent attempts then incorrectly trying to register it again? Is there a way to verify or reset the domain registration for this Client ID? Diagnostics report: ca271ef2-4d70-49ef-93ae-dd3485647ca0 ---
**Author:** ![RonnyW](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/ronnyw/32/10879_2.png) [@RonnyW](https://community.homey.app/u/RonnyW)\ **Post date:** [September 12, 2026, 6:09pm UTC](https://community.homey.app/t/app-pro-tesla-car-energy-zero-emissions-zero-compromises/100824/1351 "2026-09-12T18:09:09Z")
No, there is no way to reset the domain. It’s then bound to your clientID. So just use the client id you used for first login. Tesla doesn’t offer an API for removing the domain. I requested that but never got an answer… The domain is a virtual subdomain for your Homey cloud ID and that’s linked to your Tesla client ID. If you start pairing again with the same client ID, the public certificate is re-used and domain registration is done again. You can force the generation of a new public certificate in client if form (the button below). Perhaps this could fix the domain registration (but I don’t think that’s the reason). After some research in Tesla documention, the error http 412 error says that the app (client ID) is not yet registered for the Tesla region (NA or EU). In normal pairing, an error in domain registration should stop paiting. Were you able to proceed to oAuth and device list? ---
**Author:** ![RonnyW](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/ronnyw/32/10879_2.png) [@RonnyW](https://community.homey.app/u/RonnyW)\ **Post date:** [September 12, 2026, 6:14pm UTC](https://community.homey.app/t/app-pro-tesla-car-energy-zero-emissions-zero-compromises/100824/1352 "2026-09-12T18:14:18Z")
> [@Paul\_Nas](#): > > FSD version? I’ll take a look at the Telemetry fields… ---
**Author:** ![RonnyW](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/ronnyw/32/10879_2.png) [@RonnyW](https://community.homey.app/u/RonnyW)\ **Post date:** [September 13, 2026, 9:32am UTC](https://community.homey.app/t/app-pro-tesla-car-energy-zero-emissions-zero-compromises/100824/1353 "2026-09-13T09:32:37Z")
> [@Paul\_Nas](#): > > FSD version? I haven’t found a data field for FSD. The only FSD field is: SelfDrivingMilesSinceReset 🤷‍♂️ > **[Available Data | Tesla Fleet API](https://developer.tesla.com/docs/fleet-api/fleet-telemetry/available-data)** ---
**Author:** ![Tariq](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/tariq/32/122207_2.png) [@Tariq](https://community.homey.app/u/Tariq)\ **Post date:** [September 14, 2026, 9:00am UTC](https://community.homey.app/t/app-pro-tesla-car-energy-zero-emissions-zero-compromises/100824/1354 "2026-09-14T09:00:43Z")
Thanks Ronny. I’ve only ever created one Tesla Developer account/application, so there has only ever been one Client ID on this Homey. I am still using that same Client ID. The domain registration therefore appears to have succeeded/bound during the initial setup, but Energy Site pairing still fails afterwards with: `412 Precondition Failed: Account must be registered in the current region https://fleet-api.prd.na.vn.cloud.tesla.com` My Tesla account region is United Kingdom and OAuth completes successfully. All required scopes are granted. Fresh diagnostics report: f1ce10e8-93c7-446e-9350-fbf08ae6cfa4 ---
**Author:** ![RonnyW](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/ronnyw/32/10879_2.png) [@RonnyW](https://community.homey.app/u/RonnyW)\ **Post date:** [September 14, 2026, 2:19pm UTC](https://community.homey.app/t/app-pro-tesla-car-energy-zero-emissions-zero-compromises/100824/1355 "2026-09-14T14:19:53Z")
Hi, First some words about your log… I can still see these error from pair/repair: ```auto 2026-09-12T13:32:38.654Z [log] [ManagerDrivers] [Driver:car] registerDomain() => Error NA domain registration: 422 Unprocessable Entity: {"response":null,"error":"Validation failed: Domain has already been taken","error_description":"","txid":"7e1af98f6d68e1301485a7dbb91b6981"} 2026-09-12T13:32:39.586Z [log] [ManagerDrivers] [Driver:car] registerDomain() => Error EU domain registration: 422 Unprocessable Entity: {"response":null,"error":"Validation failed: Domain has already been taken","error_description":"","txid":"a20c93d182dbc90b1e61fd0df31e1491"} ``` You are trying to pair the car, right? There, the domain registration error occours. That normally means, for Tesla this domain (including your Homey ID) is already registered for a client ID. The car and the energy site are using independent oAuth authorization, you could also use another Tesla account to add a device. But both must use the same client ID from your developer account, because both are using the domain registration. The client ID and certificate is Homey specific. The following Tesla oAuth popup is device specific. Both devices can have different Tesla account/authentification, but both will use the one client ID. I can see you are using the same client ID for car and energy site (good). But I can also see the domain error. And I found a pair step issue for Energy Site the caused the app to jump over the domain registration. But like already said, this registration is the same for car and energy site. I fixed it, but I think you will get now also the “domain has taken” error for energy site. New test version: 4.4.9: > **[Tesla Car & Energy | Homey](https://homey.app/en-us/app/com.tesla.car/Tesla-Car-&-Energy/test/)** > > Zero emissions. Zero compromises. The Homey is your own one or a second hand device? Not that y previous owner already used and registered it for Tesla 🤔 ---
**Author:** ![Tariq](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/tariq/32/122207_2.png) [@Tariq](https://community.homey.app/u/Tariq)\ **Post date:** [September 15, 2026, 9:17am UTC](https://community.homey.app/t/app-pro-tesla-car-energy-zero-emissions-zero-compromises/100824/1356 "2026-09-15T09:17:19Z")
Hi Ronny Thanks, I did buy this Homey Pro second-hand . So it’s quite possible a previous owner registered the Homey-specific Tesla domain with their own Client ID. I obviously don’t have access to that Client ID. Given Tesla doesn’t provide an API to remove the domain binding, is there any workaround for a second-hand Homey in this situation? ---
**Author:** ![RonnyW](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/ronnyw/32/10879_2.png) [@RonnyW](https://community.homey.app/u/RonnyW)\ **Post date:** [September 15, 2026, 3:57pm UTC](https://community.homey.app/t/app-pro-tesla-car-energy-zero-emissions-zero-compromises/100824/1357 "2026-09-15T15:57:32Z")
I opened a ticket at Tesla. But I have no hope that they can/will help. Do you know the previous user? ---
**Author:** ![Paul\_Nas](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/paul_nas/32/80581_2.png) [@Paul\_Nas](https://community.homey.app/u/Paul_Nas)\ **Post date:** [September 23, 2026, 8:25pm UTC](https://community.homey.app/t/app-pro-tesla-car-energy-zero-emissions-zero-compromises/100824/1358 "2026-09-23T20:25:47Z")
Thanks for checking! I’m trying to build a smart charging flow but my charger app has lost support so I’m stuck using Tesla commands… I can cut down on the number of starts/stops I need to send if I can edit the charge schedule, but it looks like you’re using the old endpoints. New ones are: 1. add\_charge\_schedule / remove\_charge\_schedule 2. add\_precondition\_schedule / remove\_precondition\_schedule 3. preconditioning\_schedule\_data from vehicle\_data (required to find the schedule to edit/delete) Would it be possible to expose those so I can charge and precondition my car based on calendar entries? Thanks a bunch in advance! ---
**Author:** ![Rudi\_Hendrix](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/rudi_hendrix/32/31931_2.png) [@Rudi\_Hendrix](https://community.homey.app/u/Rudi_Hendrix)\ **Post date:** [September 24, 2026, 5:18am UTC](https://community.homey.app/t/app-pro-tesla-car-energy-zero-emissions-zero-compromises/100824/1359 "2026-09-24T05:18:00Z")
Sounds like you are also hit by the 50Five MFA “support” ☹ I am using Tibber and have given them access to both my Tesla and Homey. They make sure the Tesla starts charging at the best moments. When the price is the lowest and optimal in combination with my solar panels. However, I do want to look into creating my own flow again as well. I’ve had some good experience with allowing ChatGPT to review and improve some of my flows. For this app I was wondering @RonnyW : is there a way to enable heating the rear window and mirrors from the app? Or doesn’t the API include that? Would be really useful in preparing the car before I leave for work. And in general: do you get a notification if the API gets updated? I am still hoping for some expansion on the media possibilities. So I can pick the correct radio station for example. ---
**Author:** ![RonnyW](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/ronnyw/32/10879_2.png) [@RonnyW](https://community.homey.app/u/RonnyW)\ **Post date:** [September 24, 2026, 6:09am UTC](https://community.homey.app/t/app-pro-tesla-car-energy-zero-emissions-zero-compromises/100824/1360 "2026-09-24T06:09:12Z")
> [@Rudi\_Hendrix](#): > > is there a way to enable heating the rear window and mirrors from the app? I can’t rememver that there is such a command. I only know the “preconditioning” command. But do you really want only rear window without A/C? The API is quite static. Only FleetApi got additional fields. But I will take a look at it if something changed. [Previous page](https://community.homey.app/t/app-pro-tesla-car-energy-zero-emissions-zero-compromises/100824.md?page=66) [Next page](https://community.homey.app/t/app-pro-tesla-car-energy-zero-emissions-zero-compromises/100824.md?page=68)