Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ecowitt integration - incorrectly typed sensor #106115

Closed
jefft4 opened this issue Dec 20, 2023 · 3 comments
Closed

Ecowitt integration - incorrectly typed sensor #106115

jefft4 opened this issue Dec 20, 2023 · 3 comments

Comments

@jefft4
Copy link

jefft4 commented Dec 20, 2023

The problem

Ecowitt sensor hourly_rain_rate is typed as total_increasing. It is a point-in-time measure that resets each hour, so that's not the correct type. It should be just an ordinary number value.

Logger: homeassistant.components.sensor.recorder
Source: components/sensor/recorder.py:288
Integration: Sensor (documentation, issues)
First occurred: 19 December 2023 at 10:15:10 (1 occurrences)
Last logged: 19 December 2023 at 10:15:10

Entity sensor.gw1100a_v2_2_3_hourly_rain_rate_2 from integration ecowitt has state class total_increasing, but its state is not strictly increasing. Triggered by state 2.1 (2.3) with last_updated set to 2023-12-19T10:10:28.721770+00:00. Please create a bug report at https://github.com/home-assistant/core/issues?q=is%3Aopen+is%3Aissue+label%3A%22integration%3A+ecowitt%22

Entity state:
state_class: total_increasing unit_of_measurement: mm device_class: precipitation friendly_name: Weather station Hourly Rain Rate

What version of Home Assistant Core has the issue?

2023.12.3

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant Container

Integration causing the issue

Ecowitt

Link to integration documentation on our website

https://www.home-assistant.io/integrations/ecowitt/

Diagnostics information

ecowitt-617efd866d4bd634ff5895a02438e592-GW1100A-5ecc1f91bd26ef0d2df35f60d5c494a7.json.txt

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

@home-assistant
Copy link

Hey there @pvizeli, mind taking a look at this issue as it has been labeled with an integration (ecowitt) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of ecowitt can trigger bot actions by commenting:

  • @home-assistant close Closes the issue.
  • @home-assistant rename Awesome new title Renames the issue.
  • @home-assistant reopen Reopen the issue.
  • @home-assistant unassign ecowitt Removes the current integration label and assignees on the issue, add the integration domain after the command.
  • @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
  • @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

(message by CodeOwnersMention)


ecowitt documentation
ecowitt source
(message by IssueLinks)

@sam-ward
Copy link

There is a pending PR that fixes the issue in the upstream library (#102738) . Just waiting on the maintainer to merge it.

@issue-triage-workflows
Copy link

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

@issue-triage-workflows issue-triage-workflows bot closed this as not planned Won't fix, can't repro, duplicate, stale Apr 18, 2024
@github-actions github-actions bot locked and limited conversation to collaborators May 18, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants