Categorize integrations with tags and filters (Gladys Plus, Cloud, used, ...)

[Archive] Feature request
,
24

I would say a cloud tag and a local tag :wink:

25

I’m afraid it will be too heavy, I’ll test it

26

It can indeed be cumbersome when both are available for integration, but it also makes it possible to have only local or only cloud and to filter (if you want) on just one or the other.

Or we assume that if there’s nothing then it’s local, but if both are possible, we’ll only see cloud :frowning:

27

Hence the suggestion « local/cloud Â». Indeed, given that Gladys aims to be as « local Â» as possible, on my side it’s understandable not to list the local-only integrations ^^

28

Final proposal (simple at first without filters)

  • Gladys Plus = may require a Gladys Plus subscription
  • Cloud = dependent on an external cloud service (will therefore not work without Internet)
  • Local = can operate without communication outside the local network, works without Internet

gladys_integration_tags
gladys_integration_tags2426×1502 267 KB

It’s been pushed here Feat integration tags by cicoub13 · Pull Request #2481 · GladysAssistant/Gladys · GitHub

29

I really like it, and the colors are very well chosen :star_struck:
vert : no problem locally, the indicators are green
jaune : there may be issues with the cloud so yellow but not red (red is scary!)
gladys plus : blue is social and it’s the sky, so a bit of cloud, but good cloud :sweat_smile:

30

Super clean,

Top-notch

31

I’ve taken into account the feedback on the PR
Here is the final result

Integration Local Cloud Gladys+
Devices
RTSP Camera :white_check_mark:
Xiaomi :white_check_mark:
MQTT :white_check_mark:
Zigbee2MQTT :white_check_mark:
Philips Hue :white_check_mark:
Tasmota :white_check_mark:
TP-Link :white_check_mark:
Bluetooth :white_check_mark:
eWeLink :white_check_mark:
OwnTracks :white_check_mark:
Broadlink :white_check_mark:
Nuki :white_check_mark: :white_check_mark:
Enedis :white_check_mark: :white_check_mark:
LAN Manager :white_check_mark:
Tuya :white_check_mark:
MELCloud :white_check_mark:
Node-RED :white_check_mark:
Matterbridge :white_check_mark:
Netatmo :white_check_mark:
Sonos :white_check_mark:
Z-Wave JS UI :white_check_mark:
Google Cast :white_check_mark:
AirPlay :white_check_mark:
Matter :white_check_mark:
Energy Monitoring :white_check_mark: :white_check_mark: :white_check_mark:
Calendars
CalDAV :white_check_mark: :white_check_mark:
Communications
Telegram :white_check_mark:
Nextcloud Talk :white_check_mark:
Alexa :white_check_mark: :white_check_mark:
Google Home :white_check_mark: :white_check_mark:
HomeKit :white_check_mark:
OpenAI :white_check_mark: :white_check_mark:
Free Mobile :white_check_mark:
CallMeBot :white_check_mark:
MCP :white_check_mark: :white_check_mark:
Weather
OpenWeather :white_check_mark:
32

To be honest, with this integration, I find that it becomes more confusing than showing nothing at all :slightly_smiling_face:

Energy monitoring works entirely locally in the vast majority of cases.
The only exception is for the EDF Tempo contract, where an external call is made to retrieve the color of the day.

Apart from that, everything works 100% locally.

So, even the “Cloud” label, I’m not convinced it’s relevant here

And “Gladys Plus”, definitely not: it’s not used at all for energy monitoring.

33

I’m not very familiar with this integration (it’s recent), but the documentation lists Enedis (via Gladys Plus) as an option. So it falls squarely under the Cloud and Gladys + tags

That said, I agree with you, the presence of all three tags brings more confusion than information.
Should I only put Local? Or nothing at all?

34

Yes, I see what you mean :+1:
In fact, the documentation mentions the Enedis integration as a possible data source, and this does indeed go through Gladys Plus.

But the « Energy monitoring Â» integration itself remains 100% local in its operation.

I would simply put « Local Â», that seems the clearest and most representative in this case :slightly_smiling_face:

Thanks!

35

It’s been pushed :white_check_mark:

36

Thanks @cicoub13, it’s good for me, it’s merged and it will be included in the next version of Gladys! :slight_smile:

37

This feature is live in Gladys Assistant 4.72: