Skip to content

Ecowitt not working with TLS/SSL - Can you add this to the docts #37370

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

Closed
DrSpaldo opened this issue Feb 9, 2025 · 6 comments · Fixed by #38581
Closed

Ecowitt not working with TLS/SSL - Can you add this to the docts #37370

DrSpaldo opened this issue Feb 9, 2025 · 6 comments · Fixed by #38581
Assignees

Comments

@DrSpaldo
Copy link

DrSpaldo commented Feb 9, 2025

Feedback

As Ecowitt no longer works if you are using TLS/SSL for your Home Assistant instance, you now need a proxy:

https://github.com/ChrisRomp/addon-ecowitt-proxy

Can this be added to the docs please?

URL

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

Version

2025.2.1

Additional information

No response

@home-assistant
Copy link

home-assistant bot commented Feb 9, 2025

Hey there @pvizeli, mind taking a look at this feedback 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 feedback.
  • @home-assistant rename Awesome new title Renames the feedback.
  • @home-assistant reopen Reopen the feedback.
  • @home-assistant unassign ecowitt Removes the current integration label and assignees on the feedback, add the integration domain after the command.
  • @home-assistant add-label needs-more-information Add a label (needs-more-information) to the feedback.
  • @home-assistant remove-label needs-more-information Remove a label (needs-more-information) on the feedback.

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.
If this issue is still relevant, please let us know by leaving a comment 👍
This issue has now has been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

@github-actions github-actions bot added the Stale The PR had no activity for quite some time, and is marked as Stale label Apr 10, 2025
@frenck
Copy link
Member

frenck commented Apr 16, 2025

Oh hi there @DrSpaldo 👋

Thanks for the feedback and suggestion, unfortunately, we do not support or recommend third-party add-ons. Therefore that part cannot be added to the docs.

../Frenck

@frenck
Copy link
Member

frenck commented Apr 16, 2025

I've opened up a PR to extend/clarify the part of the docs on this.

../Frenck

@github-actions github-actions bot removed the Stale The PR had no activity for quite some time, and is marked as Stale label Apr 16, 2025
@DrSpaldo
Copy link
Author

Thanks for the reply @frenck . That makes sense. Apparently the integration isn’t working well either anymore

@frenck
Copy link
Member

frenck commented Apr 16, 2025

I have the integration in active use myself, works fine 🤷

If you have an issue, please report it in the Core repository issue tracker.

../Frenck

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants