New plugin pimatic-gBridge

---

@ortin nice that it’s working. The adapter expects a number (characters) as return value. That value should be the new position of the movement and the shutter is stopped.

The simply call of my script return the Shelly standard response like:

{
	"state": "open",
	"power": 0.0,
	"is_valid": true,
	"safety_switch": false,
	"overtemperature": false,
	"stop_reason": "normal",
	"last_direction": "close",
	"current_pos": 10,
	"calibrating": false,
	"positioning": true
}

Is a little bit more as only the number. But it works! The above mentions return value ({"status":"stop","position":"15"}) is the value which returns when I ask explicit only for the status of a shutter. Somehow you are handle it in the right way.

@ortin the return value is used to update the actual position when GA ask for the status.
But it looks like that part of GA and gBridge isn’t working.
Its better is use the right return value. I will make an update that can handle both return json’s

Made a few changes to process json return values (current_pos or position)
It compiles but i can’t test it, so let me know… It’s release 0.2.19

Still works like a charm!

Hi Bert, awesome job creating this plugin!

I’m using pimatic-milight-reloaded for my lights and so far I can turn them on/off and change the brightness.
Would it be possible to also integrate RGB color switching?

Another thing I would like to request is the control of the DummyHeatingThermostat.

@jarnoglenn thanks.
I will look into your request, but first I am going to ski the coming week in Austria

The plans changed a bit, skiing is for later this year.

@jarnoglenn I added the color option for Milight to the plugin (not published)
Which of the 4 Milight devices are you using?
The gBridge API doesn’t support yet automatic adding of color features via the API.
So if you want to use color management you need to add the color control via the gBridge device management portal (where also the API key can be obtained).
It’s not very complex. For your current Milight device you just add the Color Setting(RGB) trait (besides OnOff and Brightness). The new version of the plugin will than support color.
Let me know if that is workable for you, else we need to wait for gBridge to upgrade the API

@bertreb I’m using MilightRGBWZone and MilightFullColorzone.

I already figured out I have to manually activate the color control and automatic adding is not a priority for me.
I assumed the color values (html colors or rgb values) are passed but the plugin doesn’t know what to do with it because the function does not yet exist.

So if you can make it so the values are passed through to the light plugin i would already be really happy!

Sometimes I’m just a total nitwit so I’m afraid I need some basic help:

For some reason I cannot connect to the gbridge mqtt server.
“MQTT server Connection refused, not authorized”

Only thing I can think of is the tls certificate? Installed the plugin through the GUI, created an API key, copied it to the right place, left everything default except the mqtt username (gbridge-u***) and mqtt password.

Sorry for this dumb question, I guess I’m overlooking something…

@djmvt hi, are you using mqtt or mqtts? (you can select this in the plugin settings)

@jarnoglenn said in New plugin pimatic-gBridge:

MilightFullColorzone

You can update to version 0.2.20 and test MilightRGBWZone and MilightFullColorzone

@bertreb mqtt (everything on default)

@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

@bertreb

<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…

@bertreb

yes I just deleted the info on the forum post.
Cannot get it to work for some reason

@djmvt please explain. What did you delete?
And did you restart pimatic after an update/config of the plugin?

Did you try first do add a simple switch as sub device of gBridgeDevice?