Unhandled sensor type runtime value

MeanderingWanderer commented 2 years ago

Hi This appeared in my logs. I recently added soil moisture sensor which work fine. Also noticed that the EW integration startup time was 84 seconds. Other then that I can't really give you more info because everything seems to be working correctly. I do have one of the soil sensors at max distance so it does miss some data values during 24 hour period. lmk if i've missed anything u need. great integration- thanks for contribution to community!

Logger: custom_components.ecowitt
Source: custom_components/ecowitt/__init__.py:274
Integration: Ecowitt Weather Station
First occurred: June 17, 2022 at 8:19:26 AM (495 occurrences)
Last logged: 12:55:42 AM

Unhandled sensor type runtime value 725881, file a PR.
Unhandled sensor type runtime value 726002, file a PR.
Unhandled sensor type runtime value 726123, file a PR.
Unhandled sensor type runtime value 726244, file a PR.
Unhandled sensor type runtime value 726365, file a PR.

gorillica commented 2 years ago

I've got the same issue. The value for this runtime sensor type increments gradually. I just tested by restarting the Ecowitt base station, and sure enough, the next error reported was 5. I assume therefore that the runtime sensor is counting uptime in seconds for the base station.

Daali commented 2 years ago

you can add it to the ignored sensors in const.py, or you can set it up as a sensor.runtime and do some dashboard uptime math with a template.

iculookn commented 2 years ago

I have a GW1000B_Pro setup and seems like it's all working fine, but I do get the following errors in the log. not sure what sensor it cant handle?

WARNING (MainThread) [custom_components.ecowitt] Unhandled sensor type runtime value 1024727, file a PR. WARNING (MainThread) [custom_components.ecowitt] Unhandled sensor type totalainin value 43.465, file a PR.

EDIT: just read that "totalainin" is a spelling mistake in the latest firmware. Should be "totalrainin" and will be fixed soon.

Daali commented 2 years ago

Totalrainin was just added back, but it looks like the made a spelling mistake in the firmware. I redirected it in the const.py to totalrainin until they fix it.

Claudio1L commented 1 year ago

same here: Logger: custom_components.ecowitt Source: custom_components/ecowitt/init.py:274 Integration: Ecowitt Weather Station First occurred: 19:19:00 (31 occurrences) Last logged: 19:49:30

Unhandled sensor type runtime value 2350545, file a PR.
Unhandled sensor type runtime value 2350604, file a PR.
Unhandled sensor type runtime value 2350664, file a PR.
Unhandled sensor type runtime value 2350725, file a PR.
Unhandled sensor type runtime value 2350787, file a PR.

hintringerh commented 1 year ago

same here, only way more occurrences.

This error originated from a custom integration.

Logger: custom_components.ecowitt Source: custom_components/ecowitt/init.py:274 Integration: Ecowitt Weather Station First occurred: October 8, 2022 at 01:37:37 (10451 occurrences) Last logged: 18:16:23

Unhandled sensor type runtime value 0, file a PR. Unhandled sensor type runtime value 2, file a PR. Unhandled sensor type runtime value 4, file a PR. Unhandled sensor type runtime value 1, file a PR. Unhandled sensor type runtime value 3, file a PR.

gorillica commented 1 year ago

I've just switched to the official integration. Things were pretty painless, although I had to rename entities to match the old versions.

First step was to remove the configuration for the custom component; then I removed it through HACS and restarted HA; then I added the new config for the official integration using the UI.

No problems with Unhandled sensors now, and there are a few new sensors too, including the outdoor light-level in Lx and a ‘feels-like’ temperature.

garbled1 / homeassistant_ecowitt

Unhandled sensor type runtime value #123