durosity wrote:As far as I can tell at the moment it's not possible because nothing tells HomeBridge that it's a lock. That's why I'd love to see a plugin in indigo for it that would allow you to define the type of device it is, as in device, light, lock, door, etc. I think it's quite important that devices and lights are defined separately too otherwise a command to Siri to "turn off all the lights" will result in some devices that aren't lights being turned off too. At least as far as my experiments have shown they are. Perhaps I'm missing something? But either way being able to say "lock the door" and it turn that device to "on" or "close the garage door" being translated to turning a virtual device off would be awesome!
Perhaps one day I'll finally have time to learn Python
DVDDave wrote:Mike,
I had to make a small change to Indigo.js to get it working. I use a reverse proxy to get Indigo to accept SSL (https) requests. A side effect is that all my URLs have an extra directory layer called indigo even for non-SSL requests.. I tried adding /indigo to the port in the configuration file but the URLs returned by Indigo when discovering devices already have the correct path and so Indigo.js was adding an extra layer to them.
So I changed line 48 to url: this.baseURL + "/indigo/devices.json/" , so the the extra layer would only be added to the first request.
I haven't dug into the code enough to recommend a more robust change but I wanted to alert you to the issue since I think others are using reverse proxies as well.
Thanks.
--Dave
webdeck wrote:I have an apache proxy in front of my Indigo server as well, for requests from the outside world, but why would you have homebridge talk to that? Can't you have homebridge talk directly to Indigo's web server?
DVDDave wrote:webdeck wrote:I have an apache proxy in front of my Indigo server as well, for requests from the outside world, but why would you have homebridge talk to that? Can't you have homebridge talk directly to Indigo's web server?
Hi Mike,
For some reason, even when I talk directly to Indigo I still need the extra /indigo layer, namely http://127.0.0.1:8176/indigo/devices. I would think it would work also but when I don't include it, nothing comes back. Maybe I have something misconfigured in the reverse proxy.
--Dave
RogueProeliator wrote:Perhaps one day I'll finally have time to learn Python
I'm going to go back to your posts and count how many times you have said this...
DVDDave wrote:I just remembered why the extra layer is needed to talk to Indigo directly. When I configured my reverse proxy, the links weren't coming back correctly in my control pages. Therefore, as recommended , I added /indigo/ to the Indigo root in my IndigoWebServer.conf file to make the links work.
Do you not have this issue with your reverse proxy?
webdeck wrote:I do my reverse proxy to another host name, so everything remains at the root level for me. What does your apache config look like? I thought the pair of ProxyPass and ProxyPassReverse are supposed to take care of all the rewriting transparently.
-Mike
Londonmark wrote:- is there a trick to getting the new Apple TV to act as a bridge? I've tried it but no dice. My iPhone has remote access for homekit kit enabled.
Users browsing this forum: No registered users and 11 guests