New test version 4.1.2:
- Minor changes in location/media data update.
Please add the battery device for battery specific data/flows 
Any clue how to solve this error
403 Forbidden: {“error”:“account disabled: EXCEEDED_LIMIT”}
the fleet api looks ok at first sight in Tesla developer portal, and Homey reports 0 commands sent..
Check if your 10€ limit is used.
Seems like I’m 0,00002 above limit. Not sure how as I have to flows that regularly calls api- just a button which has been out of battery for a while.
is there a limit for fetch api too? I have settings set to 5min for first param and 10 for second
Sure, for every API call. Check developer page. For you, Commands and Data is relevant.
And it’s better to switch over to Telemetry. Activate Telemetry and deactivate polling in car device settings.
Since yesterday (24-03-2026) I get the following error messages several times per day (not on regular interval - I check and log status every hour but this message has so far been received 6 times in 2 days):
Method “Get” with signature “ss” on interface “org.freedesktop.DBus.Properties” doesn’t exist
It’s not from the app itself. Look like Homey internal communication (BLE or similar).
I can only forward this to Athom and see if I get a good answer.
Can you say when or where exactly the error is shown? Commands? Then BLE is active for your car?
It’s a known issue caused by underlying software where Athom couldn’t find the root cause yet.
I wonder why you can see this error. The app should catch the error and call the FleetAPI instead 
Yes, I have BLE active, but my car is on the edge of reception so more often than not BLE doesn’t reach the car successfully. It happens when I poll the car for data (every hour - some hours this message appears). Polling completes successfully; I’m not missing any logging. I do have a retry on any error though.
Great, thanks! I haven’t seen the error since, so I’m guessing this solved it 
I’m at 4.1.3 now. Errors I find in my logging are:
Method “Get” with signature “ss” on interface “org.freedesk.DBus.Properties” doesn’t exist.
BLEServer: Failed to find advertisement with ID: Sc03d73a1ba0afb5cC
Could not connect to peripheral ec9a345ab373
system
Not Connected
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
Especially on the BLEServer one, which can happen several times per logging attempt (retry on error). Eventually I get a successful logging attempt though. Never missed one. It’s not consistent though, some days it’s 9 times, some days it’s none. Some logging attempts are retried 3 times, most are just retried 1 time (retry interval is 5 mins).
This one I already reported to Athom. It’s a sporadically error in a driver/subsystem. No fix so far.
That are standard BLE errors when Homey could not find the device or could not connect. But I don’t know if the device is really not accessible or if it’s still a buffer issue in Homey.
Do you send commands or are you reading data via BLE?
Hm, that’s a bit out of context
That was already fixed in 4.1.2
Should only happen again if only auto mode was changed. I added another check now.
The BLE I can’t debug because it’s part of the Homey core and that code is not accessible. I already tried to reproduce errors but at the end it’s up to Athom.
In my case I have a Homey bridge close to the car (just behind the window). But also there it’s different whether I place it at the right or left side of the car. Also other devices can interfere with BLE (like tablets, voice assistants, even charger).
So I’m using Telemetry for data only (no polling) and FleetAPI for commands (don’t use it regulary because my inverter/charger are doing PV charging automatically).
No data has been coming in since April 11; I’m supposed to check the vehicle authentication
When I go to “Repair” and select “Change Registration,” the following message appears after a short loading time
Failed to POST to url:``https://fleet-api.prd.eu.vn.cloud.tesla.com/api/1/partner_accounts`` error: getaddrinfo ENOTFOUND ``fleet-api.prd.eu.vn.cloud.tesla.com
This is the english thread
For me it’s working. 
I can repair and login without issues.
Hi,
I seem to bet getting:
401 Unauthorized: {“error”:“login_required”,“error_description”:“The refresh_token is invalid”}
multiple times a week, and have to re-log into tesla via homey for it to work again. We have 2 different tesla’s and it happens with both. I can only use Tesla flows for a couple of days before it fails again. Am I doing something wrong?
Thanks
Hi,
are you only using flows in this case? The error comes from a flow card?
Are you using polling or Telemetry for data reading?
Just want to narrow down to possible causes…
PS: Is it possible that you are not using the API for more than 24 hours? I think it’s possible that the auth token can’t be refreshed after this period. If you can confirm, then this can be the reason. In this case I have to add an auto refresh based on token lifetime.
Most of my Tesla operations are advanced flows, but even a simple button to unlock the car has the same error. I can see the error output on the advanced flow and I set it to text me with it when it happens to I know when to re-log back in again. It’s pretty annoying though!
I’m using Telemetry. But it is possible it’s not used for 24 hours at point yes… my main advanced flow is a morning preheat with several over functions around the house and it’s possible it can be 24 hours before the next preheat.
Thanks
Update: it’s not a 24 hour thing. I ran a flow this morning and just tried to run another now. Worked this morning but got the unauthorised token error again (it’s been about 10 hours)
Thanks
