I want to share a Custom Component for Securitas Direct Alarm systems (AKA Verisure for EU and LATAM, not USA)
It is based on API mobile so is fast and reliable enough.
https://github.com/segalion/securitasdirect
Instructions in post #25
Please, report working countrys @ issue 8
Great Job, I will definitly try it for france, changing the host name.
Thanks
I have updated all the code to v.2.
Now, I am working in configure an alarm_manual component that “sync” with real “Securitas” alarm: If you change in HA, change the Securitas alarm, and if you change the Securitas" alarm (with real panel, keys, remotes…), change the state of the HA alarm.
I have created a command line sensor that every minute get the state of the Securitas Alarm, and a shell_command for arm/disarm (call to “securitas armed_away”). But my problem now is that incredibly, HA lacks to get the output of the shell_command, so you cannot known if secuence was really completed.
I have been browsing about other websites around Europe, and seems that there are similar sites that could work. At least I found:
France: https://customers.securitasdirect.fr/
Italy: https://customers.verisure.it/
UK: https://customers.verisure.co.uk/
Portugal: https://customers.securitasdirect.pt/
Brasil: https://customers.verisure.com.br/
Netherland:
Chile
PerĂş
Please could report here or in github if it works as expected
Obviously need to be change the country and surely traslations…
Hi !
It’s a great job, but I’ve several doubts of how can I integrate it with Home assistant, any help?
Dani
Sorry about no answer.
I will try to upload my yalm config and update github next week.
I have python skills but not about HA modules and time
Thank you for your answer … I’m expecting it … 
Regards !
Any suggestion on how to use it in hassio? Thanks
Any updates?
I’m not using hassio, but I ended in this post time ago looking for a python script or something to integrate Verisure, IFTTT and Alexa everything together.
At the end I wrote the script myself:
https://github.com/Cebeerre/VerisureAPIClient
This uses the Mobile App API, so it’s quite fast (it actually has a limit rate of 1 second between calls, as the API complains if you throw too much requests).
It might be pretty simple to adapt to hassio:
https://www.home-assistant.io/components/python_script/
Hope that helps !
Xavi
Uaaauuuuh Xavi, best new about this… now it’s too late. Tomorrow I write ideas about. The mobile api is faster and probably better than my reverse engeniereD Web script .
I think we could build an alarm custom component around this.
Have you tried get the log from mobile api? As securitas hasn’t websoctets services, polling needs to be implemented to sync HA alarm and securitas alarm… so probably log access is faster than ask for state (I.e. every minute ).
Hi @segalion, I’ve added a new function called log() and modified all the outputs so it actually dumps a full json of the API response instead of just the status codes.
@segalion Well, the ID is tagged as “iPhone” as it seems Securitas is doing some kind of “check” on the beginning of the string, as I’m just adding at the end the date and time whilst the App does some kind of hash. I guess you can just swap iPhone for Android in the ID string it will work anyway.
I got the API reverse engineering the Mobile App, just proxying the requests and doing a man in the middle SSL attack. In this way, I’ve been able to just press buttons in the App and see what the App was doing. All the rest has been trial and error, as the App sends other stuff (I guess for logging and debugging) like the App version, iPhone Version … but that it doesn’t seem “mandatory” to make the API answer the requests.
I guess Securitas will keep this working with maybe minor changes, as the mobile apps need the API anyway, and doing major changes would require refactoring both the mobile apps and the API itself. I would expect less changes than in the webpage, so seems easier to maintain compared with your screen scrapping script (I tried at first your approach as well, but using Selenium, and it was ridiculously slow).
A completely different story is that maybe they detect that we’re using the API directly, making them harden the log-in process with two factor authentications and the likes. This would obviously kill any integration option.
Just for reference, I got as well the list of available API methods decompiling the Android APK. Unfortunately I just managed to get the strings, as the code is obfuscated and therefore quite tricky to figure out the actual code for the API interaction.
I haven’t debugged all of them to see the required parameters and expected outputs, but you can get an idea of the potential.
LOGIN
CLS
INS
SRV
ARM
ARMDAY
ARMNIGHT
ARMANNEX
DARMANNEX
PERI
DARM
IMG
EST
CAMLOG
CAMS
VIDS
VID
UPDCAM
CAMPSRS
INSTWORDS
INSTWORDSUPD
INSTWORDSUPD2
BILLS
IDENT
SECONDUSERS
PLAN
CONTACT
PLANUPD
CONTACTUPD
CONTACTADD
CONTACTDEL
SCHCDDEL
KEY
KEYUPD
ACT_V2
PANELCONF
PANELCONFUPD
MYINSTALLATION
DEVUPD
ATC
SECRETWORD
SRVDOMO
DOMO
DOOR
INF
CALLRING
SCHCDLIST
SCHCDADD
SCHCDUPD
SCHCDDISABLE
REMEMBERUSER
MYSD
MYSDCREATE
ALLINONE
SRVCOMMDATA
SRVCOMMDATAUPD
SRVCOMMDATAUPD2
SECONDUSERADD
SECONDUSERADD2
SECONDUSERDEL
SCHCDPROTECT
CONFIG
SOMFYSTATUS
CAMPAING
CRIALUPD
UPDPUSHSTATUS
SECONDINSTALLADD
SECONDINSTALLADD2
THUMBNAIL
UPDPROMPT
DIYRECEIVED
DIYRESEND
DIYCALLME
DIYINIT
DIYGETTAMPERS
DIYCHECK
DIYCONTINGENCIA
DIYEXTENDTIME
GETCAPMANT
SCHMANT
SENDOTPS
SENDOTP
SECUREACTIONS
SECUREACTION
GCMANT
GCCAPACITY
GCCANCELMANT
GCSCHMANT
CTCMFM
CONFORT
TEMP
HUM
AIRQ
GETCONFIGDDI
SETCONFIGDDI
SCHLIST
SCHADD
SCHUPD
SCHDEL
SCHLEGAL
SCHNOT
SCHUPDONFLY
GETASI
ASILEGAL
BAJAASI
ALTAASI
ASIRES
ASISOS
ACOMPGETTIMERS
ACOMPTRACKING
ACOMPCANCEL
GETTRACKERDATA
UPDORTRACK
GETONROADKEYDATA
UPDORKEY
NSR
GDPRPOPUP
GDPR
UPDGDPR
FIRSTCHGPASS
RESETPASS
RESETPASS2
SENDINST
ALTAWEB
ALTAWEB2
LOCKSMITH
ACCEPTLEGALSLOCKSMITH
ASKLOCKSMITH
CANCELLOCKSMITH
GETALLLOCKSMITHS
GETSECURITYINFO
CHECKOTP
PENDINGBILLSLIST
PAYMENTDATA
PAYMENTEMAIL
@Cebeerre
If you “RE” the Mobile App, more incredible and valuable work!!! (not everyone appreciates the great work that reverse engineering takes).
I think the first step could be create a custom component based on alarm panel enity, I thing the first aprox is to replicate the verisure (USA version) component here
just create a directory
/home/homeassistant/.homeassistant/custom_components/verisure_spain/alarm_control_panel/
and create 3 files inside:
manifest.json
__ini__.py
verisure.py
the manifest could be:
{
"domain": "verisure_spain",
"name": "Verisure Spain",
"documentation": "https://github.com/home-assistant/example-custom-config/tree/master/custom_components/example_sensor/",
"dependencies": [],
"codeowners": ["Cebeerre"],
"requirements": ["xmltodict"]
}
The verisure.py need to change proper calls for yours, and init the component with proper reading config yaml parameters (username, password, installation, country_code). You can see an example in my custom_component (as sensor) here
Does anyone try with this script in Italy? I can’t find a way to make it work (maybe login problems)
thanks
I got this error in raspian (both RPy 3 and 4)
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/urllib3/contrib/pyopenssl.py", line 453, in wrap_socket
cnx.do_handshake()
File "/usr/local/lib/python3.7/dist-packages/OpenSSL/SSL.py", line 1915, in do_handshake
self._raise_ssl_error(self._ssl, result)
File "/usr/local/lib/python3.7/dist-packages/OpenSSL/SSL.py", line 1647, in _raise_ssl_error
_raise_current_error()
File "/usr/local/lib/python3.7/dist-packages/OpenSSL/_util.py", line 54, in exception_from_error_queue
raise exception_type(errors)
OpenSSL.SSL.Error: [('SSL routines', 'tls_process_ske_dhe', 'dh key too small')]
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line 600, in urlopen
chunked=chunked)
File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line 343, in _make_request
self._validate_conn(conn)
File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line 841, in _validate_conn
conn.connect()
File "/usr/lib/python3/dist-packages/urllib3/connection.py", line 344, in connect
ssl_context=context)
File "/usr/lib/python3/dist-packages/urllib3/util/ssl_.py", line 344, in ssl_wrap_socket
return context.wrap_socket(sock, server_hostname=server_hostname)
File "/usr/lib/python3/dist-packages/urllib3/contrib/pyopenssl.py", line 459, in wrap_socket
raise ssl.SSLError('bad handshake: %r' % e)
ssl.SSLError: ("bad handshake: Error([('SSL routines', 'tls_process_ske_dhe', 'dh key too small')])",)
[....]
Any ideas?
Thanks
Try to add:
requests.packages.urllib3.contrib.pyopenssl.DEFAULT_SSL_CIPHER_LIST += 'HIGH:!DH:!aNULL'
just beffore the class definition
I’m going to try to develope a component based on mobile api from cebeerre
Published the first python version based on the great cebeerre work…