RoombaInfo capabilities values can be null

[kiasyn]

Just went through this getting homeassistant to detect my roomba (it is using an older version of roombapy, but I think it still applies to the current version).

Here are the capabilities I'm getting back from my i2 Roomba. (see pmaps and mc)

"cap": {
	"binFullDetect": 2,
	"addOnHw": 1,
	"oMode": 2,
	"dockComm": 1,
	"edge": 0,
	"maps": 2,
	"pmaps": null,
	"mc": null,
	"tLine": 2,
	"area": 1,
	"eco": 1,
	"multiPass": 3,
	"team": 1,
	"pp": 0,
	"lang": 2,
	"5ghz": 0,
	"prov": 3,
	"sched": 1,
	"svcConf": 1,
	"ota": 2,
	"log": 2,
	"langOta": 2
}

This was ultimately resulting in a 'Socket timeout' but actually it was failing to parse the dictionary with the null value.
In the homeassistant version I patched it with
from typing import Optional
and replacing the definition for capabilities with
capabilities: dict[str, Optional[int]] = Field(alias="cap")

I'm not actually a python dev, and things have changed between versions, but hopefully this information is useful?

[Orhideous]

It's an extremely nice catch, thank you!

[kiasyn]

Hi, not sure if #293 would fix it as the issue was a null value in capabilities, not the entire capabilities set being null