Installed Plugin with Valid Credentials But No Devices Show Up Even After Installing A Child Bridge

[charlestephen]

Describe The Bug: After installing and configuring the plugin with a valid credential set, no devices show up in Homebridge either in regular or child bridge mode.

To Reproduce:

1. Install Plugin
2. Configure Plugin
3. Restart Homebridge
4. Scan child bridge code into HomeKit app. No devices show up and no logs appear in Homebridge. Furthermore, no DNS queries are made from Homebridge to the normal endpoint, api.ocp.electrolux.one, but instead only to accounts.us1.gigya.com.

Expected behavior: In regular mode, I expected the plugin to at least make a call to Frigidaire’s servers to get devices, but it does not. Consequently, no devices show up in HomeKit.

Logs:

[19/06/2024, 12:24:17] [@reedptaylor/homebridge-frigidaire-ac-plugin] Process Ended. Code: 143, Signal: null
[19/06/2024, 12:24:24] [@reedptaylor/homebridge-frigidaire-ac-plugin] Restarting Process...
[19/06/2024, 12:24:25] [@reedptaylor/homebridge-frigidaire-ac-plugin] Launched child bridge with PID 6463
[19/06/2024, 12:24:25] Registering platform '@reedptaylor/homebridge-frigidaire-ac-plugin.FrigidaireACHomebridgePlugin'
[19/06/2024, 12:24:25] [@reedptaylor/homebridge-frigidaire-ac-plugin] Loaded @reedptaylor/homebridge-frigidaire-ac-plugin v1.0.3 child bridge successfully
[19/06/2024, 12:24:25] Loaded 0 cached accessories from cachedAccessories.0E3A86D32A97.
[19/06/2024, 12:24:25] [@reedptaylor/homebridge-frigidaire-ac-plugin] Starting to initializing FrigidaireHomebridgePlatform
[19/06/2024, 12:24:25] [@reedptaylor/homebridge-frigidaire-ac-plugin] Will cache auth token in: /var/lib/homebridge
[19/06/2024, 12:24:25] Publishing bridge accessory (name: @reedptaylor/homebridge-frigidaire-ac-plugin, publishInfo: {
  username: '0E:3A:86:D3:2A:97',
  port: 44191,
  pincode: '***-**-***',
  category: 2,
  bind: [ 'eth0', 'wlan0', [length]: 2 ],
  mdns: undefined,
  addIdentifyingMaterial: true,
  advertiser: 'avahi'
}).
[19/06/2024, 12:24:25] [@reedptaylor/homebridge-frigidaire-ac-plugin] Executed didFinishLaunching callback
[19/06/2024, 12:24:25] [@reedptaylor/homebridge-frigidaire-ac-plugin] Searching for devices...
[19/06/2024, 12:24:25] Homebridge v1.8.2 (HAP v0.12.1) (@reedptaylor/homebridge-frigidaire-ac-plugin) is running on port 44191.

Plugin Config:

{
            "username": “validuser@valid.domain",
            "password": “PASSWORD",
            "deviceId": "0d27018a-6901-4751-86a8-47815ef4a631",
            "pollingInterval": 10000,
            "cacheRefreshToken": true,
            "platform": "FrigidaireACHomebridgePlugin",
            "_bridge": {
                "username": "0E:3A:86:D3:2A:97",
                "port": 44191
            }
        }

Environment:

• Plugin Version: v1.0.3
• Homebridge Version: 1.8.2
• Node.js Version: v20.14.0
• NPM Version: 10.7.0
• Operating System: Raspbian with hb-service

[reedptaylor]

@charlestephen Can you reply with the model of AC attached to your Frigidaire account?

[charlestephen]

I have two in room air conditioners model number FGPC1244T1E00 and one window unit model number FGRC1044T100. All used to work with the older versions of the plugin until those plugins recently stopped working.

[Zackery]

Unfortunately, I am experiencing the same issue. My model A/C is FHWW082WCE.

[charlestephen]

I figured out what it was. I had stale DNS records for the Frigidaire API endpoint which resulted in the plugin not reaching the proper servers (and the Frigidaire app consistently saying I was offline when I was on my home network). Thanks for the plugin! It works great.

[Zackery]

I was also able to resolve my issue, turns out the plugin wasn't a fan of the password I had set (I'm thinking this is because my password had special characters, but I'm not sure.) Changing my password allowed the plugin to successfully connect to Frigidaire's API.

Thanks!

[reedptaylor]

Glad you found a solution for this one and apologies I was not receiving notifications from this thread for some reason.