hass-music-assistant: Errors while importing local media

Hi Marcel

I fixed most ID3 info for my local collection (ca 8000 tracks) and started importing them with debug logging on πŸ˜ƒ. Importing for most of the tracks goes well. Don’t see many albums/artists (yet), only many tracks. But it’s worth mentioning some errors and the related debug logging around that time:

Job [Add file://album/variousartistsfantasydancehitsvolume1 to database] failed with error 'NoneType' object has no attribute 'name'.
21:20:35 – (ERROR) /usr/local/lib/python3.9/site-packages/music_assistant/mass.py - message first occurred at 21:20:28 and shows up 2 times
[547391316272] Error handling message: Unknown error (unknown_error)
21:20:35 – (ERROR) Home Assistant WebSocket API (custom integration)
[547391316272] Error handling message: Unknown error (unknown_error)
21:20:28 – (ERROR) Home Assistant WebSocket API (custom integration)
[547391316272] Error handling message: Unknown error (unknown_error)
21:19:33 – (ERROR) Home Assistant WebSocket API (custom integration) - message first occurred at 21:15:26 and shows up 2 times
Job [Add file://playlist/varioushithistory1955198555m3u to database] failed with error argument of type 'NoneType' is not iterable.
21:19:33 – (ERROR) /usr/local/lib/python3.9/site-packages/music_assistant/mass.py - message first occurred at 21:15:26 and shows up 2 times

I attached also the debug log around these errors: debug.log `

About this issue

  • Original URL
  • State: closed
  • Created 2 years ago
  • Comments: 20 (20 by maintainers)

Most upvoted comments

I prefer to give it a test run with your next version πŸ˜‰

What is the best way to stop the scan?

Just reload the integration and it will continue where it left off. Maybe do that a couple op times until the full collection is synced.

That said, I’m going to change the logic a bit to make it free memory

  1. The errors your shared in the logfile I just fixed so available in next release.
  2. The initial sync caches the entire listing in memory, it should free memory again once initial scan is done.