search

simbaja / ha_gehome

GE Home Appliances (SmartHQ) for Home Assistant
MIT License
349 stars 81 forks source link

Window AC unit showing incorrect temperature #92

Closed jwagner0789 closed 1 day ago

jwagner0789 commented 2 years ago

HA is showing the target temperature incorrectly(tens of thousands). I can only resolve this if I go to the Smart HQ app and set the temperature.

simbaja commented 2 years ago

Can you provide a debug log from the websocket_example in the simbaja/gehome repository? That would help me diagnose the values you are seeing.

jwagner0789 commented 2 years ago

Not sure if this is what your asking for. I just turned on debug for the ge_home component. image

simbaja commented 2 years ago

That's helpful. Does the climate control also show an incorrect set point? What is the appliance set to? What model is it?

jwagner0789 commented 2 years ago

Currently, it is set to 74. Model: AHTK12AAW1 image

simbaja commented 2 years ago

What does the SmartHQ app show for this? If it shows correctly, we might need to get a full debug log by running the underlying code from the simbaja/gehome repository (this runs in Python, not Home Assistant)

jwagner0789 commented 2 years ago

SmartHQ is accurate. Not sure how to preform the next steps.

simbaja commented 2 years ago

If you can't run the python project, you might be able to just turn on debugging overall (instead of for the component) and find the gehomesdk calls. What I'm looking for is on startup, it should enumerate every value that's available and then we can see what is going on and locate the correct key to fix this.

simbaja commented 2 years ago

Ok, I made an easier way to get to the data needed. Install gehomesdk (pip install gehomesdk) then run gehome-appliance-data. It'll ask for your credentials, but should display the details I need.

ChrisCrewdson commented 2 years ago

I get the same issue occasionally, but have not yet been able to capture it with gehome-appliance-data. It only happens rarely for me and only in the "Target temperature" as you can see in the attached image. 2022-08-13 (2)

It is interesting that for me, the error values are the same set of values: the first two peaks are 10,791 and the other peaks are 10,222.

I think this might have something to do with a power loss based on when the spikes have been, but I have not been able to trigger it.

Perhaps a workaround would be to throw out any data above 10,000? I can't see a case where that would be a valid value.

simbaja commented 2 years ago

@jwagner0789 is it always these higher temperatures, or is it only sometimes like @ChrisCrewdson ? If it's only sometimes, I think his suggestion could work.

jwagner0789 commented 2 years ago

Yes, my values are always greater than 15,000. So setting a 10,000 limit should work.

simbaja commented 2 years ago

Is it ever correct? Or always wrong? If always wrong, I think we might need another approach (which needs data from the application I mentioned)

jwagner0789 commented 2 years ago

It's occasionally correct. Usually when I call a service and set the temp it will stay correct for a little while. Screenshot_20220816-180654~2.png

simbaja commented 1 year ago

Are you still experiencing this? Apologies, really hard to figure out when I don't have a way to reproduce myself...

ChrisCrewdson commented 1 year ago

I no longer own this AC unit. I think ignoring values above 10k is still a reasonable (although strange) solution.

jwagner0789 commented 1 year ago

Same and agree with Chris.

simbaja commented 1 day ago

I don't know if this is still happening, but please feel free to submit a pull request to add the required functionality.