letscontrolit / ESPEasy

Easy MultiSensor device based on ESP8266/ESP32
http://www.espeasy.com
Other
3.26k stars 2.21k forks source link

MLX90614 not working after ESPEasy_mega-20200310 #4149

Closed whatsupskip closed 2 years ago

whatsupskip commented 2 years ago

Checklist

I have...

Steps already tried...

If you self compile, please state this and PLEASE try to ONLY REPORT ISSUES WITH OFFICIAL BUILDS!

Summarize of the problem/feature request

I found the same behaviour as raised in this forum discussion: https://www.letscontrolit.com/forum/viewtopic.php?t=8209 Changing the lower I2C clock didn't change anything.

Expected behavior

Current versions should show the "correct" temperature.

Actual behavior

The only temperature reported was 1037.

Steps to reproduce

  1. Just using the default ESP_Easy_mega_20220616_normal_ESP8266_4M1M.bin
  2. Power cycling didn't solve the problem.
  3. It did work correctly in ESP_Easy_mega-20200310_normal_ESP8266_4M1M.bin

System configuration

Hardware: Wemos D1 mini clone on USB power.

ESP Easy version:

ESP Easy settings/screenshots:

Rules or log data

TD-er commented 2 years ago

The title suggests it has been broken for over 2 years. Was that just the previous build you used, or did you backtrack versions until it worked again?

whatsupskip commented 2 years ago

Thanks for your help with this.

I have now just tested ESP_Easy_mega_20211224_normal_ESP82664M1M.bin and realised I did have the EMONCMS controller configured, but not enabled. Also I had a "-" character in the name. After deleting the EMONcms controller, enabling Force Slow I2C speed and changing the "-" character to "". It reported the correct temperature.

I now have it working correctly with ESP_Easy_mega_20220616_normal_ESP8266_4M1M, Force Slow I2C speed enabled and no controller configured or enabled. Without the Force Slow I2C speed enabled it does show the incorrect temperature (1037.5). A couple of times with Force Slow I2C speed enabled I did see the 1037.5 flash, but that could be a browser caching issue.

TD-er commented 2 years ago

Maybe this sensor needs some tweaking of the "clock stretching" setting on the tools->Advanced page?