Securitas Direct (Verisure EU) Custom Component [TESTERS WANTED]

Which integration ?

Hi mfrodrigues.
I’m portuguese to.
Could you send me pm to clarify some doubts.
I first install it on a raspberry pi3 but unable to interact with verisure app.
It accepts my credentials but failed on arm and disarm functions.

Hi,
since I have updated I see this log.
There is any procedure to fix it?

Logger: homeassistant.components.alarm_control_panel
Source: components/alarm_control_panel/init.py:194
Integration: Pannello di Controllo degli Allarmi (documentation, issues)
First occurred: 1 luglio 2020, 22:49:31 (1 occurrences)
Last logged: 1 luglio 2020, 22:49:31

AlarmControlPanel is deprecated, modify SecuritasAlarm to extend AlarmControlPanelEntity

thanks

Hey @ Cebeerre,

I hope you have been keeping well. I have been caught up on a project over the past couple of months but i am now back looking at things.

I am giving the images a shot today. I think for Home Assistant it may have to be a seperate entity to the alarm which collects the images. I am just going through the Home Assistant API.

I will let you know how i get on.

Cheers

Ross

I have never tried on a sentinel device but i do have it working using MQTT to my lightswitches, so there are possibilities out there.

Oh, i see this in the logs as well!!
Its a warning of a future depreciation in the Home Assistant side, so i am will check this against the API. It will be a very small update needed somewhere.

UPDATE

Just to follow up on this issue reported with the AlarmControlPanel is depreciated in HomeAssistant.

It is a very small and simple update of one word thats required to a file in the custom_component folder.

  1. In Home Assistant go to your config directory
  2. Go to custom_component directory
  3. Find and open the alarm_control_panel.py file
  4. Around line 57, you will find the line class SecuritasAlarm(alarm.AlarmControlPanel):
  5. Add the word “Entity” to the end of AlarmControlPanel so the line now looks like class SecuritasAlarm(alarm.AlarmControlPanelEntity):
  6. Restart Home Assistant and all is working

I believe @segalion maintains the GitHub for this, so i have tagged him in. It may be worth seeing if this can be set for HACS or even as a full component on HA?

Cheers

Ross

1 Like

Hi

I’ve just installed the Verisure custom component and setup the configuration.yaml using an example for UK and it seems to be working fine.

I haven’t yet tested the arming/disarming so will update when I do test these.

Also, as per the last post, I just modified the alarm_control_panel.py line 57 … changed SecuritasAlarm(alarm.AlarmControlPanel) to SecuritasAlarm(alarm.AlarmControlPanelEntity), to see if it is required for UK, and then restarted the HA.

This gave problem and HA game some error starting the Verisure component - so I revered the change back and restarted the HA, and it works fine.

One question I do have is that within the HA I can now see an alarm component. Is there a way to see the state of every sensor that Verisure has installed in my house, like door and window sensors? Are these visible individually through this integration.

Thanks

Unfortunately not. Keep in mind that what you’re actually doing here is interacting with the Securitas backend (their servers in their datacenter), not the alarm panel itself. When movement is triggered in one sensor but the alarm is disarmed, the panel does not report this state change to their servers. This just happens when the alarm is armed.

Xavi

Hi.
I am in Peru.
Just configured the integration with my system and it works!
Peru’s address is https://customers.verisure.pe/

Hi, verisure just released a new app.

I am getting this error on the log, anyone with same problem?

custom_components.securitas_direct.alarm_control_panel
Source: custom_components/securitas_direct/alarm_control_panel.py:91
Integration: Securitas Direct ([documentation](https://github.com/segalion/securitasdirect))
First occurred: 21 de septiembre de 2020 8:21:05 (12 occurrences)
Last logged: 23:38:02

Securitas: disarming (res=OrderedDict([('PET', OrderedDict([('RES', 'ERROR'), ('ERR', '60067'), ('MSG', 'No hay más información disponible'), ('BLOQ', OrderedDict([('@remotereqactive', '1'), ('#text', 'Our system is under maintenance right now, try later')]))]))]))

Same in here. It stopped working a few days ago. I have had to remove this from my installation…not quite sure if this component is still being maintained…

@jimenbar @gmarquezp mine is working fine even if not maintained

I tried to sniff. Also with the my verisure app you got the same message. So it’s not HA component problem

Hello again and sorry for the low level of support for this custom component during last year.

Now, I am trying to update some requests about this component (working only during next weeks, sorry about so low spare time)…

This is what I want to include:

  1. Improve stability (time response, defense programing, better log support, etc.)
  2. Add camera support (only pictures)
    2.1 create a component for every camera (autodetected)
    2.2 service to take picture ‘camera_snapshot’
    2.3 download all pictures appearing in a location (defined by user). By default, will be the new ‘media’, so you can easyly see all pictures in browser.
  3. Create new events (for detected new pictures)
  4. Include this component in HACS, to make it more easy to install, and update…

Another things (future), but I need some help could be:

  • a flow to UI configuration
  • support for more than 1 alarm for account (please could be great send me PM with your json configations)
  • support for PERImeter alarm (idem).

Could be great to migrate to aiohttp and async mode, but probably takes too effort for me.

Thanks in advance.

1 Like

@segalion, thanks a lot for your contribution as usual. Now that you are back with some spare time I have created another pull request with a very minor fix to address the “AlarmControlPanel is deprecated, modify SecuritasAlarm to extend AlarmControlPanelEntity

Saludos, Barto

Hi all, tried to check config before updating to 0.117 and this is the outcome:

General Errors:
- Component error: securitas_direct - No module named ‘xmltodict’

So its been a while since I have been here but i have hit a wall.
Those who have been following will know i have tweaked my setup and config over time so my issues may be deeper but i do not think it is.

As of the past few days i am not able to set the alarm. I can see responses but it seems like the API has gone in to some sort of Read Only mode and returning the message below.

“We have a problem right now, try later”

The issue is only regarding arming and disarming etc. Should i go to the new UK app and interact i see the alarm updates in Home Assistant and via cmd.

Is anyone else getting anything like this? I am not sure if it was at the same time as i updated to 0.117 or not and if it was i cant see what the breaking change might be. Anyone have any ideas??

Things different in my version

  1. Annexe
  2. Photos
  3. Notification of which sensor activated the alarm

Same problem here after the same time of updating to 0.117, I can’t arm alarm or disarm. Even pressing “arm” I’m getting a disarm log:

Logger: custom_components.securitas_direct.alarm_control_panel
Source: custom_components/securitas_direct/alarm_control_panel.py:91
Integration: Securitas Direct ([documentation](https://github.com/segalion/securitasdirect))
First occurred: 12:14:46 (6 occurrences)
Last logged: 12:15:51

Securitas: disarming (res=OrderedDict([('PET', OrderedDict([('RES', 'ERROR'), ('ERR', '60060'), ('MSG', 'No hemos podido atender tu solicitud. Asegúrate de tener la última actualización de la app My Verisure. Si la incidencia persiste, por favor, contacta con nuestro servicio de Atención al cliente.'), ('NUMINST', '3405071'), ('BLOQ', OrderedDict([('@remotereqactive', '1'), ('#text', 'Estamos mejorando nuestros servicios. Por favor intentelo de nuevo mas tarde. Gracias por confiar en Securitas Direct')]))]))]))

PS: It’s seems they are working in a new Verisure app (https://apps.apple.com/es/app/my-verisure-nueva/id1473822730) but old one still working and last update is 4 months ago.

Hey @javy97,

Thing is i have been on the new app since they launched it. The API responds.
Have you montiored the alarm in Home Assistant when you change it directly from the app? Do you notice Hiome Assistant updates if you are it in the new app, we just cant change it?
I am trying to find where the update is as i am determined to fix this one

Same problem in here. The component have stopped working. I get the below same error as @javy97 javy97 :

[custom_components.securitas_direct.alarm_control_panel] Securitas: disarming (res=OrderedDict([(‘PET’, OrderedDict([(‘RES’, ‘ERROR’), (‘ERR’, ‘60060’) …

and the request to update the app to the last version. It seems as a breaking change had happened on the SecuritasDirect web interface.