Voice control via Google Home

The easiest way to run anything like this is via the OpenRemote HTTP REST API - as you can call the button presses via REST.
The “problem” is that natively, both Google and Amazon need to connect to OpenRemote to drive it.

The HA-Bridge software https://github.com/armzilla/amazon-echo-ha-bridge) can do this for you, as it run s as a bridge - but it requires Java 1.8, which can be a problem on some kit (my server runs Wheezy for example, and there is no 1.8 that is easily acquirable)

I’m looking at using IFTTT, which can access Google Home voice feeds, combined with Maker WebHooks - which can call internet URLS. Add to that ngrok.com (which provides you a secure tunnel from your LAN to the internet), and you can link back to your HTTP REST accessible buttons, and voila…

The home-cinema-on is in fact a macro which turns many devices on and switches to right channels and volume levels. Anyway, in your case you have probably defined commands to drive your z-wave devices. Then this would work like this, in ha-bridge you define that when X device is switched on then an UDP packet is sent to the openremote controller. Then, in upenremote controller, an UDP custom sensor with the UDP listener should receive this command and trigger your Z-wave device command when it does. This action should be defined in a rule. Something like this:

rule "abc"
when
  Event(source=="name of your UDP listener custom sensor", value=="UDP message defined in ha-bridge to switch the device X")
then
  execute.command("your Z-wave device switch on command");
end

Of course you can have many rules like this for all your devices.

hi

i am able to get the interface between Ha-bridge and openremote working using the udp method and rules as suggested. It seems to be working fine with the test buttons on the Ha-bridge and i can control my z-wave devices.

however, i cant figure out how to link ha-bridge to Alexa? i have the reverb app on my phone and i am logged in to it with my amazon account but it does not discover any z-wave devices.

do i have to configure any settings on the ha-bridge so it can connect to my amazon account? i clicked on the my echo tab on the ha-bridge and logged in to it also with my amazon account.

I am missing the understanding of how ha-bridge connects to amazon Alexa account so that my z-wave devices on added on ha-bridge will be discovered. To clarify, i do not have any of the Amazon devices (echo or dot)

Thanks

I never tried the path you are trying to do. All I know is that when the Alexa and ha-bridge are on the same LAN then saying "Alexa, discover devices" is enough. Otherwise, only devices known to skill's cloud API are discovered, which is not the case of ha-bridge as the Philips Hue skill is built in and it should work even without internet connection, but Alexa won't respond without Internet as all it's "intelligence" is in the cloud. All in all, IMHO you need a phisical Amazon Echo device to get it going. Usually pressing 'Test' buttons in ha-bridge is enough to check.
Don't hesitate to purchase Alexa, you'll love it in an instance ;). If you like to listen music then standard Alexa is better, otherwise Echo Dot is enough (you can still onnct it to the better audio if you wish).

Just a quick update - I am able to get a basic On / off function working. I had to have a Amazon dot device to get Alexa to discover ha-bridge. Once the dot is online, I can use the reverb app from anywhere to send voice commands.

One thing that prevented this from working that was not obvious in any start up tutorials online was on the ha-bridge the upnp ip must be set to the ip of the device it is running on ( RPI in my case). The default setting did not work for me.
Here is a link that pointed me in that direction:

https://github.com/bwssytems/ha-bridge/issues/278#issuecomment-322183346

Thanks for all the help to get me started. I will update as I add more devices and test more functionality.

Hi Aleksey,

i am playing around with homebridge to get siri / apple home kit to work with openremote and having some issues. can you share more details on how you implemented homebridge with the openremote pluggin? I installed it but the documention for this plugin is very poor. Can you share your implementation with this pluggin, devices your are controlling and the config file?

https://www.npmjs.com/package/homebridge-openremote

I also tried the multiswitch udp pluggin and it seems to send UDP messages to Openremote but i must be doing something incorrect in the config file and the payload portion coz openremote UDP listerner sensor is not recognizing the text i am sending from homebridge.

if you can provide more details on how you are using homebridge with openremote, that would be great

Hi.

I tried this way:

The image for Docker on the Synology I downloaded from here: https://hub.docker.com/r/sybdata/homebridge/

My configuration files for install and config for homebridge-openremote (for Fibaro Dimmer and the Two-channel relay) in the attachment.

In log:

*** WARNING *** For more information see <http://0pointer.de/avahi-compat?s=libdns_sd&e=node&f=DNSServiceRegister>
stdout
13:53:32
npm info it worked if it ends with ok
stdout
13:53:32
npm info using npm@4.2.0
stdout
13:53:32
npm info using node@v7.10.1
stdout
13:53:32
npm info ok
stdout
13:53:32
[37m[7/28/2017, 1:53:32 PM][39m Loaded plugin: homebridge-openremote
stdout
13:53:32
[37m[7/28/2017, 1:53:32 PM][39m Registering accessory 'homebridge-openremote.openremote'
stdout
13:53:32
[37m[7/28/2017, 1:53:32 PM][39m ---
stdout
13:53:32
[37m[7/28/2017, 1:53:32 PM][39m Loaded plugin: homebridge-server
stdout
13:53:32
[37m[7/28/2017, 1:53:32 PM][39m Registering platform 'homebridge-server.Server'
stdout
13:53:32
[37m[7/28/2017, 1:53:32 PM][39m ---
stdout
13:53:32
[37m[7/28/2017, 1:53:32 PM][39m Loaded config.json with 3 accessories and 0 platforms.
stdout
13:53:32
[37m[7/28/2017, 1:53:32 PM][39m ---
stdout
13:53:32
[37m[7/28/2017, 1:53:32 PM][39m Loading 3 accessories...
stdout
13:53:32
[37m[7/28/2017, 1:53:32 PM][39m [36m[Dimmer][39m Initializing openremote accessory...
stdout
13:53:32
[37m[7/28/2017, 1:53:32 PM][39m [36m[Switch 1][39m Initializing openremote accessory...
stdout
13:53:32
[37m[7/28/2017, 1:53:32 PM][39m [36m[Switch 2][39m Initializing openremote accessory...
stdout
13:53:32
[37m[7/28/2017, 1:53:32 PM][39m [36m[Dimmer][39m Switch received status http://192.168.1.3:8688/controller/rest/status/403148 state is currently 0
stdout
13:53:32
[37m[7/28/2017, 1:53:32 PM][39m [36m[Dimmer][39m Setting power state to off
stdout
13:53:32
[37m[7/28/2017, 1:53:32 PM][39m [36m[Switch 1][39m Switch received status http://192.168.1.3:8688/controller/rest/status/403150 state is currently 0
stdout
13:53:32
[37m[7/28/2017, 1:53:32 PM][39m [36m[Switch 1][39m Setting power state to off
stdout
13:53:32
[37m[7/28/2017, 1:53:32 PM][39m [36m[Switch 2][39m Switch received status http://192.168.1.3:8688/controller/rest/status/403151 state is currently 0
stdout
13:53:32
[37m[7/28/2017, 1:53:32 PM][39m [36m[Switch 2][39m Setting power state to off
stdout
13:53:33
[37m[7/28/2017, 1:53:33 PM][39m [36m[Switch 1][39m HTTP set power function succeeded!
stdout
13:53:33
[37m[7/28/2017, 1:53:33 PM][39m [36m[Switch 2][39m HTTP set power function succeeded!
stdout
13:53:33
[37m[7/28/2017, 1:53:33 PM][39m [36m[Dimmer][39m HTTP set power function succeeded!
stdout
13:53:33
Scan this code with your HomeKit App on your iOS device to pair with Homebridge:
stdout
13:53:33
[30m[47m                       [49m[39m
stdout
13:53:33
[30m[47m    ┌────────────┐     [49m[39m
stdout
13:53:33
[30m[47m    │ 031-45-154 │     [49m[39m
stdout
13:53:33
[30m[47m    └────────────┘     [49m[39m
stdout
13:53:33
[30m[47m                       [49m[39m
stdout
13:53:33
[37m[7/28/2017, 1:53:33 PM][39m Homebridge is running on port 51826.

stdout
13:54:43
[37m[7/28/2017, 1:54:43 PM][39m [36m[Switch 1][39m Switch received status http://192.168.1.3:8688/controller/rest/status/403150 state is currently 0
stdout
13:54:43
[37m[7/28/2017, 1:54:43 PM][39m [36m[Switch 1][39m Setting power state to off
stdout
13:54:43
[37m[7/28/2017, 1:54:43 PM][39m [36m[Switch 1][39m HTTP set power function succeeded!
stdout
13:54:03
[37m[7/28/2017, 1:55:03 PM][39m [36m[Switch 1][39m Switch received status http://192.168.1.3:8688/controller/rest/status/403150 state is currently 1
stdout
13:54:03
[37m[7/28/2017, 1:55:03 PM][39m [36m[Switch 1][39m Setting power state to on
stdout
13:54:03
[37m[7/28/2017, 1:55:03 PM][39m [36m[Switch 1][39m HTTP set power function succeeded!
stdout
13:54:29
[37m[7/28/2017, 1:55:29 PM][39m [36m[Switch 1][39m Switch received status http://192.168.1.3:8688/controller/rest/status/403150 state is currently 0
stdout
13:54:29
[37m[7/28/2017, 1:55:29 PM][39m [36m[Switch 1][39m Setting power state to off
stdout
13:54:29
[37m[7/28/2017, 1:55:29 PM][39m [36m[Switch 1][39m HTTP set power function succeeded!


``

[.env|attachment](upload://9RudXGCPAOYAg7BRe5bPdyFKfQq) (393 Bytes)



[config.json|attachment](upload://1ynl8JPCA5ZVxGSF0Hx9CQZneUL.json) (1.42 KB)



[install.sh|attachment](upload://3bCTjMMfOVJE8Dt8aI8qWEJGLcG.sh) (217 Bytes)



[package.json|attachment](upload://c8fSREJFgpvsqG2CcftfnEOCOi3.json) (852 Bytes)

Thanks for sharing! What configuration did you use on Openremote side (commands and sensors) for receiving these messages and executing on them? I appologize I have not used http before so this new to me.

Hi.

This is the OpenRemote Controller API. Previously, in the old forum, there was a section: OpenRemote Controller API, in which there were examples (xml and json).

Now I can not find this information. In my examples of configuration files, there are a few commands that I remember.

In the web browser commands

Output of panels:

http://192.168.1.7:8688/controller/rest/panels

Answer:

Panel composition:

http://192.168.1.7:8688/controller/rest/panel/MyAndroid

``

Answer: (piece)

</ Link>

</ Switch>

</ Absolute>

``

In the answer we are looking for switch id =

For example: Switch 1

For him, the command:

http://192.168.1.7:8688/controller/rest/control/395/on

http://192.168.1.7:8688/controller/rest/control/395/off

For example: Switch 2

For him, the command:

http://192.168.1.7:8688/controller/rest/control/397/on

http://192.168.1.7:8688/controller/rest/control/397/off

For Dimmer

http://192.168.1.7:8688/controller/rest/control/401/on

http://192.168.1.7:8688/controller/rest/control/401/off

Thanks you! I think I am starting to understand how this might be working- in your example above and the config.jason, what are the IP addresses 192.168.1.7 and 192.168.1.3 assigned to?

IP addresses 192.168.1.7 and 192.168.1.3 - IP addresses OpenRemote Controllers.

Alekey thanks for posting all your configs. Helped a lot. I have the lights working fine with homebride and Sirir now using the openremote plugin.

A couple of things i noticed was it only understands values “on” and “off”

Also when i try using it for status of sensors like a door sensor, if i assign the states “on” and o"off" it seems to work ok buti have to restart the Home app for the status to refresh. It does not refresh automatically. Have you used this homebridge for any other sensors other than switches? below is a sample config i am using for a door sensor which does not seem to update status automatically. I tried using GET and POST but same result. I wonder is there is any other way or plugins for sensors.

{
“accessory”: “openremote”,
“name”: “Patio door”,
“switchHandling”: “realtime”,
“http_method”: “GET”,
“status_url”: “http://192.168.1.30:8688/controller/rest/status/408980
}

Hi.

I do not have a Home app (since my iPad mini has only iOS 9.3.5). I use the Devices application (from this) for connect to homebridge.

But I also noticed this behavior of this application. It also sometimes does not determine the state of the devices - i.e. If you change the state of devices (i have dimmer, switchs, thermostats) from the Devices application itself, this works fine. But if the state of the devices changes from a third-party application or device, then the device state in the Devices application is not always correct.

With sensors I’m not very versed, but the behavior is similar.