New plugin pimatic-gBridge

---

This plugin is obsolete because the gBridge service has stopped!

A plugin for connecting your Pimatic system to Google Assistant.
When you add a supported Pimatic device to the gBridgeDevice devicelist, the device is automatically added in gBridge and Google Assistant.
The plugin uses gBridge as gateway between Pimatic en Google Assistant. Its not exposing all devices to the Google Assistant, but only the ones you select.
UPDATE release (v.0.2.14) supports the following features:

• Support of Switch, Dimmer and ButtonsDevice based Pimatic devices
• Manual addition/configuration of pimatic devices to be controlled by Google Assistant
• Acknowledgement for actions (Assistant ask “are you shure …”)

UPDATE release (v.0.3.5)

• Support of Miligtht, Contact, Shutter, DummyThermostat and Temperature/humidity Devices

You can use

or google assistant app
or google home app

to control

If you want, please test it and let me know if anything breaks or features are missing.

Hi,
first happy X-Mas! Second thx for this plugin.

I have installed it and it works with the one test device I create. It works unexpected fast.
I think you can avoid the long confirmation sentence of google: “Okay, I will switch BLA on/off”?

Would be nice when you could add button devices, if possible.

Nice that is works!
The confirmation sentence is something the Assistant does by itself and is not configurable in the plugin.
A button device type is not supported by gBridge. The switch device is the closest to a button.
The via gBridge supported devices are: Light, Outlet, Switch, Scene, Thermostat, Fan, AC, Purifier, Sprinkler, Door, Blinds, Shutter, Dishwasher, Dryer, Vacuum, Washer, Camera. Light (outlet/scene) and switch are supported

With an extra switch device and an extra rule in Pimatic you could emulate a button. But the GA command would still be “Hey Google, <device name> on”.

The idea would be the way like it works on the Echo-Plugin.
Cloud site it is a switch, but plugin internal the on command activates the button. The off command do nothing. Sure it can be done by rule and a dummy switch or similar, but it would be more elegant via a internal plugin function.

Yes, that’s the way to do the emulation in the plugin. I will give it a try and let know when its available

I now changed to the standard subscription for unlimited devices to have a better comperation between Echo and Google for daily use.

One thing that is not clear from the plugin description and which is a killer feature from my point of view. After you create a new “device” within the “GbridgeDevice” the device gets automatically transferred to Google Home and can be used within seconds. This is really cool. After I start to use the plugin I thought I have to create a device in the gBridge online portal and then I have to create a device in the GbridgeDevice with the same name as I used in the portal.

I am really happy with this plugin!

@bertreb: Regarding the MQTTS, is it recommended to use it? If so can you help me/use to get it running?

I have released version 0.2.14 with support of ButtonsDevice.

MQTTS is preferred and will lookup how I configured it my my rpi. There’s also enough info on installing the certificates on a rpi. It’s a bit of a puzzle to solve but good to understand for yourself.

Hey bertreb,
the update works with buttons now. Nice that each button of a device can be used.

Both buttons can be used for an action in Google Home!

Regarding MQTTS. I suppose my config is different to yours. I have a rpi with nginx which is linked to my thin client PC where pimatic is running. I would like to have the necessary certs for MQTTS as well on my rpi and not on the machine where pimatic is running. No idea if this can be handled easily.

One more idea, but surely not that easy. What about returning variables from devices like number (e.g. temp) or strings?

Example: “What is the state of the front door?” or "What is the temperature of the living room?"
Do you know if this is somehow possible?

Did you try ask GA for the status of a device?

Yepp I did. The state of a switch will be returned, but no dimm state.

Due to the fact that your plugin does not supports variable devices (yet) I can’t test it. I have not other native GA devices which contains texts which could be returned back.

Maybe I found a bug. When I try to delete a device from the gBridgeDevice I get this message:

Hi, what was the device type you deleted?

In the first try it was a variable device. I want to check the response of GA for it. But the gBridge device gets not online with it. So I change to a dimmer I havn’t yet configured for gBridge. But even with this device it cant be deleted. It was the first time I try to delete some stuff.

@ortin I found the bug. Release 0.2.15 fixes this.

Nice you are really fast. Today I had some time and tried out the MQTTS stuff. But I havn’t luck. I didn’t get it to work.

My pimatic system is remote accessible via HTTPS (certs via Let’s encrypt). The certs are localed on a different hardware, where the nginx reverse proxy is running. The environment contains a MQTT server (pimaitc mqtt plugin). My hope is to get it to work how it is descripted here…

@ortin said in New plugin pimatic-gBridge:

In the first try it was a variable device. I want to check the response of GA for it. But the gBridge device gets not online with it. So I change to a dimmer I havn’t yet configured for gBridge. But even with this device it cant be deleted. It was the first time I try to delete some stuff.

As far as I understand a variables device is not supported by GA and gBridge. Only the variables(states) related to a ‘normal’ device are supported.
If I look in the Google Home app, I can see the state and dimlevel of a dimmer.
But I can’t find any command to ask GA to give me the dimlevel.

Maybe I understood the MQTTS stuff wrong or I am thinking to complicated.

I changed the mqttProtocol to MQTTS. The mqttServer is untouched. My GbridgeDevice is online. Is this meaning that gBridge is really communicating over a secured connection?

This is my current config:

In the gBridge docu I found this:

This sounds to me that it should be secured, but you surely really know if it is like it sounds.

You get an error if the mqtts connection fails.
So it seems like you have the certificates installed in /etc/ssl/certs/ and mqtts is working.

@bertreb: Did you recognized as well, that the service seems to be down today (and maybe in future?). On Git a discussion starts about the end of the project… Really bad news.

@OrTiN i didn’t noticed but indeed the server is down. I’m not using voice commands, so i’m what late in detecting gbridge outages. The gBridge server went down before. Its a not a good sign and there’s no info coming from gbridge.
Thats probably the price for a kickstarter with no/low prices