@drumstick77, @Gav_in - how bizarre. I don’t see this at all on mine. In fact, there’s no history at the moment for mine as the WAN connection has been rock solid and not changed state since I rebuilt the database for HASS.
If you can grab diagnostics or a debug log when it happens then I’ll be happy to have a look at it. I have an idea what might be causing it but won’t know if I’m right until I can see some logs.
and yes, it does it again.
I can provide the log, can you please point me to the right direction of which log and how? 
Cheers
actually, I tell you what. the other linksys velop implementation also had some files under custom_components>linksys_velop folders. I will remove the integration and the all remnants files and start again…
You might be on to something there…
I have that component installed too, though don’t use it in HA. Perhaps there is a mix-up with files between the two components.
@uvjim I’ll uninstall the ‘other’ one a let you know if still happening over next few days. If it is will get you debug logs then.
Be careful… If they’re using the same name I’m not sure how HAC deals with that. You may find you need to install this one again.
Whilst the sensors are showing as unavailable use the 3-dots menu near Visit Device and select Download diagnostics.
If you could open an issue on Github and then attach the diagnotics file, I’ll have a look and see if I can find something obvious.
Badly it seems 
Both integrations get installed (copied) to same folder in custom components 🤷🏻
I uninstalled the ‘other’ one and the reinstalled your one before rebooting so hopefully caught everything.
Will keep an eye on it for a few hours and let you know…
I think I saw a bug (issue) on GitHub regarding UPnP doing the same.
Have a quick look here, might be hitting the same thing:
@uvjim looks familiar?
Awesome. thanks. would be cool to pass the log here? or somewhere else?
By the way, is there a way to show how the result of the speedtest on dashboard?
I only use UPnP to do the discovery. After that I don’t touch it all and rely solely on the JNAP API. That’s not to say that something funky isn’t going on with the discovery side that doesn’t cause this. If it is, it looks like there’s already a PR to fix it - so if it is that, then hopefully I won’t have to do anything.
I’m sure you could if you wanted to. It’ll be quite long so you’d need to make sure you formatted it correctly.
An issue on Github would be easier as I can use it to reference any changes I may need to make.
There are a few issues open with random available/unavailable states. Just search for unavailable on Github. They might lead to the same issue at the end.
By the way, is there a way to show how the result of the speedtest on dashboard?
There’s an example UI in the README that shows how to access the information. They are attributes of the sensor.
Hello @uvjim
Have let this run for the past few hours and still getting the same unavailable every so often.
Looking at the log files and looks like the integration is timing out on getting an update from the Parent Node each time the entities go unavailable (about 30 times over two hours)
Let me know if you need more detail on any of this
Line 1570: 2022-06-08 14:34:29 ERROR (MainThread) [custom_components.linksys_velop] Error fetching linksys_velop (SERIAL_PARENT_UNIT) data: Timeout Error
Line 1671: 2022-06-08 14:37:11 ERROR (MainThread) [custom_components.linksys_velop] Error fetching linksys_velop (SERIAL_PARENT_UNIT) data: Timeout Error
Line 1739: 2022-06-08 14:39:11 ERROR (MainThread) [custom_components.linksys_velop] Error fetching linksys_velop (SERIAL_PARENT_UNIT) data: Timeout Error
Line 1805: 2022-06-08 14:41:09 ERROR (MainThread) [custom_components.linksys_velop] Error fetching linksys_velop (SERIAL_PARENT_UNIT) data: Timeout Error
Line 1872: 2022-06-08 14:43:08 ERROR (MainThread) [custom_components.linksys_velop] Error fetching linksys_velop (SERIAL_PARENT_UNIT) data: Timeout Error
Line 1942: 2022-06-08 14:45:09 ERROR (MainThread) [custom_components.linksys_velop] Error fetching linksys_velop (SERIAL_PARENT_UNIT) data: Timeout Error
Line 2210: 2022-06-08 14:54:22 ERROR (MainThread) [custom_components.linksys_velop] Error fetching linksys_velop (SERIAL_PARENT_UNIT) data: Timeout Error
Line 2500: 2022-06-08 15:04:18 ERROR (MainThread) [custom_components.linksys_velop] Error fetching linksys_velop (SERIAL_PARENT_UNIT) data: Timeout Error
Line 2805: 2022-06-08 15:14:18 ERROR (MainThread) [custom_components.linksys_velop] Error fetching linksys_velop (SERIAL_PARENT_UNIT) data: Timeout Error
Line 2871: 2022-06-08 15:16:18 ERROR (MainThread) [custom_components.linksys_velop] Error fetching linksys_velop (SERIAL_PARENT_UNIT) data: Timeout Error
Line 3105: 2022-06-08 15:24:19 ERROR (MainThread) [custom_components.linksys_velop] Error fetching linksys_velop (SERIAL_PARENT_UNIT) data: Timeout Error
Line 3398: 2022-06-08 15:34:19 ERROR (MainThread) [custom_components.linksys_velop] Error fetching linksys_velop (SERIAL_PARENT_UNIT) data: Timeout Error
Line 3687: 2022-06-08 15:44:18 ERROR (MainThread) [custom_components.linksys_velop] Error fetching linksys_velop (SERIAL_PARENT_UNIT) data: Timeout Error
Line 3977: 2022-06-08 15:54:17 ERROR (MainThread) [custom_components.linksys_velop] Error fetching linksys_velop (SERIAL_PARENT_UNIT) data: Timeout Error
Line 4195: 2022-06-08 16:00:15 ERROR (MainThread) [custom_components.linksys_velop] Error fetching linksys_velop (SERIAL_PARENT_UNIT) data: Timeout Error
Line 4317: 2022-06-08 16:04:17 ERROR (MainThread) [custom_components.linksys_velop] Error fetching linksys_velop (SERIAL_PARENT_UNIT) data: Timeout Error
Line 4440: 2022-06-08 16:08:16 ERROR (MainThread) [custom_components.linksys_velop] Error fetching linksys_velop (SERIAL_PARENT_UNIT) data: Timeout Error
Line 4535: 2022-06-08 16:10:16 ERROR (MainThread) [custom_components.linksys_velop] Error fetching linksys_velop (SERIAL_PARENT_UNIT) data: Timeout Error
Line 4626: 2022-06-08 16:12:16 ERROR (MainThread) [custom_components.linksys_velop] Error fetching linksys_velop (SERIAL_PARENT_UNIT) data: Timeout Error
Line 4693: 2022-06-08 16:14:17 ERROR (MainThread) [custom_components.linksys_velop] Error fetching linksys_velop (SERIAL_PARENT_UNIT) data: Timeout Error
Line 4816: 2022-06-08 16:18:15 ERROR (MainThread) [custom_components.linksys_velop] Error fetching linksys_velop (SERIAL_PARENT_UNIT) data: Timeout Error
Line 4994: 2022-06-08 16:24:15 ERROR (MainThread) [custom_components.linksys_velop] Error fetching linksys_velop (SERIAL_PARENT_UNIT) data: Timeout Error
Line 5312: 2022-06-08 16:34:19 ERROR (MainThread) [custom_components.linksys_velop] Error fetching linksys_velop (SERIAL_PARENT_UNIT) data: Timeout Error
Line 5379: 2022-06-08 16:36:17 ERROR (MainThread) [custom_components.linksys_velop] Error fetching linksys_velop (SERIAL_PARENT_UNIT) data: Timeout Error
Line 5445: 2022-06-08 16:38:16 ERROR (MainThread) [custom_components.linksys_velop] Error fetching linksys_velop (SERIAL_PARENT_UNIT) data: Timeout Error
Line 5625: 2022-06-08 16:44:16 ERROR (MainThread) [custom_components.linksys_velop] Error fetching linksys_velop (SERIAL_PARENT_UNIT) data: Timeout Error
Line 5785: 2022-06-08 16:49:11 ERROR (MainThread) [custom_components.linksys_velop] Error fetching linksys_velop (SERIAL_PARENT_UNIT) data: Timeout Error
Line 5849: 2022-06-08 16:51:09 ERROR (MainThread) [custom_components.linksys_velop] Error fetching linksys_velop (SERIAL_PARENT_UNIT) data: Timeout Error
Sorry for this newbie questions and if I sounded like a broken radio. but I’ve tried looking under entities for these and I’m now able to find them
@Gav_in - what’s the polling interval set to? I have mine set to the following and don’t see an issue. What happens if you make it longer?
The Speetest latest sensor is the one you’re interested in…
GitHub - uvjim/linksys_velop: Home Assistant integration for the Linksys Velop should take you to the card you’d be interested in to see how it is used. Scroll slightly further up to see the screenshot for an example UI.
