-
Notifications
You must be signed in to change notification settings - Fork 2
FAQ
Q: For the web hook it is unclear if you need to put the IP of the device you want to use this with.
A: The webhook you add in Plex will send messages to the node app endpoint (/plex). So you'll need to use the ip address of the PC where you're running WebsUpTV and provide an open port. The webhook port you use in Plex settings needs to match the webhook port in your config.
If your PC running WebsUp has an ip address of 192.168.1.100, and your config has "webhookPort":8400, you'll add your webhook to Plex as http://192.168.1.100:8400/plex, and you'd want your config to include "plexServerIp": "192.168.1.100",
I think I made it confusing by assuming that the node app would be ran on the same computer where the PMS is, but that doesn't have to be the case. plexServerIp would be better if named something like websUpPcIp. Hoping that clarifies some!
Q: Also in the config it looks like you can use this with one device. Can you clarify?
A: This currently is built to show overlays on a single (Android TV) device. The overlay can currently be triggered from any device watching Plex media...which is kind of a bug, but does help me test without having to hog the TV just to have something paused. If there's demand for it, we can look into changing the config to be an array of multiple configurations, which would allow showing the overlay on any device being used, as long as it's running PiPup.
Q: I see it's in node.js. Does it really only run on Windows?
A: I think this version can run on other PMS server OS's, not just Windows. In future releases, I plan to save some files locally for facial recognition, and I'm just not sure what, if any, differences there would be for reading files (node fs library)...there may be none at all, or maybe minor stuff like / vs \ to traverse files. I have no way to truly test any differences. So that's where the 'Windows PMS only' claim came from.