very often raise PlatformNotReady to tell HA to retry the setup
disabled log spam (e.g. WARNING Couldn't update x y) when iDRAC becomes unreachable
Breaking Changes:
Changed UUIDs to be dependent on the fan and thermal MemberId rather than index in for loop, the order of the fans could change and therefore the entities could sometimes get mixed up, this will require a re-adding of the integration (remove integration, reboot, setup integration again)
I tested the following scenarios with a PowerEdge R630:
[x] When Home Assistant starts and iDRAC is not reachable: integration waits until iDRAC becomes reachable, then displays the values correctly
[x] When iDRAC becomes unreachable, after Home Assistant is started and the integration already registered the entities: The entities become unavailable. When iDRAC becomes reachable again, the values get displayed correctly again
fixes #17
Changed:
async_forward_entry_setup
toasync_forward_entry_setups
(https://developers.home-assistant.io/blog/2024/06/12/async_forward_entry_setups/)PlatformNotReady
to tell HA to retry the setupWARNING Couldn't update x y
) when iDRAC becomes unreachableBreaking Changes:
MemberId
rather than index in for loop, the order of the fans could change and therefore the entities could sometimes get mixed up, this will require a re-adding of the integration (remove integration, reboot, setup integration again)I tested the following scenarios with a PowerEdge R630: