Issue with : state change from verisur app and changing status from home app

[enzofrnt]

That impossible to get a state change without it goes unresponsive. Same for changing state from homeapp. Update ? That unusable

[lenny005]

Hello, did you find a solution ? Still having this issue

[enzofrnt]

no and you ?

[lenny005]

No, pinging the dev on twitter

[enzofrnt]

already try he do nothing, sadly

[ptz0n]

Please contribute with code, I'll review PR's.

[lenny005]

I would really like to but I am no dev. But i can contribute with coffee or else ? (Paypal ?)

[lenny005]

If you don’t have verisure anymore maybe i can give you access to mine temporary to try stuff ? @ptz0n

[ptz0n]

Problem summary; Verisure responds too slow for the Home app. We cannot receive a confirmation on requests until the Home app hits its timeout. This timeout is out of our control.

We could do an optimistic update approach. This means that we cache and return the current and target arm state before it has been confirmed by Verisure. Home app will (hopefully) be happy to get the faked confirmation when you do a state change, even before the actual state has been changed in the Verisure system.

Later, if we for some reason could not set the target state (Verisure down, slower than usual etc.) this will have to update the state again which will be communicated back to the Home app.

This is more complex but hopefully feel a bit more reliable from a user perspective.

[ptz0n]

Related issue: #1

[lenny005]

@ptz0n Here is one fork of your work that seam to be working, maybe it can help you ?

master...mmoriani:master

[lenny005]

@PIORIGIN I see that user @mmoriani forked @ptz0n as stated above (master...mmoriani:master) and he pushed it on homebridge repo if you want to try: Homebridge Securitas Direct
@ottimis/homebridge-securitas-direct v1.0.1 (2021-09-19)

He seems to have repair the plugin. Can't try it right now

[ptz0n]

Great that the fork is working. I'm happy to review, cleanup and publish these changes if @mmoriani would like to submit a PR.

[mmoriani]

Hello!
My intention was to test the changes and do a PR, but I was unable to test it thoroughly due to lack of time.
I think there is something more that could be improved/fixed.
I can try to spend some time on it in the next few weeks or do a PR directly. @ptz0n what do you prefer?

[ptz0n]

Whip up what you have and submit a PR. I'm happy to help out with reviewing and updating tests etc.

[mmoriani]

@ptz0n I remembered that I also modified the node-securitas-direct package to use the APIs that are now used in the new desktop webapp.
However, I realized that they now require MFA... So something seems to be broken at login. The rest of the code still seems to work, but need a solution for the login.
I was looking for a solution this morning, but i need more time to understand.

I've seen the same problem here.

What do you think?

[enzofrnt]

do we have any news ? need some beta tester ?