You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In, #119, we realized that in order to utilize multiple TEGs (Tesla Energy Gateways), the CQ queries need to change, and they will need to adapt to what TEGs (Tesla Energy Gateways) the user has installed in their system.
Right now these queries are written assuming a single TEG, but given that some metrics (mainly strings and alerts among others) will need to be individualized to the gateways, this needs to evolve.
I propose using Jinja2 or another Python-friendly templating engine to generate these, with an input file that characterizes the topology of the system. It will be much, much easier to dynamically generate these (and/or have a few pre-generated templates for the most common setups), then to rely on a hand-hacked bespoke SQL query file.
The text was updated successfully, but these errors were encountered:
In, #119, we realized that in order to utilize multiple TEGs (Tesla Energy Gateways), the CQ queries need to change, and they will need to adapt to what TEGs (Tesla Energy Gateways) the user has installed in their system.
Right now these queries are written assuming a single TEG, but given that some metrics (mainly strings and alerts among others) will need to be individualized to the gateways, this needs to evolve.
I propose using Jinja2 or another Python-friendly templating engine to generate these, with an input file that characterizes the topology of the system. It will be much, much easier to dynamically generate these (and/or have a few pre-generated templates for the most common setups), then to rely on a hand-hacked bespoke SQL query file.
The text was updated successfully, but these errors were encountered: