search

palazzem / ha-econnect-alarm

Home Assistant integration that provides a full-fledged Alarm Panel to control your Elmo/IESS alarm systems.
BSD 3-Clause "New" or "Revised" License
10 stars 5 forks source link

Invalid authentication #119

Closed parabag closed 7 months ago

parabag commented 9 months ago

Describe the bug During the set up of the integration with IESS/Metronet credentials I am unable to authenticate, while I am sure that user and password are correct. Thanks for your help.

Error message "invalid authentication"

Expected behavior proceed with the installation of the integration

Environment

parabag commented 9 months ago

I close this issue immediately. For anyone that encounter the same issue i had tu "default" in the domain name.

palazzem commented 9 months ago

Hello @parabag and thanks for reaching out! I'm happy to hear that you found the way to make it work, but feel free to provide any feedback you have (here or in Discord)! About your specific issue, we added this statement in the login form:

In case you don't have a vendor defined, set it to default.

As it may not be visible enough, we would like to hear your thoughts in case you have more ideas to improve the onboarding process! One thing I may investigate is to verify if using default as default (meaning you don't write anything) is a good option or not.

Anyway, feel free to give us more suggestions! We're happy to hear your thoughts to make this integration better and better over time! Thanks again!

parabag commented 9 months ago

Grazie Emanuele,The integration is simply fantastic, so first of all thank you.The only thing I would do is to set the domain as mandatory and not optionalCiaoLucaSent from my iPadOn 28 Dec 2023, at 20:05, Emanuele Palazzetti @.***> wrote: Hello @parabag and thanks for reaching out! I'm happy to hear that you found the way to make it work, but feel free to provide any feedback you have (here or in Discord)! About your specific issue, we added this statement in the login form:

In case you don't have a vendor defined, set it to default.

As it may not be visible enough, we would like to hear your thoughts in case you have more ideas to improve the onboarding process! One thing I may investigate is to verify if using default as default (meaning you don't write anything) is a good option or not. Anyway, feel free to give us more suggestions! We're happy to hear your thoughts to make this integration better and better over time! Thanks again!

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>

palazzem commented 9 months ago

Thanks for the suggestion @parabag ! I'm opening again this issue as I want to get to the bottom of it. I think what you experienced must not happen. Very likely we can find an elegant solution that doesn't require new users to read the documentation or block of texts.

I'll keep you posted on what the solution would be!

parabag commented 9 months ago

Grazie!Sent from my iPhoneOn 30 Dec 2023, at 14:47, Emanuele Palazzetti @.***> wrote: Thanks for the suggestion @parabag ! I'm opening again this issue as I want to get to the bottom of it. I think what you experienced must not happen. Very likely we can find an elegant solution that doesn't require new users to read the documentation or block of texts. I'll keep you posted on what the solution would be!

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>

palazzem commented 7 months ago

As described in #129 , now domain is required and pre-filled with default. If you don't have a vendor, just leave the pre-filled valued, otherwise replace it with your vendor. Closing!