Add types for update_stats

[kimdv]

It will be part of home-assistant/core#116737

This will add typed info for update_stats.WAN.monitors

JSON example from a UDM SE

{
  "data": [
    {
      "uptime_stats": {
        "WAN": {
          "monitors": [
            {
              "availability": 100.0,
              "latency_average": 5,
              "target": "www.microsoft.com",
              "type": "icmp"
            },
            {
              "availability": 100.0,
              "latency_average": 7,
              "target": "google.com",
              "type": "icmp"
            },
            {
              "availability": 100.0,
              "latency_average": 5,
              "target": "1.1.1.1",
              "type": "icmp"
            }
          ]
        },
        "WAN2": {
          "monitors": [
            {
              "availability": 0.0,
              "target": "www.microsoft.com",
              "type": "icmp"
            },
            {
              "availability": 0.0,
              "target": "google.com",
              "type": "icmp"
            },
            {
              "availability": 0.0,
              "target": "1.1.1.1",
              "type": "icmp"
            }
          ]
        }
      }
    }
  ]
}

[Kane610]

I have more time to look tomorrow. I was also planning on doing this for you but good you got here first :)

[kimdv]

I have more time to look tomorrow. I was also planning on doing this for you but good you got here first :)

Awesome! :D

[Kane610]

Please also extend one of the device tests for this.

[Kane610]

Almost there!

[kimdv]

@Kane610
I get this test error

FAILED tests/test_devices.py::test_device[device_payload5-reference_data5] - AssertionError: assert None == {'WAN': {'monitors': [{'availability': 100.0, 'latency_average': 5, 'target': 'www.microsoft.com', 'type': 'icmp'}, {'...ilability': 0.0, 'target': 'google.com', 'type': 'icmp'}, {'availability': 0.0, 'target': '1.1.1.1', 'type': 'icmp'}]}}

Not sure why?
Is it because that we expect an object that isn't there?
In this case I must be the uptime_stats

[kimdv]

@Kane610 I get this test error

FAILED tests/test_devices.py::test_device[device_payload5-reference_data5] - AssertionError: assert None == {'WAN': {'monitors': [{'availability': 100.0, 'latency_average': 5, 'target': 'www.microsoft.com', 'type': 'icmp'}, {'...ilability': 0.0, 'target': 'google.com', 'type': 'icmp'}, {'availability': 0.0, 'target': '1.1.1.1', 'type': 'icmp'}]}}

Not sure why? Is it because that we expect an object that isn't there? In this case I must be the uptime_stats

I needed to add in fixtures.py.

But removing the data in 13772ac don't make it fail?

[Kane610]

Change the test to use a better fixture representable to the where the data can be found for real and this is ready

[Kane610]

@Kane610 I get this test error

FAILED tests/test_devices.py::test_device[device_payload5-reference_data5] - AssertionError: assert None == {'WAN': {'monitors': [{'availability': 100.0, 'latency_average': 5, 'target': 'www.microsoft.com', 'type': 'icmp'}, {'...ilability': 0.0, 'target': 'google.com', 'type': 'icmp'}, {'availability': 0.0, 'target': '1.1.1.1', 'type': 'icmp'}]}}

Not sure why? Is it because that we expect an object that isn't there? In this case I must be the uptime_stats

I needed to add in fixtures.py.

But removing the data in 13772ac don't make it fail?

Removing the data doesn't do anything you remove the data to check against the existence of the data so when you remove it there is no comparison done for the update stats

[Kane610]

Awesome

[Kane610]

I will do a release shortly