Closed gmartenscb closed 2 months ago
@gmartenscb Hi, thank you for the information.
I am not familiar with Watchman
, but will look into it some more.
Regarding the "Watchman Report" and its "missing entities" ...
The media_player.spotifyplus_username
entity_id that is mentioned in the report corresponds to example:
entries in the service definition yaml file (e.g. custom_components/spotifyplus/services.yaml
), down to the specific line numbers (e.g. :8,29,5, ...).
These entries are simply example values that can be supplied for the entity_id
field for each custom service that requires an entity_id value. They should not be reported as missing, unless you have automations defined that use the service and have not specified an entity_id
value.
For example, the get_artist
custom service definition is:
get_artist:
name: Get Artist
description: Get Spotify catalog information for a single artist.
fields:
entity_id:
name: Entity ID
description: Entity ID of the SpotifyPlus device that will make the request to the Spotify Web API.
example: "media_player.spotifyplus_username"
required: true
selector:
entity:
integration: spotifyplus
domain: media_player
artist_id:
name: Artist Id
description: The Spotify ID of the artist.
example: "6APm8EjxOHSYM5B4i3vT3q"
required: true
selector:
text:
The Missing 1 entity(ies) from 6 found in your config:
would indicate that you have a SpotifyPlus custom service call defined somewhere in Automations, and it does not have an entity_id
defined. Can you verify that?
Thanks for your quick reply!
And you're absolutely right. I should've taken a closer look myself first, apoligies. This is a bug / issue in Watchman and not within SpotifyPlus!
Watchman is a nice HACS integration that checks your configuration and checks whether you have missing entities or services, aka; if your configuration is (in)valid.
Check that integration's issues, I do see it's brought up there before (multiple times): https://github.com/dummylabs/thewatchman/issues/25#issuecomment-1097941988 Or this one, or this one, so fair to say more people ran into this.
I'll apply the suggested fix, with ignoring the custom_components
directory in the first issue I linked.
Once again thank you for your response!
No worries - I learned something new today (brief intro to Watchman). :-)
System Health details
System Information
Home Assistant Community Store
GitHub API | ok -- | -- GitHub Content | ok GitHub Web | ok GitHub API Calls Remaining | 4970 Installed Version | 1.34.0 Stage | running Available Repositories | 1391 Downloaded Repositories | 12 HACS Data | okHome Assistant Cloud
logged_in | true -- | -- subscription_expiration | 19 July 2025 at 02:00 relayer_connected | true relayer_region | eu-central-1 remote_enabled | true remote_connected | true alexa_enabled | true google_enabled | true remote_server | eu-central-1-18.ui.nabu.casa certificate_status | ready instance_id | e6c30bf5ff0947c6887d2a4690ea0a30 can_reach_cert_server | ok can_reach_cloud_auth | ok can_reach_cloud | okHome Assistant Supervisor
host_os | Home Assistant OS 12.4 -- | -- update_channel | stable supervisor_version | supervisor-2024.06.2 agent_version | 1.6.0 docker_version | 26.1.4 disk_total | 458.4 GB disk_used | 7.8 GB healthy | true supported | true host_connectivity | true supervisor_connectivity | true ntp_synchronized | true virtualization | board | yellow supervisor_api | ok version_api | ok installed_addons | Advanced SSH & Web Terminal (18.0.0), Studio Code Server (5.15.0), MariaDB (2.7.1), Samba share (12.3.2)Dashboards
dashboards | 3 -- | -- resources | 5 views | 8 mode | storageRecorder
oldest_recorder_run | 21 July 2024 at 09:42 -- | -- current_recorder_run | 31 July 2024 at 00:31 estimated_db_size | 100.58 MiB database_engine | mysql database_version | 10.11.6SpotifyPlus
integration_version | v1.0.44 -- | -- clients_configured | 1: Gijs (premium) api_endpoint_reachable | okChecklist
Describe the issue
If I run watchman after a fresh install of the
SpotifyPlus
integration, I get a lot of warnings in regards to a missing entity. Not sure how to go about resolving this, or whether it is a bug within the integration.Let me know if you need any more information, or want me to try a couple of things out.
Watchman report:
Reproduction steps
Clean install of the SpotifyPlus integration.
Debug logs
Diagnostics dump
No response