search

guerrerotook / securitas-direct-new-api

This repository contains the new securitas direct API that can be integrated in Home Assistant
Apache License 2.0
80 stars 30 forks source link

PIN request to SECURITAS at each HA restart? #119

Open JaVier-Lloret opened 1 year ago

JaVier-Lloret commented 1 year ago

Until last week I used segalion's securitas direct integration, now I have updated to guerrerotook's and I have verified that every time I restart HA it indicates that a new "Securitas Direct" integration has been detected and when configuring it requests the PIN again to SECURITAS. Is this correct and do I have to perform the operation every time?

EddieKnight1 commented 1 year ago

Same for me. In fact every time I restart, a notification for a new integration appears and it's Securitas (when I already have it running).

What I've found as well is, if I omit the PIN request, the integration is not able to gather the panel status, which is important in my case because we use both HA and Securitas panel to disable the alarm.

I can provide logs if this helps out.

guerrerotook commented 1 year ago

Did you go through the process of doing the 2FA for Securitas? This bug was fixed, but you need to login with your phone.

JaVier-Lloret commented 1 year ago

Every time I restart HA and it tells me that SECURITAS has been discovered, I perform the 2FA check with the phone and the next time it asks me again. Today I have seen that you have put a new update I will tell you something when I install it. Thanks for your time

JaVier-Lloret commented 1 year ago

I am now using the latest version of "securitas-direct-new-api" and I keep getting the HA prompt that a new device has been discovered. I set it up and everything seems fine until the next HA reboot, when it tells me new device discovered again. When I am verifying or updating a component that involves performing several reboots, it is tedious to have to perform the operation each time. Is this correct operation? Is it a Securitas requirement and is the connection token lost on reboots? What happens if we don't verify 2FA this time?

chabou-san commented 1 year ago

I also have this behaviour on my installation, and I can tell you that not performing the 2FA prompt at every reboot doesn't prevent this integration from working. As long as you do it one time properly, the integration will keep on working, while showing this notification at every reboot, which you can skip. So I'm currently ignoring it for months, even though it bothers me to see the notification at every reboot. 😉

miquellaboria commented 1 year ago

I have the same issue. @guerrerotook you say we have to login with our phone, whit the Securitas App or using the SMS?

guerrerotook commented 1 year ago

Every time I restart HA and it tells me that SECURITAS has been discovered, I perform the 2FA check with the phone and the next time it asks me again. Today I have seen that you have put a new update I will tell you something when I install it. Thanks for your time

Maybe you can ignore, because sometimes it happens to me and still works.

guerrerotook commented 1 year ago

I have the same issue. @guerrerotook Luis Guerrero Guirado FTE you say we have to login with our phone, whit the Securitas App or using the SMS?

You need to follow the steps in the Home Assistant integration wizard.

jmservera commented 1 year ago

As this integration has a user config flow now, it can be configured directly from the UI. To avoid having a new discovery each restart you can just remove the securitas entry in the configuration.yaml file. This will prevent to "discover" it again. As a mid/long term solution for this integration: