False arming/disarming. about sector HOT 13 OPEN

Here's the diagnostics of when it told me it was armed_away but it was disarmed.

Be careful when sharing logs on github, @zucram. There's a lot of info about your alarm system, your email address and on the first post on this thread I can see your routine log (I know that info is incorrect, but anyways). This info is available to everyone. I would suggest you to delete your last answer with the file and then upload that again hiding some private info into the file. ;)

Thanks. I thought I checked the log beforehand but I guess I didnt. Deleted now.

from sector.

Seems like the reply is still quoted however. Canntou remove the link from your reply @edwardtfn

from sector.

Test with latest version (not beta).

from sector.

This is the same thing that I've reported in multiple issues and has been going on for over a year. The latest version does not fix it.

from sector.

The latest version does not seem to solve the issue.

from sector.

One aspect is out discussion in the other PR on the changed_by which has an impact here and surely is the cause of the arm to arm state changes (change of an attribute is still an update of the state even if the state doesn't change).

The other issue is why it would flip between armed/disarmed which I can't understand more than that sectors api provides false information as I'm not influencing what comes directly from them. No idea yet how to deal with that.

from sector.

Would be great if you can supply diagnostics info when you know the state is incorrect.

from sector.

Would be great if you can supply diagnostics info when you know the state is incorrect.

If you can give me detailed instructions on what logs to extract etc I'd be happy to help!

from sector.

The other issue is why it would flip between armed/disarmed which I can't understand more than that sectors api provides false information as I'm not influencing what comes directly from them. No idea yet how to deal with that.

I've looked in the sector app at the same time as HA is showing a wrong state and the app shows the correct state.

from sector.

If you can give me detailed instructions on what logs to extract etc I'd be happy to help!

Click the 3 dots on the integration and choose "Download diagnostics". You get a text-file which you can upload here

from sector.

I've looked in the sector app at the same time as HA is showing a wrong state and the app shows the correct state.

Good to know! When you can confirm the state is wrong wait an additional minute to allow another update to happen just to ensure correct data is captured. Ideally look also in your log to see that the update coordinator says the refresh was successful and not timeout errors or other stuff.

from sector.

| I've looked in the sector app at the same time as HA is showing a wrong state and the app shows the correct state.

I've seen the same thing on my side. I've also looked in the code and don't see anything obvious but I find it hard to believe that they would "randomly" return wrong values. Not completely impossible but so unlikely.

One thing I'm thinking is if mapping the status is right? It's returning a number right? 🤔

from sector.

Now it was my fault. I've then deleted my message.

from sector.