-
Notifications
You must be signed in to change notification settings - Fork 17
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
New Verisure application version leads to error #30
Comments
Same boat... What do you mean by |
Same error for FR |
Same here, PT user. |
Same here (SP) Ahora mismo solo tienes acceso a la nueva versión de My Verisure, haz clic en aceptar para acceder a la nueva versión. |
Same here (FR) |
It looks like the time has come and the old API has arrived to end of life. This is the message I get in Spain telling that the app is no longer available: Gracias por acceder a My Verisure. Esta aplicación ya no está disponible y te recomendamos desinstalarla. Pulsa aceptar para poder acceder a la nueva aplicación. |
I'm getting the same error |
Same error |
same error, country="IT" |
Hi, Same error for me, I tried Python script directly and it's working perfectly (https://github.com/Cebeerre/pysecuritas). I suppose Installation ID parameter is missing in segalion script to execute API Call. @segalion I'm not developer but you may confirm this ? |
I have found this on another thread and it's working, you have to add "installation: your_installation_id" in configuration.yaml Example:
|
Thanks for the solution @siom7!!! |
Checkout this last issue #37 |
Verisure is requesting customers in France to move to the new application with a strong deadline.
Following this "forced" migration the integration fails to work with message
L'application MyVerisure a été remplacée par My New Verisure. Veuillez télécharger la nouvelle application
16:04:31 – securitas_direct (ERROR)
-> The application MyVerisure has been replaced by "My new Verisure". Please download the new application.
When using the securitas.py program locally it is still possible to connect to the ~"API".
The text was updated successfully, but these errors were encountered: