[Device Tracker] After reboot, not connected devices have status 'unavailable'

[iMicknl]

Versions

Key	Value
Home Assistant version	latest dev
Integration version	0.2.1
Sagemcom F@st model	Sagemcom FAST3890
Sagemcom F@st firmware (optional)	FAST3890V3_DELTA-SIP_sw05.76.9.7k-3

Describe the bug

After a reboot of Home Assistant, devices that are not connected but which have been connected in the past, will show as unavailable.

To Reproduce

Steps to reproduce the behavior:

1. Connect device to network
2. Disconnect device from network
3. Reboot Home Assistant
4. Device will show as unavailable

Expected behavior

Device will be home or not home.

Additional context

We could see if we pull all devices, instead of only active. But this will clutter the entity registry a lot.

                hosts = await self._client.get_hosts(only_active=True)

Otherwise, we could loop through the entities on boot and add them to the list / dictionary. This is what other integration do.

[bug]

[arunpoudel]

I can take it if you don't want to take it.

[iMicknl]

@arunpoudel if you have time, go for it! My bandwidth is limited these weeks and there are quite some open issues on the Somfy integration to fix.

[djfanatix]

Hi, any updates? I still have this issue with a BBOX3

thanks anyway!

[iMicknl]

@djfanatix could you give https://github.com/arunpoudel/ha-sagemcom-fast/archive/refs/heads/master.zip a try? Extract this file and place custom_components/sagemcom_fast in your custom_components folder.

[djfanatix]

@iMicknl Thanks for the reply, I think this works. I will test it

[djfanatix]

@iMicknl After testing for a few days, I notice that after a reboot, everybody stays on 'away', so that's also not good

[djfanatix]

Do you have an idea how to fix this issue? with the latest update everybody stays on away.
But in the logs it seems that the integration is polling the router successful.
When removing the plugin and reinstalling, the device list and presence is correct

[djfanatix]

I just checked with the latest version, but still the same.
New entitities are also not created.

[iMicknl]

If it would have been fixed, it would have been mentioned in the changelog and this issue would have been closed. 😉

However, I just released a small maintenance update where all dependencies where updated, nothing more. I don't have time to work on this integration at the moment, thus others would need to tackle this..

[github-actions]

'There hasn't been any activity on this issue recently. Is this issue still present?
Please make sure to update to the latest Home Assistant version and version of this integration to see if that solves the issue. Let us know if that works for you by adding a comment 👍.
This issue now has been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.'