Some network endpoints are out of date

[natereprogle]

Describe the bug/issue Some network endpoints in the actions.js file no longer exist. For example, the one for nwSpecificSlide references /trigger/playlist, but Network Link uses the /v1/playlist/{identifier}/{index}/trigger endpoint as noted by the official API spec: https://renewedvision.com/api_spec/index.html

To Reproduce Create a new button with a press action using the "Specific Slide: Network Link" action type. On press, view the debug logs to see the action being sent

Expected behavior ProPresenter should trigger the slide.

Screenshots Unable to upload screenshots currently, so here are the full text descriptions.

Please add screenshots (or full text descriptions) showing:

• Playlist/Presentation is "Announcements / Announcements"
• The IP and port of my computers are configured correctly. ProPresenter also has network link enabled and the control settings on. Passwords are also correctly set. Actions such as next slide work, but not network link actions.
• Playlist Name is set to "Announcements". Presentation Name is set to "Announcements". Slide index is set to 1.
• No variables used
• No triggers used

Versions/Environment (please complete the following information):

• ProPresenter Version: 7.13
• OS of ProPresenter Machine macOS Ventura 13.1
• Companion Version: 2.4.2+4911-v2-4.2-fcb5a863
• OS of Companion machine: macOS Ventura 13.1
• Debug log output when issue occurs (Turn on debug log)

  23.04.16 08:43:34 device(DL50K1A44358): Button 2.5 released
  23.04.16 08:43:34 instance(propresenter): nwCMD.path: /trigger/playlist nwCmd.data: {"path":[{"name":"Announcements"},{"name":"Announcements"},{"index":0}]}
  23.04.16 08:43:34 device(DL50K1A44358): Button 2.5 pressed

*Any Other Context A valid workaround is to use the "Generic HTTP Requests" built into companion. Configure its base URL to http://localhost:49761, or whatever ProPresenter port you use. Enable self-signed certificates. Then, add a HTTP: GET request to your button, trigger, or whatever, and set the URI to /v1/playlist/Announcements/Announcements/0/trigger. It works perfect at this point.

[MattLinny]

Also experiencing this. Current work around is to trigger specific slide using path