and which version of MQTT Hub have you installed?
I am guessing you have the HA version?
and which version of MQTT Hub have you installed?
I am guessing you have the HA version?
Ha-branch from cli/github.
Check that you wrote window-lights in gbridge and not window-light which you said in the other thread.
Edit: looks correct from the log I guessā¦
Do you have /set on the correct topic in gbridge? On the ACTION topic?
Nvm it looks correct in MQTT Explorer.
My tip would be restarting client and then Hub in that order. Not sure what else to do.
Can you confirm that when you use MQTT-Explorer to manually change the state of the lights by using the āsetā topic that they do change state ?
I would also use the HA github branch (it wonāt matter that you donāt use HA)
Setting are wrong on gbridge. Switch place of /set to ACTION topic!
Thank youā¦ that was the caseā¦
Sorry it took so long guys but thank you so so much for helping me out
Glad you got there. The action/status topics are a bit confusing as to which should use ā/setā I think.
One thing - I have noticed the gBridge cloud MQTT broker significantly slows things down - and of course makes Internet connectivity necessary , but as it is for Google use I suppose thatās less of a concern. For an easy to setup Google integration this will suit most people but I still recommend bridging a local MQTT broker to gBridgeās just for the gBridge topics. Thatās detailed on the gBridge website here.
https://doc.gbridge.io/firstSteps/mqttServer.html#using-own-mosquitto-as-a-bridge
Thanks
I would say the confusion of the ā/setā comes from gBridge defaults to the /set being on the status line not the action line
Yeah if you intend to use node red or openhab you should probably bridge. If you only want Google home native then this is great since you donāt need additional hardware.
I have a room full of extra hardware but I just moved house so for me now, this is the best solution. Long term I do agree with you view
Actually that is very valid - I tend to forget I have an external MQTT broker just lying around awaiting some company - and I donāt think the internal Homey MQTT broker would support bridging. Even if it did there would be a speed hit anyway so this is a good solution as it requires no extra hardware.
@KonradWalsh - yes - I know about that ā/setā usage in the gBridge defaults - it caught me out first time too.
K
Hey guys,
Iām pretty new to mqtt, only configured it once to use OwnTracks.
Could someone make a very short tutorial to get me going with this?
Is this running purely on Homey and gBridge now, or do you still needs something like a Raspi?
What apps should be installed?
Thanks!
I will write a guide in the coming days, when I feel like I have the time.
Someone else is entirely free to do it before me.
Homey apps needed are
MQTT Client
MQTT Gateway/Hub
And you need an account on gBridge.
You no longer need a raspberry pi to make this work.
Edit:
a VERY short tutorial is:
Thanks, that should get me started
You will not have dimming capabilities until MQTT Hub gets updated or if you install it via CLI/Github and use the HA-branch. But On/Off works.
As a way to give backā¦ I wrote a guide. (@Fire69)
I decided to amend this topic and edit my first post
Let me know if I missed anything
oops ā¦
@KonradWalsh Thanks for the guide! More manual work then I imagined it would be
2 questions: