Closed Bit-River closed 6 years ago
@ChristianKuehnel
Same problem here. This seems to be already fixed upstream in open-homeautomation/miflora#65 . Please switch to miflora version 0.2.
miflora 0.2.0 is included in the 0.61 release (which is being prepared now).
Waiting on local temperatures to drop below zero, upgraded without issue.
You can put it in your freezer to test
Yes there was a bug in decoding the one's complement. Should be fixed in hass 61.
I can confirm that 0.61 can read negative temperatures properly.
Then I close this
This issue has reoccured for me on Hassio v1.0.1 and HA v0.62.1.
That is weird. That issue should have been fixed in version 0.2.0 of the miflora library. We do have tests for negative temperatures.
What was the last valid temperature before the spike? And the next valid temperature after the spike?
To debug this, I need more data, so that I can analyze the problem. Can you please switch on logging for the miflora library, and send me the binary data read from the sensor?
Add this to your configuration.yaml
:
logger:
default: info
logs:
homeassistant.components.sensor.miflora: debug
miflora: debug
My apologies, the update hadn't gone through! I thought it had. Mea Culpa!
I expect all is well. Thanks for this great code!
Hassio: 0.60.1, Miflora plant Sensor
Sensor reads the temperature incorrectly when the value is below zero, the value returned is 655350.
The sensor values return to normal once it has been moved back to a positive temperature area.
How it looks on Grafana: