Virtual devices

[Archive] Feature request
1

Hello everyone,
My first request is about « virtual devices ». I know that with MQTT, we can do a good part of what I am going to explain, but… it’s not fully integrated into Gladys…

Being able to create virtual devices for more flexibility:

  • Create your own designs for devices that cannot be edited (e.g., Z-Wave)
  • Manage more complex scenes (e.g., a device with multiple states instead of the device itself being non-editable)
  • Trigger a scene by a device on the dashboard
    And the Jeedom documentation:
  • Consolidate information or actions from multiple physical/virtual devices into a single device;
  • Create a device powered by an external source (Node-RED…)
  • Duplicate a device to split it into two, for example
  • Perform a calculation on multiple device values

Finally, the field of vision will be wider.

2

Hello @syper!

I’ve read your message several times, I’m having trouble understanding what the MQTT integration doesn’t allow you to do! :slight_smile:

Maybe I’m missing something concrete?

3

Where does my first sentence come from :smiley: it’s more the integrated side of gladys that I miss, doing without mqtt we would also gain in lightness (?).

4

Integrated into Gladys? I don’t see the point :stuck_out_tongue:

The devices created in the MQTT integration are quite normal, and creating an integration that would just be a copy/paste of the MQTT integration with a different name won’t change much, except the name of the integration :slight_smile:

5

It’s not very clear, MQTT indeed.
And indeed, I would like it to be something like scenes, that is to say not an integration.

I just took a look, I suggested that because it seemed to me that it would install another Docker… But in fact no? I understand the responses better.

6

Hello @syper :wave:
I would be interested in your use case regarding this request?
Can you tell me more please

7

You can run a mosquitto container with this integration, it’s very lightweight, mosquitto.

After that, from what I remember, I don’t think the MQTT integration configuration is mandatory to create MQTT devices…

In any case, even if you run a mosquitto container and there’s nothing on the other side listening to this container, it doesn’t change anything :slight_smile: Hence the fact that it is already a « virtual » integration in a sense.

8

I don’t necessarily use it personally, I just know that some people do.

@pierre-gilles Yes, that’s right, this feature isn’t necessarily useful.

9

Sorry for being a burden ^^

Can you redirect me to a link where you saw that?

10

Official Jeedom documentation: https://doc.jeedom.com/fr_FR/plugins/programming/virtual/

I also know that I saw topics on the forum a long time ago so I would not be able to find the links.

11

I partially agree with the observation about the non-integrated side of Gladys regarding certain uses of the MQTT integration.

In my case, I have rather used this integration and its « virtual » devices to make « variables ».

I set a state to 0 or 1 in a scene, and I control this state in another scene.
I really use them as variables, and therefore this requires having an MQTT bus available.

I don’t know if there is a notion of a variable (not user-related nor linked to integrations) in the backlog?
Perhaps this has already been discussed and decided since I have not followed the exchanges on the v4 development this year.

12

I thank you, I will watch it when I have time!
Thank you again