-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
v0.10.0 - New Device Vitals #95
Conversation
Getting close to ready to release. I have tested How to test using Powerwall-Dashboard First, you need to set up the host that will run your Dashboard to have a route to your Powerwall Gateway. This varies based on the OS, but will be something like this: # Change 10.x.x.x to the address of your Powerwall on your LAN
sudo ip route add 192.168.91.0/24 via 10.x.x.x
# Note: This is a temporary route. To make it survive a reboot, you need to set it in the system
# or add it to something like /etc/rc.local Edit the
Edit
Apply the changes using: ./compose-dash.sh up -d
# and to tail the logs... ^C to quit
docker logs pypowerwall -f |
Latest: jasonacox/pypowerwall:0.10.0t58-beta9 |
Device Vitals via TEDAPI
Updates
/tedapi
API access on Gateway (requires connectivity to 192.168.91.1 GW and Gateway Password) with access to "config" and "status" data./vitals
API and payload using the new TEDAPI class. This allows easy access to Powerwall device vitals.PW_GW_PWD
for Gateway Password in preparation for onboarding into Powerwall-Dashboard - Test (beta) proxy available for power users:powerwall.yml
and usejasonacox/pypowerwall:0.10.0t58-beta6
pypowerwall.env
and editPW_HOST
and addPW_GW_PWD
sudo ip route add 192.168.91.0/24 via <Powerwall_LAN_IP>
Coding Examples
Related Issues and Discussions: