Page 3 of 3 FirstFirst 123
Results 21 to 25 of 25

Thread: Cortex voice control using Amazon Echo

  1. #21
    Automated Home Guru JonS's Avatar
    Join Date
    Dec 2007
    Location
    Suffolk
    Posts
    201

    Default

    +1 for shared code on GitHub or GitLab and any further hints and tips.

  2. #22
    Automated Home Sr Member John Winter's Avatar
    Join Date
    Dec 2007
    Location
    Buckinghamshire
    Posts
    56

    Default

    +1 from me also - I'm by no means a software engineer so a very basic guide on how to do this would be useful...

    Karam - if you see this, I wonder if you've considered building 'smart speaker' integration into cortex somehow????
    --------------------------

    www.nodeone.blogspot.com

  3. #23
    Automated Home Lurker
    Join Date
    Jan 2014
    Posts
    2

    Default

    I've achieved voice control of the house using Amazon Echo dot using the below method:
    1. Get a raspberry pi (i'm using a pi3). Do a basic install of raspbian and make sure it's up to date. I've put it on a fixed IP on my network
    2. Install HABRIDGE from BWSSYSTEMS (*it presupposes a little knowledge of how to work in a linux/raspberry pi environment) - https://github.com/bwssytems/ha-brid...ster/README.md
    basics are, install the latest version (5.3.0?) as a .jar, make sure java is up to date on your pi
    run it (by hand to start with, but you can set it up as a service)
    go to the ip address of the pi in a browser, and you'll see the bridge control pages

    habridge2.jpg

    add a device, then in the device commanders lower down, you can call the http link for the "turn light on" and "turn light off" - for example "http://192.168.1.65:8000/?79~Turn%20On;" - these can be found by right clicking in the web interface for Cortex and copying link

    habridge.jpg

    3. Tell your amazon echo dot to "detect my devices" and hey presto! "Alexa, turn master bedroom light on".

    Note:
    The HABRIDGE creates a "virtual" phillips hue device that you can control via Alexa
    it needs to be on port 80 or it won't work! Previously, they allowed it to be on other ports, but now they've locked it down to port 80 only

  4. #24
    Automated Home Sr Member John Winter's Avatar
    Join Date
    Dec 2007
    Location
    Buckinghamshire
    Posts
    56

    Default

    Thanks for this David - I have been looking into this for some time and actually Karam suggested this might be a way forward, and your post tonight inspired me to have a go!

    I've been playing with HaBridge tonight and have managed to get it to link to my echo dots as a Philips device but I'm now struggling to get it to issue commands to Cortex over http. The 'link' method from the webserver page you suggested works in a browser address bar - but only when there's an active log in to the Cortex webserver. Have you successfully set any username/password combinations in your http commands, such as http://user:passwordh@192.168.1.xxx:...1~Turn%20Off;? This doesn't work for me, but maybe theres a way round it, I am not even sure that Cortex is designed for control in this way... Have you secured your webserver with passwords?
    --------------------------

    www.nodeone.blogspot.com

  5. #25
    Automated Home Lurker
    Join Date
    Jan 2014
    Posts
    2

    Default

    I'm working on it being an allowed IP address on the local network which bypasses that.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •