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

Gree climate No devices found on the network #106043

Closed
xraided opened this issue Dec 19, 2023 · 14 comments
Closed

Gree climate No devices found on the network #106043

xraided opened this issue Dec 19, 2023 · 14 comments

Comments

@xraided
Copy link

xraided commented Dec 19, 2023

The problem

Gree climate doesn't detect my AC anymore. It was working fine few days ago.
Today I saw ac not available and decided to reaload integration...and it's gone now.
I still can control my AC with Gree+ app.
I see it has IP in my router page. (same subnet as HA)
It's sound more like issue on my end or gree end, since there was no recent changes with this integration?
Any ideas/solutions what to do?

What version of Home Assistant Core has the issue?

core-2023.12.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

Gree Climate

Link to integration documentation on our website

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

Diagnostics information

No response

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 @cmroche, mind taking a look at this issue as it has been labeled with an integration (gree) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of gree 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 gree 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)


gree documentation
gree source
(message by IssueLinks)

@lozano312
Copy link

Same issue here. No devices found on the network. In gree+ app can control but dont work in HA

@Luk164
Copy link

Luk164 commented Mar 29, 2024

Same issue here, has anyone found any workaround yet?

@viotemp1
Copy link

same issue here. no good news about this integration? Maybe a custom component?

@martinblq
Copy link

same here :(

@Luk164
Copy link

Luk164 commented May 21, 2024

same here :(

Make sure your HA instance is on the same subnet as the AC. The HA only scans it's own subnet and currently has no manual override

@komatooo
Copy link

same here :(

Make sure your HA instance is on the same subnet as the AC. The HA only scans it's own subnet and currently has no manual override

Just wonder, whos "great" idea it was, to narrow scanning functionality to the same subnet? It literally means that docker/kubernetes etc. installations of ha are automatically incompatible with this integration.

@heidricha
Copy link

heidricha commented May 25, 2024

Same issue since I upgraded HA today, current version is 2024.5.5

HA runs in docker, but with networking=host, so HA IP address is in the same subnet as the climates. Climates are connected, and work wth the Gree+ app

update: different connected networks prevent integration from working.
I stopped OpenVPN, and devices has been found just fine again

@cmroche
Copy link
Contributor

cmroche commented Jun 30, 2024

While direct IP configurability will work around, it's not clear to me why OpenVPN is preventing the broadcast from working on a link-local subnet.

Could you share the greeclimate logs for when discovery is both working and not working? At the very least I would like to see if it's scanning the same interfaces to understand the problem better.

@cmroche
Copy link
Contributor

cmroche commented Jul 13, 2024

@home-assistant add-label needs-more-information

@cmroche
Copy link
Contributor

cmroche commented Jul 13, 2024

This is similar to this issue: cmroche/greeclimate#76 if you have a newer device with a different encryption key, please follow that issue including info to help test an update to bring support to those devices. Thanks

@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 Aug 3, 2024
@Luk164
Copy link

Luk164 commented Aug 4, 2024

Hey, this issue has not been resolved and only went stale because of no replies from devs. It should be re-opened

@mk-igor
Copy link

mk-igor commented Aug 26, 2024

@Luk164 I was having the same issue and was able to resolve it by installing another add-on on top of this one. https://github.com/rapi3/HA-OS-Gree
This add-on allows you to keep using standard Gree integration, but when it doesn't find devices (assuming you're just adding them as new), it will give you a pop up to enter your device ip. Note, I did have to remove from the Gree app and reset wifi on each of my Gree devices, add them back to the Gree app, then after a few minutes they were able to connect using the IP in HA.

@github-actions github-actions bot locked and limited conversation to collaborators Sep 25, 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

9 participants