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
The serves as a page to track compatibility of sensor cross-referencing in API and CLI flex model fields. That is, which fields already support pointing to a sensor:
I'd start with storage-efficiency, as this is usually very much dependent on ambient temperature, and is important in the context of heat modelling.
Then I'd treat soc-maxima, soc-minima and soc-targets as one ticket, as they are very similar.
The soc-at-start is a bit more tricky, because it is somewhat entangled with the concept of the schedule's start time. But yes, it would be next.
I imagine that after the implementation of soc-maxima and soc-minima as sensors, there is no longer any need to be able to implement soc-max and soc-min as sensors, too. If you agree, I'll add notes to the table, accordingly.
The serves as a page to track compatibility of sensor cross-referencing in API and CLI flex model fields. That is, which fields already support pointing to a sensor:
Similarly, for flex context fields:
The text was updated successfully, but these errors were encountered: