Open bulfinch opened 3 weeks ago
Disregard. It was an ip address typo in /etc/rc.local. After a reboot of the server the connection was lost.
We should add a test to the verify.sh
script to confirm connection to the 192.168.91.1 TEDAPI endpoint.
I updated verify.sh which now gives a basic test of the connectivity and mode for TEDAPI if set up:
To test, you can run upgrade.sh
or just git pull
to fetch verify.sh.
verify.sh now displays
Checking pypowerwall
----------------------------------------------------------------------------
- Config File pypowerwall.env: GOOD
- Container (pypowerwall): GOOD
- Service (port 8675): GOOD
- Version: 0.10.8 Proxy t63
- Powerwall State: CONNECTED - Firmware: 24.12.3
- Site Name: Vault 73
- Gateway TEDAPI: Available (192.168.91.1)
- TEDAPI Vitals: Connected - Mode: hybrid
- Cloud Mode: NO
thanks
thanks @bulfinch !
Problem Description After firmware 24.12.03 update, I'm no longer able to get vitals API to work, and the powerwall is no longer found @ 192.168.91.1. I do have the powerwall statically mapped at 192.168.1.114, and it is fond there.
System Details Describe the host system you are trying to use for the Dashboard: x86 Ubuntu
Verify Tool Output