Tried everything and this is what I get in log

pi BridgeRPiWARNINGwarning: 192.168.1.199: 192.168.1.199:8888: cannot connect: ECONNREFUSED
9/7/2023,
10:43:48 AMRpi BridgeRPiWARNINGwarning: 192.168.1.199: 192.168.1.199:8888: cannot connect: ECONNREFUSED

I have tried changing configuration every which way

{
"platform": "homebridge-frigidaire",
"name": "Tim's A/C",
"applianceSerial": "10314XXX",
"bridge": {
"username": "B2:6F:0A:23:XX:XX",
"port": "51XXX"
},
"username": "[email protected]",
"password": "XxX11112222!",
"cacheRefreshToken": true
}

I have tried removing an adding different items to configuration

Using the new App in Canada White Square with inner RED triangle, connected in app and working

Using Homebridge connected to a rPi
Using Hoobs 4.3.0

not having any issues with other plugins

tried using other bridges and creating its own bridge.

9/7/2023, 10:55:04 AMRpi BridgeRPiWARNINGwarning: 192.168.1.199: 192.168.1.199:8888: cannot connect: ECONNREFUSED

homebridge-frigidaire can get in a state where CPU goes runaway, causing the rest of home bridge to become slow/non-responsive.

Homebridge sees the air conditioners and adds them to home, but their status always says "no response."

2.1.3 is causing the AC unit to become unavailable every time it is polled for the filter status. Please revert or adjust!

The unavailability is unrelated and due to something that dropped with today's Home Assistant update, but these errors below are indeed new with 2.1.3 for me:

Wed, 07 Jul 2021 21:21:00 GMT frigidaire:homebridge getFilter:  0
[7/7/2021, 5:21:00 PM] [homebridge-frigidaire] This plugin generated a warning from the characteristic 'Filter Change Indication': characteristic value expected valid finite number and received "undefined" (undefined). See https://git.io/JtMGR for more info.
[7/7/2021, 5:21:00 PM] [homebridge-frigidaire] Error: 
    at FilterChangeIndication.Characteristic.characteristicWarning (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:2038:105)
    at FilterChangeIndication.Characteristic.validateUserInput (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:1931:16)
    at /usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:1533:24
    at /usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/util/once.ts:9:18
    at /homebridge/node_modules/homebridge-frigidaire/index.js:431:14
    at /homebridge/node_modules/homebridge-frigidaire/node_modules/frigidaire/lib/frigidaire.js:1004:17
    at Frigidaire.getValue (/homebridge/node_modules/homebridge-frigidaire/node_modules/frigidaire/lib/frigidaire.js:765:13)
    at Frigidaire.getFilter (/homebridge/node_modules/homebridge-frigidaire/node_modules/frigidaire/lib/frigidaire.js:1000:11)
    at FrigidaireAirConditionerAccessory.getFilter (/homebridge/node_modules/homebridge-frigidaire/index.js:416:13)
    at FilterChangeIndication.emit (events.js:376:20)

My server has been sending out of space warnings because this plugin has spammed my system logs enough to fill an entire partition! How do I tell this plugin to shut up?

Hi there,

first of all. Thanks for your idea to automate an AC with Homebridge.
I recently bought an AEG PX71-265WT which schould be the same as the frigidaire.

I read the few Issues before me an want to ask if there could have been anything done to make this plugin work with the european AC.
It would be nice to get it in my Homekit. I really hate using more than one App.
If you need an information feel free to ask. I'm not able to code but I'm able to follow instructions.

Do you have any guidance on actually setting this up with a working AC and Homebridge? I have two of this model AC and homebridge running but no idea how to get this to work.

In the Homebridge console window, I observed the “[Frigidaire AC Units]” status messages were polling the unit every 5 seconds (based on the timestamps)

The provided default / sample config does not display the config argument “pollingInterval”, which when not provided defaults to 10000 (ms).

I added pollingInterval (case sensitive) to my platform config and set the value to 30000 (ms) to observe the change in the Homebridge console output and noted the polling interval changed from the observed 5 seconds to 15 seconds.

I then modified the value to 20000 and observed the pollingInterval became 10 seconds.

With this in mind, I believe the interval is being halved (/2) somewhere in code.

The 2.0 update works! However, now my current temperature numbers are all out of whack (see image). They shouldn't be negative Celsius values... (I use Celsius in the house).

Wed, 02 Jun 2021 16:41:14 GMT frigidaire applianceId 71012357-C83DD4BA1AE2 attribute 0432 has the value 20
Wed, 02 Jun 2021 16:41:14 GMT homebridge-frigidaire getTargetTemperature: 20 -> -6.666666666666666
[6/2/2021, 12:41:14 PM] [homebridge-frigidaire] This plugin generated a warning from the characteristic 'Target Temperature': characteristic was supplied illegal value: number -6.666666666666666 exceeded minimum of 15.5. See https://git.io/JtMGR for more info.

My AC units are connected to Home Assistant via the HomeKit Controller integration.

I set "Cool" in HA, and the AC beeps to the correct mode and HA shows the new mode, but then HA switches back to the previous mode. Only after another 15-30 seconds or so does HA update to the actual AC state. Same for temperature adjustments, etc.

This results in my smart home seeing the AC turn on, turn off, then turn back on again, which breaks nearly all of my automations.

This glitch is also visible directly inside Homebridge, but it's a delay instead (the status doesn't change until the next API poll).

TL;DR:
Prevent in-between or stale data from causing update events after writing data. Be optimistic about the data write.

I have some feedback on why this could be happening / how it might be solved from one of the Home Assistant integration developers:

So theres a couple of different mechanisms at play, but it probably boils down to homebridge.
So first of all the UI gives the backend a couple of seconds. So if you toggle a light, the UI will show the new state for 2-5s to give the backend chance to update, then flip back.

The next mechanism is that when a homekit accessory accepts a change, it is expected to be consistent - you should be able to read it straight back out. so homekit_controller will apply all successful writes as though they were poll results or notifications

so as soon as target device accepts the "cool me plz" state, homekit_controller acts as thought the device send a push notification to say its in the "cool me plz" state.

like i say, spec compliant certified devices - its consistent. you write a value, you can read it back. it's actually expected that you are "optimistic" in the spec - it explicitly doesn't send events for changes that you made your self.
so if you turn a light on, you dont get a state change event to say its on, its expected that you know its on
if you weren't optimistic you'd have to poll instead

now we get to homebridge
every plugin is different [...]
some run a 60s poll loop
remember that HA does too
before events in homekit_controller that meant [...] [a] random val from 1 to 60 + another random val from 1 to 60, and thats how much lag you would see before updates were visible
we are still subject to the polling in homebridge though

so if the plugin isn't optimistic, it might accept a write but then serve stale information for a minute (or even longer i guess, its up to the plugin)

that shouldn't matter of course, because it shouldn't generate events for stale data

but.. HA still polls as sort of a backup in case events don't work [...]
so the HA poll can revert to the sale information served by homebridge
then when the homebridge plugin polls and gets the right state, it generates events that correct HA

[...]

Hi Brian,

First: Thank you for taking the time to create this.

Second: Would you please consider writing a readme for it? I have two Frigidaire Wi-Fi enabled AC units that I'd like to control via HomeKit / Siri, but I'm just getting into learning about HomeBridge, and am not sure what values I need to modify in the provided files to get a working installation for my setup.

Thanks!

Is it possible to expose the Fan Only Mode of the AC units?

When enabled, my air conditioners are showing up in the Home app, but Home is reading a temp of 1ºF. Additionally, when changes are made to the temp or fan speed via the Home app, the AC unit(s) beep to indicate they've received a command, but Home doesn't reflect any change as having been made. Is there any chance of this being resolved? I know Frigidaire seems to be messing around with having just launched yet another new app (as opposed to just updating the existing one) so I don't know if it's worth it or realistic to try to chase their changes. Thank you for the work that's been done to date.

I am having two issues with this plug-in and I think they could be related.

On start-up I am getting this error.

This plugin generated a warning from the characteristic 'Filter Change Indication': characteristic value expected valid finite number and received "undefined" (undefined). See https://homebridge.io/w/JtMGR for more info.
After about 24 hours of running, the device stops responding in HomeKit and I get this error.

This plugin slows down Homebridge. The read handler for the characteristic 'Filter Change Indication' didn't respond at all!. Please check that you properly call the callback! See https://homebridge.io/w/JtMGR for more info.

[9/12/2022, 7:30:25 PM] [Frigidaire] Launched child bridge with PID 9966
[9/12/2022, 7:30:26 PM] Registering platform 'homebridge-frigidaire.Frigidaire'
[9/12/2022, 7:30:26 PM] [Frigidaire] Loaded homebridge-frigidaire v2.1.3 child bridge successfully
craeting accessory for AC unit labeled : My RAC 71656752
[9/12/2022, 7:30:27 PM] Initializing platform accessory 'My RAC 71656752'...
[9/12/2022, 7:30:27 PM] Publishing bridge accessory (name: Frigidaire, publishInfo: {
username: '::::',
port: ,
pincode: '--*',
category: 2,
bind: undefined,
mdns: undefined,
addIdentifyingMaterial: true,
advertiser: 'bonjour-hap'
}).
[9/12/2022, 7:30:27 PM] Homebridge v1.5.0 (HAP v0.10.2) (Frigidaire) is running on port 45848.
[9/12/2022, 7:30:28 PM] [homebridge-frigidaire] Characteristic 'On': SET handler returned write response value, though the characteristic doesn't support write response. See https://homebridge.io/w/JtMGR for more info.
[9/12/2022, 7:30:28 PM] [homebridge-frigidaire] Error:
at On.Characteristic.characteristicWarning (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:2142:105)
at /usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:1756:22
at /usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/util/once.ts:10:18
at FrigidaireAirConditionerAccessory.setCleanAir (/usr/local/lib/node_modules/homebridge-frigidaire/index.js:198:14)
at On.emit (node:events:513:28)
at /usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:1725:16
at new Promise ()
at On. (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:1723:14)
at step (/usr/local/lib/node_modules/homebridge/node_modules/tslib/tslib.js:144:27)
at Object.next (/usr/local/lib/node_modules/homebridge/node_modules/tslib/tslib.js:125:57)
[9/12/2022, 7:30:28 PM] [homebridge-frigidaire] This plugin generated a warning from the characteristic 'Filter Change Indication': characteristic value expected valid finite number and received "undefined" (undefined). See https://homebridge.io/w/JtMGR for more info.
[9/12/2022, 7:30:28 PM] [homebridge-frigidaire] Error:
at FilterChangeIndication.Characteristic.characteristicWarning (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:2142:105)
at FilterChangeIndication.Characteristic.validateUserInput (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:2030:14)
at /usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:1617:24
at /usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/util/once.ts:10:18
at /usr/local/lib/node_modules/homebridge-frigidaire/index.js:431:14
at /usr/local/lib/node_modules/homebridge-frigidaire/node_modules/frigidaire/lib/frigidaire.js:1004:17
at Frigidaire.getValue (/usr/local/lib/node_modules/homebridge-frigidaire/node_modules/frigidaire/lib/frigidaire.js:765:13)
at Frigidaire.getFilter (/usr/local/lib/node_modules/homebridge-frigidaire/node_modules/frigidaire/lib/frigidaire.js:1000:11)
at FrigidaireAirConditionerAccessory.getFilter (/usr/local/lib/node_modules/homebridge-frigidaire/index.js:416:13)
at FilterChangeIndication.emit (node:events:513:28)

The readme would be really handy, but could you also publish with NPM so it would be included with most other HomeBridge options?

Installation ran smoothly, there were no error codes, all credentials entered properly in the platform, but unfortunately my new Frigidaire AC which uses Cool Connect WI-FI will not appear in my Homebridge accessories. Thoughts?

I recently changed my password but since Homebridge was already running nothing happened and things were fine. However, today I restarted my homebridge server and was given this error:

[8/7/2019, 12:50:44 PM] TypeError: Cannot read property 'attributes' of undefined
    at /usr/local/lib/node_modules/homebridge-frigidaire/node_modules/frigidaire/lib/frigidaire.js:439:58
    at Request._callback (/usr/local/lib/node_modules/homebridge-frigidaire/node_modules/frigidaire/lib/frigidaire.js:285:14)
    at Request.self.callback (/usr/local/lib/node_modules/homebridge-frigidaire/node_modules/request/request.js:185:22)
    at Request.emit (events.js:198:13)
    at Request.<anonymous> (/usr/local/lib/node_modules/homebridge-frigidaire/node_modules/request/request.js:1161:10)
    at Request.emit (events.js:198:13)
    at IncomingMessage.<anonymous> (/usr/local/lib/node_modules/homebridge-frigidaire/node_modules/request/request.js:1083:12)
    at Object.onceWrapper (events.js:286:20)
    at IncomingMessage.emit (events.js:203:15)
    at endReadableNT (_stream_readable.js:1129:12)
    at process._tickCallback (internal/process/next_tick.js:63:19)

Turns out I needed to update my password in my config.json file, but the error above gives me zero hint that this was the problem. Is there a way to make this clearer, like "Error: bad login credentials / could not login"?

I was previously using this plug-in successfully but had to rebuild my homebridge environment. Now, on the latest up to date version, when I install this plug-in, homebridge won't finish loading.

The terminal displays this message:

"This plugin is taking long time to load and preventing Homebridge from starting. See https://git.io/JtMGR for more info."

[6/5/2021, 3:03:47 PM] SyntaxError: Unexpected token u in JSON at position 0
    at JSON.parse (<anonymous>)
    at Request._callback (/usr/local/lib/node_modules/homebridge-frigidaire/node_modules/frigidaire/lib/frigidaire.js:236:42)
    at self.callback (/usr/local/lib/node_modules/homebridge-frigidaire/node_modules/request/request.js:185:22)
    at Request.emit (events.js:315:20)
    at Request.onRequestError (/usr/local/lib/node_modules/homebridge-frigidaire/node_modules/request/request.js:877:8)
    at ClientRequest.emit (events.js:315:20)
    at TLSSocket.socketErrorListener (_http_client.js:469:9)
    at TLSSocket.emit (events.js:315:20)
    at emitErrorNT (internal/streams/destroy.js:106:8)
    at emitErrorCloseNT (internal/streams/destroy.js:74:3)
[6/5/2021, 3:03:47 PM] Got SIGTERM, shutting down Homebridge...

Then Homebridge crashes and restarts. This usually happens after I set a temperature (Celsius).

I may have an older model (FGRC0844S1) but while the plugin is fully compatible, the mode names on the plugin do not match up to those on the unit itself. For instance: Auto Mode on the plugin = Eco Mode on my AC unit and Heat Mode on the plugin = Fan mode on my AC unit. Can an option be added to customize these modes for different models?

Hi,

Have a FGAC5044 dehumidifiers, any plans to add support? Would you accept pull request if I updated the code to support this option? Or should I investigate creating a separate plug-in?

I see my HomeKit tiles for my air conditioners now has a "clean air" switch, however my models don't support this. I don't see anything in the documentation for disabling this.

Is there something that needs added to the config to turn it off?

With the updates to this plugin, and supporting library, device discovery is broken.

a lot of work needs to be done to fix this.

Really just a point for documentation. If your app on the phone is using a default name, it's actually a null value. So a user must set their device's name on the frigidaire app (or a change could probably be made to address this programmatically through iteration AC #1, AC #2, etc)

new version released, looking for some folks to test.

Please manually update both this and the lib plugin from GitHub versions.

• fixed auto discvery, no need to define multiple platforms for multiple units
• fixed device ID
• optimizations to reduce callbacks to Electrolux services
• many other small changes

Looks like another upcoming potentially breaking change:

Here’s what to expect:

When it’s time to update, you will receive an app notification and email. You will be asked to download our new Frigidaire 2.0 App. Once downloaded, a password reset will be required in the new Frigidaire 2.0 App. Note: When you reset, you can use an existing or new password. After resetting your password, you will be able to enjoy our new app experience.

I find the temp to be inaccurate on my Frigidaire and use a nest for more accurate info. Since I have both hooked up it reports 2 temps in my home app. Is it possible to remove the temp from HomeKit with a “disable” line in the config?

Using HOOBS.

Not tech savvy at all.

Why is this not connecting?

New Frigidaire App is causing issues. It's preventing your plugin from working.

The fan Speed is not showing. My AC supports HI, Med, Low, Auto. However I only see the Auto option.

need to call updateValue() for each Characteristic each time we get new telemetry.

Hi all,

Thanks for developing this. I'm only running homebridge to control a Frigidaire Air Conditioner.

It discovered the AC, and offers a target temperature and actual temperature, Cool/Heat/Auto/Off in the 'Accessories' user interface.

Is there something I need to do to be able to toggle to FAN ONLY?

Thanks!

@karlg100 Thanks for your work and sharing.
I was happy to have found your plugin by chance.
I recently purchased here in Germany a AEG-PX71-265WT which should be identical to the Frigidaire Gallery

Unfortunately the plugin did not work with the AEG at the moment. But worth a try. ;)
Any chance you could modify the the plugin so that AEG Users also take advantage of your great plugin. As far as it is possible for me, I am of course happy to help.
Very appreciate your time you put in this.
Thanks in advance. 👍

Jun 24 15:07:35 raspberrypi-3BPlus homebridge[26248]: [2019-6-24 15:07:35] TypeError: Cannot read property 'attributes' of undefined
Jun 24 15:07:35 raspberrypi-3BPlus homebridge[26248]:     at /usr/local/lib/node_modules/homebridge-frigidaire/node_modules/frigidaire/lib/frigidaire.js:436:58
Jun 24 15:07:35 raspberrypi-3BPlus homebridge[26248]:     at Request._callback (/usr/local/lib/node_modules/homebridge-frigidaire/node_modules/frigidaire/lib/frigidaire.js:282:14)
Jun 24 15:07:35 raspberrypi-3BPlus homebridge[26248]:     at Request.self.callback (/usr/local/lib/node_modules/homebridge-frigidaire/node_modules/request/request.js:185:22)
Jun 24 15:07:35 raspberrypi-3BPlus homebridge[26248]:     at Request.emit (events.js:193:13)
Jun 24 15:07:35 raspberrypi-3BPlus homebridge[26248]:     at Request.<anonymous> (/usr/local/lib/node_modules/homebridge-frigidaire/node_modules/request/request.js:1161:10)
Jun 24 15:07:35 raspberrypi-3BPlus homebridge[26248]:     at Request.emit (events.js:193:13)
Jun 24 15:07:35 raspberrypi-3BPlus homebridge[26248]:     at IncomingMessage.<anonymous> (/usr/local/lib/node_modules/homebridge-frigidaire/node_modules/request/request.js:1083:12)
Jun 24 15:07:35 raspberrypi-3BPlus homebridge[26248]:     at Object.onceWrapper (events.js:281:20)
Jun 24 15:07:35 raspberrypi-3BPlus homebridge[26248]:     at IncomingMessage.emit (events.js:198:15)
Jun 24 15:07:35 raspberrypi-3BPlus homebridge[26248]:     at endReadableNT (_stream_readable.js:1139:12)
Jun 24 15:07:35 raspberrypi-3BPlus homebridge[26248]:     at processTicksAndRejections (internal/process/task_queues.js:81:17)
Jun 24 15:07:35 raspberrypi-3BPlus homebridge[26248]: [2019-6-24 15:07:35] Got SIGTERM, shutting down Homebridge...
Jun 24 15:07:37 raspberrypi-3BPlus homebridge[26248]: [2019-6-24 15:07:37] [Config] Console v4.5.1 is listening on :: port 8082
Jun 24 15:07:40 raspberrypi-3BPlus systemd[1]: homebridge-2nd-Instance.service: Main process exited, code=exited, status=143/n/a
Jun 24 15:07:40 raspberrypi-3BPlus systemd[1]: homebridge-2nd-Instance.service: Unit entered failed state.
Jun 24 15:07:40 raspberrypi-3BPlus systemd[1]: homebridge-2nd-Instance.service: Failed with result 'exit-code'.

@karlg100 - I believe the HeaterCooler accessory type was not available in homebridge when this was first created.

Do you know if this type was considered?

I believe it allows for custom mode types and a cool only (removing heat references and lower thermostat bound) modes and also more customization (so that Fan and Eco can be used with their real names), was wondering if any downsides were identified otherwise.

Was going to give a stab at this before the 1.0 to 2.0 breaking changes happened. Also, was thinking a switch for clean air and a sensor for filter cleaning needed.

Will this be updated, doesn't seem to be working anymore.

Today I unplugged my Frigidaire AC units which were added to HomeKit via this plugin. When I checked HomeKit all of my HomeBridge accessories showed as non-responsive. The only way I could get everything working again was to use NPM to uninstall homebridge-frigidaire, remove the appropriate lines from config.json, and restart homebridge.

The Problem

Homebridge won't run. Homebridge device shows "no response" in HomeKIt. It was working up until installing the frigidaire package and works with it removed.

Steps taken:

1. Installed homebridge-frigidaire using npm
2. Edited config
3. Restarted homebridge

config.json

            {
            "platform": "Frigidaire",
            "name": "Frigidaire AC Units",
            "username": "[email protected]",
            "password": "myRealPassword"
            }

/var/log/homebridge.err

Tue, 04 Sep 2018 23:17:04 GMT frigidaire getting device list, but getting telem first
Tue, 04 Sep 2018 23:17:04 GMT frigidaire getTelem()
Tue, 04 Sep 2018 23:17:04 GMT frigidaire
Tue, 04 Sep 2018 23:17:04 GMT frigidaire
Tue, 04 Sep 2018 23:17:04 GMT frigidaire get()
Tue, 04 Sep 2018 23:17:04 GMT frigidaire
Tue, 04 Sep 2018 23:17:04 GMT frigidaire no sessionId, starting auth sequence
Tue, 04 Sep 2018 23:17:04 GMT frigidaire authStage1()
Tue, 04 Sep 2018 23:17:04 GMT frigidaire
Tue, 04 Sep 2018 23:17:04 GMT frigidaire
Tue, 04 Sep 2018 23:17:04 GMT frigidaire get()
Tue, 04 Sep 2018 23:17:04 GMT frigidaire
Tue, 04 Sep 2018 23:17:04 GMT frigidaire attempts: 0
Tue, 04 Sep 2018 23:17:04 GMT frigidaire Error 403 : Forbidden
Tue, 04 Sep 2018 23:17:04 GMT frigidaire stage1 error
Tue, 04 Sep 2018 23:17:04 GMT frigidaire resetAll()
Tue, 04 Sep 2018 23:17:04 GMT frigidaire unable to get device list!
Error: 403 Forbidden
at Request._callback (/usr/local/lib/node_modules/homebridge-frigidaire/node_modules/frigidaire/lib/frigidaire.js:267:15)
at Request.self.callback (/usr/local/lib/node_modules/homebridge-frigidaire/node_modules/request/request.js:185:22)
at emitTwo (events.js:126:13)
at Request.emit (events.js:214:7)
at Request. (/usr/local/lib/node_modules/homebridge-frigidaire/node_modules/request/request.js:1161:10)
at emitOne (events.js:116:13)
at Request.emit (events.js:211:7)
at IncomingMessage. (/usr/local/lib/node_modules/homebridge-frigidaire/node_modules/request/request.js:1083:12)
at Object.onceWrapper (events.js:313:30)
at emitNone (events.js:111:20)
at IncomingMessage.emit (events.js:208:7)
at endReadableNT (_stream_readable.js:1064:12)
at _combinedTickCallback (internal/process/next_tick.js:138:11)
at process._tickCallback (internal/process/next_tick.js:180:9)

Other Notes

I have two Frigidaire "Gallery" model window ACs ("Office AC" and "Bedroom AC")
The same credentials do work for the Frigidaire app.
Based on the error message I'd suspect an authentication error, but I've triple checked the credentials, and like I mentioned, they work in the app.

Installation ran smoothly, there were no error codes, all credentials were entered properly into the platform, but unfortunately my Frigidaire AC that uses Cool Connect WI-FI won't appear in Homebridge.

Installed the plugin and entered my config so not sure where I am going wrong. I have the newer frigidare AC and I am using the new app Frigidaire 2.0 version 1.1.3 and have entered my config text below,

"platform": "Frigidaire",
"applianceSerial": "unsure what to enter here so I tried all of these (Serial Number, PNC",
"username": "my [email protected]",
"password": "my password",
"deviceId": "O2-w1yjkjewjQt2J_AjaAaeSZZlmTQ501ahP"

didnt change anything else, did also try changing the device id by a couple of characters, keep getting an error

ERROR: no appliance found! ensure correct serial number entered in config
no appliance found! ensure correct serial number entered in config
[6/7/2021, 11:35:10 AM] Error: This callback function has already been called by someone else; it can only be called one time.
at /usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/util/once.ts:6:13
at /homebridge/node_modules/homebridge-frigidaire/index.js:46:7
at /homebridge/node_modules/homebridge-frigidaire/node_modules/frigidaire/lib/frigidaire.js:692:21
at authStg1GetCallback (/homebridge/node_modules/homebridge-frigidaire/node_modules/frigidaire/lib/frigidaire.js:183:25)
at getInfoCallback (/homebridge/node_modules/homebridge-frigidaire/node_modules/frigidaire/lib/frigidaire.js:629:22)
at /homebridge/node_modules/homebridge-frigidaire/node_modules/frigidaire/lib/frigidaire.js:672:14
at Request._callback (/homebridge/node_modules/homebridge-frigidaire/node_modules/frigidaire/lib/frigidaire.js:278:25)
at Request.self.callback (/homebridge/node_modules/homebridge-frigidaire/node_modules/request/request.js:185:22)
at Request.emit (events.js:376:20)
at Request. (/homebridge/node_modules/homebridge-frigidaire/node_modules/request/request.js:1154:10)

Adding config file, and I get this error when starting up homebridge:

[7/7/2023, 10:23:23 PM] [@samthegeek/homebridge-frigidaire] This plugin is taking long time to load and preventing Homebridge from starting. See https://homebridge.io/w/JtMGR for more info.

I have triple checked the plugin config, I have reset my Frigidaire password, deleted and re added both the app, and the AC unit from my account, etc. Homebridge and all other plugins are up to date and working. Thoughts?

set max temp range of 90 and min of 60

Hi hope you can help I have the Electrolux well p7with is the same as the Frigidaire Gallery series and I was hoping the this plugin will work with Electrolux even if it was made for Frigidaire which is a brand under Electrolux. But I could not use the account created for Electrolux in Frigidaire app and can’t add the Electrolux to the Frigidaire app after i created an account for the Frigidaire, so is there anything that can be done so this plugin support Electrolux AC as well.

The Electrolux app is called Home Comfort.

Tried the fix in the prior issue, didn't work...

removed and reinstalled the plugin/libs, nope

Error: 403 Forbidden
at Request._callback (/usr/local/lib/node_modules/homebridge-frigidaire/node_modules/frigidaire/lib/frigidaire.js:267:15)
at Request.self.callback (/usr/local/lib/node_modules/homebridge-frigidaire/node_modules/request/request.js:185:22)
at Request.emit (events.js:182:13)
at Request. (/usr/local/lib/node_modules/homebridge-frigidaire/node_modules/request/request.js:1161:10)
at Request.emit (events.js:182:13)
at IncomingMessage. (/usr/local/lib/node_modules/homebridge-frigidaire/node_modules/request/request.js:1083:12)
at Object.onceWrapper (events.js:273:13)
at IncomingMessage.emit (events.js:187:15)
at endReadableNT (_stream_readable.js:1094:12)
at process._tickCallback (internal/process/next_tick.js:63:19)

Hi - this was working, but now not so much...

I'm not very familiar with home bridge or docker so I'll go try to see if I can figure out how to enable logging.

Starting to advertise 'Homebridge 951A 3B56' using bonjour-hap backend!
[6/28/2021, 9:18:46 AM] Homebridge v1.3.4 (Homebridge 951A) is running on port 53611.
getCoolingState() - no telementry, exiting
getMode() - no telementry, exiting
getRoomTemp() - no telementry, exiting
getTemp() - no telementry, exiting
getUnit() - no telementry, exiting
getFanMode() - no telementry, exiting
getCleanAir() - no telementry, exiting
getCleanAir() - no telementry, exiting
[6/28/2021, 9:18:50 AM] [homebridge-frigidaire] This plugin slows down Homebridge. The read handler for the characteristic 'Current Heating Cooling State' was slow to respond! See https://git.io/JtMGR for more info.
[6/28/2021, 9:18:50 AM] [homebridge-frigidaire] This plugin slows down Homebridge. The read handler for the characteristic 'Target Heating Cooling State' was slow to respond! See https://git.io/JtMGR for more info.
[6/28/2021, 9:18:50 AM] [homebridge-frigidaire] This plugin slows down Homebridge. The read handler for the characteristic 'Current Temperature' was slow to respond! See https://git.io/JtMGR for more info.
[6/28/2021, 9:18:50 AM] [homebridge-frigidaire] This plugin slows down Homebridge. The read handler for the characteristic 'Target Temperature' was slow to respond! See https://git.io/JtMGR for more info.
[6/28/2021, 9:18:50 AM] [homebridge-frigidaire] This plugin slows down Homebridge. The read handler for the characteristic 'Temperature Display Units' was slow to respond! See https://git.io/JtMGR for more info.
[6/28/2021, 9:18:50 AM] [homebridge-frigidaire] This plugin slows down Homebridge. The read handler for the characteristic 'Rotation Speed' was slow to respond! See https://git.io/JtMGR for more info.
[6/28/2021, 9:18:50 AM] [homebridge-frigidaire] This plugin slows down Homebridge. The read handler for the characteristic 'On' was slow to respond! See https://git.io/JtMGR for more info.
[6/28/2021, 9:18:50 AM] [homebridge-frigidaire] This plugin slows down Homebridge. The read handler for the characteristic 'Filter Change Indication' was slow to respond! See https://git.io/JtMGR for more info.
[6/28/2021, 9:18:56 AM] [homebridge-frigidaire] This plugin slows down Homebridge. The read handler for the characteristic 'Current Heating Cooling State' didn't respond at all!. Please check that you properly call the callback! See https://git.io/JtMGR for more info.
[6/28/2021, 9:18:56 AM] [homebridge-frigidaire] This plugin slows down Homebridge. The read handler for the characteristic 'Target Heating Cooling State' didn't respond at all!. Please check that you properly call the callback! See https://git.io/JtMGR for more info.
[6/28/2021, 9:18:56 AM] [homebridge-frigidaire] This plugin slows down Homebridge. The read handler for the characteristic 'Current Temperature' didn't respond at all!. Please check that you properly call the callback! See https://git.io/JtMGR for more info.
[6/28/2021, 9:18:56 AM] [homebridge-frigidaire] This plugin slows down Homebridge. The read handler for the characteristic 'Target Temperature' didn't respond at all!. Please check that you properly call the callback! See https://git.io/JtMGR for more info.
[6/28/2021, 9:18:56 AM] [homebridge-frigidaire] This plugin slows down Homebridge. The read handler for the characteristic 'Temperature Display Units' didn't respond at all!. Please check that you properly call the callback! See https://git.io/JtMGR for more info.
[6/28/2021, 9:18:56 AM] [homebridge-frigidaire] This plugin slows down Homebridge. The read handler for the characteristic 'Rotation Speed' didn't respond at all!. Please check that you properly call the callback! See https://git.io/JtMGR for more info.
[6/28/2021, 9:18:56 AM] [homebridge-frigidaire] This plugin slows down Homebridge. The read handler for the characteristic 'On' didn't respond at all!. Please check that you properly call the callback! See https://git.io/JtMGR for more info.
[6/28/2021, 9:18:56 AM] [homebridge-frigidaire] This plugin slows down Homebridge. The read handler for the characteristic 'Filter Change Indication' didn't respond at all!. Please check that you properly call the callback! See https://git.io/JtMGR for more info.

Would it be possible to expose the Fan Speed controls as a separate Fan device? I see there is some code already handling fan speed, but it doesn't appear user-controllable for the AC settings. A separate fan device may be one remedy for that, unless HomeKit has a way to control it from the Thermostat service too?

I suspect it’s this module causing that in my setup. My suspicion is the timer that polls for updates. There should be a lock to prevent multiple updates from piling up, and also set the timeout lower to get the one that stalled to clear out.