@karsten13 Awesome. That worked. Much appreciated for the assist.

Thanks @karsten13. Will await your post there. I am rewriting the module but am running into all kinds of issues. It is ugly. :-(

@sdetweil Yep, understood. node-fetch has also had some changes which could cause some issues in future. I am trying to see if I can fix the MMM-Hue module and it calls out to a bridge which sits on the local network and runs into this CORS issue. Other modules have the same issue. This is going to make module dev a bit difficult, but I am sure we will adapt. :smiling_face_with_sunglasses:

Thanks @sdetweil. I have noticed that. Is there plans on making changes to align to https?

Hi all, Is there a bigger issue with the CORS policy updates? I have noticed the below warnings in the Developer window.

The list goes. Are there any recommendations on how to get rid of this? The CORS policy update seems to be affecting other modules that now stopped working as the responses are being blocked.

Would downgrading the Electron version resolve this or is a lower version not compatible with v2.18?

Thanks @karsten13 , seems like it does not work as mentioned below by @Fozi . Seems like the modules uses jQuery and does a call to the bridge to get the data. Seems like I need to log an issue on Github for the module but it has not been touched in the last 3 to 4 years. I will fork it and see if I can make some changes to get it working. The last suggestion you made below seems like code changes module side so I will see what I can do to change it from jQuery to something that would work. Thanks for the replies.

I seem to be having an issue after updating to 2.18 yesterday. MMM-Hue seems not to be working anymore. I get the following error:

Access to XMLHttpRequest at 'http://bridgeip/api/user/groups' from origin 'http://0.0.0.0:8080' has been blocked by CORS policy: The request client is not a secure context and the resource is in more-private address space `private`.

Has anybody else had the same issue after updating? There are no errors in the logs. The above error is from the Developer Console.

@cowboysdude Same to you too from South Africa.

@aderoks said in How to send notification to module via external REST API call?:

socketNotificationReceived: function (notification, payload) {
console.log(“Receiving notification from MMM-Test”);
if(notification === “date_sent”) {
console.log(“Received”);

Generally, in the module.js you would use Log.log and it would print to the developer window Console. Or you could just do as Sam suggested and it would print to the terminal window.

@sdetweil said in MMM-Jeedom - align to left:

.MMM-Jeedom .time.align-right
{
text-align: left;
}

Should go into custom.css and not main.css right?

@sdetweil Lets see which one he is using. I am off to bed. Been a long day.

@sdetweil And there is this one as well:
https://github.com/schramkef/MMM-Carousel

@sdetweil Unless there is a 3rd one that we are not aware of…:face_with_monocle:

@sdetweil Ah, now I understand the earlier differences. We were looking at different modules. Which one is @pastormingle using?

@pastormingle So, what @sdetweil meant was that in the terminal window in the ~/MagicMirror/modules/MMM-Carousel/ folder you should run the command git remote -v and post the output of that.

For me it is:

origin  https://github.com/barnabycolby/MMM-Carousel (fetch)
origin  https://github.com/barnabycolby/MMM-Carousel (push)

@pastormingle Do you see any of the module suspended or module resumed stuff?

@pastormingle As mentioned previously, are the any errors in the developers window? Do you have any errors in the terminal window? I am using the exact same config as you for Carousel and it work just fine for me

@pastormingle What Sam was saying was the when posting your config, you need to set it in a code block. That is done by selecting the config you posted and then pressing the </> button at the top of the window. That would wrap the config in a code block and make it look “pretty”.

I am glad your Carousel is now working.

@pastormingle That means that something is already running with that IP. Do you only have 1 instance of MM running?

@pastormingle Are there any errors where you start the mirror? I.e. if you do npm start are there any errors in the terminal window or if you use pm2 you can check the pm2 logs. You can also check the Developer Console, do shift_ctrl + i and select the console tab. See if there are any errors there. If no errors you should see something like the below, modules suspended…module resumed