Keeps the integration running when Microsoft cannot resolve one family member.
Fixed
- One unresolvable family member no longer blocks the whole integration (#42). When Microsoft answers
Family.UnableToFindTargetResource/RosterErrorfor a child, typically because a reset or decommissioned device is still listed in the family, or because a school/work (Entra ID) account is enrolled on the child's device, setup used to fail and retry forever, and no entity was created for any child. The per-member requests now tolerate that specific 404: the affected child keeps empty data for the failing endpoint (devices, screen-time usage, apps, lockable platforms or spending), everything else loads normally, and a persistent notification plus aroster_errorsattribute on the Connection sensor tell you which member and which data are affected. Any other error still propagates as before.