-
Notifications
You must be signed in to change notification settings - Fork 58
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
AEH-W4F1 #17
Comments
The error you got makes it seem to me that there is a deeper error here. |
So the IP address is correct, but out of curiosity I just tried entering the wrong IP address and then running Also, just to make sure we are on the same page about those errors (I also updated my original post with this info), they showed up when I ran this command I tried running the server with --log_level=DEBUG, but unfortunately I'm not quite sure where to find that log info (system log maybe?) So for now, to me it seems like this AC/Wifi module just might not work... No worries! Either way, thanks again for your response, and let us know if you have any other thoughts or tricks up your sleeve for AEH-W4F1. |
All the logs are stored in |
Not sure if this is everything you would need to troubleshoot, but here is what I found in my syslog:
|
OK, let's take a step back, as it seems even the initial communication with the A/C fails. |
Good call, I am using the "HiSmart Air" Android app. |
If it is this one, then the code for local control is exactly the same. |
That is the one. I don't know about controlling the AC locally, but I can definitely get the "Page not found" 404 response when entering the AC's IP into a web browser. I'm starting to wonder about the reliability of the wifi module and/or app. Hisense's software is pretty terrible. If/when I get the AC connected to the app, it works for a minute and then pretty quickly becomes unavailable. But even when it is unavailable in the app, I can still reach the "Page not found" 404 response. I'll keep messing with things here and report back if anything worth reporting comes up. |
I've changed code to repeatedly retry the local registration against the A/C, in case if fails. It may resolve the flakiness issue. |
I tried messing with this a little more today, but am still facing the same issues. Curious if anybody else out there has tried AirCon with the AEH-W4F1... |
I have a dehumidifier with this module. I have a somewhat similar experience trying to control it with this project, but for me it does work fine with the app. The status command returns info, albeit inaccurate info like above. A power on/off command hangs, but the daemon doesn’t die. I don’t seem to have any errors logged like the above indicating any failures to connect. I’d love to help get this one working, if that’s at all possible. |
@henworth are you running it with |
Hi, |
Hello all, I have the same problem with two Hisense AC's (Module: AEH-W4B1). {"f_electricity": 100, "f_e_arkgrille": 0, "f_e_incoiltemp": 0, "f_e_incom": 0, "f_e_indisplay": 0, "f_e_ineeprom": 0, "f_e_inele": 0, "f_e_infanmotor": 0, "f_e_inhumidity": 0, "f_e_inkeys": 0, "f_e_inlow": 0, "f_e_intemp": 0, "f_e_invzero": 0, "f_e_outcoiltemp": 0, "f_e_outeeprom": 0, "f_e_outgastemp": 0, "f_e_outmachine2": 0, "f_e_outmachine": 0, "f_e_outtemp": 0, "f_e_outtemplow": 0, "f_e_push": 0, "f_filterclean": 0, "f_humidity": 50, "f_power_display": 0, "f_temp_in": 81.0, "f_voltage": 0, "t_backlight": "OFF", "t_control_value": null, "t_device_info": 0, "t_display_power": null, "t_eco": "OFF", "t_fan_leftright": "OFF", "t_fan_mute": "OFF", "t_fan_power": "OFF", "t_fan_speed": "AUTO", "t_ftkt_start": null, "t_power": "ON", "t_run_mode": "OFF", "t_setmulti_value": null, "t_sleep": "STOP", "t_temp": 81, "t_temptype": "FAHRENHEIT", "t_temp_eight": "OFF", "t_temp_heatcold": "OFF", "t_work_mode": "AUTO"} But when I use the Python query tool with the "--properies true" flag I see both AC's with correct values. Syslog: |
Hi, I have the W4F1 version as well, the ac works fine with the Tornado 2-wifi app, no issues. When I run the status command I get back a JSON that looks correct (and as opposed to others it only works on the correct IP of the AC). But when I try to send it a command it hangs for a while and I get this error in hisense.py:
|
Hi @kaaspad, you seem to be getting a 404 error for the key exchange, which is really strange. Could you please try re-running discovery, and update the config file with the version at HEAD? |
@deiger, was just trying with my AC with the same version, your last commit created a syntax error, see bellow please, TracebTraceback (most recent call last): |
Also, when running with the new code(and new discovery) and running I get this: HTTP/1.1 400 Bad Request 400: Bad Request% The status curl command works well.. |
Oops, fixed the bug now. |
👍 I can approve this is working using MQTT(HA). With auto discovery it picked the AC. |
I'm using Torando with Hisense w4F1.
|
Just picked up a new Hisense portable AC (AP1419CW1G) and decided to see if this might work with it, and it seems close... My AC unit has the AEH-W4F1 wifi module, which does not appear to be very widespread yet.
Running the
curl -ik 'http://localhost:8888/hisense/status'
command gives me the following (which seemed encouraging, although the temperature readings did not seem accurate):But when I try the
curl -ik 'http://localhost:8888/hisense/command?property=t_power&value=ON'
command the CLI/service appears to hang, and I need to restart the service before the "status" command will work again.Not completely sure if this is related but checking the status of the service (by running this command
systemctl status hisense.service
) I get these errors:Any thoughts on getting this AC to work?
Thanks for working on this project @deiger , and thanks in advance for any and all support!
The text was updated successfully, but these errors were encountered: