Verisure Plugin

Posted on
Mon Apr 01, 2019 6:22 am
CrazyFin offline
Posts: 325
Joined: Jan 08, 2015
Location: Stockholm, SWEDEN

Re: Verisure Plugin

@micke_lindgren:

I had similar problems until I renamed my Doorman locks to NOT use Swedish characters åäöÅÄÖ.

Posted on
Tue Apr 02, 2019 4:36 am
micke__lindgren offline
Posts: 2
Joined: Mar 19, 2018

Re: Verisure Plugin

@Crazyfin:

I had a hunch that would be the issue but but sadly i get the same result after renaming and re-adding the locks :(
Have you got your locks working as we speak?

Posted on
Tue Apr 02, 2019 1:50 pm
CrazyFin offline
Posts: 325
Joined: Jan 08, 2015
Location: Stockholm, SWEDEN

Re: Verisure Plugin

@micke_lindgren:

Yepp, my 4 locks are working fine and I can both see status of the locks in Indigo as well as lock and unlock them from Indigo.

If you log in to "Mina Sidor" @ Verisure, can you see the status of your locks there and can you control them there?

Posted on
Tue May 28, 2019 12:39 am
CrazyFin offline
Posts: 325
Joined: Jan 08, 2015
Location: Stockholm, SWEDEN

Re: Verisure Plugin

@lindehoff:

Latest Verisure system update (rolled out during the last 2-3 days to users in Sweden) has caused issues for your cool Verisure Plugin:

"Verisure Error AttributeError: Unable to login to Verisure (4), retry in 240 sec. Reason: 'NoneType' object has no attribute 'group' "

I see that this bug has already been report on GitHub (https://github.com/lindehoff/Indigo-Verisure/issues)

Posted on
Tue May 28, 2019 1:31 am
CrazyFin offline
Posts: 325
Joined: Jan 08, 2015
Location: Stockholm, SWEDEN

Re: Verisure Plugin

I went to https://github.com/persandstrom/python-verisure and downloaded Per Sandström's code and run it in my local terminal window and that code seems to work properly:

When I execute the command:
vsure ,<my login name> <my pwd> armstate

I get the following reply
{
"date": "2019-05-28T04:49:50.000Z",
"statusType": "DISARMED",
"changedVia": "HOMEPAD",
"cid": "<CID NUMBER SHOWN HERE>"
}

So it seems to work fine when using Per Sandström's code and running it in command line mode.

I see that Per Sandström's Verisure Python module is updated on Dec 2018 while the Verisure plugin in Indigo is from Nov 2016.
I guess that the Indigo Verisure plugin needs to be rebuilt to include the Dec 2018 version of the Verisure module from Per Sandström?

Posted on
Tue May 28, 2019 2:02 am
CrazyFin offline
Posts: 325
Joined: Jan 08, 2015
Location: Stockholm, SWEDEN

Re: Verisure Plugin

UPDATE!

User "vsvirtan" at @lindehoff's GitHub page (https://github.com/lindehoff/Indigo-Verisure/issues/26) told me that he got it to work just by re-entering his username and pwd in the config window for the Verisure plugin.

I tested it by re-entering my login data and pressing <SAVE>. That generated an error
"Verisure Error 'NoneType' object has no attribute 'group' "
BUT the plugin logged in to Verisure without problems now! :shock:

Not sure what the problem was but it seems to be working as it should now.

Posted on
Tue May 28, 2019 2:09 am
CrazyFin offline
Posts: 325
Joined: Jan 08, 2015
Location: Stockholm, SWEDEN

Re: Verisure Plugin

I guess I was jumping of joy too early... :oops:

When the Verisure plugin tries to do its updated check (I have set it to check alarm status every minute) I get the error again:

"Verisure Error AttributeError: Unable to login to Verisure (3), retry in 180 sec. Reason: 'NoneType' object has no attribute 'group' "

So it seems to work only the first time I have re-entered the login details and pressed save. Any subsequent login attempts by the plugin to Verisure API fails.

So strange, when I now have enabled the DEBUG flag it seems to work ok on the subsequent login attempts as well....

I'll keep monitoring this and report back after few hours.

Posted on
Tue May 28, 2019 2:19 am
CrazyFin offline
Posts: 325
Joined: Jan 08, 2015
Location: Stockholm, SWEDEN

Re: Verisure Plugin

Ok, so if I re-enter my login name and pwd to Verisure and press SAVE then it all works fine until I RELOAD the plugin.
After I have reloaded the plugin I need to re-enter login details in order to get it to work again.

Nope, after about 1 hour the same error came back again even though I had not reloaded the plugin... :cry:


2019-05-28 10:33:07.299 Verisure Debug Checking status for all Verisure Devices
2019-05-28 10:33:07.303 Verisure Debug Getting update for device: ALARM
2019-05-28 10:33:07.497 Verisure Error ResponseError: Unable to update device state on server. Connection to Verisure will be reseted. Device: ALARM, Reason: Unable to validate response form My Pages, status code: 500 - Data:
2019-05-28 10:33:07.505 Verisure Debug Currently not logged in, try again.


Re-entering login details again and pressing SAVE helps. It will probably continue to work for another hour or so until login fails again.

Posted on
Tue May 28, 2019 4:04 am
tazswe offline
Posts: 23
Joined: Mar 13, 2017

Re: Verisure Plugin

I have made some tests with the plugin and you can get status of a lot of things, for example who unlocked the door and so on. :D
Problem is that you can’t change status more frequently than the update rate that currently have a minimum of 15 seconds.
For example you need to keep your door open for 15 seconds to get a notification of who opened the look.
With the option of a shorter update rate at about 4 seconds you should be able to get a status of who opened the door and that could trigger a lot of things.

Posted on
Wed Jun 12, 2019 12:35 am
CrazyFin offline
Posts: 325
Joined: Jan 08, 2015
Location: Stockholm, SWEDEN

Re: Verisure Plugin

I am still having the issue with the Verisure plugin stopping to work every now and then.
I have tested with increasing the polling time from 1 minute to 5 minutes and that has reduced the occasions of when the plugin gets the login error that it can not handle which causes it not being able to login anymore.

If I just go to the configuration panel and just press SAVE (without changing anything) the configuration panel closes and I see the following error in the log:

Code: Select all
2019-06-12 08:28:10.859   Verisure Debug   Plugin config dialog window closed.
2019-06-12 08:28:10.861   Verisure Debug   Logging in
2019-06-12 08:28:11.615   Verisure Error   'NoneType' object has no attribute 'group'

However, the plugin is now able to login and get current alarm state.


This morning the state was "unknown" again and when I look in the log I see a new type of error message:
Code: Select all
2019-06-12 06:17:28.925   Verisure Debug   Checking status for all Verisure Devices
2019-06-12 06:17:28.928   Verisure Debug   Getting update for device: ALARM
2019-06-12 06:17:29.040   Verisure Error   ResponseError: Unable to update device state on server. Connection to Verisure will be reseted. Device: ALARM, Reason: <_sre.SRE_Match object at 0x109d52b58>
2019-06-12 06:17:29.049   Verisure Debug   Currently not logged in, try again.

And after this error the plugin is again not able to login and I have to open the config panel and just press save and it all starts to work again. The plugin is trying to login every 5th minute (which is the polling time I have configured at the moment) but this is the only two rows on those login attempts that I see:
Code: Select all
2019-06-12 06:22:30.728   Verisure Debug   Checking status for all Verisure Devices
2019-06-12 06:22:30.735   Verisure Debug   Currently not logged in, try again.



When I had the polling time set to 1 minute the plugin stopped working several times per day when it received the following error message on its login attempts:
Code: Select all
2019-06-09 23:43:21.909   Verisure Debug   Checking status for all Verisure Devices
2019-06-09 23:43:21.912   Verisure Debug   Getting update for device: ALARM
2019-06-09 23:43:22.075   Verisure Error   ResponseError: Unable to update device state on server. Connection to Verisure will be reseted. Device: ALARM, Reason: Unable to validate response form My Pages, status code: 500 - Data:
2019-06-09 23:43:22.083   Verisure Debug   Currently not logged in, try again.


Every time this error happens the plugin is not able to login anymore and I have to do the parameter save of the plugin to trigger it to log in again.

Who is online

Users browsing this forum: No registered users and 0 guests

cron