Closed xraided closed 2 months ago
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!
(message by CodeOwnersMention)
gree documentation gree source (message by IssueLinks)
Same issue here. No devices found on the network. In gree+ app can control but dont work in HA
Same issue here, has anyone found any workaround yet?
same issue here. no good news about this integration? Maybe a custom component?
same here :(
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
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.
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
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.
@home-assistant add-label needs-more-information
This is similar to this issue: https://github.com/cmroche/greeclimate/issues/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
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.
Hey, this issue has not been resolved and only went stale because of no replies from devs. It should be re-opened
@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.
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