# \[APP\]\[Pro\] Tesla Car & Energy - Zero emissions. Zero compromises

**URL:** https://community.homey.app/t/app-pro-tesla-car-energy-zero-emissions-zero-compromises/100824
**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:** 1
**Showing post:** 2

<div class="post-metadata">

### 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: [January 11, 2024, 5:16pm UTC](https://community.homey.app/t/app-pro-tesla-car-energy-zero-emissions-zero-compromises/100824/2 "2024-01-11T17:16:09Z")

</div>

**FAQ**

- Error message **“session info hmac invalid”** sendign commands:  
This is caused by a discrepancy between the app certificate and the registered car key. In normal case, this can be fixed using a new certificate and update the car key:

- Error message **“Validation failed: Domain has already been taken”** after Client ID page:  
This is caused by using a second Client ID on your Homey.  
During initial setup, the app certificate is provided on a Homey specific URL. This certificate is used to add the car key. The Client ID provided during pairing is bound to this URL as ad requirement to use FleetAPI in conjunction with the Client ID.  
If a second Client ID is used on the Homey, it can’t be bound to the Homey specific URL because the other ID is already registerd.

---

_[View the full topic](https://community.homey.app/t/app-pro-tesla-car-energy-zero-emissions-zero-compromises/100824)._