I’ve created a github project that uses github actions to build the firmware
this eliminates a need to install esphome locally
feel free to fork & build
1 Like
@gekkehenkie11
So finally I was able to build it to flash and install and it works!!!
So alot of thanks to you for your work! BTW web ui also works !
Yet the beeper seems to always on, despite I disabled it
Any ideas ?
1 Like
Great to hear it works. About the beeper, not sure, maybe your ac model doesn’t support turning it off, or maybe it’s encoded differently. You did try it via wifi, right, cause it doesn’t work for the remote control
Ok yeah I’d then think that your airco might not support it. Or it could be an alternative encoding of the command for your specific model.
can you give some hint of how to put my hands on the correct command ?
Keep in mind that some AC’s don’t seem to support turning the beeper off, yours might be one of those. That being said, if you have the original wifi module you can experiment with tomikaa87’s code, read this thread here: Command to disable beeping · Issue #44 · tomikaa87/gree-remote · GitHub
The interesting part starts here: Command to disable beeping · Issue #44 · tomikaa87/gree-remote · GitHub
If that does work you can try it with the HA gree integration too, that also supports turning the beeper off. With that you can then dump the packets and see what’s going wrong (or post them here and I’ll take a look). Or just start with the HA gree integration instead:
Again, keep in mind that in both threads there are people reporting that their AC doesnt support the beeper-off mode.
giving up. seems like my units will beep until the end of the days
Hi, I’m new and familiar with ESPHome, I understand that this project is to replace the existing Gree WIFI Module so you can control it locally using ESPHome. But how do I check if my AC support WIFI module? I have 5 Gree AC (tropical country, cold only) but I don’t see any additional cables for the module when I opened the unit. Pictures below
Model number is: GWC-05MOO5S
Anyone know if this model is wifi supported?
some knowledge contribution :
had same build running on same esp connected to almost same ac model, one is older and one is newer.
On the newer model the beeper disable is actually works
On the older ones - no
1 Like
BTW @henkvdt I had ordered some of these connectors from Aliexpress and they fit 100% correctly!! Thanks again, awesome find! I ordered these:
https://es.aliexpress.com/item/1005009830663057.html
Of course I selected the 4 pins version and ordered the “same direction”. The package came with 10 cables but you can cut them in half and then end up with 20 usuable connectors. I also updated the photo in my first post with this info and the installation info on my github. As you can see I simply connected them to 4 du pont cables and then to the module.
Thanks again!
1 Like
Awesome work gekkehenkie11, and piotrva also for the basis. I forked your version which already worked amazingly well and added some twist of my own taste:
- ported FAN_MODES back to stock, HA compliant climate::CLIMATE_FAN_*. This means the stock climate UI element can control it, no need for a (imo) bulky and messy select that looks out of place (this also means I can only use auto, quiet, low, mid, high - but that’s totally fine with me)
- ported boost to be a preset and thus be stock HA compliant. This means I didn’t lose the boost functionality with porting back the fan modes and somehow it feels more at home for me as a preset. At least with my unit, doesn’t feel as if it’s simply overdriving the fan
- ported sleep to be also compliant of the stock sleep preset
Subtle changes but makes it look much more minimal and easily controlled, at least for me.
I also reverted & started using both FAN_SPD1 & FAN_SPD2. I’m not really sure what they’re both doing, I’d be thankful if you could explain? For now I’m trying to test out / figure out why there are two and what each does?
3 Likes
Great you like it! Regarding fanspeed1 and fanspeed2, that’s what piotrva used in his original code. What I made out of that is that some models come with two fans. I’m only using wallmounted AC’s in my house and they all have just 1 fan so I changed the code for that. My original idea was to see if we can make the code more dynamically adapt to the specific AC, so query the model and depending on that change for example the amount of fans. But at the moment I don’t have any time for that.
it’s interesting interfce version whre it’s on github?
@gekkehenkie11
Great work thanks you for resersh and share. I repeted your project on my Daichi DC invertor. For connection used dupont cable by inserting metal terminal snap to plastic part of female connector wich was like a dummy on wifi male cable. Beep swith doesen’t works.
But faced more important issue - AC beginnig works like a on/off AC, not inwertor. It’s heat (in my case i nee heating) at 2 degree more then target and turn to fan only mode till temperature dropping at 2 degree less then trget. At same time external unit works in on/off mode and doesen’t adjust performance smoothly. And now it works like this even if I turn it on using the IR remote. On picture inverter mode before and on/off mode after ESP32 inserting.
hey that’s extremely odd. So you’re saying that the AC’s algo changed by using the ESP and that you can’t change it back, even when using the remote? Normally that’s impossible: Even if there would be a ‘secret’ setting for this, the moment you use the remote control it simply sends all bytes to the AC, changing any setting that you might have changed via WIFI. Unless in your specific model there maybe is some kind of debug mode that’s activated by for example the last few bytes and these bytes are not getting sent by your remote control? Weird … What you’re seeing now is a regular cooling algo by the way, my (inverter) AC’s from all brands work like that, even the highest SEER ones. I only use them for cooling though (i live in a hot climate). I’ve never even seen that first part of your power consumption chart. I guess that’s something specific for heating modes maybe? I’ve also never seen that before using the ESP’s… BTW, it also doesn’t make much sense anyway, I mean if the AC would (before) heat continually with 500 watts, then what would happen if the temp would become too high?
Do you have stored charts from this from before? I would like to see a whole day of how it used to be, I almost can’t believe it would be a straight 500w line.
Either way, did you try resetting your AC by unplugging the power source (or flipping the breaker in your panel)?
For example, this is last night for a specific AC, but all models and brands I have show this behaviour:
This BTW is a high SEER (energy efficient) model from panasonic, it doesn’t even have WIFI.
In my experience, this pattern happens when the AC has to much power for current temperature. Even on the lowest possible compressor mode, it still generates too much heat. This triggers the ‘on/off’ pattern. On each compressor start, the power usage always shortly peaks. My assumption is that when the outside temperature drops again (for example coming night), your pattern will be steady again.
1 Like
Yeah makes sense. I can’t believe that there would be a secret command in the last few bytes, because the last byte is checksum! So if anything, it would not work at all. I’m pretty sure it’s something like you say @henkvdt
So to explain, what I’m saying is that each time you send a command to the AC, it sends the same X amounts of bytes, where every bit/byte represents a setting/command. So if you change a setting via WIFI, it simply sends all bytes every time, so all commands/settings, the whole bunch. The same goes for the remote control. So how would it be possible that there would be a setting that’s only changeable via WIFI and not via the remote? The only thing i could think of is if the ESP code would send some ‘extra’ bytes that are not being sent via the control. HOWEVER that doesnt make any sense, since the last byte is always checksum. So there are no ‘extra’ bytes possible here. So, long story short, if there were a setting that was changed via wifi, simply using your remote control should always revert that setting.
So for example, if you change the AC mode from cooling to heating via wifi and then on your remote control press the ‘temp down’ key, it will revert back to cooling, since your remote control is still set to that, and it sends ALL bytes, so the complete configuration every time. It doesn’t just send a ‘temp down’ command, it sends the complete AC configuration every time.