![]() ![]() It's conceivable that the publicAddressMatches check could be changed to be a configuration option on the integration (e.g. Plexamp running on a mobile device may not always pass the x.presence test (if discovery runs when Plexamp is not running on the device, the cached state has presence stored as 0). The discovery seems reliable enough, but might need some tweaking to allow handling strange edge cases (i.e. Manually removing the x.publicAddressMatches works to resolve this issue for me, at least when the device plays a track - the player_source now shows as, and supported_features returns as 152127 - same as other Plexamp clients. All other working clients are returned by the GDM check (as they're on the same broadcast domain as the Home Assistant container). 12:25:16 DEBUG (SyncWorker_3) Linked accounts: ]Īn authenticated request to does contain the Player tag with matching machineIdentifier value, but in my specific case I suspect this is complicated by my network having a /28 v4 block, and the device that is failing to show player controls has a different external IP to what the Plex server or Home Assistant container do, so the publicAddressMatches check inside extv_clients() would fail to include this client. Please report issue to the custom component author for shelly using this method at custom_components/shelly/_init_.py, line 356: await _registry.async_get_registry() 12:25:15 WARNING (MainThread) Detected integration that uses deprecated `async_get_registry` to access entity registry, use async_get instead. ![]() Please report issue to the custom component author for localtuya using this method at custom_components/localtuya/_init_.py, line 315: ent_reg = await er.async_get_registry(hass) ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |