-
-
Notifications
You must be signed in to change notification settings - Fork 115
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
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
Template variable warning: 'dict object' has no attribute 'temp' #888
Comments
There was a whole thread about this in #466 85 is indeed an invalid reading, typically from cheaper DS18B20 clones. I thought in EMS-ESP we filter them out and don't send the MQTT payload but I couldn't find it in the code (@MichaelDvP do you remember?) |
@proddy You have already referenced #466. As harvey637 wrote, 85°C is a sign of underpower. But it is in the valid range, so we dont filter it. The guy in #466 have used parasite sensors, but i think not enabled parasite powering. (instead lower pullups). I guess this case is similar, the sensor reports one/some 85 values and then gives error. After 5 errors in row the sensor is removed. But without any information about the system it's only a guess. |
thanks @MichaelDvP . Your brain is like an elephant. Can you take this one? |
Ok, as far as i see we only need a
to remove the broken sensor from HA. (as for device values). |
in dev-16 |
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
I'm using EMS-ESP v3.4.4 with MQTT auto-discovery in Home Assistant. When a Dallas sensor reports 85,0 °C, the value is not available in the MQTT payload, and Home Assistant reports a warning:
Ideally the
temp
attribute should be set to the value of the Dallas sensor (85,0 °C
), or it could even be set tonull
to report to Home Assistant that no valid temperature is available.The text was updated successfully, but these errors were encountered: