home-assistant / core

:house_with_garden: Open source home automation that puts local control and privacy first.
https://www.home-assistant.io
Apache License 2.0
73.43k stars 30.66k forks source link

Missing Lightning Strike Distance for Ecowitt integration #124876

Open RadioFreeOklahoma opened 2 months ago

RadioFreeOklahoma commented 2 months ago

The problem

I have a 90ft amatuer radio tower on a hilltop, lightning distance is a critically needed parameter. The same issue was reported in August 2023 for the Ambient Weather Integration, and resolved, but is missing from Ecowitt. Also, "Last Lightning Strike", and "Wind Chill" parameters appear in the integration, but are labeled as "Unavailable"; they are being reported by Ecowitt.

What version of Home Assistant Core has the issue?

Core 2024.8.3

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

Ecowitt

Link to integration documentation on our website

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

Diagnostics information

Diagnostics are ecowitt-01J5KW233BJ8PC5NF9GBBQZHM5-GW1200B-a7d564590b23ab3acd55d2932d6ed471.json

Example YAML snippet

Nothing to Reproduce, integration is missing the parameter needed. All other parameters for the Ecowitt integration are functional.

Anything in the logs that might be useful for us?

I examined three days ofd logs, there were no error log entries for Ecowitt

Additional information

Sorry, wish I could provide more helpful info. The "Lightning DIstance" does appear in the Ecowitt App (Iphone) and functions normally within that app.

### Tasks
### Tasks
home-assistant[bot] commented 2 months ago

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)

RadioFreeOklahoma commented 2 months ago

@pvizeli I realize that the work you do is volunteer and non paid, but I desperately need this modification for the safety of my radio station. I would be happy to send a donation or sponsor you in return for the assistance.

vix66 commented 2 weeks ago

me too

RadioFreeOklahoma commented 1 week ago

Waste of time. This is why I have quit Home Assistant, people develop APIs that provide functionality, then when the API breaks the developer has abandoned it. I understand these are volunteer positions, but there is no program oversight to keep the ship sailing straight. Home Assistant is just a circus, it’s a toy for people that have time to constantly fix the broken software. It’s not a serious home automation ecosystem, the whole point of home automation is to make life easier and save time, how am I saving time or making life easier when I’m constantly having to fix my system every other week?