v1.4.0

Discover.GetOrConnectSharedAsync (updateState: true) previously only loaded device state the first time a shared instance was created for a given device identity (host/port); every later cache hit silently returned that same instance with whatever state it captured at first connect, regardless of the caller's own updateState value. This was most visible on hubs/strips (e.g. KP303) whose Children list was empty at first connect and then stayed permanently empty for every later caller, even after child devices were paired. GetOrConnectSharedAsync now calls KasaDevice.UpdateAsync on a cache-hit shared instance before returning it when updateState: true is requested, so LightState, IsOn, Children, and other state are refreshed for every caller that asks for it, not just the first. Callers that pass updateState: false are unaffected and continue to receive the cached instance without an extra refresh.

Full Changelog: v1.3.1...v1.4.0