Thanks for rtorchia for spotting that the handling of the number of doors was incorrect, and submitting a PR to fix it.
It appears that the `door_num` value in the API responses is always returning `3` - so rather than the configured number of doors, it appears to be the maximum number of doors supported by the device. As such, the `doors` array will now contain "extra" doors if you don't actually have the maximum number supported by your device; users of this library will have to accommodate for this rather than relying on the number of doors or the length of the `doors` array.