-
-
Notifications
You must be signed in to change notification settings - Fork 29.6k
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
min_max doesn't wait for template entities to be ready #41931
Comments
min_max documentation |
have we had some recognition of this issue yet?
the lines in the error have changed so that's why I ask and report the error once more. Additional info: this also happens upon reload of template entities (because that's what the min-max sensor uses in my config). |
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. |
0n 2021.1.5 and haven't seen the error for some time now |
and they're back, probably simply missed it before:
happening after each reload of the template entities. template sensors havent changed, nor has the min_max sensor this is on HA 2021.2.1 now |
so we are on 2021.3.4 and on each restart/reload of templates this error returns. consider the error catch in the integration is
I have availability_templates on all relevant sensors:
and still the error persists. Please help me sort this? |
keeping this alive before it is declared stale.. |
@frenck sorry for the tag, but since this has been around for half a year now, could you please help me get some attention for the issue? |
Please don't tag @Mariusthvdb, you know better. |
wow, very helpful. thanks. |
Hey Frenck, what's up.. I excused myself for the tag in advance, and merely asked for help. Literally. What more need polite users do not to offend you. a much friendlier answer could have been: ‘o sorry mariusthvbd, we skipped that one, lets have a look, it will take some more time, but you got our attention. Won't tag you again, and again sorry for that. |
☝️ For full transparency, attached a screenshot of the message you accused me of scrutinizing you. Which was more a general warning. I'm happy to do the warning publicly as well. You are around long enough to know that it is not appreciated to pull people into the conversation. (As made clear on how you started the ping in the first place). My comment on private in Discord was meant to directly instead of putting out a warning here in public, just because you are around for a long time. But if you want it public this way, that is fine too. There are many issues open and things rely on contributions. I don't have time for more contributions at this point as I'm already swamped with things I still need (well want) to do. So I'm not sure what you expected to happen? Really, as with all issues and PRs open, if anybody wants something to move faster, help out! |
tbh, I would hope for senior dev's that aren't happy to scrutinize people at all, privately or publicly. What I expected was some help 'getting this some attention', not for you to solve it in any way, right away. Also, since you yourself were already in this conversation since oct 2020, I didnt think the harmless tag would be very 'impolite'. I can see through the unnecessary abusive words you use, and do understand you don't want to be tagged al day long, by anyone, and I respect that. Goes without saying. So, I don't want a warning at all, I expect some mutual respect, because that has 2 be bi-directional. Enough said. I'll be glad to have a go at the issue at hand, but, I would need guidance and help for that. I would rather close this because of the discussion on the matter of the tag, but the core issue is still open, so I can't. Hope to clear the air with this. |
This is no longer about this issue at this point. There was no scrutinizing, only a warning on behavior we generally don't appreciate. It is documented within our community as well. There is nothing personal about that, it just not helpful. Some devs turned of mention notifications because of it, which is even a worse outcome as communication becomes hard. Just... don't do it, please 🙏
I added a label to help categorizing issues, I did not take part in the conversion.
Just don't tag at random, thanks 👍
We have our developer documentation to help you get started, if you have additional questions, we have developer channels on Discord for that 👍 |
ok thanks. please don't let it die here, it is a nasty issue, which I, with the knowledge in templating and None type that I have right now, can't solve. |
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. |
The problem
At startup, the min_max integration throws errors on entities which are template sensors. After startup, the integration does its job alright, and creates the ( in this case) average temperature based on the configuration
Environment
Problem-relevant
configuration.yaml
these calibrated sensors are based on the core HUE sensors:
Traceback/Error logs
Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/helpers/event.py", line 254, in _async_state_change_dispatcher hass.async_run_job(action, event) File "/usr/src/homeassistant/homeassistant/core.py", line 384, in async_run_job target(*args) File "/usr/src/homeassistant/homeassistant/components/min_max/sensor.py", line 164, in async_min_max_sensor_state_listener if new_state.state is None or new_state.state in [ AttributeError: 'NoneType' object has no attribute 'state'
Additional information
happening on reload of template entities too
The text was updated successfully, but these errors were encountered: