Gree AC different subnet

andymarden commented 1 year ago

The problem

This does not find my 3 Gree ACs. They are on a different subnet to HA - that may be the issue. Both subnets can see each other however. There is precious little in the documentation about what prerequisites exist (ie they must be on the same subnet), the way the integration tries to detect (does it use of respond to multicast?) or a way to configure manually/ I would have though that it should be possible for me to supply the IP addresses and go from there.

Raising as a bug because there is nothing that says my setup should not work.

What version of Home Assistant Core has the issue?

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

Link to integration documentation on our website

No response

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

andymarden commented 1 year ago

I see this is also covered here but was not resolved: https://github.com/home-assistant/core/issues/42758

home-assistant[bot] commented 1 year 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!

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.

_{^{(message by CodeOwnersMention)}}

gree documentation gree source _{^{(message by IssueLinks)}}

kspearrin commented 9 months ago

I fixed this with https://github.com/home-assistant/core/pull/100731

issue-triage-workflows[bot] commented 6 months ago

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.

bkupidura commented 6 months ago

Not solved

issue-triage-workflows[bot] commented 3 months ago

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.

kspearrin commented 3 months ago

Not solved