Ideally the presence check could be considered during the PlexServer.process_sessions method - if there's an active play session, the client is much more likely to be active, regardless of the cached presence status. "Show all clients, even if the external address does not match"), but the other filtering would still cause occasional issues. Does our heart break over this Having just finished adding RasPlex to all the televisions in our houseyes, yes it does. ago no, seems the the plex team is more interested in making alexa work than making google work. ago How do you like the support in the regular Plex app wade001 2 yr. What version of Home Assistant Core has the issue Core-2022.6.1 What was the last working version of Home Assistant. Just wondering will PlexAmp ever have support for the Google Assistant 11 3 3 comments Best Add a Comment paulrharve圓 2 yr. It's conceivable that the publicAddressMatches check could be changed to be a configuration option on the integration (e.g. Plex Media Player Plex Web App Roku Windows/Windows Phone Sadly, this means the Plex client your smart TV has access to might not work, and unofficial and unlisted clients like RasPlex don’t work either. The problem Plexamp (ersion 4.2.2) doesnt show media controls in the media card. 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. Learn more about how you can get help from your Assistant. Discover what your Google Assistant can do. You can access it with long press home on Android, Ok Google, or a squeeze on Pixel phones. There’s even support for the PiFi Digi+ board, which attaches to the top of a Raspberry Pi and adds an enhanced audio chip and optical output. Dont say anything other than movie and options should come up. You can also install the Plexamp server as a system service that starts at boot, for a more Chromecast Audio-like experience. 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. Your one Google Assistant extends to help you across devices, like Google Home, your phone, and more. You have to go through the shields assistant. Limbus Company APK Download for Android Plexamp APK Download for Android Happy Valentine s. All other working clients are returned by the GDM check (as they're on the same broadcast domain as the Home Assistant container). When do you update the Google Analytics data. 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 |