VEML7700 and VEML6030 light sensors

[latonita]

What does this implement/fix?

Implements component for ambient light sensors from Vishay - VEML7700 and VEML6030

Types of changes

• Bugfix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Other

Related issue or feature (if applicable): fixes
esphome/feature-requests#2493
esphome/feature-requests#218
esphome/feature-requests#1915

Pull request in esphome-docs with documentation (if applicable): esphome/esphome-docs#3525

Test Environment

• ESP32
• ESP32 IDF
• ESP8266
• RP2040
• BK72xx
• RTL87xx

Example entry for config.yaml:

# Example config.yaml
esphome:
  name: veml7700-test

esp32:
  board: esp32dev
  framework:
    type: arduino

# esp8266:
#   board: nodemcuv2

logger:
  level: DEBUG

i2c:

sensor:
  - platform: veml7700
    address: 0x10
    update_interval: 30s
    # lux_compensation: false
    # glass_attenuation_factor: 1.10
    # auto_mode: false
    # gain: 1x
    # integration_time: 100ms
    ambient_light:
      name: "Ambient light"
    full_spectrum:
      name: "Full spectrum"
    infrared:
      name: "Calculated Near-IR"
    actual_integration_time:
      name: "Actual integration time"
    actual_gain:
      name: "Actual gain"
    # ambient_light_counts:
    #   name: "Ambient light counts"
    # full_spectrum_counts:
    #   name: "Full spectrum counts"

Checklist:

• The code change is tested and works locally.
• Tests have been added to verify that the new code works (under tests/ folder).

If user exposed functionality or configuration variables are added/changed:

• Documentation added/updated in esphome-docs.

[probot-esphome]

Hey there @latonita,
Thanks for submitting this pull request! Can you add yourself as a codeowner for this integration? This way we can notify you if a bug report for this integration is reported.
In __init__.py of the integration, please add:

CODEOWNERS = ["@latonita"]

And run script/build_codeowners.py

_{^{(message by NeedsCodeownersLabel)}}

[codecov-commenter]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 53.50%. Comparing base (4d8b5ed) to head (0dbda99).
Report is 89 commits behind head on dev.

Additional details and impacted files

@@            Coverage Diff             @@
##              dev    #6067      +/-   ##
==========================================
- Coverage   53.70%   53.50%   -0.21%     
==========================================
  Files          50       50              
  Lines        9408     9515     +107     
  Branches     1654     1683      +29     
==========================================
+ Hits         5053     5091      +38     
- Misses       4056     4117      +61     
- Partials      299      307       +8     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[jesserockz]

Thank you for your contribution.

I got as far as wait_for_device and decided to stop reviewing there as it will need quite a bit of reworking to be accepted in.

Please take a look at my comments below.

[esphome]

Please take a look at the requested changes, and use the Ready for review button when you are done, thanks 👍

Learn more about our pull request process.

[mrtoy-me]

Hi @latonita
I have tested the component on veml6030 seems to work fine ... but I will do some more testing overnight and let you know if I pick up anything.

Two suggestions I have
1.
I was getting some compile warnings around the packed ConfigurationRegister for IntegrationTime ALS_IT relating to gcc4.4
From what I have read, it related to the compiler complaining about the packed structure crossing a type boundary with uint8_t.
In the .h file, I changed enum IntegrationTime : uint16_t rather than uint8_t and no more warnings :) - makes no difference to packed structure anyway.
2.
There are plenty of ESP_LOGD messages in the component and I can understand why they are there when you were debugging but now it is working it makes the logs pretty noisy - I changed all the ESP_LOGD to ESP_LOGV so you can get the messages as verbose if you want and in debug there are enough messages on what values are being sent.

They are minor changes so I didn't do a PR to you, but I think they are worth you considering.

Anyway thanks a lot for developing the component - great work.

[latonita]

@mrtoy-me thanks for taking a look and testing

1. I don't believe its a good thing, it just a hack which works due to specific bit positions in the struct. Stupid compilation note from the GCC drives people craze since 2010... Moreover another GCC bug doesn't let to suppress this with #pragma GCC diagnostic ignored "-Wxxxxx" :) It was fixed in 2022 in GCC 13, but extensa-gcc is based on gcc8 i believe.
   What works properly is #pragma pack(push), #pragma pack(1) ..... #pragma pack(pop) but this was removed by request from @jesserockz .
2. Good catch, thanks! I actually forgot to change them to LOGV. Fixed.

[kbx81]

LGTM -- thanks for working on this!

Changes applies

[latonita]

LGTM -- thanks for working on this!

Thanks. There are several more PRs to review! :)