-
-
Notifications
You must be signed in to change notification settings - Fork 33.8k
Ecowitt Integration: Unhandled sensor type srain_piezo #137171
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
Comments
Hey there @pvizeli, mind taking a look at this issue as it has been labeled with an integration ( Code owner commandsCode owners of
(message by CodeOwnersMention) ecowitt documentation |
Temporary fix until someone finally looks at my PR and approves it for merging: |
I can not still see the rain binary sensor, shouldn’t it appear automatically? Thanks. |
same here, still no binary sensor |
Same here. No binary sensor when using the standard component distributed with Home Assistant. The temporary fix from @smuliv does, however, work and show the sensor. |
The problem
I'm using an Ecowitt GW3000A weather station and receiving constant log messages about an unhandled sensor type.
Device Details:
The
srain_piezo
appears to be a binary rain sensor (0/1) but is currently not handled by the integration, resulting in constant log messages:Unhandled sensor type srain_piezo value 0/1
Raw data example from the sensor:
[Raw data from your JSON]
Request:
Could we add support for this sensor type as a binary_sensor with device_class: moisture?
What version of Home Assistant Core has the issue?
2025.1.4
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant OS
Integration causing the issue
No response
Link to integration documentation on our website
No response
Diagnostics information
No response
Example YAML snippet
Anything in the logs that might be useful for us?
Additional information
ecowitt-01JK0G2K899FHHZ8P77R2WZG5E-GW3000A-99e4a9d6f36faed8dc9098c02c00210b.json
The text was updated successfully, but these errors were encountered: