-
Notifications
You must be signed in to change notification settings - Fork 8
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 is not working "Invalid email address" #19
Comments
Hey there, I'm getting an identical error message as well. Happy to dig into the code a bit if y'all can point me in the right direction! |
Same issue, does anyone know if this addon is still working if you do the old manual configuration that's explained in the forum for the feeder? (Looking for a Litterbox addon but maybe it would connect to that as well), |
@dcmeglio, just this evening my feeder integration is failing. All attributes show as unavailable. Re-adding the integration from scratch yields “invalid email address”. Are others experiencing same? EDIT: After 2-3 hours, service restored, making me suspect vendor outage. |
I am not having these issues. I'll try to see if I can find something but it's working fine for me. |
@dcmeglio, just want to make sure you saw the last comment in my message above — service was restored after a couple hours. I suspect a vendor outage. My environment works now too since that outage. |
Hmm, i'm still having issues with the integration, do you know if i can check somehting else then just trying to login or would you be able to help me out? :-) |
Same as above, just invalid e-mail during config flow, but if I request tokens via API I can get them.. Is the config flow supposed to work? |
Hi there!
I recently bought a "PetSafe ScoopFree Litter Box" and I came across that this integration had been made for Home Assistant, but when I install the latest version (V.1.3.5) and log in, it keeps writing "Invalid email address"
Has anyone here experienced this before?
I have attached the log from my ha
petsafe-HA_log.txt
The text was updated successfully, but these errors were encountered: