-
-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Login Restriction #57
Comments
This is interesting, thanks for writing this up and including their response. Levoit has consistently worked hard to prevent this plugin and its use in HomeBridge, and I wonder if this is a new attempt to do that. I'll try to investigate what triggers the logout and see if I can mitigate it later today. |
@atwoodjw Does this happen consistently for you? I don't see this on my setup. Do you have any steps to trigger it? |
@atwoodjw I'm having a hard time understanding how VeSync determined the requests were coming specifically from HomeKit. We use the Android app's user agent for all requests, so if they knew we were spoofing the agent, they couldn't possibly know the requests were coming from HomeKit / this plugin and not some other homebrew home ecosystem. Can you give me some more details when you have a chance? |
Sorry for the radio silence. I have 3x LV600S. Yes, this happens consistently. If the Homebridge plugin is enabled, I can't sign into the VeSync iOS app when on my home WiFi (same external IP address). If I toggle WiFi off and use cellular data, I can sign into the iOS app. If I disable the Homebridge plugin and wait a day, I can sign into the iOS app on my home WiFi again. Very strange. If Levoit is able to determine that logins are coming from HomeKit, I would expect them to block them, yet the plugin seems to be working flawlessly; it's their first-party app that breaks as a result of the login restriction. 🤷♂️ Ultimately, this isn't that big a deal. I rarely use the iOS app now, in favor of the Home app. Just a minor annoyance. Feel free to close. |
Thanks for the info! Would you mind removing showOffWhenDisconnected from your config and seeing if the issue persists? I'm intrigued by this issue tbh. |
Issue persists, even with showOffWhenDisconnected set to false. |
Experiencing identical behavior as @atwoodjw. Was constantly getting logged out of the Vesync app on iOS after setting up the Homebridge plugin. Here's my config:
However, I did find a workaround to continue to use both Homebridge and the Vesync iOS app (which I've done for other plugins). I created a new Levoit account using a gmail alias ( This of course doesn't help solve the auth issue. No clue what kind of auth they are doing for their APIs, but it seems like access/id tokens are being revoked for that user due to the login behavior/attempts from the Homebridge plugin. |
Thanks for the info and workaround. I'm wondering if they're only allowing a single token for some users (slow rollout). I can't repro with my setup. More questions: |
@pschroeder89 - Sorry for the delayed response:
|
Thanks for the info, unfortunately there's nothing glaring that I can see that would cause this for some users. Whatever it is seems to be on VeSync's end. I'll pass around your workaround to other users as needed, and will close this issue. |
Describe The Bug:
Vesync iOS app is constantly getting logged out. When logged out, I must turn off WiFi to log back in successfully. I reached out to support and they wrote the following.
So it appears that the plugin is frequently logging in and causing a restriction to be place on some combination of account + IP address. (If I toggle WiFi off, I'm able to sign in.)
To Reproduce:
Connect iOS device to WiFi. Log in to Vesync iOS app. Configure plugin. Wait a few hours, then try to open Vesync iOS app. Notice you've been signed out and can't sign back in. Disable WiFi, then sign in successfully.
Expected behavior:
Vesync iOS app not constantly logged out.
Logs:
No relevant plugin logs. Issue manifests in first-party app.
Plugin Config:
Screenshots:
![IMG_0518](https://private-user-images.githubusercontent.com/362805/291328507-b4cba7aa-49ac-43d5-819c-2f168880a86e.jpg?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MTk0MzQyNzksIm5iZiI6MTcxOTQzMzk3OSwicGF0aCI6Ii8zNjI4MDUvMjkxMzI4NTA3LWI0Y2JhN2FhLTQ5YWMtNDNkNS04MTljLTJmMTY4ODgwYTg2ZS5qcGc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjQwNjI2JTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI0MDYyNlQyMDMyNTlaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT1kYTcwZTE5ZmQ1YWQ4NTgyZGFlODNkZWU4MDI5YmIwOWUyYjVkZGZhZDM0NzEzMGVhZmUyYmUxZDNlYzMyZWE4JlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCZhY3Rvcl9pZD0wJmtleV9pZD0wJnJlcG9faWQ9MCJ9.DRYcaVNg3Tna2pgLrw-1gOmfxs3uSEhgK5UPeFDu_FQ)
Environment:
The text was updated successfully, but these errors were encountered: