Integration state switches frequently to "Unavailable" when there is a blip with the Cloud API polling

[palazzem]

Integration state switches frequently to "Unavailable" when there is a blip with the Cloud API polling

[palazzem]

cc @andr3a88

[palazzem]

Reopening the issue as the "Unavailable" state has been fixed in #150, but automations are still triggered when the reconnection happens. In that case, we have the following situation:

State -> Disarmed -> State

This blip happens after the reconnection when the integration, while keeping the previous state correctly, sends an incorrect update to Home Assistant, triggering automations when another update happens.

[palazzem]

The fact that the device goes in Disarmed state, is because when there is a reconnection the Cloud API provides an empty state regardless of what are the actual armed sectors. After the reconnection, this is an example of what the backend returns:

{
  "last_id":1,
  "sectors":{
    "0":{
      "id":1,
      "index":0,
      "element":1,
      "name":"S1",
      "activable":false,
      "status":false
    },
    "1":{
      "id":1,
      "index":1,
      "element":2,
      "name":"S2",
      "activable":false,
      "status":false
    },
    "2":{
      "id":1,
      "index":2,
      "element":3,
      "name":"S3",
      "activable":false,
      "status":false
    },
    "3":{
      "id":1,
      "index":3,
      "element":4,
      "name":"S4",
      "activable":false,
      "status":false
    }
  }
}

In this example, S4 should had status: true. At this point we can assume that when last_id == 1, the backend returns the actual empty state (connection reset).