Notice who supplies the catalogue structure
A Kodi device may display a remote collection organised by year, title or performer. The UPnP manual explains that these browse nodes come from the server, which controls their organisation. A server-provided Movies node is therefore not proof that the client has imported those entries into its own library database. Confirm whether you are browsing a remote source or viewing a locally scanned library before looking for missing management features.
Choose the route according to the intended task
Kodi explicitly distinguishes UPnP browsing from creating a library on the client. Its source-creation guide recommends another supported sharing protocol, such as SMB, for a library built from network files. That is an architectural choice rather than a promise that every server supports the same credentials or protocol. If the goal is simply to browse and play a server’s existing organisation, the UPnP route may already be doing the intended job.
Test the layer you actually changed
Use one authorised sample and record whether it appears in the server tree, starts playback and exposes the controls you need. If your requirement is local library management, establish the supported direct file-sharing arrangement and source configuration before scanning. Do not enable every sharing or remote-control option merely to make an absent client feature appear. This distinction is separate from codec compatibility: a visible item can still need supported decoding on the receiving player.
Questions, answered
Does a Movies node from a UPnP server mean Kodi has scanned a local library?
No. It can be a server-provided browse node; the documented client-library limitation still applies.