HTTP client not connecting

[shermanjoshua]

After attempting a restart to scan for a new device, I noticed that it wasn't connecting. The new device would use the AWS client, but as you can see from the logs, that isn't starting because the HTTP client can't start. It's obviously failing somewhere in the login() function in http.js. I have not yet had a chance to look at the response from the api, but I did notice the message about needing to wait for the reset on the attempt timer, so I suspected either the PW was incorrect or something. After waiting for the timer and re-attempting (restarting everything in Homebridge), the message just came back, but the timer was reset to 5 minutes. So my suspicions were:

• PW is wrong - Nope. Confirmed multiple times by copy/pasting from the config and PW works to log in to Govee site. Also confirmed that it matches PW exactly for other plugins (for other controllers I use). No extra whitespace or anything. Looked for hidden CR/LF chars as well.
• Plugin version, node version etc... - Don't think so. Tried as many different configurations as I could think of
• String manip happening in http.js line 51-54 - Nope, see comment from me below
• Govee gonna Govee - Need to debug, but would love to play with creds to see if maybe Govee is just messing w/ stuff on their end and making this a moving target

Details of your setup.

• Do you use (1) Homebridge UI-X (2) Homebridge CLI or (3) HOOBS?

  • Homebridge UI-X

• Which version of Homebridge/HOOBS do you have?

  • 1.7.0

• Which platform do you run Homebridge/HOOBS on (e.g. Raspberry Pi/Windows/HOOBS Box)? Please also mention your version of Node.js/NPM if known.

  • Mac OS Sonoma
  • node 20.10.0 (I use n to manage node versions, so I can try others if you like. I've tried 18.x already)

• Which version of this plugin (homebridge-govee) do you have? Has the issue started since upgrading from a previous version?

  • 10.5.0 (I've already tried the 10.4 beta as well)
  • I don't know if the issue was happening before. I just got a new humidifier device, so that was what caused me to start digging in. My other device still works fine)

• Which Govee devices do you have that are causing issues? Please include product models if applicable.

  • H7142 is the device I was trying to get connected

Please paste any relevant logs below.

[3/30/2024, 10:27:02 AM] [Govee] Initializing Govee platform...
[3/30/2024, 10:27:02 AM] [Govee] Initialising plugin v10.5.0 | System darwin | Node v20.10.0 | HB v1.7.0 | HAPNodeJS v0.11.1...
[3/30/2024, 10:27:02 AM] [Govee] Plugin initialised. Setting up accessories...
[3/30/2024, 10:27:04 AM] [Govee] [LAN] client enabled and found 1 device(s).
[3/30/2024, 10:27:04 AM] [Govee] [HTTP] could not use existing access token as does not exist, this is normally not an issue.
[3/30/2024, 10:27:05 AM] [Govee] [HTTP] disabling client as The number of consecutive failed logins for this account has reached the maximum. Please try again in 3 minutes. at default.login (file:///usr/local/lib/node_modules/homebridge-govee/lib/connection/http.js:58:15).
[3/30/2024, 10:27:05 AM] [Govee] [AWS] disabling client as requires HTTP client.
[3/30/2024, 10:27:05 AM] [Govee] [BLE] disabling client as not supported on mac devices.
[3/30/2024, 10:27:05 AM] [Govee] [4C:25:CD:33:33:35:12:65] initialising with options {"adaptiveLightingShift":0,"aws":"unsupported","ble":"unsupported","brightnessStep":1,"colourSafeMode":false,"lan":"enabled"}.
[3/30/2024, 10:27:05 AM] [Govee] [4C:25:CD:33:33:35:12:65] initialised with id [4C:25:CD:33:33:35:12:65] [H6066].
[3/30/2024, 10:27:05 AM] [Govee] ✓ Setup complete. This plugin has been made with ♥ by bwp91, please consider a ☆ on GitHub if you are finding it useful!
[3/30/2024, 10:27:35 AM] [Govee] [4C:25:CD:33:33:35:12:65] current colour [4590K / 218M].

User Note:

I did go ahead and grab the code to peek at what was failing. I also looked through docs and issues and have a thread to pull -

I am 90% sure this is some weird issue with login like you have noted in the docs somewhere (I'll find the link). I can log in to my account on the Govee site using the name/password from the config just fine. Rather than just default to the solution there, I figured I'd log this to give a chance to look for a solve. Also, I don't want to change my PW very much just because I have a bunch of other controls around that I'd have to update after realizing they are no longer working 😂

If I have the time in the next few days, I'll also plug away at this. Just need to read up on how to debug these plugins...

[shermanjoshua]

Got the console debugger going at least. Govee IS indeed returning {status: 400, message: 'Incorrect password'} in the response (this is on the initial run). I confirmed again that the PW does work to log me into Govee manually. I also tried this with the string manipulation of the password removed (commented out the lines, ran the rebuild script, waited the requisite 5 minutes, and hit debug - if these are not the right steps please let me know. I'm just assuming this is correct based on what the project looks like) and still got the same PW error.

I also see another message in the response about having too many requests altogether (the message says that the max attempts is 30 in 24 hours). That definitely is NOT enough attempts for someone trying to debug the authentication. Thanks Govee 🙄

It certainly does seem like this is something weird on Govee's side. Maybe they lose info on PWs between the site/app and this service for some reason? I haven't changed PWs recently or anything, so I'm definitely confused without knowing more about their internal workings.

I think my ideas around a PR (or a few) I could work on for this are:

• First, remove whatever login retry logic we have. Or cut back on when it gets hit/make it configurable/something else... (separate PR)
• If this api doesn't always work, maybe it makes sense to have a secondary path that users can attempt if they are comfortable that uses the API key? Offhand, I think we'd have to update the auth flow to handle for a new config option that accepts the API key for a user (if present, take new path etc), and also update docs of course - to tell users how to get a key, input it in the new configs, and what new logging/messaging to expect
• Maybe add EPIPE to the error code enum so that we can route that like we do with some of the others

I may take a pass at that if I have some more time, but would love to hear thoughts from anyone interested 😃

[bwp91]

Try changing your password in the govee app.

i believe the accounts on their website are separate to govee app accounts.

The plugin needs credentials that are used for the app, not their website