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
Latest version as of today, and lates opeHasp firmware as of today.
Configuration
N/A
Describe the bug
When you add a plate to HA, de-select the dim when idle setting, add the device to your configuration.yaml file, restart HA. Everything comes up fine, however, the panel still dims on idle, and turns off on long idle! Checking the setting in HA, the checkbox for dim is selected. Uncheck, click save, HA reports setting saved, but when you check the box is selected again and the panel still dims on idle.
unfortunately makes this integration unusable :(
Dim on idle should be handled by automations! so a sensor for idle should be added and used ideally. or just remove this "feature" for now.
Thanks!
Debug log
N/A
The text was updated successfully, but these errors were encountered:
Yes, we need to be able to disable the different idle events individually or just globally.
I'm fiddling with a custom code proximity sensor implementation and needed a solution for this.
So I've made a crude openHASP CC light.py hack to identity a single openHASP nodename and exclude idle off events specifically for this single device only.
Version of the custom_component
Latest version as of today, and lates opeHasp firmware as of today.
Configuration
N/A
Describe the bug
When you add a plate to HA, de-select the dim when idle setting, add the device to your configuration.yaml file, restart HA. Everything comes up fine, however, the panel still dims on idle, and turns off on long idle! Checking the setting in HA, the checkbox for dim is selected. Uncheck, click save, HA reports setting saved, but when you check the box is selected again and the panel still dims on idle.
unfortunately makes this integration unusable :(
Dim on idle should be handled by automations! so a sensor for idle should be added and used ideally. or just remove this "feature" for now.
Thanks!
Debug log
The text was updated successfully, but these errors were encountered: