My mistake or weakness? (ecowitt API integration)

Hi guys, just activated Ecowitt integration using Ecowitt cloud and API keys. It seems that the LUX value is not handled; not received by WD. Is it a my fault or this kind of integration does not provide this feature?
thanks

Is this integration with WD? And, if you have chosen the API route, I presume you do not have a console or gateway that WD can interrogate on the local LAN – which is a lot simpler.

When you say the lux value is not handled by WD, do you get any solar reading at all? What solar units did you choose to upload to Ecowitt?

I have moved from local integration to the cloud integration right today, because of a lot of crashes. Local supports Lux value, it seems not the API. The integration program is provided by WD, and supports both local and API.
Thanks if someone could investigate, maybe simply the Lux field should be added on the WD program that integrates Ecowitt API

You’ll maybe have to contact Brian ([email protected]) direct about that.

EDIT: I bet WD can’t handle the third option Ecowitt offer – foot-candles :wink:

1 fc = 1 lm/ft2 = 0.006944 lm/in2 = 10.76391 lx (lm/m2)

W/m2 is used for solar irradiance, which includes IR and UV (if the sensor can handle them).

Lux and fc are used for solar illuminance, which only refers to visible light. For sunlight:

1 lux = 1 lm/m2 ≈ 0.008 W/m2

I would like to thank Brian because the issue is solved; misconfiguration on my side and a fix was released. Great support! Come on WD! Number one!

1 Like