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

Support for Multiple Gateways #148

Open
jasonacox opened this issue Jan 4, 2023 · 11 comments
Open

Support for Multiple Gateways #148

jasonacox opened this issue Jan 4, 2023 · 11 comments
Labels
enhancement New feature or request

Comments

@jasonacox
Copy link
Owner

There are Tesla Solar + Powerwall installations with 400A service connections, where two separate gateways are required. Currently, to get a dashboard, you need to run two instances, representing each gateway. I'm opening this issue to track the addition of support for this setup and the addition of a feature to provide a combined view.

Assumptions:

  • For the primary "Live Monitoring" energy usage graph and the Power Meters, you would want combined data for solar, grid, home and powerwalls.
  • For the power flow animation we would need two instances (side-by-side?)
  • The detail graphs below would likely work best as separate breakouts for each gateway, but let me know what you think.

Originally posted by @jasonacox in #62 (reply in thread)

@jasonacox jasonacox added the enhancement New feature or request label Jan 4, 2023
@nberardi
Copy link

nberardi commented Jan 9, 2023

@jasonacox Hey wanted to let you know that I was able to get this working about 90%. Unfortunately it is a pretty major change, and was easier done in InfluxDB 2.x.

  • Fully working dashboard for individual power walls
  • Live Monitoring and Power Meters is working for combined units
  • The rest is a work in progress for combined units

Happy to give you a preview of my progress, however I am not quite sure how to export InfluxDB 2.x work.

@jasonacox
Copy link
Owner Author

Awesome! Thanks for the update @nberardi ! Feel free to share details (or even screenshots). 😁

What caused you to move to InfluxDB 2.x? I attempted to upgrade and saw that it was a fairly steep breaking change. For example, all the continuous queries need to be converted from QL to Flux and moved to tasks. It also failed to run on older ARM RPis, but that is likely less of an issue now. Would love any tips as part of your effort!

@nberardi
Copy link

nberardi commented Jan 9, 2023

@jasonacox It was actually less of a breaking change than you would expect, and in many respects I was able to eliminate most of the CQ's, and simplify the dashboard queries without loss of functionality.

The only CQ's I kept were autogen and kwh. The others were easily represented as standard queries with aggreateWindow mean queries.

The main reason for the move is that I was going to need to rewrite the entire dashboard to make the powerwall gateway's selectable via a variable, and the QL's were very complex compared to the Flux counter parts for introducing a new filter. I will post what I have in the morning to give you an idea of what changed. But what I have should be backwards compatible.

@jasonacox
Copy link
Owner Author

Awesome! Thanks @nberardi !

@BuongiornoTexas
Copy link
Contributor

Count me in for some beta testing if a move to Flux is afoot!

I'm hoping this will allow for dynamic tracking of ToU billing and valuing internal consumption (at least a lot more easily than this can be done in InfluxQL).

@fasternfaster
Copy link

if you have a fork/branch of the repo to share, i would love to try it out.

@nberardi
Copy link

nberardi commented Feb 27, 2023 via email

@jwvanderbeck
Copy link

Just wondering where this sits? I just had a system finish install today sat my home with split panels so I had to have two gateways and batteries split between my two electrical panels :( Not ideal but wanted to see if this application can help make monitoring easier.

@jasonacox
Copy link
Owner Author

I know there are several in the community who have made this work with quite a bit of customization. Naturally you could se tit up as separate install (someone used separate RPI's) with no change, but that doesn't seem ideal.

If we built multi-PW gateway support, would 2 be enough?

@jwvanderbeck
Copy link

Two gateways is what I have and would seem to be the most common multi-gateway setup for newer homes with split service. I think this is becoming more common in new construction.

@jwvanderbeck
Copy link

jwvanderbeck commented Sep 21, 2024

How would the TEDAPI setup work? Clearly both gateways can't be on the same 192.168.91.1 address
EDIT: Actually it is the same, since they are on their own networks. The only thing that changes is the IP address of the powerwall you use as the bridge.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

5 participants