Skip to content
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

Error - Firmware 241203 detected - Does not support vitals API - disabling. #501

Open
bulfinch opened this issue Jul 11, 2024 · 5 comments
Labels
troubleshooting Help setup or fix an installation

Comments

@bulfinch
Copy link

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

Verify Powerwall-Dashboard 4.4.5 on Linux - Timezone: America/Los_Angeles
----------------------------------------------------------------------------
This script will attempt to verify all the services needed to run
Powerwall-Dashboard. Use this output when you open an issue for help:
https://github.com/jasonacox/Powerwall-Dashboard/issues/new


Checking pypowerwall
----------------------------------------------------------------------------
 - Config File pypowerwall.env: GOOD
 - Container (pypowerwall): GOOD
 - Service (port 8675): GOOD
 - Version: 0.10.8 Proxy t63
 - Powerwall State: CONNECTED - Firmware Version: 24.12.3
 - Cloud Mode: NO

Checking telegraf
----------------------------------------------------------------------------
 - Config File telegraf.conf: GOOD
 - Local Config File telegraf.local: GOOD
 - Container (telegraf): GOOD
 - Version: Telegraf 1.28.2 (git: HEAD@8d9cf395)

Checking influxdb
----------------------------------------------------------------------------
 - Config File influxdb.conf: GOOD
 - Environment File influxdb.env: GOOD
 - Container (influxdb): GOOD
 - Service (port 8086): GOOD
 - Filesystem (./influxdb): GOOD
 - Version: InfluxDB shell version: 1.8.10

Checking grafana
----------------------------------------------------------------------------
 - Config File grafana.env: GOOD
 - Container (grafana): GOOD
 - Service (port 9000): GOOD
 - Filesystem (./grafana): GOOD
 - Version: Grafana CLI version 9.1.2

Checking weather411
----------------------------------------------------------------------------
 - Container (weather411): GOOD
 - Service (port 8676): GOOD
 - Weather: {"temperature": 63.37}
 - Version: 0.2.3

All tests succeeded.

@bulfinch bulfinch added the troubleshooting Help setup or fix an installation label Jul 11, 2024
@bulfinch
Copy link
Author

Disregard. It was an ip address typo in /etc/rc.local. After a reboot of the server the connection was lost.

@jasonacox
Copy link
Owner

We should add a test to the verify.sh script to confirm connection to the 192.168.91.1 TEDAPI endpoint.

@jasonacox
Copy link
Owner

I updated verify.sh which now gives a basic test of the connectivity and mode for TEDAPI if set up:

image

To test, you can run upgrade.sh or just git pull to fetch verify.sh.

@bulfinch
Copy link
Author

bulfinch commented Jul 12, 2024

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

@jasonacox
Copy link
Owner

thanks @bulfinch !

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
troubleshooting Help setup or fix an installation
Projects
None yet
Development

No branches or pull requests

2 participants