Gladys Assistant 4.84: External integrations are here 🚀

Hello everyone !

I’m really excited to release tonight a version that, I think, will really change the pace of the project’s evolution.

External integrations are finally coming to Gladys! They will allow us to enrich the list of compatible devices and services much faster, while allowing everyone to develop and share their own integrations.

I explain everything in this article :backhand_index_pointing_down:

Indeed, I think this development is a turning point in Gladys’ life. This missing piece that was slowing down the software’s opening to a wider audience (especially from HA) is, in my opinion, the beginning of a major paradigm shift.

Thanks to all the developers, thanks to Antrhopic ^^ and let’s get the tests started!!!

I have a practical question about the migration


If I switch from the original Tuya integration to the new, external one, what happens to my data? The devices need to be recreated in the new integration, but is it possible to replace them directly to avoid losing their consumption data and related scenes? Or do we treat it as if it were new equipment?

Second thing, for information, the Telegram migration worked perfectly! Well done!

We’ll need to add a button to disable the old Tuya later


Excellent work anyway! What an evolution!

For info, Telegram migration:

Copy the key from the old integration and paste it into the new one.

Deactivate the old integration.

In the new integration (community), click on â€č link my account â€ș and copy the provided code.

Open Telegram and paste/send the code in your Gladys channel.

That should be it!

Hi @GBoulvin!

There is no automatic migration procedure planned to switch from internal integration to external integration.

However, if this is really a blocking point for you and you already have a lot of data configured, we can look together in private how to migrate them. :blush:

Given the low number of users of the original Tuya integration, I don’t think this justifies developing an automated migration process.

Super new version and thanks for the work :slight_smile:
However, for the Telegram integration, I was able to migrate with my main user and link the account
However, the integration does not appear for a regular user and I don’t know if this is normal, especially since the Telegram that will be deprecated appears on both :wink:

Great to hear back! I’ll look into fixing it :grinning_face_with_smiling_eyes:

I was asking the question in general
 Netatmo, Melcloud, and others are affected. Data isn’t too much of an issue for me, but in the scenes, it’s a bit annoying because it’s difficult to find out in which scenes a device is used to modify it. I think there was a feature request for that though


Edit: here: https://community.gladysassistant.com/t/determiner-dans-quelle-scene-apparait-un-device

I’ll figure it out, no problem!

Thanks again for this development!

Super evolution all that, but just one question about Ewelink, still nothing?

Thanks anyway for all the work, even if I don’t use a quarter of a quarter of it

Super MAJ, I’m impressed by the work done!

I think this will indeed give Gladys a boost, it’s really great.

I started installing Telegram, it’s really well done, easy and transparent for the user. No need to know about Docker etc :slight_smile:

I love the supervision and logs tabs, it’s really well done

I’ll show you the external integrations and how to create one (without writing a single line, with Claude):

@pierre-gilles what do you recommend for integrations that exist both â€č internally â€ș AND externally: should we stick with the internal one? Is it better to switch to the external one?

@pierre-gilles explains the future here: Intégrations externes dans Gladys Assistant - #104 par pierre-gilles

Thanks @mutmut, I had missed this explanation.

I’ll add a migration system, you’re right :slight_smile:

Basically, you’ll just need to configure the new integration and add all your devices, then from the old integration, there will be a « migrate Â» button on each device that will ask you to select the destination device, and it will migrate:

  • Scenes
  • Dashboards
  • History

Would that work for you? :slight_smile:

That sounds great to me!

For those interested, the spec is defined here: Gladys/docs/specs/device-migration.md at claude/native-integrations-migration-ed6m34 · GladysAssistant/Gladys · GitHub

The PR: