I've been using the VCC feature to measure battery voltage for my remote battery powered BME280 temperature, humidity and pressure device for a few months. The build that last worked (for me) was the ESP_Easy_mega-20180522_test_ESP8266_4096_VCC.bin. Since then, my experience with more recent builds has been that the battery voltage measurement bit seems to work fine but the temper/humidity/press aspects stop communicating with my Domoticz. i.e. Still have good values in my device config. Having tried to update to recent builds, such as ESP_Easy_mega-20180723_test_ESP8266_4096_VCC.bin, and a few preceeding it, seem to have the same problem.
Anyone else finding the same problem? ...or know of a solution.
VCC and BME280 Device Problem on recent builds
Moderators: grovkillen, Stuntteam, TD-er
-
- Normal user
- Posts: 69
- Joined: 18 Mar 2017, 22:13
- Location: Newcastle/UK
-
- New user
- Posts: 5
- Joined: 03 Jan 2017, 07:23
Re: VCC and BME280 Device Problem on recent builds
I'm also having problems with the BME280 sensor output and recent builds (currently ESP_Easy_mega-20180723_dev_ESP8266_4096.bin). The BME280 device values are only updated once after a reboot and then stay static. Also the log doesn't show any sensor readings for the BME280 apart from the one after a reboot.
Tried a different BME280 sensor with the same results.
Tried a different BME280 sensor with the same results.
-
- Core team member
- Posts: 9905
- Joined: 01 Sep 2017, 22:13
- Location: the Netherlands
Re: VCC and BME280 Device Problem on recent builds
Around that time, I made a change to BME280 plugin how the data was read.
Before that change, I2C transfers were done per 8 or 16 bits. But that results in reading data in between measurements.
This resulted in too high temperature readings and too low humidity readings.
That change is to read all measurements related data in 1 run, which results in more accurate readings.
I didn't have issues with hanging communications, but good to know VCC may lead to these issues.
I will add an issue on Github about it and look into it. https://github.com/letscontrolit/ESPEasy/issues/1621
Before that change, I2C transfers were done per 8 or 16 bits. But that results in reading data in between measurements.
This resulted in too high temperature readings and too low humidity readings.
That change is to read all measurements related data in 1 run, which results in more accurate readings.
I didn't have issues with hanging communications, but good to know VCC may lead to these issues.
I will add an issue on Github about it and look into it. https://github.com/letscontrolit/ESPEasy/issues/1621
-
- Normal user
- Posts: 69
- Joined: 18 Mar 2017, 22:13
- Location: Newcastle/UK
Re: VCC and BME280 Device Problem on recent builds
Thanks for looking into it.
The recent builds (none VCC) do work fine on another of my BME280 devices. Seems to be some connection there.
Regards, Rob
The recent builds (none VCC) do work fine on another of my BME280 devices. Seems to be some connection there.
Regards, Rob
RobUpNorth
Who is online
Users browsing this forum: Anthropic Claude Bot [bot], Google [Bot] and 12 guests