Unhandled Sensor Type In Logs

[pkscout]

2022-04-08 12:21:27 WARNING (MainThread) [custom_components.ecowitt] Unhandled sensor type runtime value 417745, file a PR.

I'm using two WH31 Multi-Channel 2-in-1 Temperature and Humidity Sensors in addition to the Ecowitt bridge. These are the multi-channel ones, so I have one on Channel 1 and the other on Channel 2.

https://www.ecowitt.com/shop/goodsDetail/55

[PCjabber]

I also receive these messages in the log. I also have a WH31 multi-channel T&H, in addition to a WS80 anemometer, WH40 rain cup, connected via a GW1100 gateway. Gateway firmware is latest 2.1.4 (GW1100B_V2.1.4).

2022-04-18 23:54:27 WARNING (MainThread) [custom_components.ecowitt] Unhandled sensor type runtime value 282191, file a PR.
2022-04-18 23:54:44 WARNING (MainThread) [custom_components.ecowitt] Unhandled sensor type runtime value 282208, file a PR.
2022-04-18 23:55:01 WARNING (MainThread) [custom_components.ecowitt] Unhandled sensor type runtime value 282225, file a PR.
2022-04-18 23:55:18 WARNING (MainThread) [custom_components.ecowitt] Unhandled sensor type runtime value 282242, file a PR.

These messages repeat about 2-4 times per minute.
When I reboot the GW1100, the logged value that appears in the HA log is close to 0 (e.g. 4). It seems this may be an uptime counter (seconds since reboot) for the Gateway/Console that's pushing the data.

[dkirker]

I created this pull request #110 which adds "runtime" as an ignored sensor and also adds quotes in the logging output. It looks like that was also added with #109