@bertreb mqtt (everything on default)
-
New plugin pimatic-gBridge
-
@djmvt when everything is default no tls is used. Your setup is the simplest and should work. Unfortunately the gbridge mqtt server is sometimes offline but this error message indicates there is still communication.
Could you post the gbridge plugin config info from the config.json file?You could also try a mqtt tester like MQTT.fx to test if the mqtt server is connecting
-
<code>
{
“gbridgeApiKey”: “***************************************************************************************************************************************",
“mqttUsername”: "gbridge-u",
“mqttPassword”: ".”,
“plugin”: “gbridge”,
“active”: true
}
</code>this is how the plugin code looks (dashed the info ofcourse)
-
@djmvt thats should be good, just to double check.
- for the mqttUsername there should be digits behind gbridge-u
- mqttPassword is probably not a “.” You can set a new MQTT password in gBridge portal to be sure
- you can generate a new API key and copy that exactly to the API field in de config
-
Did you create an MQTT Password on gBridge.io? I assume that behind
gbridge-u
there is a four-digit ID in your plugin config. If so an you put the full API key into the config it should work. Try MQTT first to ensure it legs not on the certs.EDIT:
Damned bertreb was little faster… -
yes I just deleted the info on the forum post.
Cannot get it to work for some reason -
Did you try first do add a simple switch as sub device of gBridgeDevice?
-
@bertreb deleted my username, password and apikey before posting on the forum.
yes i did restart pimatic after updating and configuring. -
@ortin absolutely, thats when the errors started because the plugin doesn’t connect with gbridge (authorization error).
-
And your subscription type is “free”
-
@djmvt said in New plugin pimatic-gBridge:
@ortin absolutely, thats when the errors started because the plugin doesn’t connect with gbridge (authorization error).
Thats logical because the plugin starts connecting when the first pimatic device is added to the gbridge device
-
@bertreb said in New plugin pimatic-gBridge:
MQTT.fx
Just tried to connect to the MQTT gbridge server with the same credentials as in my pimatic plug config, no problem at all!
Strange… -
@djmvt strange, but it could be hopeful
Could you post the debug/error log when you have enabled the debug in the plugin.
And just to check are you running version 0.2.19 or 0.2.20 of the plugin? -
@bertreb Well as a famous old saying in Dutch “schiet mij maar lek” it seems to work now.
Deleted the plugin and device, re-installed the plugin, entered the exact same settings, created a new gbridge-device and there it is!
Now to see how to configure the device: it’s a “klikaan klikuit” switch. I can turn it on by saying “hey google zet de keukenlampjes aan” but when trying to turn it off google responded with “it looks like this device is not configured yet”.Thanks for assisting so far!
-
@djmvt deleting and reinstalling would have been my last advice
You must be more specific with the ‘smart’ assistant. My experience that “Hey google… keukenlampjes aan” is the way assistant works.
The device should be visible in the google home app. If not you could try reload the page in ge Home App. In the app you can also control/test the device.
In gbridge.io the device should be visible with the name you gave it, with the device type ‘switch’ and ‘onoff’ trait. -
@bertreb ah yeah that works. The assistant is indeed picky with the “zet de” phrase.
Thanks for the help! Looks like connecting Google assistant and pimatic is getting better and better.
Now for a simple way to do the opposite: use pimatic to switch on tuya devices hahahaha. But that’s another story. Thanks a lot for your help, learning every day! -
@bertreb Color switching works like a charm! Thank you very much!
The only minor issue is I can’t change the lights back to white.
Whenever I use the google color picker or voice commands to set the lights to white I can read in debug it translates to #FFDEAD which should be #FFFFFF for milights to be changed to white. But this probably should be changed in the gBridge API I guess?