Connect Frigate to Gladys Assistant

Configuration
1

@guim31 and those who use Frigate, have you been able to interconnect to Gladys via MQTT?

I’d like to have an alert in case of motion and it’s possible in Frigate’s configuration, but the MQTT topic configured in Gladys doesn’t seem to match what’s being sent. So Gladys doesn’t see anything.

2

Go through Node-RED otherwise :slight_smile:

3

I also use Node-RED.

4

@lmilcent I’ve split these discussions into a new thread so as not to interfere with the camera live alpha :slight_smile:

How does this MQTT alert for motion on Frigate work? If there’s a way to integrate it into the MQTT integration, it would allow doing it without Node-RED — that could be cool!

1 Like
5

Yes, exactly. Frigate can send an MQTT message on a predefined topic (and not changeable as far as I know).
However, when I configure an MQTT device in Gladys it gives me a different topic specific to Gladys. I don’t think I can tell Gladys which topic to use.

6

What is the topic and what is the message format?

7

frigate/<camera_name>/motion

Whether camera_name is currently detecting motion. Expected values are ON and OFF. NOTE: After motion is initially detected, ON will be set until no motion has been detected for mqtt_off_delayseconds (30 by default).

8

Ok that’s very clear :slight_smile:

Indeed, in the short term Node-RED is the best option.

In the long term, two options (which are not mutually exclusive):

  • Create a Frigate integration in Gladys. You’ll need to listen to the Frigate topics on MQTT and then publish the right events to Gladys / manage scene triggers.
  • Offer a scene trigger « When an MQTT message arrives » that allows listening on a custom topic and reacting to that message.

Edit: Well, after looking at the Frigate product, I realize that it remains a very, very developer/geek product; I don’t know if a native integration into Gladys makes sense because it’s not self-service

1 Like
9

Hi @pierre-gilles
Would it be possible to offer an editable list in Gladys to map « external MQTT topic » to « Gladys MQTT topic » and vice versa? It would be simpler and more universal, right?
That way Gladys would subscribe to the external MQTT topic and publish to a Gladys-formatted topic, and then Gladys would interpret it as intended

10

This is clearly the solution for MQTT integrations. It makes it possible to do without dedicated services for more or less geeky setups.

Frigate is really great but it’s a shame that you have to do the configuration directly in text files. That makes the product less accessible to the general public.

11
12

I prefer the scene :slight_smile:

Because the topic is one thing, and the message content is another. MQTT is like HTTP, it’s just a protocol, but inside each client puts what it wants.

The advantage of creating a scene is being able to react to a particular topic AND message, even to use the message content in the rest of the scene via a variable.

@lmilcent Thanks for the request!

1 Like
13

Let’s say this lets you distinguish the system configuration part from the home-automation scenarios part
We configure once the adaptation of external Gladys messages <=> external Gladys, and the scenarios won’t