I understand the reason why the caching has been implemented in NPM for List ressource.
Please consider having an expiration time frame (customizable) that would automagically send the request to the resource instead of showing old and stale data. If the device is there, there is a reason why we want to list and validate what we are really polling. fine by me if the data is a day or two old, but grabbing data from 3 year back is useless to us. I feel this would be a simple thing to implement as this could be checked daily during database maintenance, and simply add a flag to the ressource list to have it considered as stale/old.