Playing on sonos device error 800

System Health details
System Information

version
core-2024.10.2

installation_type
Home Assistant Supervised

dev
false

hassio
true

docker
true

user
root

virtualenv
false

python_version
3.12.4

os_name
Linux

os_version
4.4.302+

arch
x86_64

timezone
Europe/Paris

config_dir
/config

Home Assistant Community Store

GitHub API
ok

GitHub Content
ok

GitHub Web
ok

HACS Data
ok

GitHub API Calls Remaining
4982

Installed Version
2.0.1

Stage
running

Available Repositories
1443

Downloaded Repositories
9

Home Assistant Cloud

logged_in
false

can_reach_cert_server
ok

can_reach_cloud_auth
ok

can_reach_cloud
ok

Home Assistant Supervisor

host_os
null

update_channel
stable

supervisor_version
supervisor-2024.10.2

agent_version
null

docker_version
20.10.23

healthy
failed to load: Unhealthy

supported
failed to load: Unsupported

host_connectivity
null

supervisor_connectivity
true

ntp_synchronized
null

virtualization

supervisor_api
ok

version_api
ok

installed_addons
Tautulli (4.1.0), AirSonos (4.2.2), Spotify Connect (0.13.0), Mosquitto broker (6.4.1), deCONZ (7.0.0), Terminal & SSH (9.15.0), File editor (5.8.0), Zigbee2MQTT (1.40.2-1)

Dashboards

dashboards
5

resources
5

views
10

mode
storage

Recorder

oldest_recorder_run
October 12, 2024 at 6:23 PM

current_recorder_run
October 18, 2024 at 12:46 PM

estimated_db_size
549.94 MiB

database_engine
sqlite

database_version
3.45.3

Spotify

api_endpoint_reachable
ok

SpotifyPlus

integration_version
v1.0.60

clients_configured
1: John Doe (premium)

api_endpoint_reachable
ok

Checklist

[X] I have enabled SmartInspect debug logging for my installation.
[X] I have filled out the issue template to the best of my ability.
[X] This issue only contains 1 issue (if you have multiple issues, open one issue for each issue).
[X] This issue is not a duplicate issue of any previous issues..

Describe the issue
Hello,
I have followed step by step your amazing guide to install and configure the integration.
I have a homeassistant on a docker container running on a synology NAS and two player one first gen that work perfectly with the very bad Sonos application.

Spotify plays perfectly (playlists/artists, etc...) from your integration when  I choose my computer with Spotify desktop (in the logs)
Spotifyplus can pause/play on sonos when something is playing
I have successfully generated the OAuth2 Token file for Sonos via your Python script, renamed it to spotifyplus_tokens.json (not mentioned clearly on the wiki so I copied multiple times the same file with original name and auto-generated name) in the below folders (not clear in the wiki and it  can't hurt ^^ ):
- config/storage
- homeassistant\homeassistant\custom_components\spotifyplus (Core)
- homeassistant\homeassistant.storage (Core)
- homeassistant\config (Supervisor)
- homeassistant\config.storage (Supervisor)
Step 4b - Select Application Credential -> never appeared to me but I don't think this is the issue as spotify works perfectly
Step "Integration Options" -> the cannonical name in the id returned by the Spotify developers API was my spotify username and not an id as you listed.  Therefore it is the same as the username in the Options (see attached jpg)

I think I did not forget anything, please don't hesitate to get back to me.
Thanks a lot for this integration, this is exactly what I am looking for :) Great job :)
Reproduction steps

Click on the on/off button in the integration
select my sonos device
Choose a title
...

Debug logs
2024-10-18 13:54:16.889 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration spotifyplus which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant

Traceback (most recent call last):
  File "/config/custom_components/spotifyplus/media_player.py", line 4552, in service_spotify_player_media_play_context
    self.data.spotifyClient.PlayerMediaPlayContext(contextUri, offsetUri, offsetPosition, positionMS, deviceId, delay)
  File "/usr/local/lib/python3.12/site-packages/spotifywebapipython/spotifyclient.py", line 11018, in PlayerMediaPlayContext
    self.MakeRequest('PUT', msg)
  File "/usr/local/lib/python3.12/site-packages/spotifywebapipython/spotifyclient.py", line 807, in MakeRequest
    msg.ResponseData = self._CheckResponseForErrors(msg, response)
                       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/spotifywebapipython/spotifyclient.py", line 611, in _CheckResponseForErrors
    raise SpotifyWebApiError(errCode, errMessage, msg.MethodName, response.reason, _logsi)
spotifywebapipython.spotifywebapierror.SpotifyWebApiError: SAM1001E - Spotify Web API returned an error status while processing the "PlayerMediaPlayContext" method.
Status: 404 - Not Found
Message: "Player command failed: No active device found"

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/components/websocket_api/commands.py", line 245, in handle_call_service
    response = await hass.services.async_call(
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/core.py", line 2761, in async_call
    response_data = await coro
                    ^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/core.py", line 2804, in _execute_service
    return await target(service_call)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 996, in entity_service_call
    single_response = await _handle_entity_call(
                      ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 1068, in _handle_entity_call
    result = await task
             ^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/media_player/__init__.py", line 878, in async_play_media
    await self.hass.async_add_executor_job(
  File "/usr/local/lib/python3.12/concurrent/futures/thread.py", line 58, in run
    result = self.fn(*self.args, **self.kwargs)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/config/custom_components/spotifyplus/media_player.py", line 265, in wrapper
    result = func(self, *args, **kwargs)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/config/custom_components/spotifyplus/media_player.py", line 844, in play_media
    self.service_spotify_player_media_play_context(media_id, deviceId=deviceId)
  File "/config/custom_components/spotifyplus/media_player.py", line 265, in wrapper
    result = func(self, *args, **kwargs)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/config/custom_components/spotifyplus/media_player.py", line 4567, in service_spotify_player_media_play_context
    raise HomeAssistantError(ex.Message)
homeassistant.exceptions.HomeAssistantError: Player command failed: No active device found

Diagnostics dump
2024-10-18 13:54:16.889 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration spotifyplus which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-10-18 13:54:18.009 WARNING (MainThread) [homeassistant.helpers.translation] Failed to load integration for translation: Integration 'default' not found.
2024-10-18 13:54:22.851 ERROR (MainThread) [homeassistant.setup] Setup failed for 'default': Integration not found.
Traceback (most recent call last):
File "/config/custom_components/spotifyplus/media_player.py", line 4552, in service_spotify_player_media_play_context
self.data.spotifyClient.PlayerMediaPlayContext(contextUri, offsetUri, offsetPosition, positionMS, deviceId, delay)
File "/usr/local/lib/python3.12/site-packages/spotifywebapipython/spotifyclient.py", line 11018, in PlayerMediaPlayContext
self.MakeRequest('PUT', msg)
File "/usr/local/lib/python3.12/site-packages/spotifywebapipython/spotifyclient.py", line 807, in MakeRequest
msg.ResponseData = self._CheckResponseForErrors(msg, response)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/spotifywebapipython/spotifyclient.py", line 611, in _CheckResponseForErrors
raise SpotifyWebApiError(errCode, errMessage, msg.MethodName, response.reason, _logsi)
spotifywebapipython.spotifywebapierror.SpotifyWebApiError: SAM1001E - Spotify Web API returned an error status while processing the "PlayerMediaPlayContext" method.
Status: 404 - Not Found
Message: "Player command failed: No active device found"
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/components/websocket_api/commands.py", line 245, in handle_call_service
response = await hass.services.async_call(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/core.py", line 2761, in async_call
response_data = await coro
^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/core.py", line 2804, in _execute_service
return await target(service_call)
^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 996, in entity_service_call
single_response = await _handle_entity_call(
^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 1068, in _handle_entity_call
result = await task
^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/media_player/init.py", line 878, in async_play_media
await self.hass.async_add_executor_job(
File "/usr/local/lib/python3.12/concurrent/futures/thread.py", line 58, in run
result = self.fn(*self.args, **self.kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/spotifyplus/media_player.py", line 265, in wrapper
result = func(self, *args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/spotifyplus/media_player.py", line 844, in play_media
self.service_spotify_player_media_play_context(media_id, deviceId=deviceId)
File "/config/custom_components/spotifyplus/media_player.py", line 265, in wrapper
result = func(self, *args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/spotifyplus/media_player.py", line 4567, in service_spotify_player_media_play_context
raise HomeAssistantError(ex.Message)
homeassistant.exceptions.HomeAssistantError: Player command failed: No active device found
2024-10-18 14:02:39.768 DEBUG (SyncWorker_5) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Scan interval 30 check - commandScanInterval=0, currentScanInterval=1, lastKnownTimeRemainingSeconds=0, state=paused
2024-10-18 14:02:39.768 DEBUG (SyncWorker_5) [custom_components.spotifyplus] 'SpotifyPlus John Doe': update method - getting Spotify Connect Player state
2024-10-18 14:02:39.768 DEBUG (SyncWorker_5) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Getting Spotify Connect Player state
2024-10-18 14:02:39.768 DEBUG (SyncWorker_5) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Currently selected Source: 'None'
2024-10-18 14:02:39.814 DEBUG (SyncWorker_5) [custom_components.spotifyplus] 'SpotifyPlus John Doe': MediaPlayerState set to 'paused'
2024-10-18 14:02:39.814 DEBUG (SyncWorker_5) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Source value is not set; using Spotify Web API player name ('None')
2024-10-18 14:02:48.775 DEBUG (SyncWorker_9) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Scan interval 30 check - commandScanInterval=0, currentScanInterval=21, lastKnownTimeRemainingSeconds=0, state=paused
2024-10-18 14:02:49.775 DEBUG (SyncWorker_11) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Scan interval 30 check - commandScanInterval=0, currentScanInterval=20, lastKnownTimeRemainingSeconds=0, state=paused
.....
2024-10-18 14:03:06.789 DEBUG (SyncWorker_4) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Scan interval 30 check - commandScanInterval=0, currentScanInterval=3, lastKnownTimeRemainingSeconds=0, state=paused
2024-10-18 14:03:07.790 DEBUG (SyncWorker_9) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Scan interval 30 check - commandScanInterval=0, currentScanInterval=2, lastKnownTimeRemainingSeconds=0, state=paused
2024-10-18 14:03:08.791 DEBUG (SyncWorker_8) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Scan interval 30 check - commandScanInterval=0, currentScanInterval=1, lastKnownTimeRemainingSeconds=0, state=paused
2024-10-18 14:03:08.791 DEBUG (SyncWorker_8) [custom_components.spotifyplus] 'SpotifyPlus John Doe': update method - getting Spotify Connect Player state
2024-10-18 14:03:08.791 DEBUG (SyncWorker_8) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Getting Spotify Connect Player state
2024-10-18 14:03:08.791 DEBUG (SyncWorker_8) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Currently selected Source: 'None'
2024-10-18 14:03:08.844 DEBUG (SyncWorker_8) [custom_components.spotifyplus] 'SpotifyPlus John Doe': MediaPlayerState set to 'paused'
2024-10-18 14:03:08.845 DEBUG (SyncWorker_8) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Source value is not set; using Spotify Web API player name ('None')
2024-10-18 14:03:09.791 DEBUG (SyncWorker_7) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Scan interval 30 check - commandScanInterval=0, currentScanInterval=29, lastKnownTimeRemainingSeconds=0, state=paused
2024-10-18 14:03:10.792 DEBUG (SyncWorker_10) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Scan interval 30 check - commandScanInterval=0, currentScanInterval=28, lastKnownTimeRemainingSeconds=0, state=paused
2024-10-18 14:03:11.792 DEBUG (SyncWorker_1) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Scan interval 30 check - commandScanInterval=0, currentScanInterval=27, lastKnownTimeRemainingSeconds=0, state=paused
2024-10-18 14:03:12.793 DEBUG (SyncWorker_7) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Scan interval 30 check - commandScanInterval=0, currentScanInterval=26, lastKnownTimeRemainingSeconds=0, state=paused
2024-10-18 14:03:13.795 DEBUG (SyncWorker_3) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Scan interval 30 check - commandScanInterval=0, currentScanInterval=25, lastKnownTimeRemainingSeconds=0, state=paused
2024-10-18 14:03:14.795 DEBUG (SyncWorker_1) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Scan interval 30 check - commandScanInterval=0, currentScanInterval=24, lastKnownTimeRemainingSeconds=0, state=paused
2024-10-18 14:03:15.796 DEBUG (SyncWorker_7) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Scan interval 30 check - commandScanInterval=0, currentScanInterval=23, lastKnownTimeRemainingSeconds=0, state=paused
2024-10-18 14:03:16.797 DEBUG (SyncWorker_9) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Scan interval 30 check - commandScanInterval=0, currentScanInterval=22, lastKnownTimeRemainingSeconds=0, state=paused
2024-10-18 14:03:17.797 DEBUG (SyncWorker_2) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Scan interval 30 check - commandScanInterval=0, currentScanInterval=21, lastKnownTimeRemainingSeconds=0, state=paused
2024-10-18 14:03:17.935 DEBUG (SyncWorker_6) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Getting Spotify Connect Player state
2024-10-18 14:03:17.935 DEBUG (SyncWorker_6) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Currently selected Source: 'None'
2024-10-18 14:03:17.974 DEBUG (SyncWorker_6) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Transferring playback from source device name: '' (id=)
2024-10-18 14:03:18.798 DEBUG (SyncWorker_8) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Update - Integration is in a command event; bypassing update
2024-10-18 14:03:19.775 DEBUG (SyncWorker_11) [custom_components.spotifyplus] 'SpotifyPlus John Doe': MediaPlayer is executing service 'media_play'
2024-10-18 14:03:19.798 DEBUG (SyncWorker_10) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Update - Integration is in a command event; bypassing update
2024-10-18 14:03:19.894 DEBUG (SyncWorker_11) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Processed a media player command - forcing a playerState scan window for the next 5 updates
2024-10-18 14:03:19.895 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [140439745844496] Unexpected exception
Traceback (most recent call last):
File "/config/custom_components/spotifyplus/media_player.py", line 265, in wrapper
result = func(self, *args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/spotifyplus/media_player.py", line 656, in media_play
self.data.spotifyClient.PlayerMediaResume()
File "/usr/local/lib/python3.12/site-packages/spotifywebapipython/spotifyclient.py", line 11377, in PlayerMediaResume
self.MakeRequest('PUT', msg)
File "/usr/local/lib/python3.12/site-packages/spotifywebapipython/spotifyclient.py", line 807, in MakeRequest
msg.ResponseData = self._CheckResponseForErrors(msg, response)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/spotifywebapipython/spotifyclient.py", line 611, in _CheckResponseForErrors
raise SpotifyWebApiError(errCode, errMessage, msg.MethodName, response.reason, _logsi)
spotifywebapipython.spotifywebapierror.SpotifyWebApiError: SAM1001E - Spotify Web API returned an error status while processing the "PlayerMediaResume" method.
Status: 404 - Not Found
Message: "Player command failed: No active device found"
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/components/websocket_api/commands.py", line 245, in handle_call_service
response = await hass.services.async_call(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/core.py", line 2761, in async_call
response_data = await coro
^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/core.py", line 2804, in _execute_service
return await target(service_call)
^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 996, in entity_service_call
single_response = await _handle_entity_call(
^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 1068, in _handle_entity_call
result = await task
^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/media_player/init.py", line 826, in async_media_play
await self.hass.async_add_executor_job(self.media_play)
File "/usr/local/lib/python3.12/concurrent/futures/thread.py", line 58, in run
result = self.fn(*self.args, **self.kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/spotifyplus/media_player.py", line 279, in wrapper
raise HomeAssistantError(ex.Message)
homeassistant.exceptions.HomeAssistantError: Player command failed: No active device found
2024-10-18 14:03:20.112 DEBUG (SyncWorker_6) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Transferring playback to target device name: 'Salon (29254b4896dbcc7c5b632f4bddd5fd5104a045c9)'
2024-10-18 14:03:20.112 DEBUG (SyncWorker_6) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Target device is a Sonos device; creating SoCo Controller instance for Sonos device '<IP_ADDRESS>' ('Salon')
2024-10-18 14:03:20.127 DEBUG (SyncWorker_6) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Sonos device '<IP_ADDRESS>' ('Salon') music source: 'WEB_FILE'
2024-10-18 14:03:20.127 DEBUG (SyncWorker_6) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Activating Spotify Connect music source on Sonos device '<IP_ADDRESS>' ('Salon')
2024-10-18 14:03:20.157 DEBUG (SyncWorker_6) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Sonos device '<IP_ADDRESS>' ('Salon') music source (after activation): 'WEB_FILE'
2024-10-18 14:03:20.169 DEBUG (SyncWorker_6) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Sonos device '<IP_ADDRESS>' ('Salon') current_transport_state (before activation transfer): 'PAUSED_PLAYBACK' (Status=OK)
2024-10-18 14:03:20.170 DEBUG (SyncWorker_6) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Spotify Web API PlayerState Item reference not set (nothing is playing)
2024-10-18 14:03:20.170 DEBUG (SyncWorker_6) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Issuing command to Sonos device '<IP_ADDRESS>' ('Salon'): PLAY
2024-10-18 14:03:20.192 DEBUG (SyncWorker_6) [custom_components.spotifyplus] Delaying for 0.5 seconds to allow Sonos Soco API to process the change
2024-10-18 14:03:20.692 DEBUG (SyncWorker_6) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Getting Spotify Connect Player state
2024-10-18 14:03:20.692 DEBUG (SyncWorker_6) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Currently selected Source: 'None'
2024-10-18 14:03:20.733 DEBUG (SyncWorker_6) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Selected source was changed to: 'Salon'
2024-10-18 14:03:20.733 DEBUG (SyncWorker_6) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Processed a transfer playback command - forcing a playerState scan window for the next 5 updates
2024-10-18 14:03:20.733 DEBUG (SyncWorker_6) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Selected source was changed to: 'Salon'
2024-10-18 14:03:20.733 DEBUG (SyncWorker_6) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Processed a media player command - forcing a playerState scan window for the next 5 updates
2024-10-18 14:03:20.738 DEBUG (SyncWorker_3) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Scan interval 30 check - commandScanInterval=6, currentScanInterval=20, lastKnownTimeRemainingSeconds=0, state=playing
2024-10-18 14:03:20.738 DEBUG (SyncWorker_3) [custom_components.spotifyplus] 'SpotifyPlus John Doe': update method - getting Spotify Connect Player state
2024-10-18 14:03:20.738 DEBUG (SyncWorker_3) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Getting Spotify Connect Player state
2024-10-18 14:03:20.739 DEBUG (SyncWorker_3) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Currently selected Source: 'Salon'
2024-10-18 14:03:20.802 DEBUG (SyncWorker_3) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Sonos device detected; setting Sonos Control API reference for Sonos device '<IP_ADDRESS>' ('Salon')
2024-10-18 14:03:20.802 DEBUG (SyncWorker_3) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Getting Sonos device status via Sonos Control API for device: '<IP_ADDRESS>' ('Salon')
2024-10-18 14:03:20.836 DEBUG (SyncWorker_3) [custom_components.spotifyplus] 'SpotifyPlus John Doe': MediaPlayerState set to 'playing'
2024-10-18 14:03:21.800 DEBUG (SyncWorker_7) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Scan interval 30 check - commandScanInterval=5, currentScanInterval=29, lastKnownTimeRemainingSeconds=0, state=playing
2024-10-18 14:03:21.800 DEBUG (SyncWorker_7) [custom_components.spotifyplus] 'SpotifyPlus John Doe': update method - getting Spotify Connect Player state
2024-10-18 14:03:21.801 DEBUG (SyncWorker_7) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Getting Spotify Connect Player state
2024-10-18 14:03:21.801 DEBUG (SyncWorker_7) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Currently selected Source: 'Salon'
2024-10-18 14:03:21.852 DEBUG (SyncWorker_7) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Sonos device detected; setting Sonos Control API reference for Sonos device '<IP_ADDRESS>' ('Salon')
2024-10-18 14:03:21.852 DEBUG (SyncWorker_7) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Getting Sonos device status via Sonos Control API for device: '<IP_ADDRESS>' ('Salon')
2024-10-18 14:03:21.908 DEBUG (SyncWorker_7) [custom_components.spotifyplus] 'SpotifyPlus John Doe': MediaPlayerState set to 'playing'
2024-10-18 14:03:22.802 DEBUG (SyncWorker_11) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Scan interval 30 check - commandScanInterval=4, currentScanInterval=29, lastKnownTimeRemainingSeconds=0, state=playing
2024-10-18 14:03:22.802 DEBUG (SyncWorker_11) [custom_components.spotifyplus] 'SpotifyPlus John Doe': update method - getting Spotify Connect Player state
2024-10-18 14:03:22.802 DEBUG (SyncWorker_11) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Getting Spotify Connect Player state
2024-10-18 14:03:22.802 DEBUG (SyncWorker_11) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Currently selected Source: 'Salon'
2024-10-18 14:03:22.842 DEBUG (SyncWorker_11) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Sonos device detected; setting Sonos Control API reference for Sonos device '<IP_ADDRESS>' ('Salon')
2024-10-18 14:03:22.842 DEBUG (SyncWorker_11) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Getting Sonos device status via Sonos Control API for device: '<IP_ADDRESS>' ('Salon')
2024-10-18 14:03:22.873 DEBUG (SyncWorker_11) [custom_components.spotifyplus] 'SpotifyPlus John Doe': MediaPlayerState set to 'playing'
2024-10-18 14:03:22.897 DEBUG (SyncWorker_5) [custom_components.spotifyplus] 'SpotifyPlus John Doe': MediaPlayer is executing service 'media_pause'
2024-10-18 14:03:22.898 DEBUG (SyncWorker_5) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Issuing command to Sonos device '<IP_ADDRESS>' ('Salon'): PAUSE
2024-10-18 14:03:22.944 DEBUG (SyncWorker_5) [custom_components.spotifyplus] Delaying for 0.5 seconds to allow Sonos Soco API to process the change
2024-10-18 14:03:23.444 DEBUG (SyncWorker_5) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Processed a media player command - forcing a playerState scan window for the next 5 updates
2024-10-18 14:03:23.446 DEBUG (SyncWorker_0) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Scan interval 30 check - commandScanInterval=6, currentScanInterval=29, lastKnownTimeRemainingSeconds=0, state=paused
2024-10-18 14:03:23.447 DEBUG (SyncWorker_0) [custom_components.spotifyplus] 'SpotifyPlus John Doe': update method - getting Spotify Connect Player state
2024-10-18 14:03:23.447 DEBUG (SyncWorker_0) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Getting Spotify Connect Player state
2024-10-18 14:03:23.447 DEBUG (SyncWorker_0) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Currently selected Source: 'Salon'
2024-10-18 14:03:23.500 DEBUG (SyncWorker_0) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Sonos device detected; setting Sonos Control API reference for Sonos device '<IP_ADDRESS>' ('Salon')
2024-10-18 14:03:23.500 DEBUG (SyncWorker_0) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Getting Sonos device status via Sonos Control API for device: '<IP_ADDRESS>' ('Salon')
2024-10-18 14:03:23.541 DEBUG (SyncWorker_0) [custom_components.spotifyplus] 'SpotifyPlus John Doe': MediaPlayerState set to 'paused'
2024-10-18 14:03:23.772 DEBUG (MainThread) [custom_components.spotifyplus] 'SpotifyPlus John Doe': MediaPlayer is browsing main media library index content id 'None'
2024-10-18 14:03:23.803 DEBUG (SyncWorker_1) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Scan interval 30 check - commandScanInterval=5, currentScanInterval=29, lastKnownTimeRemainingSeconds=0, state=paused
2024-10-18 14:03:23.803 DEBUG (SyncWorker_1) [custom_components.spotifyplus] 'SpotifyPlus John Doe': update method - getting Spotify Connect Player state
2024-10-18 14:03:23.803 DEBUG (SyncWorker_1) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Getting Spotify Connect Player state
2024-10-18 14:03:23.803 DEBUG (SyncWorker_1) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Currently selected Source: 'Salon'
2024-10-18 14:03:23.854 DEBUG (SyncWorker_1) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Sonos device detected; setting Sonos Control API reference for Sonos device '<IP_ADDRESS>' ('Salon')
2024-10-18 14:03:23.854 DEBUG (SyncWorker_1) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Getting Sonos device status via Sonos Control API for device: '<IP_ADDRESS>' ('Salon')
2024-10-18 14:03:23.891 DEBUG (SyncWorker_1) [custom_components.spotifyplus] 'SpotifyPlus John Doe': MediaPlayerState set to 'paused'
2024-10-18 14:03:24.803 DEBUG (SyncWorker_10) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Scan interval 30 check - commandScanInterval=4, currentScanInterval=29, lastKnownTimeRemainingSeconds=0, state=paused
2024-10-18 14:03:24.804 DEBUG (SyncWorker_10) [custom_components.spotifyplus] 'SpotifyPlus John Doe': update method - getting Spotify Connect Player state
2024-10-18 14:03:24.804 DEBUG (SyncWorker_10) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Getting Spotify Connect Player state
2024-10-18 14:03:24.804 DEBUG (SyncWorker_10) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Currently selected Source: 'Salon'
2024-10-18 14:03:24.851 DEBUG (SyncWorker_10) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Sonos device detected; setting Sonos Control API reference for Sonos device '<IP_ADDRESS>' ('Salon')
2024-10-18 14:03:24.851 DEBUG (SyncWorker_10) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Getting Sonos device status via Sonos Control API for device: '<IP_ADDRESS>' ('Salon')
2024-10-18 14:03:24.882 DEBUG (SyncWorker_10) [custom_components.spotifyplus] 'SpotifyPlus John Doe': MediaPlayerState set to 'paused'
2024-10-18 14:03:24.977 DEBUG (MainThread) [custom_components.spotifyplus] 'SpotifyPlus John Doe': MediaPlayer is browsing media node content id 'spotify_user_playlists'
2024-10-18 14:03:24.981 DEBUG (SyncWorker_9) [custom_components.spotifyplus.browse_media] 'SpotifyPlus John Doe': querying spotify for Playlist Favorites
2024-10-18 14:03:25.805 DEBUG (SyncWorker_4) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Scan interval 30 check - commandScanInterval=3, currentScanInterval=29, lastKnownTimeRemainingSeconds=0, state=paused
2024-10-18 14:03:25.805 DEBUG (SyncWorker_4) [custom_components.spotifyplus] 'SpotifyPlus John Doe': update method - getting Spotify Connect Player state
2024-10-18 14:03:25.805 DEBUG (SyncWorker_4) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Getting Spotify Connect Player state
2024-10-18 14:03:25.805 DEBUG (SyncWorker_4) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Currently selected Source: 'Salon'
2024-10-18 14:03:25.855 DEBUG (SyncWorker_4) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Sonos device detected; setting Sonos Control API reference for Sonos device '<IP_ADDRESS>' ('Salon')
2024-10-18 14:03:25.855 DEBUG (SyncWorker_4) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Getting Sonos device status via Sonos Control API for device: '<IP_ADDRESS>' ('Salon')
2024-10-18 14:03:25.898 DEBUG (SyncWorker_4) [custom_components.spotifyplus] 'SpotifyPlus John Doe': MediaPlayerState set to 'paused'
2024-10-18 14:03:26.631 DEBUG (SyncWorker_6) [custom_components.spotifyplus] Playing via PlayerMediaPlayContext: contextUri='spotify:playlist:1h8McMFTTNvrffm6nquUDZ', deviceId='Salon'
2024-10-18 14:03:26.632 DEBUG (SyncWorker_6) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Issuing command to Sonos device '<IP_ADDRESS>' ('Salon'): CLEAR_QUEUE
2024-10-18 14:03:26.649 DEBUG (SyncWorker_6) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Issuing command to Sonos device '<IP_ADDRESS>' ('Salon'): ADD_SHARE_LINK_TO_QUEUE (uri=spotify:playlist:1h8McMFTTNvrffm6nquUDZ)
2024-10-18 14:03:26.805 DEBUG (SyncWorker_3) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Update - Integration is in a command event; bypassing update
2024-10-18 14:03:26.909 ERROR (SyncWorker_6) [custom_components.spotifyplus] UPnP Error 800 received:  from <IP_ADDRESS>
Traceback (most recent call last):
File "/config/custom_components/spotifyplus/media_player.py", line 265, in wrapper
result = func(self, *args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/spotifyplus/media_player.py", line 4529, in service_spotify_player_media_play_context
sharelink.add_share_link_to_queue(uri)
File "/usr/local/lib/python3.12/site-packages/soco/plugins/sharelink.py", line 279, in add_share_link_to_queue
raise fault
File "/usr/local/lib/python3.12/site-packages/soco/plugins/sharelink.py", line 261, in add_share_link_to_queue
response = self.soco.avTransport.AddURIToQueue(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/soco/services.py", line 207, in _dispatcher
return self.send_command(action, *args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/soco/services.py", line 515, in send_command
self.handle_upnp_error(response.text)
File "/usr/local/lib/python3.12/site-packages/soco/services.py", line 571, in handle_upnp_error
raise SoCoUPnPException(
soco.exceptions.SoCoUPnPException: UPnP Error 800 received:  from <IP_ADDRESS>
2024-10-18 14:03:26.912 DEBUG (SyncWorker_6) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Processed a media player command - forcing a playerState scan window for the next 5 updates
2024-10-18 14:03:26.912 DEBUG (SyncWorker_6) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Processed a media player command - forcing a playerState scan window for the next 5 updates
2024-10-18 14:03:26.916 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [140439745844496] Unexpected exception
Traceback (most recent call last):
File "/config/custom_components/spotifyplus/media_player.py", line 265, in wrapper
result = func(self, *args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/spotifyplus/media_player.py", line 4529, in service_spotify_player_media_play_context
sharelink.add_share_link_to_queue(uri)
File "/usr/local/lib/python3.12/site-packages/soco/plugins/sharelink.py", line 279, in add_share_link_to_queue
raise fault
File "/usr/local/lib/python3.12/site-packages/soco/plugins/sharelink.py", line 261, in add_share_link_to_queue
response = self.soco.avTransport.AddURIToQueue(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/soco/services.py", line 207, in _dispatcher
return self.send_command(action, *args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/soco/services.py", line 515, in send_command
self.handle_upnp_error(response.text)
File "/usr/local/lib/python3.12/site-packages/soco/services.py", line 571, in handle_upnp_error
raise SoCoUPnPException(
soco.exceptions.SoCoUPnPException: UPnP Error 800 received:  from <IP_ADDRESS>
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/components/websocket_api/commands.py", line 245, in handle_call_service
response = await hass.services.async_call(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/core.py", line 2761, in async_call
response_data = await coro
^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/core.py", line 2804, in _execute_service
return await target(service_call)
^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 996, in entity_service_call
single_response = await _handle_entity_call(
^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 1068, in _handle_entity_call
result = await task
^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/media_player/init.py", line 878, in async_play_media
await self.hass.async_add_executor_job(
File "/usr/local/lib/python3.12/concurrent/futures/thread.py", line 58, in run
result = self.fn(*self.args, **self.kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/spotifyplus/media_player.py", line 265, in wrapper
result = func(self, *args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/spotifyplus/media_player.py", line 844, in play_media
self.service_spotify_player_media_play_context(media_id, deviceId=deviceId)
File "/config/custom_components/spotifyplus/media_player.py", line 282, in wrapper
raise HomeAssistantError(str(ex)) from ex
homeassistant.exceptions.HomeAssistantError: UPnP Error 800 received:  from <IP_ADDRESS>
2024-10-18 14:03:27.806 DEBUG (SyncWorker_7) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Scan interval 30 check - commandScanInterval=6, currentScanInterval=29, lastKnownTimeRemainingSeconds=0, state=playing
2024-10-18 14:03:27.807 DEBUG (SyncWorker_7) [custom_components.spotifyplus] 'SpotifyPlus John Doe': update method - getting Spotify Connect Player state
2024-10-18 14:03:27.807 DEBUG (SyncWorker_7) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Getting Spotify Connect Player state
2024-10-18 14:03:27.807 DEBUG (SyncWorker_7) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Currently selected Source: 'Salon'
2024-10-18 14:03:27.850 DEBUG (SyncWorker_7) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Sonos device detected; setting Sonos Control API reference for Sonos device '<IP_ADDRESS>' ('Salon')
2024-10-18 14:03:27.850 DEBUG (SyncWorker_7) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Getting Sonos device status via Sonos Control API for device: '<IP_ADDRESS>' ('Salon')
2024-10-18 14:03:27.887 DEBUG (SyncWorker_7) [custom_components.spotifyplus] 'SpotifyPlus John Doe': MediaPlayerState set to 'paused'
2024-10-18 14:03:28.128 ERROR (SyncWorker_11) [homeassistant.components.influxdb] Cannot connect to InfluxDB due to 'HTTPConnectionPool(host='a0d7b954-influxdb', port=8086): Max retries exceeded with url: /write?db=homeassistant (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7fba863e2180>: Failed to establish a new connection: [Errno -5] Name has no usable address'))'. Please check that the provided connection details (host, port, etc.) are correct and that your InfluxDB server is running and accessible. Retrying in 60 seconds.
2024-10-18 14:03:28.808 DEBUG (SyncWorker_8) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Scan interval 30 check - commandScanInterval=5, currentScanInterval=29, lastKnownTimeRemainingSeconds=0, state=paused
2024-10-18 14:03:28.808 DEBUG (SyncWorker_8) [custom_components.spotifyplus] 'SpotifyPlus John Doe': update method - getting Spotify Connect Player state
2024-10-18 14:03:28.808 DEBUG (SyncWorker_8) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Getting Spotify Connect Player state
2024-10-18 14:03:28.808 DEBUG (SyncWorker_8) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Currently selected Source: 'Salon'
2024-10-18 14:03:28.853 DEBUG (SyncWorker_8) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Sonos device detected; setting Sonos Control API reference for Sonos device '<IP_ADDRESS>' ('Salon')
2024-10-18 14:03:28.854 DEBUG (SyncWorker_8) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Getting Sonos device status via Sonos Control API for device: '<IP_ADDRESS>' ('Salon')
2024-10-18 14:03:28.895 DEBUG (SyncWorker_8) [custom_components.spotifyplus] 'SpotifyPlus John Doe': MediaPlayerState set to 'paused'
2024-10-18 14:03:29.808 DEBUG (SyncWorker_5) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Scan interval 30 check - commandScanInterval=4, currentScanInterval=29, lastKnownTimeRemainingSeconds=0, state=paused
2024-10-18 14:03:29.808 DEBUG (SyncWorker_5) [custom_components.spotifyplus] 'SpotifyPlus John Doe': update method - getting Spotify Connect Player state
2024-10-18 14:03:29.808 DEBUG (SyncWorker_5) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Getting Spotify Connect Player state
2024-10-18 14:03:29.809 DEBUG (SyncWorker_5) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Currently selected Source: 'Salon'
2024-10-18 14:03:29.852 DEBUG (SyncWorker_5) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Sonos device detected; setting Sonos Control API reference for Sonos device '<IP_ADDRESS>' ('Salon')
2024-10-18 14:03:29.853 DEBUG (SyncWorker_5) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Getting Sonos device status via Sonos Control API for device: '<IP_ADDRESS>' ('Salon')
2024-10-18 14:03:29.893 DEBUG (SyncWorker_5) [custom_components.spotifyplus] 'SpotifyPlus John Doe': MediaPlayerState set to 'paused'
2024-10-18 14:03:30.809 DEBUG (SyncWorker_2) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Scan interval 30 check - commandScanInterval=3, currentScanInterval=29, lastKnownTimeRemainingSeconds=0, state=paused
2024-10-18 14:03:30.809 DEBUG (SyncWorker_2) [custom_components.spotifyplus] 'SpotifyPlus John Doe': update method - getting Spotify Connect Player state
2024-10-18 14:03:30.810 DEBUG (SyncWorker_2) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Getting Spotify Connect Player state
2024-10-18 14:03:30.810 DEBUG (SyncWorker_2) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Currently selected Source: 'Salon'
2024-10-18 14:03:30.854 DEBUG (SyncWorker_2) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Sonos device detected; setting Sonos Control API reference for Sonos device '<IP_ADDRESS>' ('Salon')
2024-10-18 14:03:30.854 DEBUG (SyncWorker_2) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Getting Sonos device status via Sonos Control API for device: '<IP_ADDRESS>' ('Salon')
2024-10-18 14:03:30.886 DEBUG (SyncWorker_2) [custom_components.spotifyplus] 'SpotifyPlus John Doe': MediaPlayerState set to 'paused'
2024-10-18 14:03:31.810 DEBUG (SyncWorker_1) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Scan interval 30 check - commandScanInterval=2, currentScanInterval=29, lastKnownTimeRemainingSeconds=0, state=paused
2024-10-18 14:03:31.810 DEBUG (SyncWorker_1) [custom_components.spotifyplus] 'SpotifyPlus John Doe': update method - getting Spotify Connect Player state
2024-10-18 14:03:31.810 DEBUG (SyncWorker_1) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Getting Spotify Connect Player state
2024-10-18 14:03:31.810 DEBUG (SyncWorker_1) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Currently selected Source: 'Salon'
2024-10-18 14:03:31.867 DEBUG (SyncWorker_1) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Sonos device detected; setting Sonos Control API reference for Sonos device '<IP_ADDRESS>' ('Salon')
2024-10-18 14:03:31.868 DEBUG (SyncWorker_1) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Getting Sonos device status via Sonos Control API for device: '<IP_ADDRESS>' ('Salon')
2024-10-18 14:03:31.906 DEBUG (SyncWorker_1) [custom_components.spotifyplus] 'SpotifyPlus John Doe': MediaPlayerState set to 'paused'
2024-10-18 14:03:32.810 DEBUG (SyncWorker_6) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Scan interval 30 check - commandScanInterval=1, currentScanInterval=29, lastKnownTimeRemainingSeconds=0, state=paused
2024-10-18 14:03:33.811 DEBUG (SyncWorker_11) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Scan interval 30 check - commandScanInterval=0, currentScanInterval=28, lastKnownTimeRemainingSeconds=0, state=paused
2024-10-18 14:03:34.811 DEBUG (SyncWorker_2) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Scan interval 30 check - commandScanInterval=0, currentScanInterval=27, lastKnownTimeRemainingSeconds=0, state=paused
2024-10-18 14:03:35.812 DEBUG (SyncWorker_5) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Scan interval 30 check - commandScanInterval=0, currentScanInterval=26, lastKnownTimeRemainingSeconds=0, state=paused
2024-10-18 14:03:36.813 DEBUG (SyncWorker_1) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Scan interval 30 check - commandScanInterval=0, currentScanInterval=25, lastKnownTimeRemainingSeconds=0, state=paused
2024-10-18 14:03:37.814 DEBUG (SyncWorker_6) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Scan interval 30 check - commandScanInterval=0, currentScanInterval=24, lastKnownTimeRemainingSeconds=0, state=paused
2024-10-18 14:03:38.814 DEBUG (SyncWorker_11) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Scan interval 30 check - commandScanInterval=0, currentScanInterval=23, lastKnownTimeRemainingSeconds=0, state=paused
2024-10-18 14:03:39.815 DEBUG (SyncWorker_9) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Scan interval 30 check - commandScanInterval=0, currentScanInterval=22, lastKnownTimeRemainingSeconds=0, state=paused
2024-10-18 14:03:40.817 DEBUG (SyncWorker_5) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Scan interval 30 check - commandScanInterval=0, currentScanInterval=21, lastKnownTimeRemainingSeconds=0, state=paused
2024-10-18 14:03:41.818 DEBUG (SyncWorker_1) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Scan interval 30 check - commandScanInterval=0, currentScanInterval=20, lastKnownTimeRemainingSeconds=0, state=paused
2024-10-18 14:03:42.819 DEBUG (SyncWorker_6) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Scan interval 30 check - commandScanInterval=0, currentScanInterval=19, lastKnownTimeRemainingSeconds=0, state=paused
2024-10-18 14:03:43.820 DEBUG (SyncWorker_5) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Scan interval 30 check - commandScanInterval=0, currentScanInterval=18, lastKnownTimeRemainingSeconds=0, state=paused
2024-10-18 14:03:44.820 DEBUG (SyncWorker_4) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Scan interval 30 check - commandScanInterval=0, currentScanInterval=17, lastKnownTimeRemainingSeconds=0, state=paused
2024-10-18 14:03:45.821 DEBUG (SyncWorker_7) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Scan interval 30 check - commandScanInterval=0, currentScanInterval=16, lastKnownTimeRemainingSeconds=0, state=paused
2024-10-18 14:03:46.822 DEBUG (SyncWorker_9) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Scan interval 30 check - commandScanInterval=0, currentScanInterval=15, lastKnownTimeRemainingSeconds=0, state=paused
2024-10-18 14:03:47.823 DEBUG (SyncWorker_11) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Scan interval 30 check - commandScanInterval=0, currentScanInterval=14, lastKnownTimeRemainingSeconds=0, state=paused
2024-10-18 14:03:48.824 DEBUG (SyncWorker_4) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Scan interval 30 check - commandScanInterval=0, currentScanInterval=13, lastKnownTimeRemainingSeconds=0, state=paused
2024-10-18 14:03:49.825 DEBUG (SyncWorker_7) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Scan interval 30 check - commandScanInterval=0, currentScanInterval=12, lastKnownTimeRemainingSeconds=0, state=paused
2024-10-18 14:03:50.826 DEBUG (SyncWorker_3) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Scan interval 30 check - commandScanInterval=0, currentScanInterval=11, lastKnownTimeRemainingSeconds=0, state=paused
2024-10-18 14:03:51.827 DEBUG (SyncWorker_9) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Scan interval 30 check - commandScanInterval=0, currentScanInterval=10, lastKnownTimeRemainingSeconds=0, state=paused
2024-10-18 14:03:52.829 DEBUG (SyncWorker_11) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Scan interval 30 check - commandScanInterval=0, currentScanInterval=9, lastKnownTimeRemainingSeconds=0, state=paused
2024-10-18 14:03:53.830 DEBUG (SyncWorker_7) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Scan interval 30 check - commandScanInterval=0, currentScanInterval=8, lastKnownTimeRemainingSeconds=0, state=paused
2024-10-18 14:03:54.831 DEBUG (SyncWorker_0) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Scan interval 30 check - commandScanInterval=0, currentScanInterval=7, lastKnownTimeRemainingSeconds=0, state=paused
2024-10-18 14:03:55.832 DEBUG (SyncWorker_9) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Scan interval 30 check - commandScanInterval=0, currentScanInterval=6, lastKnownTimeRemainingSeconds=0, state=paused
2024-10-18 14:03:56.823 ERROR (MainThread) [hole] Can not load data from *hole: <IP_ADDRESS>:3030
2024-10-18 14:03:56.832 DEBUG (SyncWorker_11) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Scan interval 30 check - commandScanInterval=0, currentScanInterval=5, lastKnownTimeRemainingSeconds=0, state=paused
2024-10-18 14:03:57.833 DEBUG (SyncWorker_1) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Scan interval 30 check - commandScanInterval=0, currentScanInterval=4, lastKnownTimeRemainingSeconds=0, state=paused
2024-10-18 14:03:58.834 DEBUG (SyncWorker_6) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Scan interval 30 check - commandScanInterval=0, currentScanInterval=3, lastKnownTimeRemainingSeconds=0, state=paused
2024-10-18 14:03:59.835 DEBUG (SyncWorker_10) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Scan interval 30 check - commandScanInterval=0, currentScanInterval=2, lastKnownTimeRemainingSeconds=0, state=paused
2024-10-18 14:04:00.835 DEBUG (SyncWorker_8) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Scan interval 30 check - commandScanInterval=0, currentScanInterval=1, lastKnownTimeRemainingSeconds=0, state=paused
2024-10-18 14:04:00.836 DEBUG (SyncWorker_8) [custom_components.spotifyplus] 'SpotifyPlus John Doe': update method - getting Spotify Connect Player state
2024-10-18 14:04:00.836 DEBUG (SyncWorker_8) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Getting Spotify Connect Player state
2024-10-18 14:04:00.836 DEBUG (SyncWorker_8) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Currently selected Source: 'Salon'
2024-10-18 14:04:00.881 DEBUG (SyncWorker_8) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Sonos device detected; setting Sonos Control API reference for Sonos device '<IP_ADDRESS>' ('Salon')
2024-10-18 14:04:00.881 DEBUG (SyncWorker_8) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Getting Sonos device status via Sonos Control API for device: '<IP_ADDRESS>' ('Salon')
2024-10-18 14:04:00.913 DEBUG (SyncWorker_8) [custom_components.spotifyplus] 'SpotifyPlus John Doe': MediaPlayerState set to 'paused'
2024-10-18 14:04:01.836 DEBUG (SyncWorker_1) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Scan interval 30 check - commandScanInterval=0, currentScanInterval=29, lastKnownTimeRemainingSeconds=0, state=paused
2024-10-18 14:04:02.837 DEBUG (SyncWorker_6) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Scan interval 30 check - commandScanInterval=0, currentScanInterval=28, lastKnownTimeRemainingSeconds=0, state=paused
2024-10-18 14:04:02.932 DEBUG (SyncWorker_7) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Getting Spotify Connect Player state
2024-10-18 14:04:02.933 DEBUG (SyncWorker_7) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Currently selected Source: 'Salon'
2024-10-18 14:04:02.987 DEBUG (SyncWorker_7) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Sonos device detected; setting Sonos Control API reference for Sonos device '<IP_ADDRESS>' ('Salon')
2024-10-18 14:04:02.988 DEBUG (SyncWorker_7) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Getting Sonos device status via Sonos Control API for device: '<IP_ADDRESS>' ('Salon')
2024-10-18 14:04:03.034 DEBUG (SyncWorker_7) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Transferring playback from source device name: 'Salon' (id=29254b4896dbcc7c5b632f4bddd5fd5104a045c9)
2024-10-18 14:04:03.034 DEBUG (SyncWorker_7) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Sonos device is active; issuing command to PAUSE Sonos player name 'Salon'
2024-10-18 14:04:03.047 DEBUG (SyncWorker_7) [custom_components.spotifyplus] Delaying for 0.5 seconds to allow Sonos Soco API to process the change
2024-10-18 14:04:03.838 DEBUG (SyncWorker_11) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Update - Integration is in a command event; bypassing update
2024-10-18 14:04:04.252 DEBUG (SyncWorker_5) [custom_components.spotifyplus] 'SpotifyPlus John Doe': MediaPlayer is executing service 'media_play'
2024-10-18 14:04:04.253 DEBUG (SyncWorker_5) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Issuing command to Sonos device '<IP_ADDRESS>' ('Salon'): PLAY
2024-10-18 14:04:04.288 DEBUG (SyncWorker_5) [custom_components.spotifyplus] Delaying for 0.5 seconds to allow Sonos Soco API to process the change
2024-10-18 14:04:04.788 DEBUG (SyncWorker_5) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Processed a media player command - forcing a playerState scan window for the next 5 updates
2024-10-18 14:04:04.791 DEBUG (SyncWorker_4) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Scan interval 30 check - commandScanInterval=6, currentScanInterval=27, lastKnownTimeRemainingSeconds=0, state=playing
2024-10-18 14:04:04.791 DEBUG (SyncWorker_4) [custom_components.spotifyplus] 'SpotifyPlus John Doe': update method - getting Spotify Connect Player state
2024-10-18 14:04:04.791 DEBUG (SyncWorker_4) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Getting Spotify Connect Player state
2024-10-18 14:04:04.792 DEBUG (SyncWorker_4) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Currently selected Source: 'Salon'
2024-10-18 14:04:04.838 DEBUG (SyncWorker_4) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Sonos device detected; setting Sonos Control API reference for Sonos device '<IP_ADDRESS>' ('Salon')
2024-10-18 14:04:04.838 DEBUG (SyncWorker_4) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Getting Sonos device status via Sonos Control API for device: '<IP_ADDRESS>' ('Salon')
2024-10-18 14:04:04.888 DEBUG (SyncWorker_4) [custom_components.spotifyplus] 'SpotifyPlus John Doe': MediaPlayerState set to 'playing'
2024-10-18 14:04:05.119 DEBUG (SyncWorker_8) [custom_components.spotifyplus] 'SpotifyPlus John Doe': MediaPlayer is executing service 'media_pause'
2024-10-18 14:04:05.120 DEBUG (SyncWorker_8) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Issuing command to Sonos device '<IP_ADDRESS>' ('Salon'): PAUSE
2024-10-18 14:04:05.148 DEBUG (SyncWorker_8) [custom_components.spotifyplus] Delaying for 0.5 seconds to allow Sonos Soco API to process the change
2024-10-18 14:04:05.653 DEBUG (SyncWorker_8) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Processed a media player command - forcing a playerState scan window for the next 5 updates
2024-10-18 14:04:05.670 DEBUG (SyncWorker_7) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Transferring playback to target device name: 'DESKTOP-G14 (be063b84c3b61e8a63bbf18434aea26cbd71a31a)'
2024-10-18 14:04:05.683 DEBUG (SyncWorker_3) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Scan interval 30 check - commandScanInterval=6, currentScanInterval=29, lastKnownTimeRemainingSeconds=0, state=paused
2024-10-18 14:04:05.683 DEBUG (SyncWorker_3) [custom_components.spotifyplus] 'SpotifyPlus John Doe': update method - getting Spotify Connect Player state
2024-10-18 14:04:05.683 DEBUG (SyncWorker_3) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Getting Spotify Connect Player state
2024-10-18 14:04:05.683 DEBUG (SyncWorker_3) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Currently selected Source: 'Salon'
2024-10-18 14:04:05.865 DEBUG (SyncWorker_3) [custom_components.spotifyplus] 'SpotifyPlus John Doe': MediaPlayerState set to 'paused'
2024-10-18 14:04:05.866 DEBUG (SyncWorker_3) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Source value ('Salon') does not match Spotify Web API player name ('DESKTOP-G14'); using Spotify Web API player name
2024-10-18 14:04:05.866 DEBUG (SyncWorker_3) [custom_components.spotifyplus] 'SpotifyPlus John Doe': playerState track ProgressMS=23332, DurationMS=227735, lastKnownTimeRemainingSeconds=204
2024-10-18 14:04:06.391 DEBUG (SyncWorker_7) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Getting Spotify Connect Player state
2024-10-18 14:04:06.391 DEBUG (SyncWorker_7) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Currently selected Source: 'DESKTOP-G14'
2024-10-18 14:04:06.472 DEBUG (SyncWorker_7) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Selected source was changed to: 'DESKTOP-G14'
2024-10-18 14:04:06.472 DEBUG (SyncWorker_7) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Processed a transfer playback command - forcing a playerState scan window for the next 5 updates
2024-10-18 14:04:06.473 DEBUG (SyncWorker_7) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Selected source was changed to: 'DESKTOP-G14'
2024-10-18 14:04:06.473 DEBUG (SyncWorker_7) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Processed a media player command - forcing a playerState scan window for the next 5 updates
2024-10-18 14:04:06.476 DEBUG (SyncWorker_0) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Scan interval 30 check - commandScanInterval=6, currentScanInterval=29, lastKnownTimeRemainingSeconds=204, state=paused
2024-10-18 14:04:06.476 DEBUG (SyncWorker_0) [custom_components.spotifyplus] 'SpotifyPlus John Doe': update method - getting Spotify Connect Player state
2024-10-18 14:04:06.476 DEBUG (SyncWorker_0) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Getting Spotify Connect Player state
2024-10-18 14:04:06.476 DEBUG (SyncWorker_0) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Currently selected Source: 'DESKTOP-G14'
2024-10-18 14:04:06.574 DEBUG (SyncWorker_0) [custom_components.spotifyplus] 'SpotifyPlus John Doe': MediaPlayerState set to 'paused'
2024-10-18 14:04:06.574 DEBUG (SyncWorker_0) [custom_components.spotifyplus] 'SpotifyPlus John Doe': playerState track ProgressMS=23332, DurationMS=227735, lastKnownTimeRemainingSeconds=204
2024-10-18 14:04:06.842 DEBUG (SyncWorker_11) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Scan interval 30 check - commandScanInterval=5, currentScanInterval=29, lastKnownTimeRemainingSeconds=204, state=paused
2024-10-18 14:04:06.843 DEBUG (SyncWorker_11) [custom_components.spotifyplus] 'SpotifyPlus John Doe': update method - getting Spotify Connect Player state
2024-10-18 14:04:06.843 DEBUG (SyncWorker_11) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Getting Spotify Connect Player state
2024-10-18 14:04:06.843 DEBUG (SyncWorker_11) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Currently selected Source: 'DESKTOP-G14'
2024-10-18 14:04:06.963 DEBUG (SyncWorker_11) [custom_components.spotifyplus] 'SpotifyPlus John Doe': MediaPlayerState set to 'paused'
2024-10-18 14:04:06.963 DEBUG (SyncWorker_11) [custom_components.spotifyplus] 'SpotifyPlus John Doe': playerState track ProgressMS=23332, DurationMS=227735, lastKnownTimeRemainingSeconds=204
2024-10-18 14:04:07.651 DEBUG (SyncWorker_4) [custom_components.spotifyplus] 'SpotifyPlus John Doe': MediaPlayer is executing service 'media_play'
2024-10-18 14:04:07.843 DEBUG (SyncWorker_6) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Update - Integration is in a command event; bypassing update
2024-10-18 14:04:08.525 DEBUG (SyncWorker_4) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Processed a media player command - forcing a playerState scan window for the next 5 updates
2024-10-18 14:04:08.527 DEBUG (SyncWorker_9) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Scan interval 30 check - commandScanInterval=6, currentScanInterval=29, lastKnownTimeRemainingSeconds=204, state=playing
2024-10-18 14:04:08.528 DEBUG (SyncWorker_9) [custom_components.spotifyplus] 'SpotifyPlus John Doe': update method - getting Spotify Connect Player state
2024-10-18 14:04:08.528 DEBUG (SyncWorker_9) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Getting Spotify Connect Player state
2024-10-18 14:04:08.528 DEBUG (SyncWorker_9) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Currently selected Source: 'DESKTOP-G14'
2024-10-18 14:04:08.623 DEBUG (SyncWorker_9) [custom_components.spotifyplus] 'SpotifyPlus John Doe': MediaPlayerState set to 'playing'
2024-10-18 14:04:08.623 DEBUG (SyncWorker_9) [custom_components.spotifyplus] 'SpotifyPlus John Doe': playerState track ProgressMS=24040, DurationMS=227735, lastKnownTimeRemainingSeconds=203
2024-10-18 14:04:08.639 DEBUG (SyncWorker_2) [custom_components.spotifyplus] 'SpotifyPlus John Doe': MediaPlayer is executing service 'media_pause'
2024-10-18 14:04:08.843 DEBUG (SyncWorker_1) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Update - Integration is in a command event; bypassing update
2024-10-18 14:04:09.446 DEBUG (SyncWorker_2) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Processed a media player command - forcing a playerState scan window for the next 5 updates
2024-10-18 14:04:09.449 DEBUG (SyncWorker_8) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Scan interval 30 check - commandScanInterval=6, currentScanInterval=29, lastKnownTimeRemainingSeconds=203, state=paused
2024-10-18 14:04:09.449 DEBUG (SyncWorker_8) [custom_components.spotifyplus] 'SpotifyPlus John Doe': update method - getting Spotify Connect Player state
2024-10-18 14:04:09.449 DEBUG (SyncWorker_8) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Getting Spotify Connect Player state
2024-10-18 14:04:09.449 DEBUG (SyncWorker_8) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Currently selected Source: 'DESKTOP-G14'
2024-10-18 14:04:09.539 DEBUG (SyncWorker_8) [custom_components.spotifyplus] 'SpotifyPlus John Doe': MediaPlayerState set to 'paused'
2024-10-18 14:04:09.540 DEBUG (SyncWorker_8) [custom_components.spotifyplus] 'SpotifyPlus John Doe': playerState track ProgressMS=24106, DurationMS=227735, lastKnownTimeRemainingSeconds=203
2024-10-18 14:04:09.844 DEBUG (SyncWorker_4) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Scan interval 30 check - commandScanInterval=5, currentScanInterval=29, lastKnownTimeRemainingSeconds=203, state=paused
2024-10-18 14:04:09.845 DEBUG (SyncWorker_4) [custom_components.spotifyplus] 'SpotifyPlus John Doe': update method - getting Spotify Connect Player state
2024-10-18 14:04:09.845 DEBUG (SyncWorker_4) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Getting Spotify Connect Player state
2024-10-18 14:04:09.845 DEBUG (SyncWorker_4) [custom_components.spotifyplus] 'SpotifyPlus John Doe': Currently selected Source: 'DESKTOP-G14'
2024-10-18 14:04:09.924 DEBUG (SyncWorker_4) [custom_components.spotifyplus] 'SpotifyPlus John Doe': MediaPlayerState set to 'paused'
2024-10-18 14:04:09.924 DEBUG (SyncWorker_4) [custom_components.spotifyplus] 'SpotifyPlus John Doe': playerState track ProgressMS=24106, DurationMS=227735, lastKnownTimeRemainingSeconds=203

@Glohoui
Hi Glo - thanks for reaching out, and your observations on the confusing wiki docs.  I try to be clear and concise in my docs, but sometimes I fail miserably in those attempts.  LOL.  Thanks for bringing these issues to my attention.
I updated the documentation for the Spotify Connect Device LoginId value, making a note that the LoginId and the Username could be the same.  I have noticed that in the past with other support questions, and just forgot to document it.
Regarding the location of the spotifyplus_tokens.json file, it needs to be placed in the Home Assistant /config/.storage location.  Note that this folder could be hidden (for some operating system directory displays) due to the dot prefix.  Use the How to find the HA configuration directory instructions for how to locate the base /config folder, then the .storage folder will be located beneath it.  I will revise the docs to make that more clear.
Now, on to your problem ...
You mentioned "Step 4b - Select Application Credential -> never appeared to me but I don't think this is the issue as spotify works perfectly".  It should have prompted you for the application credential to use when setting up the integration.  SpotifyPlus will require an application credential to be defined (even if the HA Spotify integration does not).  Can you verify that an application credential is assigned for SpotifyPlus?  To do this, go to the HA Application Credentials dialog and see if you have any credentials assigned to SpotifyPlus.  It should look something like this (I have 2 credentials defined, for my 2 Spotify accounts):

I think you have a credential assigned, otherwise you would be having issues selecting a playlist or controlling the player.  But it does not hurt to verify that.
I see a UPnP Error 800 received: from <IP_ADDRESS> error, which indicates that the Sonos App (or something else) may have control of the device.  You will want to make sure that the Sonos App is shut down while you are controlling the device from HA SpotifyPlus media player.  I would also reboot the device, just to make sure it's not in a weird state.  I have only been able to test Sonos functionality using my Ikea Symfonisk device, and I would see these same UPnP Error 800 messages whenever the device gets confused by multiple control sources (e.g. Sonos App, Spotify Mobile App, HA SpotifyPlus media player).  I have found that not using the Sonos App at all works the best.
I would also try to start play on the Sonos Salon device from the official Spotify Desktop / Mobile App (not HA Spotify media player), just to make sure you don't get any UPnP 800 errors.

Was the playlist you are trying to play the Spotify DJ maybe?  There are known issues with trying to play that specific playlist with the Spotify Web API (see SpotifyPlus Sonos Limitations wiki for more information).  I get a UPnP Error 804 received: from 192.168.1.xx on my device as well when trying to play that specific playlist; there may be other "special" playlists out there as well, but that's the only one I have encountered thus far.
It also sounds like your Sonos device is playing content from its local queue instead of Spotify Connect, which can happen if playback cannot be transferred from a Spotify app (desktop / mobile) to SpotifyPlus.  The SpotifyPlus integration transfers play to the Sonos device by issuing a play command via the Sonos SoCo API.  If a Spotify Connect connection could not be established, then a local queue on the Sonos device is built from the Spotify Web API users queue, and a SoCo play command is issued to play the local queue. Note that Sonos playback control is transferred from the SPOTIFY_CONNECT music source to the Sonos device local queue when this happens; the Spotify Connect source is paused after control is transferred to the Sonos local queue. The only way for Spotify Connect to regain control on the Sonos Device is via a Spotify Desktop / Mobile application.
Not sure if that fully explains what is happening in this case, but without the specific Sonos gear that you have it's hard to tell.


Unable to sign in.

I did a fresh install on Arch Linux using the install script, tried both GL and DXVK, installation works fine and fusion launches into the login screen. It redirects me to the browser but when I come back fo fusion it freezes and does nothing until I kill it. Tried both firefox and chromium, also no difference between xorg and wayland sessions.

Also have the exact same issues using Linux Mint.
Login takes me to Firefox, but won't go back to fusion. Fusion then freezes up and will eventually lead to a Force quit prompt, or I manually kill it.

i have added a new issue which i think is duplicate of this one. https://github.com/cryinkfly/Autodesk-Fusion-360-for-Linux/issues/387

Yeah same here on Arch also and I'm using Firefox.

I managed to login thanks to this comment on issue #387 : https://github.com/cryinkfly/Autodesk-Fusion-360-for-Linux/issues/387#issuecomment-1936390044     This now leads me to believe that the default location of adskidmgr has changed (maybe an update pushed by autodesk[?]). All I had to do was to find where this executable is, point wine to it and execute it with the copied login from the sign in page. Also the default .desktop entry for adskmgr is incorrect, this leads me to believe that the whole installation thinks the login manager is somwhere else and fails to execute it, but I may be wrong, I'm just guessing based on what I did.

Same issue with firefox.

I am also having the same issue on Firefox and Chrome. Thanks in advance for your help!

Solved.


Page does not have details to explain how this will be enough

To enable multi-region writes in your application, set ApplicationRegion to the region in which the application is being deployed
The above sentence is there, but it is not clear to me how setting one region in the policy makes it multi region write. And I wonder how a centralized setting at the account level be influenced by the client SDK. It sounds very weird to me that a client can change the setting at the account level. An example with read or write done will help understand

Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: 5feaa520-6f8a-6b30-7cd1-3a85593f758f
Version Independent ID: 2a121426-b973-fa0b-6a09-299193809723
Content: How to configure multi-region writes in Azure Cosmos DB
Content Source: articles/cosmos-db/sql/how-to-multi-master.md
Service: cosmos-db
Sub-service: cosmosdb-sql
GitHub Login: @seesharprun
Microsoft Alias: sidandrews

Hi, @sijucm Thank you for reaching out. We will look into it and update you as appropriate.

@sijucm, the sentence is unclear.
You enable multi-region writes at the account level.
At the application level, you write to a specific region.
The best solution here would be to update the text to say "To take advantage of multi-region writes in your application, set ApplicationRegion to the specific region you want to write to." I'm sure that sentence can be improved with copy editing. Then, the code sample can show an example of writing to a specific region (ex. Web app with instance in West US writes to East US even though that's not the first region on the account).
Would that type of clarification help?

That could help. I still have the question: If at the account level it's
set as multi region write how could a client side override that with a
region? Shouldn't it write in both regions (and probably also
synchronously). Maybe a clarification on when an override will make sense
will clarify the case. The question is why specify a write region.
Would that be okay to add that information. I leave it to you
On Fri, Sep 30, 2022, 17:23 Sidney Andrews @.***> wrote:

@sijucm https://github.com/sijucm, the sentence is unclear.
You enable multi-region writes at the account level.
At the application level, you write to a specific region.
The best solution here would be to update the text to say "To take
advantage of multi-region writes in your application, set
ApplicationRegion to the specific region you want to write to." I'm sure
that sentence can be improved with copy editing. Then, the code sample can
show an example of writing to a specific region (ex. Web app with instance
in West US writes to East US even though that's not the first region on
the account).
Would that type of clarification help?
—
Reply to this email directly, view it on GitHub
https://github.com/MicrosoftDocs/azure-docs/issues/99276#issuecomment-1263713609,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABJBWQMF4V32NGHAF62ANJ3WA4AYJANCNFSM6AAAAAAQZRC74I
.
You are receiving this because you were mentioned.Message ID:
@.***>

So, the client-side setting affects which region the client will try to write to. It doesn't change anything with configuration server-side.
Consider this application
flowchart RL
    webappeastus(["Azure Web App (East US)"])
    webappwestus(["Azure Web App (West US)"])
    cosmoseastus("Replica (East US)")
    cosmoswestus("Replica (West US)")
    webappeastus --> cosmoseastus
    webappwestus --> cosmoswestus
    subgraph cosmos[Azure Cosmos DB]
        cosmoseastus
        cosmoswestus
    end

In the application you deploy to an Azure Web App in West US, you will set the ApplicationRegion setting to point to the West US region. This will ensure that the client doesn't try to "guess" which region it connects to our use some other priority mechanism. This places the application "closer" to the data replica.
In single-write, multiple-read scenarios that it's commonly used to give each globally deployed application good read performance. In multi-write scenarios, you can get the same performance benefit by only writing to the region "close" to your application instance and letting Azure Cosmos DB handle the replication for you behind the scenes.
Does that help?

Sure that helps a lot. Thanks
On Fri, Sep 30, 2022, 21:38 Sidney Andrews @.***> wrote:

So, the client-side setting affects which region the client will try to
write to. It doesn't change anything with configuration server-side.
Consider this application
flowchart RL
webappeastus(["Azure Web App (East US)"])
webappwestus(["Azure Web App (West US)"])
cosmoseastus("Replica (East US)")
cosmoswestus("Replica (West US)")
webappeastus --> cosmoseastus
webappwestus --> cosmoswestus
subgraph cosmos[Azure Cosmos DB]
cosmoseastus
cosmoswestus
end
In the application you deploy to an Azure Web App in West US, you
will set the ApplicationRegion setting to point to the West US region.
This will ensure that the client doesn't try to "guess" which region it
connects to our use some other priority mechanism. This places the
application "closer" to the data replica.
In single-write, multiple-read scenarios that it's commonly used to give
each globally deployed application good read performance. In multi-write
scenarios, you can get the same performance benefit by only writing to the
region "close" to your application instance and letting Azure Cosmos DB
handle the replication for you behind the scenes.
Does that help?
—
Reply to this email directly, view it on GitHub
https://github.com/MicrosoftDocs/azure-docs/issues/99276#issuecomment-1263948668,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABJBWQLGZVE4FHAPFISCWZ3WA46SJANCNFSM6AAAAAAQZRC74I
.
You are receiving this because you were mentioned.Message ID:
@.***>

Hi @sijucm and @seesharprun,
Thanks for your inputs. Closing this thread as per the above discussions.


View Command

Purpose is to repurpose the User command

[X] Add view command (3 variants)
[x] Ensure change in UserProfilePanel upon execution of the view command
[x] Documentation (Less Developer Guide)
[ ] Testing for coverage (Deferred for a seperate PR)

This PR is ready for review!

@mynameizzhafeez I have made changes to the structure as per your recommendation. Please take a look. Thanks!


"Power on/off" switch not working on dishwasher

The problem
The "power on/off" switch does not work for my dishwasher - I got a 400 error in the logs (malformed request according to the API documentation, but unfortunately it has already rotated out by now). I've attached the logs for ”power off", though.
Version of miele integration having the issue?
miele-0.0.17
Version of Home Assistant Core having the issue?
core-2022.3.3
Anything in the logs that might be useful for us?
2022-03-11 23:07:23 DEBUG (MainThread) [custom_components.miele.switch] turn_off -> kwargs: {}
2022-03-11 23:07:23 ERROR (MainThread) [custom_components.miele.switch] Turn_off: 400 - Bad Request

Additional information
No response

There is no easy solution to this problem. The integration is sending the command to the API irrespective of if the API is expected to accept it or not. It is the same thing that happens if you just send the command with Swagger without checking all relevant preconditions.
We can avoid the error message by checking the relevant state and suppress the actual API call if preconditions are not met.
But I am not sure it will be perfect anyway. My freezer and fridge signals that they accept powerOff. The API accepts the command but nothing happens on the device.
I would appreciate if you could catch a diagnostic download on the device just before you toggle the switch so we can see what the API says it will accept in that moment.

I initially thought it's the API state when unsuccessfully trying to switch on the device. I'm less sure now that I've gotten the same error when trying to switch it off. I had switched on the dishwasher by opening the door. I'll try that again with Swagger.

OK, I've experimented with Swagger and it's indeed the API state/device support. Good news is that the actions array does seem to reflect what is actually possible here.
Example when door is open ("switch.power_on" = "on"):
    "actions": {
      "processAction": [],
      "light": [],
      "ambientLight": [],
      "startTime": [],
      "ventilationStep": [],
      "programId": [],
      "targetTemperature": [],
      "deviceName": true,
      "powerOn": false,
      "powerOff": false,
      "colors": [],
      "modes": []
    },

Example of dishwasher programmed with smart start (again, the switch entity is on):
    "actions": {
      "processAction": [],
      "light": [],
      "ambientLight": [],
      "startTime": [],
      "ventilationStep": [],
      "programId": [],
      "targetTemperature": [],
      "deviceName": true,
      "powerOn": false,
      "powerOff": false,
      "colors": [],
      "modes": []
    },

Again, the powerOff action is not available, but two processActions are (start and stop, although weirdly I managed to start the program by tapping stop – which looked like ”cancel” - twice in the app).

I am unsure if switch is the right platform for this and if it wouldn't be better to present a series of button entitities (enabled/disabled depending on actions state).

I agree that buttons are probably better representations of start & stop process actions,
Power on/off is seems to be something else but it is not clear to me what API data we should use as the current state for poweOn. I had to make something up: https://github.com/astrandb/miele/blob/26aec12643fd10508c727bd973b7df4551b6579e/custom_components/miele/switch.py#L177
I will start to work on a button implementation so we test an see what fits best in what situation.
#68

I have pushed a branch "ButtonPlatform". It exposes buttons for Start & Stop according to Miele's capability matrix. No guard yet for availablity as stated in actions. Coming soon...
@mundschenk-at can you test this branch?

Sure! Could you create a "pre-release" from it for easy installation?

I have just merged the added button platform. Buttons for start, stop, powerOn and powerOff are created for our devices for testing purposes.
If you select Redownload in HACS you can download main. That is always the head of main branch which includes all merged changes regardless of if it is released or not.

Ah, sure, I didn't realize main was available in HACS. (Though creating a pre-release from a branch has the benefit you don't have to merge first, that's why I suggested it.)

Mhm, that didn't seem to work, @astrandb. I am at 743db48b7761438d32115c8d37734de0d993dd18, but no button entities have been created.

Odd. It works fine on my development system, but no buttons appear on my production system.  Something is wrong with HACS. I'll be back...

@mundschenk-at Repeated the redownload of main - and then it worked.
Btw I had forgotten how easy it was to make a release from a branch. Will do that next time.

There might be a problem with using the main branch from HACS. I use a github action to pack all relevant files in a zip archive. This action is triggered every time a release is created and I don't know how HACS  will behave if there is no zip file available.

@mundschenk-at v0.0.18-beta1 released.

Logger: homeassistant.components.button
Source: custom_components/miele/button.py:202
Integration: Taste (documentation, issues)
First occurred: 17:19:11 (1 occurrences)
Last logged: 17:19:11

Error while setting up miele platform for button
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 249, in _async_setup_platform
    await asyncio.shield(task)
  File "/config/custom_components/miele/button.py", line 166, in async_setup_entry
    MieleButton(
  File "/config/custom_components/miele/button.py", line 202, in __init__
    self._attr_name = f"{self.coordinator.data[self._ent][self.entity_description.type_key]} {self.entity_description.name}"
KeyError: None

v0.0.18-beta2 is out!

Looking good so far with the washer dryer (which didn't get a switch entity, BTW). The dishwasher is waiting to be unloaded, so I could not try anything there (and it doesn't want to be switched on, as we know).

Looks right for the dishwasher as well, @astrandb.

Sound good!

Sounds good!
I just followed the compatibility matrix - so switch for washer/dryer.
The question to think about is how we should set up the default configuration. In what cases is the switch the best representation and in what cases are buttons better? E. g. a switch is logical for superfreeze on and off in a freezer.

I just followed the compatibility matrix - so no switch for washer/dryer.

The compatibility matrix is incorrect. In fact, it looks like my dishwasher doesn't support powerOn/powerOff whereas the washer-dryer does. (It would also seem unlikely that washer-dryer deviated from both washing machine and tumble dryer.)

The question to think about is how we should set up the default configuration. In what cases is the switch the best representation and in what cases are buttons better? E. g. a switch is logical for superfreeze on and off in a freezer.

Superfreeze sounds logical for a switch, I agree. For devices that really* support powerOn/powerOff a switch might be OK, though state should be inverse of available actions. If that's not possible, buttons are probably better.

Not sure how that could be determined.

I tried to summarize our discussions on the design here: https://github.com/astrandb/miele/wiki
Will do some cleanup in the code and release within a day or two.

With the latest beta, I have both push buttons and switch entities for power on/off. Is that intentional?

The buttons should be inactive!? They are still defined and can be deleted in the UI and they should then disappear for good.
I was too lazy to create procedures for clean up after testing different variants between the beta releases.

No, the work in parallel to the switch entity, i.e. I can switch the washing machine on using the switch entity and switch it off using the button entity (or vice-versa).

(Haven't renamed the power on/off buttons because I assumed they would be gone.)

My mistake. Forgot to remove these buttons before releasing the beta. New version coming soon. You may need to manually remove the stale buttons from the UI though.


made python 2to3 fixes

Made changes as discussed in previous pull request.

Thanks, pull has been merged


Adding a root category gives them a parent_version_id

I added a root category in the administration and saw on database level it has no parent_id which is plausible but it has a parent_version_id. How can a non-existing parent have a version id? I know the logic of version_ids being always the same unless you start to create an alternating version of something but this is confusing. This might impact other parent/child aware entities.

Hi @JoshuaBehrens,
this is currently still a problem which we cannot solve so easily because the \Shopware\Core\Framework\DataAbstractionLayer\FieldSerializer\ReferenceVersionFieldSerializer cannot check if a value is set in the corresponding field.
However, we are aware of the problem and will work out a solution.

Cool to see you guys already working on that one.


cert-sync-tokens: implemented ability to certify data and sync tokens

implemented ability to certify data and sync access_tokens between canisters

Can you explain why all the nft-m stuff (It seems all the streaming media stuff) has been removed?

it's because of the dynamic range is not fit with certificates logic - we need to know and fetch the exact length


Add save/load for the CNN

Admittedly, it took a while until we got some time on our hands to work on this... :)
We should have it done by the end of the week. For now, save/load to JSON will be supported.

Save yes but similar Marshal (from Ruby)
I woul like to export to C.
For example I learn in crystal, test in crystal and when finish create a C file with only one function. All weights, bias etc. are inside C. Only put input data and get output
int shainet(data *input, output...)
{

@fab1an2 saying that here: https://github.com/NeuraLegion/crystal-fann/issues/11 was enough :)
It's a crystal thing, not related to either crystal-fann or SHAInet

sound like uTensor, converter tensorflow to .cpp .h files for embeded in project C
Very interesting


Bug: utils.lua:1192: attempt to index local 'opts' (a nil value)

RTFM Checklist

[X] I have searched exisiting issues / discussions
[ ] I have read the Wiki including the Advanced section
[ ] I have read man fzf / I am well versed in shell fzf

Operating system
Mac
Shell
zsh
Neovim version (nvim --version)
NVIM v0.10.1
Fzf version (fzf --version)
0.51.0 (260a65b)
Output of :lua print(os.getenv('FZF_DEFAULT_OPTS'))
nil
Is the problem reproducible with mini.sh?

[X] My issue is reproducible with mini.sh
[ ] My issue IS NOT reproducible with mini.sh
[ ] I have not tested with mini.sh (not relevant, requires LSP, Windows, etc)

Fzf-lua configuration
require('fzf-lua').setup({
})

Describe the bug / steps to reproduce
:checkhealth gives
E5009: Invalid $VIMRUNTIME: /usr/local/share/nvim/runtime
Error executing lua: function health#fzf_lua#check, line 1: Vim(lua):E5108: Error executing lua ...fwu/.local/share/nvim/lazy/fzf-lua/lua/fzf-lua/utils.lua:1192: attempt to index local 'opts' (a nil value)
stack traceback:
...fwu/.local/share/nvim/lazy/fzf-lua/lua/fzf-lua/utils.lua:1192: in function 'fzf_version'
...u/.local/share/nvim/lazy/fzf-lua/lua/fzf-lua/_health.lua:75: in function 'check'
[string ":lua"]:1: in main chunk
[C]: in function 'call'
/usr/local/share/nvim/runtime/lua/vim/health.lua:429: in function '_check'
[string ""]:1: in main chunk
stack traceback:
[C]: in function 'call'
/usr/local/share/nvim/runtime/lua/vim/health.lua:429: in function '_check'
[string ""]:1: in main chunk

reverting the most recent commit, e2f7165788ab36431680867d087d093470cc236e, fixes this

Ty for reporting @WuTheFWasThat, should be ok now.

great!  very quick :)

great! very quick :)

Ty @WuTheFWasThat :)


Add optional backoff to HttpOutputWriter retries Refs T57729

Should we use the com.github.rholder.guava-retrying library for this? It's Apache Licensed and 33 kb in size. Seems to be more comprehensive than the basis implementation. What are other people's opinions?

Closing in favor of 7c16c04f54b8832befc8a36402c274b5a15022e6


Fix WALLY pipeline post repo migration

Describe the task
Resolve broken WALLY pipeline from migration of BCGOV-C to BCGOV.
Purpose
to deploy new changes to WALLY.
Acceptance Criteria

[ ] can deploy to Dev
[ ] can deploy to WALLY staging
[ ] can deploy to WALLY production

Additional context

Will need to remove BCGOV-C from a bunch of instances
webhooks may be stored as secrets in OpenShift

We Scaled up the Jenkins pods successfully
We updated the Jenkinsfile.ocp4 file with the correct url: https://github.com/bcgov/wally.git (from bcgov-c)
One of the two webhooks now work
We temporarily disabled the other webhook as we don't believe it is used anymore (need to circle back to confirm)
Currently there is a "Bad credentials" error when trying to spin up the api.
There also seems to be an issue with the image missing from artifactory (Trying to pull artifacts.developer.gov.bc.ca/docker-remote/python@sha256:639a3c1c75...)

May need a separate ticket for dependency updates.

Pulling python version 3.7.7-buster from docker.io instead of artifactory.
Didn't push all the way to production on purpose for now, however it works perfectly in staging.
Tested end to end deployment by making a small change in the readMe, which then triggered the build and deploy process all the way through.


Document: styleProps

As of #169, there exists a specific prop (styleProps) which are not passed to the inner component.
This feature is not yet documented.
CC: @davidkearns

Better little docs than nothing, right?
https://gist.github.com/jaxxreal/a0831c2f1ec5be1f3ef15034bb49cf4b.
I made that for my fellows, probably will be useful till the official doc will come.

The proposal in #196 has been landed. Docs have been updated in https://github.com/rtsao/styletron/pull/217


Salesforce CLI does not pull ExperienceBundle metadata from scratch org

Summary
The force:source:pull command appears to be ignoring ExperienceBundle metadata when executing against a scratch org.
Steps To Reproduce:
Repository to reproduce: reference-source-pull-not-getting-digexp-issue
See the README.md file in the reference project for steps to reproduce issue
Expected result
force:source:pull command should pull ExperienceBundle metadata to the local project
Actual result
force:source:pull command is not pulling ExperienceBundle metadata to the local project
System Information

Which shell/terminal are you using? (e.g. bash, zsh, powershell 5, powershell 7, cmd.exe, etc.).   I am using zsh and bash

sfdx version info

{
  "cliVersion": "sfdx-cli/7.183.0",
  "architecture": "darwin-x64",
  "nodeVersion": "node-v18.12.1",
  "pluginVersions": [
    "@dx-cli-toolbox/sfdx-toolbox-package-utils 0.8.4 (user)",
    "@dx-cli-toolbox/sfdx-toolbox-utils 0.1.3 (link) /Users/john/workspace/_cli-related/sfdx-toolbox-utils",
    "@mshanemc/plugin-streaming 1.1.7 (user)",
    "@mshanemc/sfdx-sosl 1.1.0 (user)",
    "@oclif/plugin-autocomplete 1.3.10 (user)",
    "@oclif/plugin-commands 2.2.2 (core)",
    "@oclif/plugin-help 5.1.20 (core)",
    "@oclif/plugin-not-found 2.3.11 (core)",
    "@oclif/plugin-plugins 2.1.8 (core)",
    "@oclif/plugin-search 0.0.6 (core)",
    "@oclif/plugin-update 3.0.9 (core)",
    "@oclif/plugin-version 1.1.4 (core)",
    "@oclif/plugin-warn-if-update-available 2.0.16 (core)",
    "@oclif/plugin-which 2.2.4 (core)",
    "alias 2.1.14 (core)",
    "apex 1.3.0 (core)",
    "auth 2.3.8 (core)",
    "community 2.0.18 (core)",
    "config 1.4.22 (core)",
    "custom-metadata 2.0.5 (core)",
    "data 2.1.19 (core)",
    "generator 2.0.13 (core)",
    "info 2.3.1 (core)",
    "limits 2.2.0 (core)",
    "org 2.2.20 (core)",
    "packaging 1.12.0 (core)",
    "schema 2.2.2 (core)",
    "signups 1.2.12 (core)",
    "source 2.3.12 (core)",
    "telemetry 2.0.5 (core)",
    "templates 55.1.0 (core)",
    "trust 2.2.4 (core)",
    "user 2.1.24 (core)",
    "@salesforce/sfdx-plugin-lwc-test 1.0.1 (core)",
    "@steampunk/sfdx-steampunk-org 0.1.1 (user)",
    "salesforce-alm 54.8.5 (core)",
    "sfdmu 4.23.2 (user)",
    "shane-sfdx-plugins 4.43.0 (user)",
    "soqlx-opener 0.1.12 (user)"
  ],
  "osVersion": "Darwin 22.2.0",
  "shell": "zsh",
  "rootPath": "/Users/john/.local/share/sfdx/client/7.183.0-87b32e0"
}

Additional information
n/a

thanks as always for the great repo and steps @ImJohnMDaniel - we'll get this fixed 👍

Hey @ImJohnMDaniel, I spoke too soon,
ExperienceBundle and DigitalExperienceBundles don't have source tracking enabled until v57.0... which is rolling out now. https://developer.salesforce.com/docs/metadata-coverage/56, as a workaround you can use force:source:retrieve -m DigitalExperienceBundle

After discussion with @ImJohnMDaniel, things are working as designed so closing this.


Print or Export Outline

I tried searching the feature requests for this but couldn't find anything, so please forgive me if the request exists elswhere.
It would be really useful if there was an option to export the Outline as text or copy it to the clipboard. Something that would work similarly to the Show Functions extension but would be native and have the same fidelity of the Outline. For example--thinking in C++--it could give you the option of exporting only variables or classes, or only declarations without definitions, or only objects of certain types, etc. Even if it was just a straight copy of what's shown in the Outline would be great and could be parsed manually afterward.
This would be super helpful for creating documentation and also as a more "qualitative" search tool.

This is cool idea for an extension, and also easy to do: Use the vscode.executeDocumentSymbolProvider-api command (like in this test) and you'll have the outline of a file.

Thanks!


[CT-1016] [Bug] test tmp files aren't cleaned up when running /tests/functional/simple_seed

Is this a new bug in dbt-core?

[X] I believe this is a new bug in dbt-core
[X] I have searched the existing issues, and I could not find an existing issue for this bug

Current Behavior
After running tests/functional/simple_seed/ a file is found at tests/functional/simple_seed/data/tmp.csv`
Expected Behavior
Running tests doesn't litter the repo with unwanted files.
Steps To Reproduce
/dbt-core/.tox/py-integration/bin/python -m pytest tests/functional/simple_seed
Check to see if file exists at tests/functional/simple_seed/data/tmp.csv
Relevant log output
No response
Environment
- OS:
- Python:
- dbt:

Which database adapter are you using with dbt?
No response
Additional Context
No response

Resolved by #5749


Repo paging in dashboard shows too many pages with 30 repos

Gitea version (or commit ref): 1.13 (Codeberg), 1.15 (try.gitea.io)
Database (use [x]):

[ ] PostgreSQL
[x] MySQL
[ ] MSSQL
[ ] SQLite

Can you reproduce the bug at https://try.gitea.io:

[x] Yes https://try.gitea.io/30repos (feel free to join this org as admin)

Description
The paging of repos is broken in the user dashboard with (n)*15 repos, n >= 2.
So with 15 repos, there is no paging yet, but with exactly 30 repos, you can click to the second page, and it also offers you to navigate to the third page (repos 31 - 45) - but it is just empty because there are no more repos to show.
I assume that this also happens with 45, 60, 75, 90 repos etc.
Feel free to join the 30repos org on try.gitea.io, I assume the maintainers have admin accounts on the instance.
Screenshots

Since this is just a minor thing, it's probably a good first issue? Won't find the time to look at the code the coming weeks though ...

Hi, I would like to work on it. Is it ok?


Doc : Add docstring examples

Reference issue
Relates to #7168
What does this implement/fix?
Add docstring examples for:

fftpack.fft2
fftpack.ifft2
io.savemat

LGTM now, merged. Thanks @jjerphan


ignore force remove container error

Signed-off-by: Ye Sijun<EMAIL_ADDRESS>$ sudo docker rm -f <not-exist>
$ echo $?
0

Windows CI is failing
=== CONT  TestRemoveContainer
    rm_test.go:35: assertion failed: res.ExitCode is 0
--- FAIL: TestRemoveContainer (1.15s)


Publish on npm

According to a recent cordova announcement here: https://cordova.apache.org/announcements/2015/04/21/plugins-release-and-move-to-npm.html, the cordova plugins registry is going away in favor of npm for publishing plugins.
In order to be discoverable, the cordova-plugin-fonts plugin needs to move over to npm.

Done - release 0.4.0