Skip to content

Home Assistant

25 Topics 233 Posts
  • https not allowed in reactor?

    9
    0 Votes
    9 Posts
    2k Views
    toggledbitsT
    OK. Of course, I was assuming, because of your example in reply to me, that you were making an HTTP request (via the HTTP Request action in reactions) to HA, not trying to use the secure websocket at the Controller interface level. This is why details in reports are important. More better than less. Also, if you have posted information from log files, it also would have been obvious that I was thinking about the wrong connection.
  • Home Assistant Fork

    1
    0 Votes
    1 Posts
    782 Views
    No one has replied
  • Interfacing Alexa with Reactor via Routines and Dimmer VS

    42
    0 Votes
    42 Posts
    15k Views
    LibraSunL
    @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.
  • EspHome acquired by Nabu Casa

    1
    1 Votes
    1 Posts
    446 Views
    No one has replied
  • Latest HA release

    1
    0 Votes
    1 Posts
    449 Views
    No one has replied

Recent Topics