Hi, is your car selected in Widget settings?
Yes, and I’ve also tried removing and adding the widget again as well. If I change the car to the Model Y in the same widget the information appears, but changing it back to the Model 3 it then disappears again 
Are there differences between both cars (child devices missing)?
Are all capabilities present in device details?
Can you change the car in widget settings, then change back, then directly send a diagnostics report (I hope the telemetry data is not filling up the log too fast). Let’s see I there is any error. Perhaps the error is on html side. Then we don’t see it.
The devices seems identical wrt capabilities and both update fine. I turned off telemetry, restarted the app, changed from Model 3 to Y and back to 3 again.
Diagnostics report: 4826ede3-b682-4832-bb0e-21d35a44a35a
No error in the log. I think an error would apper in html view (in the browser you would check the developer console).
And the widget stays empty even if the app gets new Telemetry data from the car?
I published a new test version 4.4.6 with an error logging for data request coming from the widget. It’s just a try…
Just update. Open the widget. Then send a diagnostics report again.
Nothing changes when the car gets new telemetry data either, unfortunately. Never seen the widget work with this car.
d1d6002f-8075-4c3c-b572-14d14db874b8
That seems to be correct! It doesn’t show a value there, didn’t notice that before 
How old is your M3? Perhaps it’s related to FW or hardware.
I will add a check to skip not existing units…
Version 4.4.7 is ready to test 
It seems I should pass battery range to the widget is estimated range is not available 
Can you check v4.4.8 if the “ideal battery range” is shown?
Hello,
Is there a way to implement more capabilities in flow ? I’d love for example to adjust the car heating? Thank you
What exactly do you mean? Climate heating is available in climate device. Add it in addition to car device.
Battery heating (if that was meant) is not available via API.
Sorry I didn’t know i needed to add a new device and then choose climate. Sorted
I splitted the features/data across some child devices to get better overview in app details or when searching flow cards. So tale also a look at location device.
Hi Ronny,
I have used this app already for a long time and have been very happy with it. It runs stable and gives me the option to fully automate the authentication of my charging station.
However since 22nd of august I do not recieve any new data. I already tried to restart the app, did a new login on the tesla portal via the repair function, but to no avail.
Looking at the developer.tesla.com website I seem to still have lots of calls left. I also see that my homeassistant integration is still pulling data.
Can you help me diagnose the issue? f555fe6e-12bf-4b2b-a45a-f6812657356f
Can you please check the devcie settings? Is only BLE active or also FleetAPI?
Based on the log it looks like the app is trying to connect via BLE, but that never finishes.
This is causing the app hang in active polling state, so other pollings are not executed.
Just looking at the Homey FW changlog it seems, there are some BLE bugs in 13.4.x
Changelog for 13.5.0 rc4 (test version only):
BLE
- Fixes a number of issues that could cause BLE to stop working as expected until a reboot is performed.
So first try a Homey restart. If BLE stills hangs, try to deactivate BLE.
Or best: activate Telemetry and deactivate polling 
That’s much cheaper and you get realtime updates.
