New test version 4.2.1:
- Fixed ‘Energy Backup’ flow action.
@Lars_Bluhm FYI and test. Thanks for reporting.
New test version 4.2.1:
@Lars_Bluhm FYI and test. Thanks for reporting.
Hi Ronny,
I’ve noticed that from time to time, the telemetry turns itself off; the last time it happened was 4 days ago, as I just realized. I can then turn it back on via the advanced settings.
I noticed this because a Flow didn’t start this morning.
What do you think could be causing this?
Or is something wrong with my settings?
Hi Ronny, looks like it is working! Great enhancement, that helps a lot in my total setup!
I will check it.
That should only happen on app start if there are errors connecting to Telemetry server or send the Telemetry request to Tesla API.
Did you restart the App or Homey? Was internet connection down?
If the app could not initialize Telemetry, then the setting is set to “false” and connection is closed.
I try to add a kind of retry and at least a trigger for errors.
Yes, I definitely restarted the app, but probably only after I noticed it wasn’t working anymore. Yes, I restarted Homey about four days ago; I can see that in the Homey log data. This might be a silly question, but just to be sure: Does telemetry also stop working if Homey is updated? Because then both Homey and the app restart, right?
That would be great
Thank you so much for your efforts and support.
If app or Homey is restarted, all should be ok. The app should revonnect to Telemetty. But in this case, it seems, there was an error during connect. I’m not sure about a reason. It can be a simple network issue. I will check if I can find something in the code.
Any possibility of adding a card that can toggle/set off grid mode for powerwall??
I don’t think so. It seems, only self-powered and tima-based modes is possible.
New test version 4.2.3:
This version addes a retry logic for Telemetry connection on app start.
If connect is not possible, the app tries to connect up to 10 times every 1 minute.
If there is still an error, Telemetry will be deactivated in device settings.
You will get Timeline notifications like this:
There is no specific trigger card. Please activate push messages for this app in timeline settings to get an instant notification. Let’s see if this enough.
This retry only affects the app start (or initial Telemetry connect). If the connect was succesful, and if the connection gets broken, the server connection will be established again automatically.
But if the car stops communication, the Telemetry server can’t see it. The car just pushes messages and you don’t know if the car is offline, asleep or stopped telemetry. This can perhaps happen after a car firmware update. If that happens, the deactivate Telemetry in car device settings, save, activate again. This not only connects to Telemetra server but also sends the Telemetry registration to the car.
Hi RonnyW
That sounds promising—thank you very much![]()
New test version 4.3.0:
This version re-addes the energy meter data to get missing energy data back into Homey Energy.
Using the /calendar_history/ API endpoint (as replacement of deprecated /history/ endpoint), the app is reading the data of today and yesterday to calculate the used energy. Using this data, a virtual meter is filled. The meter_energy capability is providing the data for Homey Energy.
Please check the device data and HomeyEnergy screen (HomeyEnergy should report correct data next day after update). If there are issues with meter data, please report it. Compare Tesla app and Homey app if there are differences. If yes, please check if this can be caused by a timezone offset.
@Lars_Bluhm @Paul_H @Ryan_guinn1 FYI and test
And new test version is installed?
The old values are from the old API endpoint. But the capabilities should be updated now.
If your car is asleep (not to spam the log with telemetry data) you can wait 5min, then send a diagnostics report. Perhapd I can see something.
Yes test version 4.3.0 is running. But the two values have not been changed, since yesterday still 0,34 kWh and 26,92 kWh. I only have the powerwall 2 gateway version1.
New test version 4.3.1:
Hi Ronny,
I have a quick question about the location tile. As you can see in the screenshot, the last update (on the left) was two days ago (July 2, 2026). On the right, it shows the vehicle’s correct location and that it was updated 7 minutes ago today (July 4, 2026).
How is this possible, or what’s causing it?
It really confuses me every time, because I always think the location might not have been updated.
Do I need to adjust something in the settings?
App Vers: V 4.3.1
HP23, Vers. 13.4.0-rc.2
Thank you very much for your efforts and quick response.
I think that’s an issue when using Telemetry data. A data request returns a whole set of data, Telemetry only one field. Perhaps I missed something while adding Telemetry. I’ll check what’ missing next days.
New test version 4.4.0: