GeorgePatsias commented 8 months ago

The problem

Eveything was working fine, but suddently all the Gree AC devices went unavailable one day (4-5 days now). My air-condition units have IP and are online and I can controll them with the Gree App fine.

In the Home Assistant they show unavailable, even reloading the intergration, delete and reinstall, reboot, reset AC, delete AC from app and add them again.

What version of Home Assistant Core has the issue?

core-2024.1.6

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 AC model GWH09AGA-K6DNA1A/I

Link to integration documentation on our website

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

Diagnostics information

home-assistant_gree_2024-01-31T17-09-45.153Z.log

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

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

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)}}

Csontikka commented 8 months ago

Hello! I am experiencing the same issue with my GREE air conditioners. Reviewing the logs of my automations, it is evident that the error occurred right after the core-2024.1.6 update and has persisted since then. Despite restarting Home Assistant and the entire system, the issue remains unresolved.

(ping for the climates work well, GREE app works well and I haven't experienced such an issue until this update.

JongsmaSimon commented 8 months ago

Same problem here. Constantly ‘unavailable’..

reyo commented 8 months ago

I'm getting "not binding" error in the log, the latest HA update broke Gree HACS component also.

tslashd commented 7 months ago

Gree device is Unavailable after the latest 2024.2.1 Core update. Device is available in Gree mobile app and is also responsive

Anyone found any fixes for this yet? 🤔

#

Power Cycle fixed it 🤷

aalmarshad commented 7 months ago

Still not solved even after power cycle. The Ac is showing in the Gree+ app and connected but HA does not see it

lozano312 commented 7 months ago

Still not solved even after power cycle. The Ac is showing in the Gree+ app and connected but HA does not see it

Same issue here. Gree app conected and work good. But in home assistant dont found dispositives. I update HA and wifi gree

lozano312 commented 7 months ago

Power Cycle

Dont work for me. Reset wifi of AC, reset AC, reset HA. Same issue.

MikeInMaine commented 7 months ago

same here.. North America

aalmarshad commented 7 months ago

It looks like a general problem with the integration.

MikeInMaine commented 7 months ago

Mine is working again. I reregistered the minisplit in the app after power cycling it at the breaker. One possible factor for mine is that I use the app to register it but I've never been able to get the app to actually connect to it. HA is working again though.

aalmarshad commented 7 months ago

Mine is working again. I reregistered the minisplit in the app after power cycling it at the breaker. One possible factor for mine is that I use the app to register it but I've never been able to get the app to actually connect to it. HA is working again though.

How many AC do you have? I have two and I got one working fine but the other one doesn't work!

tslashd commented 7 months ago

I cannot pinpoint exactly where the issue lies but I will give some more information about my AC unit: It is currently running on v3.76 (Europe) as I have been unable to update to v3.77 through the app ever since the update came out, the update screen just spins around as if it is updating but even after 15 minutes of the screen being on (not sleeping or anything as they have described in order to update your unit). Have sent a couple of Feedback messages to them about this but to no avail, still unable to update the firmware on it which supposedly fixes some Known Wi-Fi module issues

I can recommend for the people having issues with the HA integration to check the version on your AC and try to update it, then see if the Unavailable issue persists.

Hope this can help some of the people with this issue.

It would be really funny if the Known Wi-Fi module issues is what actually is "blocking" me from updating the firmware. 😄

lozano312 commented 7 months ago

I cannot pinpoint exactly where the issue lies but I will give some more information about my AC unit: It is currently running on v3.76 (Europe) as I have been unable to update to v3.77 through the app ever since the update came out, the update screen just spins around as if it is updating but even after 15 minutes of the screen being on (not sleeping or anything as they have described in order to update your unit). Have sent a couple of Feedback messages to them about this but to no avail, still unable to update the firmware on it which supposedly fixes some Known Wi-Fi module issues

I can recommend for the people having issues with the HA integration to check the version on your AC and try to update it, then see if the Unavailable issue persists.

Hope this can help some of the people with this issue.

It would be really funny if the Known Wi-Fi module issues is what actually is "blocking" me from updating the firmware. 😄

I could update and same issue. Dont work for me. Europe version. Ewpe smart app.

Csontikka commented 7 months ago

I'm experiencing the same issue with the update that you've described; my devices won't update to 3.77 either (currently running on 3.76, on various types of air conditioners). I've tried using different applications (gree and ewpe smart), changed regional settings, device resets, etc., but nothing has yielded any results. Please, if you receive any substantial response from Gree support, share it with us too!

MikeInMaine commented 7 months ago

I only have one unit. I did check the firmware of the unit in the phone app and it says that there are no updates available. Mike

On Wed, Feb 21, 2024 at 12:48 AM aalmarshad @.***> wrote:

Mine is working again. I reregistered the minisplit in the app after power cycling it at the breaker. One possible factor for mine is that I use the app to register it but I've never been able to get the app to actually connect to it. HA is working again though.

How many AC do you have? I have tow and I got one working fine but the other one doesn't work!

— Reply to this email directly, view it on GitHub https://github.com/home-assistant/core/issues/109230#issuecomment-1955940109, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABAU7PEMMAIOCNO6QR3ZT6TYUWDB3AVCNFSM6AAAAABCTNZ4LCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNJVHE2DAMJQHE . You are receiving this because you commented.Message ID: @.***>

chal086 commented 7 months ago

I have two Dehumidifiers and also no connection to HA, app works fine. I also have tried on both to update this mysterious 3.77 firmware but no luck.

mjkvaak commented 7 months ago

I suddenly experienced this a few days ago. Tried reconnecting the AC to wifi, but it didn't help. I rechecked the climate.yaml that the IP and the MAC addresses were correct and also tried restarting the docker, but those didn't fix it either. What turned out to fix this was to enter the MAC address with no "-" and ":" and in all-small letters; e.g. AB:CD:12:34... becomes abcd1234.... This was inspired by this answer.

lozano312 commented 6 months ago

No solution for that? Cant edit climate.yaml because havent this document

bajor-attila-orgware commented 6 months ago

Same here. 3 AC on wifi. 2 accessible, 1 unavailable. HA Core 2023.11.2

Siwus90 commented 6 months ago

Same here 2 unavalible.

 Rejestrator:` homeassistant.components.gree.bridge
Źródło: helpers/update_coordinator.py:350
integracja: Gree Climate (dokumentacja, Problemy)
Pierwsze zdarzenie: 20:21:11 (10 zdarzenia)
Ostatnio zalogowany: 20:30:31

Error fetching gree-xxxx data: Device gree-xxxx is unavailable
Error fetching gree-xxxx data: Device gree-xxxx is unavailable

MikeInMaine commented 6 months ago

I've had it go offline once since I posted here last. Rebooting via the breaker for the unit fixed it. Mike

On Mon, Mar 25, 2024 at 3:33 PM Siwus90 @.***> wrote:

Same here 2 unavalible.

`Rejestrator: homeassistant.components.gree.bridge Źródło: helpers/update_coordinator.py:350 integracja: Gree Climate (dokumentacja, Problemy) Pierwsze zdarzenie: 20:21:11 (10 zdarzenia) Ostatnio zalogowany: 20:30:31

Error fetching gree-xxxx data: Device gree-xxxx is unavailable Error fetching gree-xxxx data: Device gree-xxxx is unavailable`

— Reply to this email directly, view it on GitHub https://github.com/home-assistant/core/issues/109230#issuecomment-2018761318, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABAU7PAVMJNAZ76WVQEEO6LY2B3ZVAVCNFSM6AAAAABCTNZ4LCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMJYG43DCMZRHA . You are receiving this because you commented.Message ID: @.***>

Siwus90 commented 6 months ago

I've had it go offline once since I posted here last. Rebooting via the breaker for the unit fixed it. Mike … On Mon, Mar 25, 2024 at 3:33 PM Siwus90 @.> wrote: Same here 2 unavalible. Rejestrator: homeassistant.components.gree.bridge Źródło: helpers/update_coordinator.py:350 integracja: Gree Climate (dokumentacja, Problemy) Pierwsze zdarzenie: 20:21:11 (10 zdarzenia) Ostatnio zalogowany: 20:30:31 Error fetching gree-xxxx data: Device gree-xxxx is unavailable Error fetching gree-xxxx data: Device gree-xxxx is unavailable — Reply to this email directly, view it on GitHub <#109230 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABAU7PAVMJNAZ76WVQEEO6LY2B3ZVAVCNFSM6AAAAABCTNZ4LCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMJYG43DCMZRHA . You are receiving this because you commented.Message ID: @.>

Thank you, it worked!

lozano312 commented 6 months ago

I've had it go offline once since I posted here last. Rebooting via the breaker for the unit fixed it. Mike … On Mon, Mar 25, 2024 at 3:33 PM Siwus90 @._> wrote: Same here 2 unavalible. Rejestrator: homeassistant.components.gree.bridge Źródło: helpers/update_coordinator.py:350 integracja: Gree Climate (dokumentacja, Problemy) Pierwsze zdarzenie: 20:21:11 (10 zdarzenia) Ostatnio zalogowany: 20:30:31 Error fetching gree-xxxx data: Device gree-xxxx is unavailable Error fetching gree-xxxx data: Device gree-xxxx is unavailable — Reply to this email directly, view it on GitHub <#109230 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABAU7PAVMJNAZ76WVQEEO6LY2B3ZVAVCNFSM6AAAAABCTNZ4LCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMJYG43DCMZRHA . You are receiving this because you commented.Message ID: _@_._>

Thank you, it worked!

How do that? I reset wifi of unit and not work. I power off general breaker and not work

Siwus90 commented 6 months ago

How do that? I reset wifi of unit and not work. I power off general breaker and not work

Wait 30 seconds after turning off general breaker.

lozano312 commented 6 months ago

How do that? I reset wifi of unit and not work. I power off general breaker and not work

Wait 30 seconds after turning off general breaker.

Not work. No devices

omarkhali commented 5 months ago

I have the same problem here. My Gree integration get unavailable randomly. Core 2024.4.3

KiralyCraft commented 5 months ago

People with problems, can you check the "Firmware update" version of your AC units? I've been researching this for a while, and it seems verion V1.21 broke something. GREE is also very careful about us not being able to extract the encryption keys used by it with the devices.

The gree.db database file on EWPE Smart 1.18.6.5 is now encrypted (!!)

You can get this information from the GREE app (or from EWPE Smart). It looks like this:

lozano312 commented 5 months ago

Screenshot_20240420_174844_Ewpe Smart

This dont work

Muzzygizmo commented 5 months ago

People with problems, can you check the "Firmware update" version of your AC units? I've been researching this for a while, and it seems verion V1.21 broke something. GREE is also very careful about us not being able to extract the encryption keys used by it with the devices.

The gree.db database file on EWPE Smart 1.18.6.5 is now encrypted (!!)

You can get this information from the GREE app (or from EWPE Smart). It looks like this:

I Also have the same problem. 2 units with firmware V1.16 : connected & responding 1 unit with firmware V1.21 : unavailable

Terikos commented 5 months ago

Today 2 new units were installed in my home. Both with wifi firmware v1.21 and both are unavailable in home assistant 🙁. In EWPE all Air conditioners are visible and operatioanl.

KiralyCraft commented 5 months ago

If it's not working for you, would you mind running a python gree.py --discovery from here?

https://github.com/cmroche/greeclimate

In the responses, you might get something like this: https://github.com/cmroche/greeclimate/issues/70#issue-2254538333

From here you might have the device HID embedded, from which we can then extract the firmware. If you're comfortable, you can also use the nc command directly, like echo {"t": "scan"} | nc -u 192.168.0.131 7000 (my device was at 192.168.0.131)

Muzzygizmo commented 5 months ago

Here is my discovery result :

asyncio - DEBUG - Using selector: EpollSelector
__main__ - DEBUG - Scanning network for Gree devices
greeclimate.discovery - INFO - Scanning for Gree devices ...
greeclimate.discovery - DEBUG - Listening for devices on 192.168.1.255
greeclimate.discovery - DEBUG - Listening for devices on 172.30.233.255
greeclimate.discovery - DEBUG - Listening for devices on 172.30.33.255
greeclimate.network - DEBUG - Sending packet:
{"t": "scan"}
greeclimate.network - DEBUG - Sending packet:
{"t": "scan"}
greeclimate.network - DEBUG - Sending packet:
{"t": "scan"}
greeclimate.network - DEBUG - Received packet from 192.168.1.235:
{"t": "pack", "i": 1, "uid": 0, "cid": "", "tcid": "", "pack": {"t": "dev", "cid": "9424b8b448f9", "bc": "00000000000000000000000000000000", "brand": "gree", "catalog": "gree", "mac": "9424b8b448f9", "mid": "10001", "model": "gree", "name": "", "lock": 0, "series": "gree", "vender": "1", "ver": "V2.0.0", "ModelType": "32792", "hid": "362001065280+U-WB05RT11V1.21.bin"}}
greeclimate.discovery - INFO - Found gree device Device: 9424b8b448f9 @ 192.168.1.235:7000 (mac: 9424b8b448f9)
greeclimate.network - DEBUG - Received packet from 192.168.1.253:
{"t": "pack", "i": 1, "uid": 0, "cid": "", "tcid": "", "pack": {"t": "dev", "cid": "", "bc": "00000000000000000000000000000000", "brand": "gree", "catalog": "gree", "mac": "9424b896b70a", "mid": "10001", "model": "gree", "name": "", "lock": 0, "series": "gree", "vender": "1", "ver": "V3.0.0", "hid": "362001065280+U-WB05RT11V1.16.bin"}}
greeclimate.discovery - INFO - Found gree device Device: 9424b896b70a @ 192.168.1.253:7000 (mac: 9424b896b70a)
greeclimate.network - DEBUG - Received packet from 192.168.1.251:
{"t": "pack", "i": 1, "uid": 0, "cid": "", "tcid": "", "pack": {"t": "dev", "cid": "", "bc": "00000000000000000000000000000000", "brand": "gree", "catalog": "gree", "mac": "9424b896b054", "mid": "10001", "model": "gree", "name": "", "lock": 0, "series": "gree", "vender": "1", "ver": "V3.0.0", "hid": "362001065280+U-WB05RT11V1.16.bin"}}
greeclimate.discovery - INFO - Found gree device Device: 9424b896b054 @ 192.168.1.251:7000 (mac: 9424b896b054)
__main__ - INFO - Done discovering devices

All three devices are recognized by homeassistant but the 192.168.1.235 is the only one to be unavailable. The 192.168.1.253 and .251 have V1.16 firmware, while the .235 (unavailable) has V1.21

All tree are working perfectly with the EWPE Smart application.

Urusus2 commented 4 months ago

With the new firmware version 1.53, the old method of obtaining the private key works...

For info: work with firmware versions (tested): 1.16, 1.17, 1.53 not work (tested): 1.20, 1.21, 1.22

philips1923 commented 4 months ago

I can confirm - Gree Pular - 4 devices with v1.21 software - doesnt work (visible in HA but not responsible) - https://github.com/home-assistant/core/issues/117353

Moustachauve commented 4 months ago

I also have two gree pular, one with 1.16 and the other with 1.21 and only the one with 1.16 works with the integration. Both are recognized in HA but the one with 1.21 always goes to unavailable.

philips1923 commented 4 months ago

I'm looking for a way to downgrade firmware but it's not so easy for non-programmer like me :) if anybody knows way to do this I'd be grateful for any help/link

EDIT_____

just a little bit closer - found great place with appropriate to my module version (1.21 -> 1.53) https://github.com/maxim-smirnov/gree-wifimodule-firmware/tree/main/362001065279 but I have no idea how to force this update, I tried to change region of my AC from PL to USA or Maledives but than my gree app even can't find my AC

KiralyCraft commented 4 months ago

The procedure would be to run the Android APK of GREE+ in debug mode. Then, all regions are mapped to the test server, where firmware 1.53 can be applied. This is quite a complicated process and is not without risks (as anything).

You can use this procedure to launch the app in debug mode: https://developer.android.com/studio/debug/apk-debugger ; After this, you need to create your account again, with the same email. The email code arrives very slow, be patient (I wasn't). Reset the WiFi of your AC and pair them again with the app, while still in debug mode. Then do the firmware update. Wait until it's 99%, and until it errors out. Then, try to pair them with Home Assistant.

At this point, you could try to reset the module again, run the app in normal mode and try to re-pair the devices with your normal app account. I was afraid to do this.

Now my AC units are running 1.53, and can't be controlled through the application anymore, they appear offline. Still, they are connected to the network and respond to local queries, so this is nice. They also work in Home Assistant now.

I didn't try repairing the app, as I was afraid I'd break them and would be unable to get them to link to the network. If anyone wants to test this, please let me know.

edoras1 commented 4 months ago

Same experience ... Now I bought 4 new air conditionings Sinclair. There is Gree modules inside. One AC has fw 1.05, it works without problems. Three ACs have fw 1.21 and they are unavailable.

szaman-89 commented 4 months ago

The procedure would be to run the Android APK of GREE+ in debug mode. Then, all regions are mapped to the test server, where firmware 1.53 can be applied. This is quite a complicated process and is not without risks (as anything).

You can use this procedure to launch the app in debug mode: https://developer.android.com/studio/debug/apk-debugger ; After this, you need to create your account again, with the same email. The email code arrives very slow, be patient (I wasn't). Reset the WiFi of your AC and pair them again with the app, while still in debug mode. Then do the firmware update. Wait until it's 99%, and until it errors out. Then, try to pair them with Home Assistant.

At this point, you could try to reset the module again, run the app in normal mode and try to re-pair the devices with your normal app account. I was afraid to do this.

Now my AC units are running 1.53, and can't be controlled through the application anymore, they appear offline. Still, they are connected to the network and respond to local queries, so this is nice. They also work in Home Assistant now.

I didn't try repairing the app, as I was afraid I'd break them and would be unable to get them to link to the network. If anyone wants to test this, please let me know.

How did you run GREE+ apk in Android Studio? I can't pass different structure of Android Studio and apk because of X86_64 structure in apk. Do you somehow get AARCH64 version of GREE+ apk?

2024-05-18 09:15:49.079 5846-5846 AndroidRuntime com.gree.greeplus D Shutting down VM 2024-05-18 09:15:49.086 5846-5846 AndroidRuntime com.gree.greeplus E FATAL EXCEPTION: main Process: com.gree.greeplus, PID: 5846 java.lang.UnsatisfiedLinkError: dlopen failed: "/data/data/com.gree.greeplus/.jiagu/libjgcgg_64.so" is for EM_X86_64 (62) instead of EM_AARCH64 (183) at java.lang.Runtime.load0(Runtime.java:933) at java.lang.System.load(System.java:1625) at sulpeerg.eerg.moc.a.a(SourceFile:233) at sulpeerg.eerg.moc.StubApp.attachBaseContext(SourceFile:188) at android.app.Application.attach(Application.java:346) at android.app.Instrumentation.newApplication(Instrumentation.java:1283) at android.app.LoadedApk.makeApplicationInner(LoadedApk.java:1458) at android.app.LoadedApk.makeApplicationInner(LoadedApk.java:1395) at android.app.ActivityThread.handleBindApplication(ActivityThread.java:6959) at android.app.ActivityThread.-$$Nest$mhandleBindApplication(Unknown Source:0) at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2236) at android.os.Handler.dispatchMessage(Handler.java:106) at android.os.Looper.loopOnce(Looper.java:205) at android.os.Looper.loop(Looper.java:294) at android.app.ActivityThread.main(ActivityThread.java:8177) at java.lang.reflect.Method.invoke(Native Method) at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:552) at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:971) 2024-05-18 09:15:49.635 5846-5846 Process com.gree.greeplus I Sending signal. PID: 5846 SIG: 9 2024-05-18 10:18:29.856 6213-6213 AndroidRuntime com.gree.greeplus D Shutting down VM 2024-05-18 10:18:29.856 6213-6213 AndroidRuntime com.gree.greeplus E FATAL EXCEPTION: main Process: com.gree.greeplus, PID: 6213 java.lang.UnsatisfiedLinkError: dlopen failed: "/data/data/com.gree.greeplus/.jiagu/libjgcgg_64.so" is for EM_X86_64 (62) instead of EM_AARCH64 (183) at java.lang.Runtime.load0(Runtime.java:933) at java.lang.System.load(System.java:1625) at sulpeerg.eerg.moc.a.a(SourceFile:233) at sulpeerg.eerg.moc.StubApp.attachBaseContext(SourceFile:188) at android.app.Application.attach(Application.java:346) at android.app.Instrumentation.newApplication(Instrumentation.java:1283) at android.app.LoadedApk.makeApplicationInner(LoadedApk.java:1458) at android.app.LoadedApk.makeApplicationInner(LoadedApk.java:1395) at android.app.ActivityThread.handleBindApplication(ActivityThread.java:6959) at android.app.ActivityThread.-$$Nest$mhandleBindApplication(Unknown Source:0) at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2236) at android.os.Handler.dispatchMessage(Handler.java:106) at android.os.Looper.loopOnce(Looper.java:205) at android.os.Looper.loop(Looper.java:294) at android.app.ActivityThread.main(ActivityThread.java:8177) at java.lang.reflect.Method.invoke(Native Method) at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:552) at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:971)

KiralyCraft commented 4 months ago

How did you run GREE+ apk in Android Studio? I can't pass different structure of Android Studio and apk because of X86_64 structure in apk. Do you somehow get AARCH64 version of GREE+ apk?

Yes, I used the normal AARCH64 version. You also have to set debugging mode to "Java Only" (instead of "Auto" or "Debug native and Java"). I forgot where this option is, but it was somewhere in the debug configuration. It was called "Debug type", see here: https://developer.android.com/studio/run/rundebugconfig

EDIT: You don't run the app in Android Studio, but you use Android Studio to run the app in debug mode on your phone (not sure if an emulator works)

szaman-89 commented 4 months ago

Ok, thank you. I'm one step closer now :D Paired my Oneplus smartphone over wifi debugging with Android Studio. Changed debugging type to "Java Only".

Now this happened:

Cannot debug application from module GREE+_1.18.6.8_APKPure on device oneplus-ne2213-adb-c2dbbfa6-R5UjC2._adb-tls-connect._tcp. This application does not have the 'debuggable' attribute enabled in its manifest. If you have manually set it in the manifest, then remove it and let the IDE automatically assign it. If you are using Gradle, make sure that your current variant is debuggable.

Have you any idea what's wrong?

omarkhali commented 4 months ago

The procedure would be to run the Android APK of GREE+ in debug mode. Then, all regions are mapped to the test server, where firmware 1.53 can be applied. This is quite a complicated process and is not without risks (as anything).

You can use this procedure to launch the app in debug mode: https://developer.android.com/studio/debug/apk-debugger ; After this, you need to create your account again, with the same email. The email code arrives very slow, be patient (I wasn't). Reset the WiFi of your AC and pair them again with the app, while still in debug mode. Then do the firmware update. Wait until it's 99%, and until it errors out. Then, try to pair them with Home Assistant.

At this point, you could try to reset the module again, run the app in normal mode and try to re-pair the devices with your normal app account. I was afraid to do this.

Now my AC units are running 1.53, and can't be controlled through the application anymore, they appear offline. Still, they are connected to the network and respond to local queries, so this is nice. They also work in Home Assistant now.

I didn't try repairing the app, as I was afraid I'd break them and would be unable to get them to link to the network. If anyone wants to test this, please let me know. Hello brother, can you create video clips?

KiralyCraft commented 4 months ago

Hmm, that's interesting - Mine didn't do that. I also have that exact same version, GREE+_1.18.6.8_APKPure.apk. Mine debugged without issue, although I do not have Google Apps on my phone. Maybe that's why?

It looks like you're almost there. I did set the GREE+ as the "Select debug app" in Developer Options (I'm on LineageOS 20). Urusus2 told me that he added the debuggable field to his AndroidManifest.xml from within the app. I assume he used apktool, which can unpack and repack APKs: https://www.kali.org/tools/apktool/

It's strange that it worked for me without questions - Android Studio didn't complain one bit, despite using that exact same APK.

Hello brother, can you create video clips?

Sorry, I don't really have time for that, but I've described in quite some detail the procedure here.

szaman-89 commented 4 months ago

That's interesting. Will try to play with repacking APK tommorow. As I understand @Urusus2 have debbugable APK compiled right? If yes, can we @Urusus2 ask you to upload that APK?

KiralyCraft commented 4 months ago

I wonder, have you uninstalled the app from your phone? Or, could you try to run it from an adb shell like am start -D -n "package/package.SomeActivity" (quote from here). You can find the activity name (and the package name) by opening up the app before uninstalling, and running some command to figure out your foreground activity. I've honestly forgot how I did it, but it was probabably something along the lines of this StackOverflow post

I can't remember if I started it this way first, but it did work with letting Android Studio do the install in debug mode, I changed nothing about the APK

Urusus2 commented 4 months ago

That's interesting. Will try to play with repacking APK tommorow. As I understand @Urusus2 have debbugable APK compiled right? If yes, can we @Urusus2 ask you to upload that APK?

Yes. I will upload apk and write instruction, as soon as possible....

Urusus2 commented 4 months ago

@KiralyCraft , with version 1.53 work in Home Assistant and in Gree+ app without any problems...

KiralyCraft commented 4 months ago

@KiralyCraft , with version 1.53 work in Home Assistant and in Gree+ app without any problems...

Hmm, is your app still in test mode? Did you try resetting wifi and connecting again, and it works?

Urusus2 commented 4 months ago

@KiralyCraft , with version 1.53 work in Home Assistant and in Gree+ app without any problems...

Hmm, is your app still in test mode? Did you try resetting wifi and connecting again, and it works?

Is original apk in normal mode, region EU.. Yes, after upgrade firmware in debug mode I reset wifi and add AC in normal mode... P.s. In debug mode need new account, with actual account you can't login, need new registration (may be the same email)...

home-assistant / core

Unavailable Gree AC devices #109230

The problem

What version of Home Assistant Core has the issue?

What was the last working version of Home Assistant Core?

What type of installation are you running?

Integration causing the issue

Link to integration documentation on our website

Diagnostics information

Example YAML snippet

Anything in the logs that might be useful for us?

Additional information

Power Cycle fixed it 🤷