Here’s a very basic device handler for the Tesla Powerwall II
It will show you charge level and the current power for grid, site, solar and Powerwall.
It requires a FQDN for your Powerwall, because SmartThings is a PITA about allowing direct access via IP addresses unless you also write a device handler app - and I lost the will to live trying to decipher the awful documentation on doing this. Someone that knows what they are doing could probably sort this out really quickly.
The SmartApp simply sends you a push notification when the charge level goes through configurable upper or lower limits, with the simple purpose of alerting you when the battery is full so that you can turn something on to make use of excess solar. The SmartApp could be easily modified to switch a load on and off for you in response to charge levels.
This is great, thank you Robin. I’m still waiting for my PW to be installed so can’t make use of this quite yet however my plan is to pull the solar generation and PW % (Charging/discharging) to display on a LaMetric device. I’m assuming the DH will give me access to those parameters?
In the UK it will be limited to 3.5kW, unless you get a G59 approval from the local grid company.
Even then, you will not get over about 5.7 in real power.
If you have more than one PW they are all connected to the same gateway, and the storage capacity is increased. You’ll have to check with your installer if you can install to give a higher output. There are issues with interference and messing up the AC supply phase.
I miss the luxury of 240V * everywhere * in the UK, if you even have a slight hobby for power tools or power amps for A/V, then it becomes a struggle on 120V with the majority of outlets limited to 15A…
It was just http, they may have changed it to https now. However if your hub and the PW are on the same network then it’s only a local call, no port forwarding required. If you do need to open it up to external access at the very least put a remote IP address restriction on it, as you can turn a PW on and off and work out what the system password is without any authentication.
Hi Robin, does this still work following the latest 1.22.1 PW firmware upgrade? I can pull stats using domain:port so know connectivity is ok but despite that the app is unable to display any data. Could they have altered the api calls?
Tesla introduced a self-signed certificate to achieve a HTTPS connection. Unfortunately the Groovy language doesn’t support calls that use self signed certificates. I asked Tesla about doing it in a better way to allow continued access and they weren’t interested (putting it politely). So it will need a workaround using an app on another device (Raspberry Pi is a possibility) to fetch the data and pass it to SmartThings.
Not sure if they are all the same, but I noted that the hub they connected to my router has a zigbee address. Can’t see it on a search, but maybe some hope for a more natural integration?
