Skip to content
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

Can't log into settings #111

Open
gdtms247 opened this issue Jul 24, 2020 · 5 comments
Open

Can't log into settings #111

gdtms247 opened this issue Jul 24, 2020 · 5 comments
Labels
question Further information is requested

Comments

@gdtms247
Copy link

The component:

  • Home Assistant: 0.112.4
  • BWAlarm (ak74 edition): v1.12.6
  • Hassio VM

Setup is only a few days old, on initial setup I logged into the alarm, updated password and choose the devices to trigger alarm etc. Now that I have it working I want to remove the test device and noticed my password no longer works. Tried the default and it doesn't work either. I've reinstalled, manually deleted and re-added the entire custom components folder for bwalarm and no change. I can see the following in my alarm_control_panel.py:

#---------------------------PANEL RELATED---------------------------
vol.Optional(CONF_ADMIN_PASSWORD, default='HG28!!&dn'):       cv.string,     # Admin panel password

However on the login page this password doesn't bring up the settings menu. Anything else to try?

@akasma74
Copy link
Owner

Sounds like you used HACS..
Anyway, do you know where your bwalarm.yaml resides?
It should be in <HA config folder>/resources/bwalarm and if you open it, the password is there as admin_password.
If it's there and yet you cannot get into Settings, please update the issue posting your bwalarm.yaml here.

@gdtms247
Copy link
Author

Yep that was it, I don't know how that got changed but it was set to my alarm panel arm/disarm code. Thanks!!

@akasma74
Copy link
Owner

Cool.
Could you change it as you did it before and keep an eye on it for a while?
If it doesn't get changed and everythig works as expected, then there's nothing to fix and you can close the issue.
Just take your time ;)

@gdtms247
Copy link
Author

Will do! I'll admit I probably did it to myself :) but i'll keep my eye on it next week. thanks!

@akasma74 akasma74 added the question Further information is requested label Jul 26, 2020
@akasma74
Copy link
Owner

Is the issue resolved or you still experience it?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants