-
Notifications
You must be signed in to change notification settings - Fork 289
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
improve DS1820 logging #1394
improve DS1820 logging #1394
Conversation
Hey, is it tested and ready to merge? |
The fix was not needed (turned out to be another issue), but we might keep the updated logging. I can't do some tests now, will report back in some days. |
I can test, but any test in particular? Just connect up and post some cmd logs? |
Thanks, it's indeed just checking the logs, if all hex values are now in the same format 0xXX (always two values after 0x) |
Does negative temperature works alright in the latest builds? I have a battery sensor with waterproof DS18B20 cable soldered onto it (so probably a clone), but in HA, for the last several days, every temperature reading reported is -0.01. |
BK-N.txt
|
@NonPIayerCharacter: I'll check again but negative temperatures should work. @divadiow thanks for testing, this should be enough, logs aren't depending on the platform |
|
@divadiow could you please check again, if log of negative temperatures is better now? |
1394_merge_c5cfa0c6b801
|
:-( will try again later with a little more time... |
55e2066
to
c505156
Compare
New PR #1416 |
Have you been able to fetch some more information? I think it might also be an issue if reading the sensors temperature failed, because in this case the last read value is kept and will be sent repeadtedly, even for days. We maybe should "invalidate" the temperature after some time, which has to be defined: Maybe 5 minutes? or even one minute? Can (how) MQTT handle "invalid" or non present values? |
No description provided.