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

"WP_Status_Betriebszustand" is always 1 #15

Open
optimismus opened this issue Nov 14, 2023 · 1 comment
Open

"WP_Status_Betriebszustand" is always 1 #15

optimismus opened this issue Nov 14, 2023 · 1 comment

Comments

@optimismus
Copy link
Contributor

After deleting the second "Betriebszustand" line the status seems to be always "1":
grafik

@optimismus optimismus changed the title "WP_Betriebszustand" is always 1 "WP_Status_Betriebszustand" is always 1 Nov 14, 2023
@cbrosius
Copy link
Owner

Can you please check again with the new 'WorkInProgress"-branch version?
Maybe there were 2 WP_Status_Betriebszustand.
Seems that Homeassistant does not like the removal of values/channels of an existing device.
I had similar things happen, when I added buttons in the code and removed them again, later.
Inside of HomeAssistant the buttons remain, but do no longer work.

No sure how to reinitialize the ESPHome-Device in HomeAssistant without loosing the history.

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

2 participants