Hello guys,

Thanks for reminding me to do this. This script has needed some work for a while now and I keep delaying it.

There’s an issue with cross-site scripting I need to resolve (so resolving external URL’s may fail) - I also want to establish the issue with node inspections. I’m going to begin fixing these issues as soon as my exams are up (So beginning of June) - So you can expect an update then. Apologies for the inconvenience in the mean time.

As an added bonus, I’ll be releasing a new module also :) It’s pretty cool looking and I’m looking forward to giving it to all of you.

Thanks!

There appears to be a cross domain issue with the module. I’m currently travelling and I’m going to make it a top priority when I return to repair it. In addition, I have a very cool module upcoming :)

I’ll get the fix done as soon as I can guys. Sorry for the wait.

In the meantime if you have access to the server side clients of your request, please look into making requests accepted from any source as a temporary fix.

Download available here

https://github.com/Eunanibus/MMM-HTTPRequestDisplay

I need to make some fixes to the module so for right now consider it in Beta :)

I’ve updated the ReadMe appropriately for this module, and this is available on the github page.

There are a few outstanding issues I need to address such as the calls to external domains (and a few other underlying issues), but I’m in the USA until the 6th of August and I won’t have time to address those issues until I return home.

Once the module is copied to the Modules folder, and the relevant config changes have been made, you shouldn’t need to “npm install” anything. You should simply be able to launch the MM software. No installations should be necessary. Be sure to read the Readme carefully, but if you can be more specific about the steps you have taken I can help you further.

Thanks @strawberry-3-141 - I’ll take a look and see if there are any changes I can make.

Yeah that’s what I based my original request functionality on. The OpenWeather API response is CORS compatible due to the response header - this is why the example response works well. Outside of this domain though (say on http://www.w3schools.com/xml/cd_catalog.xml (or any other external server). This unfortunately makes problems - I’m still looking for a work-around.

You can execute the server by navigating to the MM folder (after you’ve cloned it) and executing node server only on the command line.

Then you would need to navigate using a browser to your localhost address (i.e http://127.0.0.1) where you would see the app.

You can think of the electron application as a browser in a window (the bit that relies on chromium) - But if you can’t use that, you can always just navigate to the address yourself. Setting up borderless windows and stuff is something you can do manually elsewhere. There’s more information on how to rotate the display and do all the borderless windows stuff on this blog

@KirAsh4 I’ve isolated the issue as a Cross-Domain Access issue. Do you know of any particular way to make XMLHTTPRequests to external domains?

I wasn’t aware this would be an issue but apparently anybody who wants to use this and map to an external domain will have this issue unless they have a running PHP server that can store the XML results locally (or if they can access a server, they can add the line Access-Control-Allow-Origin: * to their HTML headers.

Any ideas?

@KirAsh4 can you confirm MM startup with my module with this config file?

The module won’t show any results but MM should boot?

Can you Zip up and upload your config file somewhere I can download it and I’ll take a look? Somewhere like pastebin.