The sensor seems to pull a correct reading at boot and always returns this value regardless of modifying the update_frequency or force_update. If you reboot the MTR-1 it will grab a fresh reading and then back to returning that original boot value.

Logs:

[16:56:50][D][sensor:094]: 'LTR390 Light': Sending state 0.00000 lx with 1 decimals of accuracy
[16:56:51][D][ltr390:055]: Waiting for data
[16:56:51][D][ltr390:055]: Waiting for data
[16:56:51][D][ltr390:055]: Waiting for data
[16:56:51][D][ltr390:055]: Waiting for data
[16:56:51][D][ltr390:055]: Waiting for data
[16:56:51][D][ltr390:055]: Waiting for data
[16:56:51][D][sensor:094]: 'LTR390 UV Index': Sending state 0.00000 UVI with 5 decimals of accuracy
[16:56:51][D][sensor:094]: 'ESP Temperature': Sending state 49.80000 °C with 1 decimals of accuracy
[16:56:59][D][sensor:094]: 'Uptime': Sending state 72712.82812 s with 0 decimals of accuracy
[16:57:05][D][sensor:094]: 'DPS310 Temperature': Sending state 64.49789 °C with 1 decimals of accuracy
[16:57:05][D][sensor:094]: 'DPS310 Pressure': Sending state 1006.69940 hPa with 1 decimals of accuracy
[16:57:12][D][sensor:094]: 'RSSI': Sending state -57.00000 dBm with 0 decimals of accuracy
[16:57:35][D][sensor:094]: 'DPS310 Temperature': Sending state 64.54720 °C with 1 decimals of accuracy
[16:57:35][D][sensor:094]: 'DPS310 Pressure': Sending state 1006.70319 hPa with 1 decimals of accuracy
[16:57:50][D][sensor:094]: 'LTR390 Light': Sending state 0.00000 lx with 1 decimals of accuracy
[16:57:51][D][ltr390:055]: Waiting for data
[16:57:51][D][ltr390:055]: Waiting for data
[16:57:51][D][ltr390:055]: Waiting for data
[16:57:51][D][ltr390:055]: Waiting for data
[16:57:51][D][ltr390:055]: Waiting for data
[16:57:51][D][ltr390:055]: Waiting for data

You see the Uptime which says it was last rebooted at night but the room has daylight now.

The non-functional lux meter makes the device pointless for my needs. Willing to perform any additional troubleshooting and logging as necessary.

Errors below in logs after updating to home assistant beta

Entity sensor.apollo_mtr_1_c64a28_target_1_speed (<class 'homeassistant.components.esphome.sensor.EsphomeSensor'>) is using native unit of measurement 'mm/s' which is not a valid unit for the device class ('speed') it is using; expected one of ['Beaufort', 'km/h', 'm/s', 'ft/s', 'mph', 'in/h', 'kn', 'mm/d', 'mm/h', 'in/d']; Please update your configuration if your entity is manually configured, otherwise create a bug report at https://github.com/home-assistant/core/issues?q=is%3Aopen+is%3Aissue+label%3A%22integration%3A+esphome%22
Entity sensor.apollo_mtr_1_c64a28_target_2_speed (<class 'homeassistant.components.esphome.sensor.EsphomeSensor'>) is using native unit of measurement 'mm/s' which is not a valid unit for the device class ('speed') it is using; expected one of ['Beaufort', 'km/h', 'm/s', 'ft/s', 'mph', 'in/h', 'kn', 'mm/d', 'mm/h', 'in/d']; Please update your configuration if your entity is manually configured, otherwise create a bug report at https://github.com/home-assistant/core/issues?q=is%3Aopen+is%3Aissue+label%3A%22integration%3A+esphome%22
Entity sensor.apollo_mtr_1_c64a28_target_3_speed (<class 'homeassistant.components.esphome.sensor.EsphomeSensor'>) is using native unit of measurement 'mm/s' which is not a valid unit for the device class ('speed') it is using; expected one of ['Beaufort', 'km/h', 'm/s', 'ft/s', 'mph', 'in/h', 'kn', 'mm/d', 'mm/h', 'in/d']; Please update your configuration if your entity is manually configured, otherwise create a bug report at https://github.com/home-assistant/core/issues?q=is%3Aopen+is%3Aissue+label%3A%22integration%3A+esphome%22