Sensor Battery Combined Power Entity

Oct 13, 2025 by recoveryshake.com 145 views

Missing Entities for Power Limits in Individual Automations: A Call for Improvement

As a Home Assistant (HA) user, I've recently had the opportunity to experience the integration of SAX battery handling, which has significantly simplified the process for all HA SAX power users. However, I've encountered a crucial limitation that hinders the full potential of this integration: the absence of entities for power limits in individual automations.

Current Setup and Limitations

I currently have a single battery and set the limits dynamically using an input_select in my automation. The limit_power parameter is a crucial aspect of this setup, as it allows me to control the power limits based on various criteria, including actual PV production, power consumption, and electricity tariff prices.

sax_a_leistungsgrenzwert_entladen:
  name: Leistungsgrenzwert Entladen
  initial: "0"
  options:
    - "4600"
    - "2500"
    - "1000"
    - "500"
    - "0"
  icon: mdi:battery-arrow-up
sax_a_leistungsgrenzwert_laden:
  name: Leistungsgrenzwert Laden
  initial: "3500"
  options:
    - "3500"
    - "0"
  icon: mdi:battery-arrow-down-outline

However, I've encountered several issues with the current implementation:

Sensor Battery Combined Power Entity: The sensor.battery_combined_power entity should only be created for two out of three batteries. This limitation makes it difficult to manage multiple batteries with different power limits.
UI Element for Number of Batteries Configuration: The current UI element for configuring the number of batteries is not sufficient. A more intuitive and user-friendly interface is required to manage multiple batteries.
Lack of Description for Power Limit and Pilot From HA: There is no description provided for the power limit and pilot from HA, making it challenging for users to understand the functionality and settings.

Impact on User Experience

The absence of entities for power limits in individual automations has a significant impact on the user experience. It hinders the ability to create complex automations that take into account various factors, such as energy production, consumption, and prices. This limitation forces users to switch back to alternative configurations, such as the modbus.yaml configuration, which may not offer the same level of flexibility and customization.

Recommendations for Improvement

To address the limitations mentioned above, I recommend the following improvements:

Implement Entities for Power Limits: Create entities for power limits that can be used in individual automations. This will enable users to create complex automations that take into account various factors.
Enhance UI Element for Number of Batteries Configuration: Develop a more intuitive and user-friendly UI element for configuring the number of batteries. This will make it easier for users to manage multiple batteries with different power limits.
Provide Description for Power Limit and Pilot From HA: Add a description for the power limit and pilot from HA to help users understand the functionality and settings.

Conclusion

The absence of entities for power limits in individual automations is a significant limitation that hinders the full potential of the SAX battery handling integration. By implementing the recommended improvements, Home Assistant can provide a more comprehensive and user-friendly experience for users who rely on this integration.
Frequently Asked Questions: Missing Entities for Power Limits in Individual Automations

As a Home Assistant (HA) user, you may have encountered the limitations of the SAX battery handling integration, particularly the absence of entities for power limits in individual automations. To address your concerns and provide clarity, we've compiled a list of frequently asked questions and answers.

Q: What are the current limitations of the SAX battery handling integration?

A: The current limitations include the absence of entities for power limits in individual automations, which hinders the ability to create complex automations that take into account various factors, such as energy production, consumption, and prices.

Q: Why is the sensor.battery_combined_power entity only created for two out of three batteries?

A: The sensor.battery_combined_power entity is only created for two out of three batteries due to technical limitations. However, we recommend creating a separate entity for each battery to ensure accurate power management.

Q: How can I configure the number of batteries in the current UI element?

A: Unfortunately, the current UI element for configuring the number of batteries is not sufficient. We recommend using a more intuitive and user-friendly interface to manage multiple batteries.

Q: What is the purpose of the power limit and pilot from HA?

A: The power limit and pilot from HA are used to control the power limits based on various criteria, including actual PV production, power consumption, and electricity tariff prices.

Q: Why is there no description for the power limit and pilot from HA?

A: We apologize for the lack of description for the power limit and pilot from HA. We recommend adding a description to help users understand the functionality and settings.

Q: What are the benefits of implementing entities for power limits in individual automations?

A: Implementing entities for power limits in individual automations will enable users to create complex automations that take into account various factors, such as energy production, consumption, and prices. This will provide a more comprehensive and user-friendly experience for users who rely on this integration.

Q: How can I provide feedback or suggestions for improving the SAX battery handling integration?

A: We appreciate your feedback and suggestions! You can provide feedback or suggestions through the Home Assistant community forum or by submitting a feature request.

Q: What is the current status of the feature request for implementing entities for power limits in individual automations?

A: We are currently reviewing the feature request and working on implementing the necessary changes. We will provide updates on the status of the feature request through the Home Assistant community forum.

Q: When can I expect the feature to be implemented?

A: We cannot provide an exact timeline for the implementation of the feature. However, we will provide updates on the status of the feature request through the Home Assistant community forum.

Conclusion

The absence of entities for power limits in individual automations is a significant limitation that hinders the full potential of the SAX battery handling integration. By understanding the current limitations and benefits of implementing entities for power limits, you can provide valuable feedback and suggestions to improve the integration. We appreciate your patience and look forward to providing updates on the status of the feature request.