I’ve finished with the code and step-by-step description: https://github.com/meke1111/gree-controller-openhab-habpanel .
yoiu could configuere a log filter in log4j.xml
see here: Log filtering in OH 3
I think this is the better option, because it also saves resources
1 Like
I’ll have a look to it after my vacation and then we could integrated it to the documentation as a use case document.
1 Like
I’ve started this binding recently and I have the same problem - did you find any workaround?
If you ask for the created widget by me, you can set it by clicking on the target knob bar.
Hello Markus,
thanks alot for providing this binding.
I have been using it with 2 TOSOT (by Gree) Split AC Appliances.
On OH2.x it has been working glueless but since I updated to
OH3 and using the Gree-Binding “org.openhab.binding.gree-3.2.0-SNAPSHOT.jar”, I still
get sporadically the following log messages:
“Thing initialization failed: Unable to bind to device”
This had been discussed once, but I could not find a confirmed
solution. Can you pls tell me what the status or even
better the solution is to stop the reason for those messages ?
Thank you.
Best regards
funcarver72
I‘m not aware of a specific fix. Is it just log noise or do you have service interruptions?
Yes, I encounter connection interruptions during the time of the log messages. The AC interface does not react immediately, the instructions get stacked and executed upon reconnection.
still can’t control temperature maybe you find something?
Hi all,
I keep getting following error in the taillog after configuring the Thing:
2022-07-26 17:03:49.952 [INFO ] [ng.gree.internal.handler.GreeHandler] - mygreeID001: Thing initialization failed: Decryption of recieved data failed
Any hints on how to solve this?
Thanks
Which firmware version are you running on your indoor unit? I was always afraid of firmware updates from Gree, we never know when they will change the communication from plain to encrypted, which would break the binding, so i did not allow any updates in the past year… Lets collect which firmware version do we run yet successfully.
These are the firmwares which i can confirm working:
MID: 10001-v9.6
Firmware: v3.56, v3.58, v3.67
The app reports latest available for download: v3.72
Anyone using the latest already?
I could log in with the newer app finally. Unit is MID 100001-v9.6, SW is 3.8 and it offers 3.9. Unit itself min 5-6 years old and I do not remember that I have ever refreshed the SW on it.
Firmware:
MID: 10001-v8.4
Firmware: V1.08
Region: Europe
I’ve installed the brand new gree wifi modules in my Vaillant airco’s but it seems that the firmware is way older then the one that you are using… strange. No update possible because server version is also V1.08 
Interesting as my model is quite old as well. Mine with 3.8 works very well. I forget to mention it.
My units are 6, 4 and 3 years old ones, all of them have the same model number and called Comfort X units. @kovacsi2899 yours are the same? Very strange you have fw v3.8, its not available to me for my units (or maybe first i have to update to 3.72?). Cant see the logic here…
guys, different product lines may have different firmware
turn on debugging and at least we see if the is an initial response when the bindings starts communication. Otherwise, this is an indicator that the unit is not compatible (implementing a different API)
1 Like
Hi Markus, thanks its good idea. We thought MID is somehow related to the hardver version and that is the same for me and @kovacsi2899, so my logic would say fw should be the same. I will check by debug.
My device discovery looks like this:
2022-07-24 10:12:43.975 [DEBUG] [ng.gree.internal.handler.GreeHandler] - 2059a0b49c2f: Automatic refresh started (60 second interval)
2022-07-24 10:12:43.975 [DEBUG] [.internal.discovery.GreeDeviceFinder] - Sending scan packet to 192.168.50.70
2022-07-24 10:12:44.006 [DEBUG] [.internal.discovery.GreeDeviceFinder] - Response received from address 192.168.50.70: {"t":"dev","cid":"2059a0b49c2f","bc":"gree","brand":"gree","catalog":"gree","mac":"2059a0b49c2f","mid":"10001","model":"gree","name":"a0b49c2f","series":"gree","vender":"1","ver":"V1.1.13","lock":0}
2022-07-24 10:12:44.006 [DEBUG] [.internal.discovery.GreeDeviceFinder] - Discovered device at 192.168.50.70:7000
2022-07-24 10:12:44.006 [DEBUG] [.internal.discovery.GreeDeviceFinder] - Response received from address 192.168.50.70: {"t":"dev","cid":"2059a0b49c2f","bc":"gree","brand":"gree","catalog":"gree","mac":"2059a0b49c2f","mid":"10001","model":"gree","name":"a0b49c2f","series":"gree","vender":"1","ver":"V1.1.13","lock":0}
2022-07-24 10:12:44.006 [DEBUG] [.internal.discovery.GreeDeviceFinder] - Discovered device at 192.168.50.70:7000
2022-07-24 10:12:44.022 [DEBUG] [.internal.discovery.GreeDeviceFinder] - Response received from address 192.168.50.70: {"t":"dev","cid":"2059a0b49c2f","bc":"gree","brand":"gree","catalog":"gree","mac":"2059a0b49c2f","mid":"10001","model":"gree","name":"a0b49c2f","series":"gree","vender":"1","ver":"V1.1.13","lock":0}
2022-07-24 10:12:44.022 [DEBUG] [.internal.discovery.GreeDeviceFinder] - Discovered device at 192.168.50.70:7000
2022-07-24 10:12:51.013 [DEBUG] [ernal.discovery.GreeDiscoveryService] - 1 eszköz található.
2022-07-24 10:12:51.013 [DEBUG] [ernal.discovery.GreeDiscoveryService] - Adding uinits to Inbox
2022-07-24 10:12:51.013 [DEBUG] [ernal.discovery.GreeDiscoveryService] - A a0b49c2f eszközt 192.168.50.70 címen találtam, MAC=2059a0b49c2f
2022-07-24 10:12:51.013 [DEBUG] [ernal.discovery.GreeDiscoveryService] - 1 eszköz található.
2022-07-24 10:12:51.013 [DEBUG] [ernal.discovery.GreeDiscoveryService] - Adding uinits to Inbox
2022-07-24 10:12:51.013 [DEBUG] [ernal.discovery.GreeDiscoveryService] - A a0b49c2f eszközt 192.168.50.70 címen találtam, MAC=2059a0b49c2f
2022-07-24 10:12:53.644 [DEBUG] [.gree.internal.handler.GreeAirDevice] - Response from device: {"t":"dat","mac":"2059a0b49c2f","r":200,"cols":["Pow","Mod","SetTem","WdSpd","Air","Blo","Health","SwhSlp","Lig","SwingLfRig","SwUpDn","Quiet","Tur","TemUn","StHt","HeatCoolType","TemRec","SvSt","NoiseSet","TemSen"],"dat":[0,1,25,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0]}
2022-07-24 10:12:53.644 [DEBUG] [ng.gree.internal.handler.GreeHandler] - 2059a0b49c2f: Executing automatic update of values
2022-07-24 10:12:53.644 [DEBUG] [ng.gree.internal.handler.GreeHandler] - 2059a0b49c2f: Updating channel power : OFF
2022-07-24 10:12:53.644 [DEBUG] [ng.gree.internal.handler.GreeHandler] - 2059a0b49c2f: Updading mode channel with 1/cool
2022-07-24 10:12:53.644 [DEBUG] [ng.gree.internal.handler.GreeHandler] - 2059a0b49c2f: Updating channel mode : cool
2022-07-24 10:12:53.644 [DEBUG] [ng.gree.internal.handler.GreeHandler] - 2059a0b49c2f: Updating channel temperature : 25 °C
2022-07-24 10:12:53.644 [DEBUG] [ng.gree.internal.handler.GreeHandler] - 2059a0b49c2f: Updating channel currentTemperature : UNDEF
2022-07-24 10:12:53.644 [DEBUG] [ng.gree.internal.handler.GreeHandler] - 2059a0b49c2f: Updating channel air : OFF
2022-07-24 10:12:53.644 [DEBUG] [ng.gree.internal.handler.GreeHandler] - 2059a0b49c2f: Updating channel dry : OFF
2022-07-24 10:12:53.644 [DEBUG] [ng.gree.internal.handler.GreeHandler] - 2059a0b49c2f: Updating channel turbo : OFF
2022-07-24 10:12:53.644 [DEBUG] [ng.gree.internal.handler.GreeHandler] - 2059a0b49c2f: Updating channel windspeed : 0
2022-07-24 10:12:53.644 [DEBUG] [ng.gree.internal.handler.GreeHandler] - 2059a0b49c2f: Updating channel quiet : off
2022-07-24 10:12:53.644 [DEBUG] [ng.gree.internal.handler.GreeHandler] - 2059a0b49c2f: Updating channel swingUpDown : 0
2022-07-24 10:12:53.660 [DEBUG] [ng.gree.internal.handler.GreeHandler] - 2059a0b49c2f: Updating channel swingLeftRight : 0
2022-07-24 10:12:53.660 [DEBUG] [ng.gree.internal.handler.GreeHandler] - 2059a0b49c2f: Updating channel powersave : OFF
2022-07-24 10:12:53.660 [DEBUG] [ng.gree.internal.handler.GreeHandler] - 2059a0b49c2f: Updating channel light : ON
2022-07-24 10:12:53.660 [DEBUG] [ng.gree.internal.handler.GreeHandler] - 2059a0b49c2f: Updating channel health : OFF
This is my device:
Gree GWH18QD-K3DNBG4 and it was installed in 2016 - 6 years ago.
Thanks for this binding. After update from OH2 to OH3 (fresh installation) I’m not able to set target temperature (is read only). The ON/OFF switch work perfect.
How can I fix that?
Check channel data types of the new binding, something was changed if i remember correctly…