Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Consider and support "unavailable" power/socket entities #38

Open
amitkeret opened this issue Sep 20, 2024 · 0 comments
Open

Consider and support "unavailable" power/socket entities #38

amitkeret opened this issue Sep 20, 2024 · 0 comments

Comments

@amitkeret
Copy link

I've been using this automation for some time and it's great.

The problem I'm having comes from the fact the state machine does not support a case when the power consumption (or socket) entities become unavailable. In that situation, I think the state machine should switch to unavailable as well.
I have some cards which display entity values, and also monitor and alert if they become unavailable. That doesn't work for the state machine.

See below:
image
The can icon (for an ultrasonic sensor entity) has an alert since it's unavailable.
The dryer comes up as "off" because the state_machine is idle, even though the underlying power entity is unavailable.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant