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
Describe the current behavior
The current BinarySensor "Grid Status" does not have a default BinarySensorDeviceClass.
You can select the deviceClass in the Entity Settings, but I think, it should be "Energy" by default.
By having a specific DeviceClass assigned, the BinarySensor can be selected as alert-class in the Area-Card, like shown in this screenshot.
This Icon will be shown, whenever the Sensor is "ON"
Since an alarm should be displayed whenever there's a "problem", I think the logic should be inverted - but this would be something that needs to be done from HomeAssistant.
What should be updated or changed?
The Binary Sensor "Grid Status" should have a default BinarySensorDeviceClass, preferred "Energy"
Home Assistant (please complete the following information):
Home Assistant Core Version: 2024.7.2
solaredge-modbus-multi Version: 2.4.17
Additional context
Add any other context about the request here.
The text was updated successfully, but these errors were encountered:
Describe the current behavior
The current BinarySensor "Grid Status" does not have a default BinarySensorDeviceClass.
You can select the deviceClass in the Entity Settings, but I think, it should be "Energy" by default.
By having a specific DeviceClass assigned, the BinarySensor can be selected as alert-class in the Area-Card, like shown in this screenshot.
This Icon will be shown, whenever the Sensor is "ON"
Since an alarm should be displayed whenever there's a "problem", I think the logic should be inverted - but this would be something that needs to be done from HomeAssistant.
What should be updated or changed?
The Binary Sensor "Grid Status" should have a default BinarySensorDeviceClass, preferred "Energy"
Home Assistant (please complete the following information):
Additional context
Add any other context about the request here.
The text was updated successfully, but these errors were encountered: