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

Do not throw an error if heater/cooler entity is not yet available on startup #172

Merged
merged 1 commit into from
Feb 14, 2024

Conversation

Chupaka
Copy link
Contributor

@Chupaka Chupaka commented Oct 15, 2023

There can be troubles when optimistically convert state value to float:

float(self.hass.states.get(self.heater_or_cooler_entity).state)

Fixes #170

@Chupaka Chupaka changed the title Do not throw error if heater/cooler entity is still not available on startup Do not throw an error if heater/cooler entity is not yet available on startup Oct 23, 2023
@Chupaka
Copy link
Contributor Author

Chupaka commented Nov 27, 2023

@ScratMan any thoughts?..

@ScratMan ScratMan merged commit a3720ef into ScratMan:master Feb 14, 2024
2 checks passed
@Chupaka Chupaka deleted the patch-1 branch February 15, 2024 10:51
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

Successfully merging this pull request may close these issues.

Error at startup with valve. PID P stays 0 from debug
2 participants