You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 18, 2023. It is now read-only.
great work with gBridge, I really do enjoy the experience!
Here's a problem that came up when I integrated my Tasmota-enabled Sonoff S20 power plugs with gBridge. I have a similar setup as the user in #11 and my problem might also have to do with the interpretation of topics between Tasmota and gBridge.
Here's my basis setup:
Tasmota-enabled device <--MQTT-unencrypted--> Mosquitto-Bridge <--MQTT-TLS--> gBridge <---> Google Home
As mentioned in #11 the prefix can be cmnd or stat and there is also the suffix POWER. Therefore, the resulting topics of my Tasmota are gBridge/uXX/cmnd/wallsocket/POWER and gBridge/uXX/stat/wallsocket/POWER as verified in the log of Tasmota and in the log of the Mosquitto bridge.
Google Home
Has been linked with gBridge and sees the device.
Problem
The setup described above seems to work just fine. Google Home sees the device in gBridge. The bridge also works and successfully connecty the Tasmota to gBridge. I can toggle the light in the Google Home app or via voice commands.
However, Google Home always reports the light as being turned on. I can toggle it off but as soon as i close the Home app and reopen the device it is again shown as switched on. Therefore, I think the issue is with the status topic.
gBridge does not interpret the result of the status topic correctly? The gBridge Docs state that for the onoff trait, the values 0, off, false, as well as 1, on, true are allowed. However, In the logs of my Tasmota it says MQT: gBridge/uXX/stat/wallsocket/POWER = OFF. I know that topics are case senstive. But are results also case-sensitive?
Something else entirely since I am kinda new to the the MQTT protocol.
Do you know what could be the issue? Can you suggest ways how I can better debug what went wrong?
Thanks in advance!
The text was updated successfully, but these errors were encountered:
@peterkappelt hi
i tried with many configurations and still cant make it work :(
is ther any logs for gbridge? mosquito is connecting but its not working in goolge home, any reaction.
Hi Peter,
great work with gBridge, I really do enjoy the experience!
Here's a problem that came up when I integrated my Tasmota-enabled Sonoff S20 power plugs with gBridge. I have a similar setup as the user in #11 and my problem might also have to do with the interpretation of topics between Tasmota and gBridge.
Here's my basis setup:
Tasmota-enabled device <--MQTT-unencrypted--> Mosquitto-Bridge <--MQTT-TLS--> gBridge <---> Google Home
Setup
Here are my configs:
Tasmota
As mentioned in #11 the prefix can be
cmnd
orstat
and there is also the suffixPOWER.
Therefore, the resulting topics of my Tasmota aregBridge/uXX/cmnd/wallsocket/POWER
andgBridge/uXX/stat/wallsocket/POWER
as verified in the log of Tasmota and in the log of the Mosquitto bridge.Mosquitto
Nothing spectacular here. Compared to the section on bridge configuration in the gBridge Docs I only changed the
topic
to match my topic format.gBridge
gBridge was configured to match the Tasmota topics. I hope that I interpreted it correctly that cmnd is the action topic and stat is the status topic, see https://github.com/arendst/Sonoff-Tasmota/wiki/MQTT-Overview
Google Home
Has been linked with gBridge and sees the device.
Problem
The setup described above seems to work just fine. Google Home sees the device in gBridge. The bridge also works and successfully connecty the Tasmota to gBridge. I can toggle the light in the Google Home app or via voice commands.
However, Google Home always reports the light as being turned on. I can toggle it off but as soon as i close the Home app and reopen the device it is again shown as switched on. Therefore, I think the issue is with the status topic.
Possible things that could be wrong:
MQT: gBridge/uXX/stat/wallsocket/POWER = OFF
. I know that topics are case senstive. But are results also case-sensitive?Do you know what could be the issue? Can you suggest ways how I can better debug what went wrong?
Thanks in advance!
The text was updated successfully, but these errors were encountered: