Regularly Querying HTTPS API causes "shutdown"

[makeplants]

I'm building a simple RPi powered LED display that displays the album art of the currently playing song. I've found that when I query the WiiM API more frequently than every ~5 seconds, the WiiM hangs itself up. I'm not able to access it in the app and have to unplug/plug it back in to restart (which fixes things). Although a 5 second polling rate is workable, it causes a noticeable delay between when the song changes and when the album art is updated.

Also, if I'd like to add extra info to the display (i.e. position in the song) I'd want to ping the API at least once a second.
This only happens when the API has been queried at a higher rate for more than 30 minutes - if I'm not querying the API the WiiM runs great!

Do folks know if this is an inherent limitation of the WiiM Mini/API, or if there could be something else going on?

 

[dustin]

It is an issue with the wiim mini. Four months ago support said they will send me a firmware to address this, but it hasn't happened yet. I encourage you to open a support ticket. If they hear from more people it may get more attention.

 

[makeplants]

It is an issue with the wiim mini. Four months ago support said they will send me a firmware to address this, but it hasn't happened yet. I encourage you to open a support ticket. If they hear from more people it may get more attention.

Unfortunate, but thanks for the quick reply. I filed a support ticket & will update you with the response.

 

[hoohoohoo]

Also, if I'd like to add extra info to the display (i.e. position in the song) I'd want to ping the API at least once a second.
This only happens when the API has been queried at a higher rate for more than 30 minutes - if I'm not querying the API the WiiM runs great!

Couldn't you fake it by interpolating the expected position? A 12 Hz signal (every 5s) vs a 60 Hz signal (every 1s).

The WiiM Mini uses a dual-core ARM Cortex-A7 CPU, complemented by 128 MB of DRAM and 128 MB of flash memory from what I can tell. It would be clocked somewhere in the middle of 800 MHz to 1.2 GHz. It seems adequate but they haven't optimized for frequent API queries.

https://www.audioadvice.com/products/wiim-mini-wireless-audio-streamer?srsltid=AfmBOopL_f3D5c9l7HoJZF4PGHvLTZRVy8aPDnUNHQWdk9Vtxf2zlmsu

 

[cc_rider]

I've always used the UPnP API in the past, but switched to the https API for my most recent project. Working fine for me at ~1 request/second.

GitHub - retired-guy/WiiM-Presto: Display WiiM now playing on Pimoroni Presto

Display WiiM now playing on Pimoroni Presto. Contribute to retired-guy/WiiM-Presto development by creating an account on GitHub.

github.com