Device Tracker

[PaulusThe1]

Hi. Why some device are losing? I loose my desktop pc tracker. Various device seems to disappear without reason. Can you help me? Thanks and sorry for my english

[uvjim]

I'm not sure I know what's going on based on what you've said.

I have a new release waiting to come out - currently in beta. Maybe you could try that and see if it still happens or if it gives more insight into what is happening.

[PaulusThe1]

With new release, the number of disappeared devices is bigger then previous release. some device, like Alexa, shelly, etc, now are "unavailable"

[uvjim]

OK. You're going to have to help me out here then. Do you have any logs? Can you show me screenshots of where you're looking and how you're creating them? Do they show as online in the Linksys app?

[PaulusThe1]

I keep a device like sample:Device BeSmartall 1 screenshot Linksys AppAll 2 screenshot HomeAssistant.After new release, Besmart is unavailebleP.s.: Sorry for my english -------- Messaggio originale --------Da: uvjim @.> Data: 28/10/24 16:55 (GMT+01:00) A: uvjim/linksys_velop @.> Cc: PaulusThe1 @.>, Author @.> Oggetto: Re: [uvjim/linksys_velop] Device Tracker (Issue #487) OK. You're going to have to help me out here then. Do you have any logs? Can you show me screenshots of where you're looking and how you're creating them? Do they show as online in the Linksys app?

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>

[uvjim]

I can't see any screenshots if you attached them. Maybe, explain in your native language and I'll try to translate it.

Please provide any logs, screenshots and what you're attempting to do. Also, if you explain or screenshot the states in the Linksys app, that would help.

[PaulusThe1]

Ciao e grazie per la tua collaborazione.

Cerco di spiegarti il problema:

Sull’app Linksys al momento vedo che sono connessi 42 devices, come si nota dal seguente screenshot:

Su HomeAssistant invece ne risultano solo 39

Ma il problema vero è che di device connessi non ne vedo nessuno, nonostante siano regolarmente connessi (con la tua precedente release, invece, i device erano presenti).

Prendiamo un device campione:

Device Besmart (cronotermostato della caldaia), regolarmente presente sull’app della Linksys:

Su HomeAssistant questo è quello che compare (con la precedente release il device prima veniva rilevato, mentre adesso non più).

Come si nota dallo storico, il device era presente prima della nuova release, che ho installato il 28.10 alle 10.

E questo vale anche per tutti gli altri device.

Grazie per la collaborazione.

Da: uvjim @.> Inviato: martedì 29 ottobre 2024 10:00 A: uvjim/linksys_velop @.> Cc: PaulusThe1 @.>; Author @.> Oggetto: Re: [uvjim/linksys_velop] Device Tracker (Issue #487)

I can't see any screenshots if you attached them. Maybe, explain in your native language and I'll try to translate it.

Please provide any logs, screenshots and what you're attempting to do. Also, if you explain or screenshot the states in the Linksys app, that would help.

— Reply to this email directly, view it on GitHub https://github.com/uvjim/linksys_velop/issues/487#issuecomment-2443621382 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AT2UUHHH2REANK43L755S6LZ55FAZAVCNFSM6AAAAABQHWX3QCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINBTGYZDCMZYGI . You are receiving this because you authored the thread. https://github.com/notifications/beacon/AT2UUHCINBGGIM3JW3C4RMDZ55FAZA5CNFSM6AAAAABQHWX3QCWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTURU22AM.gif Message ID: @. @.> >

-- Questa email è stata esaminata alla ricerca di virus dal software antivirus Avast. www.avast.com

[uvjim]

Thanks for the info. I didn't get the screenshots. Maybe they were stripped from the email. Could you add the. Using the GitHub website or app please?

If the translation was correct then hopefully the screenshots will help me work out what is going on.

[PaulusThe1]

Cerco di spiegarti il problema:

Sull’app Linksys al momento vedo che sono connessi 42 devices, come si nota dallo screenshot 01: Su HomeAssistant invece ne risultano solo 39 (screenshot 02) Ma il problema vero è che di device connessi non ne vedo nessuno, nonostante siano regolarmente connessi (con la tua precedente release, invece, i device erano presenti).

Prendiamo un device campione: Device Besmart (cronotermostato della caldaia), regolarmente presente sull’app della Linksys (screenshot 03) Su HomeAssistant il device non è più disponibile (screenshot 4), con la precedente release il device prima veniva rilevato, mentre adesso non più. Come si nota dallo storico (screenshot no.5), il device era presente prima della nuova release, che ho installato il 28.10 alle 10. E questo vale anche per tutti gli altri device.

[uvjim]

Thanks for the screenshots. I see what you see now. If you expand the attributes for the Online Devices sensor, is there an entry for the device in there?

If you could also download the diagnostics for the integration in Home Assistant and attach that here, it would be much appreciated.

[PaulusThe1]

config_entry-linksys_velop-01J9HWZ0PEH0DM0HCNDCEQX8X9.json

[PaulusThe1]

Ans: If you expand the attributes for the Online Devices sensor, is there an entry for the device in there? Resp: Yes

[uvjim]

I've found the device in the list based on the diagnostics you sent over. It looks like it should be found.

Could you let me know the entity id of the device tracker in Home Assistant please?

[PaulusThe1]

Non ho l'identity_id perché "Questa entità non viene più fornita dall'integrazione linksys_velop. Se l'entità non è più utilizzata, eliminala nelle impostazioni." -------- Messaggio originale --------Da: uvjim @.> Data: 30/10/24 21:10 (GMT+01:00) A: uvjim/linksys_velop @.> Cc: PaulusThe1 @.>, Author @.> Oggetto: Re: [uvjim/linksys_velop] Device Tracker (Issue #487) I've found the device in the list based on the diagnostics you sent over. It looks like it should be found. Could you let me know the entity id of the device tracker in Home Assistant please?

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>

[uvjim]

Is it not available if you click the cog in the header?

[PaulusThe1]

Not available -------- Messaggio originale --------Da: uvjim @.> Data: 30/10/24 21:58 (GMT+01:00) A: uvjim/linksys_velop @.> Cc: PaulusThe1 @.>, Author @.> Oggetto: Re: [uvjim/linksys_velop] Device Tracker (Issue #487) Is it not available if you click the cog in the header?

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>

[uvjim]

Hmm... This should really have been a state to get into. What version of Home Assistant are you using?

What should happen (tested here), when a device no longer exists on the Mesh (based on its unique id) an issue/repair is raised (you should see those in the settings menu). You can then click Submit to clean the device up.

The unique id of a device on the Mesh is governed by Linksys, so I'm not 100% sure what criteria they use for changing them.

So, could you reconfigure the integration, ensuring that you remove all devices trackers. That should remove the unavailable device.

Could you then confirm why you're using a device tracker? I assume the thermostat is stationary and shouldn't leave the network, so would not help with presence tracking. It might be that the UI device is a better option for you.

Without being able to see the unique_id of the device it's difficult to say why it's failing. I may update the diagnostics so that it includes the unique_id property of the device trackers as well. That could help diagnose when there's a mismatch happening.

[PaulusThe1]

Con il nuovo aggiornamento, la situazione è peggiorata.Adesso si blocca già in fase di configurazione.Ho disinstallato e poi reinstallato l'integrazione, ma adesso da sempre : Configurazione non riuscita" -------- Messaggio originale --------Da: uvjim @.> Data: 31/10/24 08:56 (GMT+01:00) A: uvjim/linksys_velop @.> Cc: PaulusThe1 @.>, Author @.> Oggetto: Re: [uvjim/linksys_velop] Device Tracker (Issue #487) Hmm... This should really have been a state to get into. What version of Home Assistant are you using? What should happen (tested here), when a device no longer exists on the Mesh (based on its unique id) an issue/repair is raised (you should see those in the settings menu). You can then click Submit to clean the device up. The unique id of a device on the Mesh is governed by Linksys, so I'm not 100% sure what criteria they use for changing them. So, could you reconfigure the integration, ensuring that you remove all devices trackers. That should remove the unavailable device. Could you then confirm why you're using a device tracker? I assume the thermostat is stationary and shouldn't leave the network, so would not help with presence tracking. It might be that the UI device is a better option for you. Without being able to see the unique_id of the device it's difficult to say why it's failing. I may update the diagnostics so that it includes the unique_id property of the device trackers as well. That could help diagnose when there's a mismatch happening.

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>

[uvjim]

I'll need logs and the diagnostics files again please. I still don't know what is happening, but you also haven't explained why you need to use a static device as a device tracker.

[PaulusThe1]

Ciao. La situazione è tornata come prima. Ora i nodi sono correttamente configurati e vedo anche tutti i device, ma li vedo tutti nello stato "Not home"

[PaulusThe1]

linksys_velop-01JCGR7M47PJ5AXMQ9JMSBDDAK-Mesh-81b4ae3d87c1429d78b39b55c8d102f7.json

[uvjim]

I can't see anything wrong in that file. I'll need a full debug log as per the documentation so I can see if any errors are occurring in there.

[PaulusThe1]

home-assistant.log Hi. Ecco il log fatto adesso. Thank you so much for support

[PaulusThe1]

Now I see all device connected, but all is "not home"

[uvjim]

The log shows issues with a number of integrations. The errors all seem to be network related. I'm not convinced this is the only integration having problems.

• Bosch is executing a blocking call at startup.
• slixmpp is executing a blocking call at startup.
• ingv_centro_nazionale_terramoti is executing a blocking call at startup.

pyvelop is timing out, but the error message doesn't appear to be getting translated.

You also have timeouts reaching a camera on the network as well.

You can try increasing the timeout for the extension to see if that helps. Go to configure and increase the time out. Then reload the integration.

[PaulusThe1]

Hi. I have no problem with other integration. Some problems are due to network (but another network, because Bosch, for example, is in another house)

[uvjim]

So, try increasing the timeout as per my previous message.

I can only go based on what I can see. The log is saying you have issues with other integrations as well.

We're going to have to close this at some point because the only thing reported in the logs is a timeout issue, which you should be able to solve by increasing the timeout.

Other calls that are handled by pyvelop seem to be working according to the log.

[PaulusThe1]

Prima c'era un'altra integrazione Linksys che funzionava senza problemi, poi è stata deprecata e l'ho dovuta disinstallare. Ma ti confermo che non ho problemi di rete: il mio HomaAssitant è connesso via ethernet direttamente al nodo mesh Linksys e tutto funziona regolarmente. Grazie comunque per il tuo supporto. Sarebbe interessante sapere se altri hanno lo stesso problema. Ho aumentato i tempi nella configurazione, ma non è cambiato nulla

[uvjim]

Did you reload the integration after setting the timeout value?

[PaulusThe1]

Yes

[PaulusThe1]

Ciao. Ho ricaricato l'integrazione, cancellato tutti i device tracker, ho rimesso solo alcuni e ora sembra funzionare. Aspettiamo un giorno per avere la conferma definitiva

[PaulusThe1]

L'integrazione sta funzionando senza problemi. Grazie ancora per il supporto