MMM-Hue CORS Policy Issue

OberfragGER

@sdetweil Thank you for you clarification.
Thats really not good. So i have to decide to get rid og MMM-Motioneye for another camera module which is working…or not to use MMM-Remotecontrol… or not to Update from 2.17 (i have an old image with a fresh install).

sdetweil

@oberfragger you might try with address:“192.168.x.y”

where x and y are from the IP address of the mm machine

OberfragGER

@sdetweil said in MMM-Hue CORS Policy Issue:

@oberfragger you might try with address:“192.168.x.y”

where x and y are from the IP address of the mm machine

Hey @sdetweil,
sorry for the late reply. Thanks for your help, again. With that, i have MM running with 2.18 an d MMM-Motionseye is displaying the stream.

Thanks a lot.

Edit: For anyone who reads this. After set

adress: "192.168.X.X"

the module GoogleBirthdaysProvider was not working any longer due the config of that module.
Just change

url: 'http://localhost:8080/mmm-googlebirthdaysprovider',

to

url: 'http://192.168.X.X:8080/mmm-googlebirthdaysprovider',

sdetweil

@oberfragger just to let you know ip
addresses

192.168
and
10.

are not routable over the internet . they are intended only for local private networks. so having your full address doesn’t allow anyone to access it unless they are also on your network. (if they are on your network, they can find all the active addresses in a few seconds.

my desktop is 192.168.2.106

spitzlbergerj

@CarstenD said in MMM-Hue CORS Policy Issue:

There is now a new version available for MMM-Homematic that also works w/o changing the config.

Hi @CarstenD ,

where can I find this new version? At https://github.com/Sickboy78/MMM-Homematic is still the old version.

Sorry, but i don’t get it

Regards
Josef