Enable deep sleep (standby) for VL53L0X

[AIexBV]

Description:

The VL53L0X sensor draws approx. 20 mA which is to much for battery driven applications. This change switched the sensor into the standby mode if deep sleep applies. This reduces the current down to some µAmps.

Related issue (if applicable): fixes # n.a.

Checklist:

• The pull request is done against the latest development branch
• Only relevant files were touched
• Only one feature/fix was added per PR and the code change compiles without warnings
• The code change is tested and works with Tasmota core ESP8266 V.2.7.8
• The code change is tested and works with Tasmota core ESP32 V.3.1.0.241030
• I accept the CLA.

NOTE: The code change must pass CI tests. Your PR cannot be merged unless tests pass

[barbudor]

Why?
It doesn't save neither memory nor code

[AIexBV]

Using integer implies integer values can occur. But this is clearly a true/false situation. There are some other bool variables in the code. Why do you see a difference here?

[barbudor]

We are maximizing the use of "sized int" as much as possible because we control the implementation size.
With bool I'm unsure if this is being implement as a single byte or as an int which takes up 4 bytes and may be using more because of alignment.
Can you prove it's using only 1 byte ?

[AIexBV]

Totally agree. Using uint8 is a common way to ensure that only 8 bits are used. To be sure, I checked if bool behaves the same way. And I can confirm it is also only 8 bits.

AddLog(LOG_LEVEL_DEBUG, PSTR("Size of uint8_t: %d"), sizeof(uint8_t));
AddLog(LOG_LEVEL_DEBUG, PSTR("Size of bool: %d"), sizeof(bool));
AddLog(LOG_LEVEL_DEBUG, PSTR("Size of variable 'ready': %d"), sizeof(Vl53l0x_data[i].ready));

[Jason2866]

Still 'bool' used. Please change as for the reason explained.

[joba-1]

bool is more clear and uses less flash - looks like bool wins?

#include <Arduino.h>

uint8_t f;  // or bool...

void setup() {
  f = true;
}

void loop() {
  if (f) {
    Serial.println("true");
  }
  else {
    Serial.println("false");
  }
  f = !f;
  delay(1000);
}

bool
RAM: [= ] 6.5% (used 21320 bytes from 327680 bytes)
Flash: [== ] 18.5% (used 242545 bytes from 1310720 bytes)

uint8_t
RAM: [= ] 6.5% (used 21320 bytes from 327680 bytes)
Flash: [== ] 18.5% (used 242549 bytes from 1310720 bytes)

Probably because afaik in C/C++ integer calculations are done with the natural int of the platform, which may need extra instructions to expand the operands and shrink the results.
Anyways, being more specific generally helps compilers generate better code.