Upgrade to Gladys v4: where is my FGD-212 to put it in a scene to turn the light on/off?

Configuration
1

Hello everyone,

I finally have time to migrate from v3 to v4 :grin:

I have just integrated all the Xiaomi side (gateway/sensors/buttons/etc…) and for this part, I just need to identify which opening sensor corresponds to which door/window, because I have a lot :sweat_smile:

But I am having a problem with the Z-wave side… And since I have been searching for 1 hour, I think I will ask the pros here to not waste more time :wink:

My Z-wave outlets are recognized and working, the FGD-212 also (since if I want, I can add it to the home screen and see the consumption in real time), but I don’t see how to integrate the latter into a scene to turn the lights on/off…

In the « Scenes » tab, I:

  • Choose my trigger (Xiaomi button for example)
  • Give a value « equal to » (2 for example)
  • Click on « New Action »
  • List « action type » => « Turn on the light » and in the list of lights, only the Xiaomi gateway (which, by the way, does not light up if I test) appears… No trace of the FGD-212…

Did I miss something somewhere? Because I have looked at the whole list of actions and everywhere else, and I find nothing… :thinking:

Thanks for reading!

2

The FGD-212 is a multilevel and not a binary switch, in my opinion that’s why

EDIT: I misread, you also looked in the switches

3

I’ve looked through all the items in the dropdown list, I couldn’t find the FGD…

I was ordering it with v3… It must be somewhere in v4… :thinking:

4

Yes, it is available on the dashboard but not in the scene actions (this needs to be developed)

5

Damn… :scream: This is one of (if not the) things I use the most with Gladys… :worried:

I can’t wait for development to resume on this point! Otherwise, I’ll have to go back to V3 until it’s back…

6

What is the missing feature exactly?

Don’t hesitate to create a feature request on the forum (Demande de fonctionnalités - Gladys Assistant community) @Retlaw, that’s how we work on the v4

7

Hello @pierre-gilles!

Since Covid has taken up all my time these past few months, I haven’t had time to see how the forum and Gladys have evolved. Thanks for the info on how to do it regarding V4 :wink:

To answer your question about the missing feature: When I want to create a scene « a trigger » then « an action », I unfortunately don’t find my Fibaro FGD-212 that controls the lights in my living room in the actions.
I find my Z-wave outlets in the list of outlets (logical), but not the Fibaro in the list of lights (It doesn’t appear in any list either)
Yet I was controlling the latter in V3.

I will therefore post a request in the dedicated section of the forum :wink:

Edit: Oh, I think I understand that it’s a voting system for integrations? So if there are no or few votes, no integration??

8

It’s more about priority, it doesn’t mean it won’t be developed :slightly_smiling_face:… Example with the tuya service which has quite a few votes and yet other services arrive before, I think it’s more related to the developer of the service, if he doesn’t have tuya for example, it won’t be a priority for him.

9

Thanks @Jean34, I understand better.

But judging by the Zwave topic, the developer (Romuald it seems) has little time according to his latest message… so I won’t be able to control my living room with my Xiaomi buttons anytime soon… :worried:

So I’ll probably go back to v3 for now :disappointed_relieved: (I should have checked if everything was available on v4 before migrating… :man_facepalming:)

10

Set a value via scenes

11

Yes, something like that for example :slightly_smiling_face:

If such action is taken then send such value to such device.

12

So if I understand correctly, your FDG is not a binary device, it’s not « on/off », it’s more like 0 to 100?

The control via the interface on the dashboard works, but the same control slider is missing in the scenes?

If that’s the case, I’d be happy to have a feature request to prioritize that :+1:

You are hundreds like you who have feature requests, without necessarily being a developer to help contribute, so the ratio of « developer to feature requester » is very low. We have a list to prioritize developments as time is limited for everyone.

13

That’s it, it’s a dimmer. (I don’t remember if it’s from 0 to 100 or from 0 to 255 though… :shushing_face: )

It is actually recognized as such natively by Gladys during integration via the Z-wave module.

:shushing_face: That’s almost it:
I can indeed adjust the intensity via a slider on the Dashboard without any problem (the slider even moves to the correct position when I turn the lights on/off from a classic switch)

But saying that a control slider is missing in the scenes, I don’t know. For me, a free field allowing to enter a numerical value would probably be easier, but if a slider is easier on the development side, it should have the same result I think.

(concrete example of what happened in v3:
I use Xiaomi buttons (100% operational in v4) that allow 3 types of clicks.
I therefore made scenes like: If so many clicks on Xiaomi button, then send value XXX to the Fibaro. And I put the values off/on/half to have 3 light intensities.
In use, it gave 1 click = the light was at max, 2 clicks = dimmed light, long click = light off)

I don’t know what would be easiest for you to integrate into a scene to send a value to the FGD, free field or slider…

We therefore seem to be talking about the same thing.

It would be cool to create a feature request!! :grin:

If testers are needed, I am obviously available with great pleasure!

I don’t doubt it for a moment rest assured! What you do is already simply amazing! :clap:

My question was more to know what I should do: go back to v3 and recover all the functions of Gladys or stay in v4 and wait a bit to recover this functionality (which, I think, will not apply only to the Fibaro FGD-212 but to all non-binary devices)

14

I invite you to do it, it’s you who needs this feature :slight_smile:

You can do a hybrid version while waiting:

Move as much as possible to v4 to be on v4, but keep your Fibaro in V3 and use the Gladys v3 HTTP API that you would call in the Gladys v4 scenes with the « HTTP request » action.

The documentation:

15

I already thought about that, but I can’t do that. Because in this case, I would have to switch the entire Z-wave part to Gladys v3 (since I only have one Z-wave dongle and I don’t just have the Fibaro using this technology) and currently, I unfortunately don’t have any RPi available to run a V3… :worried:

Arf, so it’s a lost cause for me… :worried:
I looked quickly and it seems that you need to propose code to integrate into Gladys. However, I don’t know enough about github and/or don’t have enough coding knowledge to create such a request… :pensive:

I will therefore have to switch everything back to v3, too bad… :disappointed_relieved:

16

He was talking about a feature request on the forum :wink:

Is it not possible to put Gladys 3 on a Docker container, on the same machine as Gladys 4? @contributors

17

Ah!! :man_facepalming: I’m an idiot! (I was also thinking Pierre Gilles’ request was surprising! :sweat_smile:)
But from this angle, it’s already done :wink:

18

Great! I’ve edited your feature request to make it generic and not specific to Z-Wave.

19

:+1:

It’s true that I’m not the only one to have noticed this problem with v4.

20

The problem is that access to the serial port is exclusive (the first container started will have access to the Z-Wave dongle)