@Flippage said:
This is really coming along amazingly.One question in relation to:
My intention as of right now is to package this as a self-contained version of XAMPP/LAMP/WAMP.
How difficult is it going to be to set up on an existing XAMPP setup?
I’m already running a webserver with all of my other apps, so I’d prefer not to have to setup a second instance, or to overwrite what I have.
This is probably a bit early to be asking, but I figured I’d throw it out there. If you factor in that most people with Plex would probably have a webserver running already.
Can’t wait until this is ready to test with PMP
- My excitement is palpable.
Once again, amazing work mate. You’re doing so much with this project, and meanwhile the PMP devs haven’t done anything for the last few months. That may be why you’re not getting a response from the PMP devs? They’re supposedly releasing a new version of PMP… One day.
Might be easier to integrate with this, once the new version is released.
Shouldn’t be that difficult at all. You need CURL enabled. You need to suppress some warning messages, but those should be squashed on my end before release. It’ll need a valid SSL certificate. And more than likely, I’m thinking my final implementation will need to be able to listen on a custom port, as I may wind up using the devices.xml endpoint directly on Plex in order to facilitate figuring out the IP address of the Phlex server. 
Today, yesterday, I worked mainly on UI stuff and making the API.ai stuff smarter. There’s now a button in Settings to allow deploying the API.ai config directly to their site in the event I update the code, etc. I have little “test” buttons set up to verify that Phlex can talk to Sonarr/CouchPotato/Plex/Etc. The login screen isn’t just an ugly black voide.
And for API.ai, I’ve now added the ability to detect multiple results for a search, and then ask you which one to play and respond by playing the title you stated, etc. It can now handle search requests directly, as well as most “play, stop, pause, skip, seek” commands. And, as I’ve mentioned, if you do not have a piece of media you requested to play, it’ll ask if you want to download it…and then it’ll download it.
Behind all this is a lot of work to adhere to Google’s requirements for conversation stuff. You have to queue the app to stop listening for requests after playing something or downloading something. You have to tell it to switch to a new intent when downloading or asking for results. It’s a lot to learn in a short time.
Still have to figure out how I handle the bit of linking up every individual Phlex server to a main one, which in turn handles the authorization between Google/Alexa and Phlex, and shuttles commands to the specific server. Fortunately, I can use a person’s Plex username and password to authorize against Plex.tv, then pull the device list and find the public IP of the Phlex server, so I shouldn’t have to personally cache any kind of information for anybody. I hope. I really don’t want anybody’s info, I just want this to work like an official app.
So, that’s what I’m working toward. Not just some hacky thing only master developers can install, but that anybody with the ability to install Plex can set up and use with minimal hassle.
Anybody familiar with the process of google authorization…hit me up. That’s next on my list to crack into - API # 6 or 7 to learn. 
