@howartp:
You actually do not need to change status of the Verisure devices at all to get this error.
Just set the plugin to login every minute and check the status of the alarm and all the other Verisure devices the user might have (like door locks, smart wall pugs etc).
Then you will just have to wait until the error appears. It can happen within an hour or so or it can take 5-6 hours until it happens.
So the error does not happen when one tries to send a command to CHANGE the state of the alarm or any other Verisure device.
The error happens only when the Verisure plugin makes a login attempt (for example every minute if the plugin is configured to check state every minute).
You could even set the status checks to every 15th second. That will most likely trigger the error much sooner.
Polling for status every 15th second is the current lowest possible setting and I do not think a user need so much more frequent polling. In fact, I really believe that we should not poll the Verisure web page too often since Verisure might start taking action against us if we do frequent polls.
I have been using 1 minute polling frequency and the lowest I would like to have is 30 seconds which is currently not available as a setting in lindehoff's plugin. This might be something you maybe can change in the code for us?