home-assistant / core

:house_with_garden: Open source home automation that puts local control and privacy first.
https://www.home-assistant.io
Apache License 2.0
74.11k stars 31.11k forks source link

APCUPSd Binary sensor reports "off" when UPS status is "TRIM ONLINE" #22631

Closed DoctorOctagonapus closed 5 years ago

DoctorOctagonapus commented 5 years ago

Home Assistant release with the issue:

0.90.2 **Last working Home Assistant release (if known):** N/A **Operating environment (Hass.io/Docker/Windows/etc.):** HassOS 2.11 on Raspberry Pi 3B+ **Component/platform:** apcupsd (specifically the binary_sensor component) **Description of problem:** APSUPSd binary sensor is configured to report an "on" state when UPS status is "ONLINE", however if the UPS reports a status of "TRIM ONLINE" (i.e. compensating for high input voltage), the binary sensor reports an "off" state even though there is still a mains power supply and it is not running on battery. Is it possible to reconfigure the sensor so it will ignore a TRIM status or so that it will stay reporting "on" whenever the UPS is not on battery? **Problem-relevant `configuration.yaml` entries and (fill out even if it seems unimportant):** ```yaml apcupsd: host: [IP ADDRESS] binary_sensor: - platform: apcupsd name: "AC Power" ``` **Traceback (if applicable):** ``` N/A ``` **Additional information:** UPS model is an APC Smart-UPS 750 connected to another device.
stale[bot] commented 5 years ago

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue now has been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

DoctorOctagonapus commented 5 years ago

Still awaiting response from the developers

stale[bot] commented 5 years ago

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue now has been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.