Interfacing Alexa with Reactor via Routines and Dimmer VS
-
@librasun said in Interfacing Alexa with Reactor via Routines and Dimmer VS:
Something tells me this involves using WinSCP into Vera and editing some file, perhaps? I'm just scared of screwing something up unless I'm told explicitly what steps to follow.
chances are high. maybe what Patrick is suggesting is easier.
-
You're missing what I'm saying. You can move the HA-Bridge container to a different port so it doesn't conflict with DSM's use of 80 by reassigning the local port in the container configuration. The only trouble that may create is if the HA-Bridge itself self-reflects at that port, either by making requests of itself, or publishing the port to others for JSONP or other forms of callback, in which case, you need to tell HA-Bridge it's on a different public port, and well-behaved apps have configuration for that.
@toggledbits No, I totally grokked what you were explaining, it's just that there's a (relatively new) well-documented problem of Amazon Alexa now only looking at port 80 during Discovery. Hence, whatever solution one rigs to intercept its inquiries, it must originate on some device's HTTP port 80. And that simply cannot happen (without major surgery and risk) on the Synology NAS, even if you try to instruct a Docker container to open it (yields red box and stern warning). Just no can do.
therealdb is recommending a work-around using Vera, and I'm inclined to try that once I pin down where his info applies.