Thanks, I’ll try out the new version later today.
I’m struggling with the next thing now, and perhaps you have some insight into it. I’m using an Advanced Flow like this:
But I’m having a hard time detecting that the chargers gets connected to the car. I do get notifications in the timeline, but not with the statuses I assumed. I don’t get any notification that the charger gets “Connected”, but when it starts and stops Charging I get notifications for “Charging” and “Finished”, like:
Am I doing something wrong, or are the states indicated/documented not the same as the states it sends? Or how should I detect that the charger is inserted/connected to the car?
Hi,
Not sure if it helps but did some changes in v1.12.1-test
I can recommend changing to the new
evcharger_charging_state
Cheers
Rune
Do you think it would be possible to change the IP address of the device in the settings because if it changes with DHCP there is no possibility of modifying it. You have to delete it and start adding it again?
No, I still get the wrong value from isConnected. It returns false, even though the car is charging from the TWC.
I also don’t seem to get any good events from connecting a TWC to my Tesla, but I’ll have to investigate that a bit more in a few days.
What I did was to assign that MAC address a fixed IP in the DHCP scope. That way I could configure it once and for all in Homey.
Hi @Rune_Vaernes
Thanks for the great app. I have checked your code because I noticed an issue while connecting my Tesla car to the wall connector and I think that the information which I have can be maybe interesting for you.
I noticed that the status is “Error” in Homey.
While checking your code I saw that the api/1/vitals .evsestatus is checked.
I saw that in this case (my car is charged at this moment at 99%)
In that case the api/v1/vitals is returning for the evsstatus code 7:
Would it make sense that status 7 and status 8 (ConnectedFullyCharged ) have thesame behaviour?
The fun part is that 11 minutes later the status changes to “4”. (Connected and ready) Maybe those statuses can be treated thesame? What do you think?
1 Like
Hi,
Thank you for your suggestion. I’ve looked into it, and I will create a test app with ConnectedFinishedCharging = 7, and we can check if it makes sense. I will also see if I can add the EVChargeState to the timeseries, so we can try to decode the rest of them.
Cheers
Rune
Hi all,
New test version out, soon to go public. Added more around EVSE_State to see if we can decode the missing items.
Cheers
Rune
Hi,
v2.0.1 is in test and published as soon as it’s approved. I’ve added translations for all the supported languages with the help of Gemini 3. If there are translation mistakes send me a PM, post here or fork the project on GitHub and correct them.
Cheers,
Rune
Hi, I discovered that Tesla has added mDNS support for the Gen 3 Wall Connector. I’m currently testing it on v3, but the implementation can be buggy.
If I get mDns to work, the app will automatically discover the TWC and update the IP address if it changes.
Cheers
Hi,
An updated test version of the app is available.
It should work as expected, but there can be odd cases, so if anyone has the time to test the latest test version, please do so and give me feedback.
Cheers
Rune
Hi,
I have tested the app with multiple cases, and everything seems to work correctly.
Updating for v1 or v2 seems to work as intended and the device is still accessible. ‘
I will change the state from Test to Published for the v3 app now.
Cheers
This was not a good idea… suddenly it stopped working. Back to debuging,
Hi,
I found a bug, dropped the publish to live… new test version is out
Cheers
Hi all,
Added the new v3.2.0 with a bug fix. Hope it works… please give feedback 
Cheers
Rune
Hi,
v3.2.0 is published to live, fingers crossed
Cheers
Rune
Update Submitted: v3.2.2 - Improving Connectivity
Version 3.2.2 has been submitted for certification and is currently available in test! This update specifically addresses connectivity issues on recent Tesla Wall Connector firmware versions.
TWC Firmware & Discovery
While Tesla’s own release notes can be sparse regarding network stack changes, I’ve observed that recent firmware updates (specifically 25.10.0 and newer) seem to affect how the Wall Connector broadcasts itself on the network (mDNS). This caused the “Device not found” error for many of you.
The Solution
To ensure you can always connect, regardless of TWC firmware quirks or complex home networks, I have:
-
Restored Manual IP Entry: You can now bypass auto-discovery and enter your IP directly. Perfect if mDNS fails or you have a specific VLAN setup.
-
Hybrid Pairing Flow: A new Start Screen lets you choose between “Search for Devices” (Auto) and “Manual IP”.
-
Full Localization: The entire pairing process is now translated into all 12 supported languages
Cheers
Rune
Hello, it’s still not working on my v3. I tried deleting the device and the application, but that didn’t change anything. Good luck with the solution.
Hi,
Can you please do a “Create Diagnostics Report” from the App ? You can find it under the “cog” wheel.
Cheers
Hi,
Thank you very much for your investment and please find attached the report number 4befc512-ee88-4b65-9490-f09a98988f10.
Have a wonderful holiday season!
Hi,
I’m not sure, but I have experienced issues with the network stack on the actual Homey with certain devices. And a reboot of the Homey often solved that issue. I frequently have it under development when I install/uninstall the app multiple times to test it with a working version, and suddenly the working app stops working correctly; a reboot fixes the issue in most cases.
Cheers
