# Guide to Connecting gBridge to Homey for Google Assistant

**URL:** <https://community.homey.app/t/guide-to-connecting-gbridge-to-homey-for-google-assistant/9234>\
**Category:** Devices\
**Created:** [February 15, 2019, 3:04pm UTC](https://community.homey.app/t/guide-to-connecting-gbridge-to-homey-for-google-assistant/9234 "2019-02-15T15:04:24Z")\
**Posts on this page:** 20\
**Page:** 10

<div class="post-metadata">

**Author:** ![Wout\_F](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/wout_f/32/7474_2.png) [@Wout\_F](https://community.homey.app/u/Wout_F)\
**Post date:** [March 2, 2019, 8:13pm UTC](https://community.homey.app/t/guide-to-connecting-gbridge-to-homey-for-google-assistant/9234/182 "2019-03-02T20:13:20Z")

</div>

_sigh_…

After a reboot (had to shut off the power while installing a dimmer) I’m now facing the exact same problem as Fire69. When I give a command to Google Home, I can see through MQTT Explorer that it shows up on the gBridge MQTT-server. That part of the connection works fine. It however doesn’t show up in the logs of the MQTT Client and consequently, nothing happens.

When I switch a device through Homey, the only thing that shows up in the Hub logs is:

> 20190302-21:07:18 Homie set value [Office.onoff]: true  
> 20190302-21:07:14 Homie set value [Office.onoff]: false

That’s it, no mention of a MQTT-command being sent. And nothing shows up in the MQTT Client logs either. I’ve already tried reinstalling the client, to no avail.

---

<div class="post-metadata">

**Author:** ![Fire69](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/fire69/32/8758_2.png) [@Fire69](https://community.homey.app/u/Fire69)\
**Post date:** [March 2, 2019, 8:22pm UTC](https://community.homey.app/t/guide-to-connecting-gbridge-to-homey-for-google-assistant/9234/183 "2019-03-02T20:22:24Z")

</div>

> [@KonradWalsh](#):
>
> I think you need uninstall each app and reinstalled the MQTT Client first, set that up and then the Hub

I did that this afternoon, didn’t change anything. 😥

> [@Wout\_F](#):
>
> I’m now facing the exact same problem as Fire69

Excuse me for saying this, but I’m actually glad you’re having the same problems as me! 😄  
I thought I was going crazy!

---

<div class="post-metadata">

**Author:** ![Camelen](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/camelen/32/9613_2.png) [@Camelen](https://community.homey.app/u/Camelen)\
**Post date:** [March 2, 2019, 8:24pm UTC](https://community.homey.app/t/guide-to-connecting-gbridge-to-homey-for-google-assistant/9234/184 "2019-03-02T20:24:33Z")

</div>

I restarted homey to see if I also got this problem and the same thing happened. So it does not work for me either.

There has to be a bug in MQTT Hub 2.1 since it has worked to reboot before.

---

<div class="post-metadata">

**Author:** ![KonradWalsh](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/konradwalsh/32/147_2.png) [@KonradWalsh](https://community.homey.app/u/KonradWalsh)\
**Post date:** [March 2, 2019, 8:25pm UTC](https://community.homey.app/t/guide-to-connecting-gbridge-to-homey-for-google-assistant/9234/185 "2019-03-02T20:25:17Z")

</div>

OK… I am NOT rebooting…😂🤣🤣🤣

---

<div class="post-metadata">

**Author:** ![HarriedeGroot](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/harriedegroot/32/56160_2.png) [@HarriedeGroot](https://community.homey.app/u/HarriedeGroot)\
**Post date:** [March 2, 2019, 8:26pm UTC](https://community.homey.app/t/guide-to-connecting-gbridge-to-homey-for-google-assistant/9234/186 "2019-03-02T20:26:52Z")

</div>

I made some changes on the BETA branch…Is someone willing to try?

---

<div class="post-metadata">

**Author:** ![Wout\_F](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/wout_f/32/7474_2.png) [@Wout\_F](https://community.homey.app/u/Wout_F)\
**Post date:** [March 2, 2019, 8:53pm UTC](https://community.homey.app/t/guide-to-connecting-gbridge-to-homey-for-google-assistant/9234/187 "2019-03-02T20:53:13Z")

</div>

Runs fine, but doesn’t seem to help with the problem I’m facing. Nothing I do on Homey comes through in MQTT Explorer. This is what I see when I switch one of my dimmers

Hub

> 20190302-21:43:07 Homie set value [wc.measure\_power]: 1.8  
> 20190302-21:43:02 Homie set value [wc.measure\_power]: 0.4  
> 20190302-21:43:01 Homie set value [wc.dim]: 0.3  
> 20190302-21:43:01 Homie set value [wc.onoff]: true

Client

> 20190302-21:43:01 SendMessageToTopic: {“qos”:0,“retain”:“1”,“mqttTopic”:“gbridge/u796/wc/onoff”,“mqttMessage”:“true”}  
> 20190302-21:43:01 publish\_options: {“qos”:0,“retain”:true}  
> 20190302-21:43:01 send true on topic gbridge/u796/wc/onoff  
> 20190302-21:43:01 SendMessageToTopic called  
> 20190302-21:43:01 SendMessageToTopic: {“qos”:0,“retain”:“1”,“mqttTopic”:“gbridge/u796/wc/dim”,“mqttMessage”:30}  
> 20190302-21:43:01 publish\_options: {“qos”:0,“retain”:true}  
> 20190302-21:43:01 send 30 on topic gbridge/u796/wc/dim  
> 20190302-21:43:02 SendMessageToTopic called  
> 20190302-21:43:02 SendMessageToTopic: {“qos”:0,“retain”:“1”,“mqttTopic”:“gbridge/u796/wc/measure-power”,“mqttMessage”:0.4}  
> 20190302-21:43:02 publish\_options: {“qos”:0,“retain”:true}  
> 20190302-21:43:02 send 0.4 on topic gbridge/u796/wc/measure-power  
> 20190302-21:43:07 SendMessageToTopic called  
> 20190302-21:43:07 SendMessageToTopic: {“qos”:0,“retain”:“1”,“mqttTopic”:“gbridge/u796/wc/measure-power”,“mqttMessage”:1.8}  
> 20190302-21:43:07 publish\_options: {“qos”:0,“retain”:true}  
> 20190302-21:43:07 send 1.8 on topic gbridge/u796/wc/measure-power

Can you guys spot anything weird? When looking in MQTT Explorer gBridge is written with a capital B, it the protocol case sensitive?

---

<div class="post-metadata">

**Author:** ![Camelen](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/camelen/32/9613_2.png) [@Camelen](https://community.homey.app/u/Camelen)\
**Post date:** [March 2, 2019, 8:56pm UTC](https://community.homey.app/t/guide-to-connecting-gbridge-to-homey-for-google-assistant/9234/188 "2019-03-02T20:56:22Z")

</div>

You seem to have the same problem that I have. The topic defaults to lower case but the topic is case sensitive. ie gbridge/u123 instead of gBridge/u123. I also wrote this in the MQTT Hub thread.

edit: oh you wrote that in the end of your post.

---

<div class="post-metadata">

**Author:** ![Wout\_F](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/wout_f/32/7474_2.png) [@Wout\_F](https://community.homey.app/u/Wout_F)\
**Post date:** [March 2, 2019, 9:00pm UTC](https://community.homey.app/t/guide-to-connecting-gbridge-to-homey-for-google-assistant/9234/189 "2019-03-02T21:00:44Z")

</div>

Yeah, I just turned off normalizing and added the capital B. And voila! Stuff is showing up in MQTT Explorer 🙂

The only thing now is that I setup my gBridge-account when I was using the ha-branch of the Hub, through a broker, so I could have normalized names, and subscribe to gBridge instead of gbridge. Renaming the topics in gBridge to match my non-normalized device names doesn’t work, because they have spaces in them. That means I’d have to replace all spaces for underscores in my Homey devices. That’s doable, but doesn’t look very nice within the gui of the app.

Ideally, we’d be able to use capitals in the root topic and still have the device names normalized. Or would that be too ‘hacky’ @HarriedeGroot?

---

<div class="post-metadata">

**Author:** ![Marc](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/marc/32/11229_2.png) [@Marc](https://community.homey.app/u/Marc)\
**Post date:** [March 2, 2019, 9:36pm UTC](https://community.homey.app/t/guide-to-connecting-gbridge-to-homey-for-google-assistant/9234/190 "2019-03-02T21:36:07Z")

</div>

Maybe stuppid question. If I send a command with the homey APP I see that Gbrige Mqtt get the True/False message, but If i send a command thru the Google Home App I see getting a 1/0. What did I do wrong?

---

<div class="post-metadata">

**Author:** ![Camelen](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/camelen/32/9613_2.png) [@Camelen](https://community.homey.app/u/Camelen)\
**Post date:** [March 2, 2019, 9:53pm UTC](https://community.homey.app/t/guide-to-connecting-gbridge-to-homey-for-google-assistant/9234/191 "2019-03-02T21:53:18Z")

</div>

This is not wrong, it’s just a difference in how they send a boolean command.  
I think that 1/0, true/false, on/off are all allowed and works.

Google Home integration should work even if they send 1/0 instead of true/false.

---

<div class="post-metadata">

**Author:** ![Marc](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/marc/32/11229_2.png) [@Marc](https://community.homey.app/u/Marc)\
**Post date:** [March 2, 2019, 9:54pm UTC](https://community.homey.app/t/guide-to-connecting-gbridge-to-homey-for-google-assistant/9234/192 "2019-03-02T21:54:16Z")

</div>

But nothing is happening if I switch the light on with Google Home

---

<div class="post-metadata">

**Author:** ![Camelen](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/camelen/32/9613_2.png) [@Camelen](https://community.homey.app/u/Camelen)\
**Post date:** [March 2, 2019, 9:54pm UTC](https://community.homey.app/t/guide-to-connecting-gbridge-to-homey-for-google-assistant/9234/193 "2019-03-02T21:54:56Z")

</div>

What are your settings in MQTT hub? Do you have “Homie convention” or “Custom”? Homie convention does not work with gBridge anymore.

---

<div class="post-metadata">

**Author:** ![Marc](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/marc/32/11229_2.png) [@Marc](https://community.homey.app/u/Marc)\
**Post date:** [March 2, 2019, 9:55pm UTC](https://community.homey.app/t/guide-to-connecting-gbridge-to-homey-for-google-assistant/9234/194 "2019-03-02T21:55:15Z")

</div>

Have Custom

---

<div class="post-metadata">

**Author:** ![Camelen](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/camelen/32/9613_2.png) [@Camelen](https://community.homey.app/u/Camelen)\
**Post date:** [March 2, 2019, 9:57pm UTC](https://community.homey.app/t/guide-to-connecting-gbridge-to-homey-for-google-assistant/9234/195 "2019-03-02T21:57:14Z")

</div>

You say that you see gBridge MQTT get true/false while Google Home sends 1 / 0.  
These two commands should not be on the same topic.  
Google Home should send 1/0 to  
gBridge/u123/LAMPNAME/onoff/set

while homey should change the state of  
gBridge/u123/LAMPNAME/onoff

Did you put the /set on the correct topic in gBridge settings? ACTION topic.

---

<div class="post-metadata">

**Author:** ![Marc](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/marc/32/11229_2.png) [@Marc](https://community.homey.app/u/Marc)\
**Post date:** [March 2, 2019, 10:00pm UTC](https://community.homey.app/t/guide-to-connecting-gbridge-to-homey-for-google-assistant/9234/196 "2019-03-02T22:00:52Z")

</div>

Thanks @Camelen that was it, i set it the wrong way…

---

<div class="post-metadata">

**Author:** ![Camelen](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/camelen/32/9613_2.png) [@Camelen](https://community.homey.app/u/Camelen)\
**Post date:** [March 2, 2019, 10:01pm UTC](https://community.homey.app/t/guide-to-connecting-gbridge-to-homey-for-google-assistant/9234/197 "2019-03-02T22:01:12Z")

</div>

The default of gBridge is the wrong way so it’s a very easy mistake to make.

---

<div class="post-metadata">

**Author:** ![Marc](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/marc/32/11229_2.png) [@Marc](https://community.homey.app/u/Marc)\
**Post date:** [March 2, 2019, 10:01pm UTC](https://community.homey.app/t/guide-to-connecting-gbridge-to-homey-for-google-assistant/9234/198 "2019-03-02T22:01:49Z")

</div>

Do I need a payed account to add all my devices in Google Home?

---

<div class="post-metadata">

**Author:** ![Camelen](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/camelen/32/9613_2.png) [@Camelen](https://community.homey.app/u/Camelen)\
**Post date:** [March 2, 2019, 10:02pm UTC](https://community.homey.app/t/guide-to-connecting-gbridge-to-homey-for-google-assistant/9234/199 "2019-03-02T22:02:15Z")

</div>

Yes. The free account only gives you four devices.

---

<div class="post-metadata">

**Author:** ![Fire69](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/fire69/32/8758_2.png) [@Fire69](https://community.homey.app/u/Fire69)\
**Post date:** [March 2, 2019, 11:23pm UTC](https://community.homey.app/t/guide-to-connecting-gbridge-to-homey-for-google-assistant/9234/200 "2019-03-02T23:23:15Z")

</div>

Soo… small problem. When you turn off the normalize, gBridge gets filled up with the wrong device names =\> Woonkamer Klein instead of woonkamer-klein… 😐

---

<div class="post-metadata">

**Author:** ![KonradWalsh](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/konradwalsh/32/147_2.png) [@KonradWalsh](https://community.homey.app/u/KonradWalsh)\
**Post date:** [March 2, 2019, 11:37pm UTC](https://community.homey.app/t/guide-to-connecting-gbridge-to-homey-for-google-assistant/9234/201 "2019-03-02T23:37:46Z")

</div>

So can you change the names now in gBridge to match

[Previous page](https://community.homey.app/t/guide-to-connecting-gbridge-to-homey-for-google-assistant/9234.md?page=9)

[Next page](https://community.homey.app/t/guide-to-connecting-gbridge-to-homey-for-google-assistant/9234.md?page=11)
