It did not start to work when I installed it.
I’m trying to investigate myself as well and might have something but I need to check it myself first.
One possible problem I seem to have is that I cannot change the topic in MQTT hub to upper case. In this scenario we need it to say “gBridge/u123” but it always defaults to “gbridge/u123” for me whatever I do. I can change the topic to say something different though (i.e. gbridge/u1234) but it will always become lowercase and the broker topic is case sensitive.
Same as @Wout_F in the other thread. It started to work.
Also have the problem that I have created all devices in the gBridge connection with normalized names which means that everything needs to be adjusted.
It’s not that big of a deal and totally possible but I’d prefer if I somehow can choose to keep my devices normalized while also having the flexibility of connecting to brokers that don’t use normalized names. If one can come with suggestions =)
As in one thing I can control while the other I can not (since we’re not using our own broker).
Going to make the topic lowercase only when Homie Convention is selected and I won’t touch the topic case if Custom protocol is selected.
I came to the same conclusion in the other thread 
(Guide to Connecting gBridge to Homey for Google Assistant). Thanks @HarriedeGroot, that sounds like the perfect solution.
What’s the fun of discussing this problem in 2 topics? And then refer to the other topic? This is becoming very messy!
It is indeed a bit messy and not very obvious what fits in which topic.
When suggesting changes for an app it seems obvious to do that in the topic that is dedicated to the app in question. But in this case we found this “shortcoming” so to speak of the app while trying to connect to a 3rd party service.
At some point we needed (IMO) to migrate the discussion from the topic of the connection to the service to the topic of the app, right?
Going to make the topic lowercase only when Homie Convention is selected and I won’t touch the topic case if Custom protocol is selected.
Isn’t this the exact way it is handled now?
No, the full topic is being normalized when normalization is turned on, because it’s part of the Homie Convention.
This is changed with the introduction of the normalization option in the app settings.
Going to disable this for Custom topic only (won’t touch the formatting of a custom topic).
So?
Its just the way it worked out and now the threads are supporting each other…
You, on the other hand are interrupting the conversation with this
Version on the debug branch does not touch the Custom topic anymore.
So the Custom topic stays the same when Normalize is enabled, but the devices do get normalized?
Because that’s a problem (for me at least ) right now (see other topic 
)
Perfect 
Could you try it? And report back if this resolves your issue?
Well… I was going to go to bed, but what the hell, sure! 
Beta branch then?
yes
Harrie, a full changelog would have helped pick this up. (Ab)using the homie3 spec to support gBridge worked and there is nothing that mandates the root topic has to be normalised in the spec is there?
I feel we’re creating unnecessary frustrations here in using MQTT-Hub - it should be straightforward, yet this and the other thread are just full of issues for users.
