We managed to get the different modes; the sticking point now is how to programmatically figure which modes any given model implements. I’ve tried several times to get the app working in an emulator with mitmproxy, but so far have been unsuccessful.
Regardless of the modes, should HA be able to at least connect to my Dehumidifier and turn it On/Off? Or is it the modes issue that’s preventing any connection? For me it just says “Unavailable”
If it’s in the ‘dry’ or ‘continuous’ modes I think it should work still. If it’s in the quiet or auto modes it will cause a crash at the moment though.
You’re right, in continuous mode HA saw it and was able to turn it off/on.
Please let me know if you’ve gotten a chance to test this more, or if I can assist in any way.
Just wondering if this is still being actively developed or not. I’ve been controlling my Frigidaire dehumidifier with a smart plug for the last 1-2 years and no found this. Installed the latest build and it seems to connect, but it constantly shows my dehumidifier as unavailable.
The unit I have is a FGAC5044W1 like others have mentioned. Arguably if even just the state could easily be changed this would be workable for me – I could leave it in continuous mode and use the humidity sensor on my ecobee to turn the unit on and off via Home Assistant (essentially the same as I have been doing with a smart plug, but without harshly adding or pulling power which can’t be great for the compressor).
Also in case it helps, if I go to logs I keep seeing errors from line 181 in humidifier.py
Hi All,
I have model FGAC7044U1, I few more options on mine like setting the desired humidity percentage or continuous mores and fan speed (High/Low), with no ionizer.
Was able to add the integration, and logged in fine but Point 6. “It should say it successfully added N number of climate entities.” didn’t happen but it did add the humidifier as an entity (still I don’t think I can’t interact with it or any other function).
@gazpachoking saw you suggested using the raw library, happy to help and do that but have no idea how?
Also looking to integrate this to automate with Ecobee and also capture data from it.
@Conundrum1911 I have started working on @bm1549 's home-assistant-frigidaire repository and I plan to be relatively active on it. I currently have a FGAC5044W1, and the most recent commit adds extra functionality for that model.
1 Like
I added the hvac_action attribute for testing on thejevans/home-assistant-frigidaire:hvac_action, but I don’t have an AC unit. If someone could test this and get back to me, we can get this functionality added.
I just sat through a UX testing session for a new frigidaire app. This seems to be coming soon, and might bring with it API changes that would break the current frigidaire API wrapper by @bm1549.
just commented on the pull request. Currently have the main branch installed, I have a generic thermostat added to my dash and can successfully command the window unit to do various actions.
Each button press on dash card returns this error however, although it still seems to perform as it should.
Hitting Auto button on the bottom left puts the unit in eco mode, cooling button in cooling mode, fan mode in fan only mode in low (can’t seem to change the fan speed beyond low), power is power and set temp slider commands as expected.
What does your hvac_action pull address specifically? Don’t have time to dig into code right now but happy to help in any way I can.
Window Unit model number FHWW063WB1
I can test out hvac_action branch later this weekend.
Thanks so much for this custom integration/add-on. It’s hugely useful. I have some newbie questions, apologies if these are old…
I have the FGAC5044W1 dehumidifier as well, and I’m somewhat perplexed at the ionizer function which isn’t available on the control panel, only in the Frigidaire app.
-
Is there a way to turn the ionizer on/off with this add-on? I currently do it in HA with Assistant Relay to Google Assistant, but would love a “native” way to do this.
-
Getting updated status from Frigidaire server is pretty slow, at 15-30 second delay at times. Maybe this is unavoidable, but is there a way to poll for status maybe 3-5 seconds after issuing a command?
-
The names of the modes on my model (Auto, Quiet, Dry and Continuous) don’t line up with what shows up in HA, as with @calllka21. Is there a way to set these manually?
-
I can change the target humidity mode fine in HA, but the dehumidifier only seems to take the changes if done in increments of 5 (45%, 50%, 55% RH, etc.) HA’s slider moves in increments of 1, which makes changing the humidity a bit of an exercise in precise finger dragging. Is there an easy way to change this?
Thanks again!
I know that this feed is super old, but I am trying to set up this integration and I am completely stuck. When I put in my email and password, it says that I failed to connect. I have no idea what I am doing wrong. Thank you for any help!
This is a new issue. It looks like Electrolux/Frigidaire is making API changes that need to be sorted out.
Thank you for the reply and explanation! I wish that I could be of help sorting it out but I am completely code-illiterate haha.
I’m also experiencing a “Failed to Connect” error when trying to authenticate with Frigidaire. Is there any information we can provide to get the component back to a workable state?
Apparently there’s a new version of the custom component that fixes this. It’s a one-line fix. It’s working again for me now!
I just installed it from HACS and logged with my frigidaire account, all works fine.
This definitely didn’t just work out of the box for me. I created a repo with the fixes mentioned here and additional changes to use the latest REST API from Frigidaire (fixes login error) and to fix an incompatibility with the latest HomeAssistant API (fixes config flow crash).
Just clone this into “config/custom_components” and it should work. Well, it works for me in my Docker-based install anyway:
Thank you for this! Worked perfectly for me (GHPC132AB1)!