Gladys Assistant 4.84.1: Fixes after external integrations!

News
1

A small patch release, but with some pretty nice new features :slightly_smiling_face:

:sparkles: New Features

  • Migration of devices for deprecated integrations (#2737): a « Migrate » button now appears on Netatmo, MELCloud, Tuya devices, and now Philips Hue and TP-Link (which are now deprecated in turn). In one click, Gladys moves the device’s history to its replacement in external integration, rewrites your scenes and dashboards, takes over the room and energy contracts, then deletes the old device. Feature mapping is automatically proposed and remains adjustable one by one before validation.
  • New « storage battery » feature category (#2682): to properly retrieve your home batteries, especially via MQTT.
  • Zigbee2MQTT: support for the SONOFF SWV connected water valve (#2631).
  • Communication external integrations are visible to non-admin users (#2739): each user can now link their own account on an installed communication integration, as was already the case with Telegram. Shared configuration, hardware, logs, and store remain reserved for admins.

:wrench: Improvements

  • RTSP Cameras: the HLS stream now starts as close to live as possible (#2698) — less latency when opening a camera.
  • AI Assistant: sensor values passed to the model now indicate their age (#2731), to prevent an outdated value from being presented as current.
  • Clearer error messages when creating a discovered device (#2733).
  • Startup: Gladys now waits for external integrations to connect at boot (#2727).
  • API host of integrations: the JSON body size limit goes up to 5 MB (#2732).

:bug: Bug Fixes

  • Backup: fix for a memory overflow (OOM) during backup export, by limiting the memory used by DuckDB (#2722).
  • Bluetooth: correct cleanup of the scan timer (#2725).
  • Energy consumption: validation and bounding of dates in the consumption tool (#2740).
  • FR Translation: « dashboards » and not « dashboards » (#2729).

:folded_hands: Thanks to Contributors

@Will_71 and @Terdious :blue_heart:

:backhand_index_pointing_right: Full release notes on GitHub

2

Magnificent!

1000012646
10000126461018×719 84.2 KB

Thank you!

3

It’s magical right now :sweat_smile:

4

Thank Fable 5 :eyes::joy:

5

Wouldn’t he know what to do for Synology users? :eyes:

6

I replied over there :slight_smile:

7

I must have missed something for Netatmo because I didn’t get any Migrate button :roll_eyes:

image
image898×812 60.7 KB

Do I need to have the internal integration still active? (linked to netatmo)
Do I need to create a new token? because I reused the old one.

8

@mutmut You’re showing the « Discovered Devices » page, it’s in the « Devices » page :slight_smile:

9

My mistake, but I have nothing:

image
image471×631 22.9 KB

10

The „migrate“ button appears on the old integration, not on the new one!

The goal is to transfer devices from the old to the new integration :slight_smile:

11

argh! actually, I hadn’t gone that far :frowning:

image
image420×882 55.8 KB

Could you add some text to indicate this, because it didn’t seem very clear to me.

So to summarize:

  • we install the external integration
  • we configure it
  • we scan the devices
  • we add the devices
  • we go to the old integration
  • we migrate the old ones
  • tada!
12

Where would you see that?

13

After analyzing the different tabs, the message should appear in the external integration devices tab, if and only if the internal integration is enabled and/or configured with devices in it, with a link to the internal integration devices tab.

14

I admit I’m not a big fan of adding these kinds of edge cases in new external integrations, especially since you’re not many to use the old Netatmo integration. :slightly_smiling_face:

However, I think we can do something more appropriate:

  • write documentation on the site explaining the migration;
  • in a future release (once we’re sure the new Netatmo integration is stable), send a startup alert on the affected Gladys instances;
  • optionally add a temporary banner with a link to the tutorial, then remove it after a few versions.

This seems to be a good compromise: we support the affected users without touching the code of the new integrations.

15

This is perfect, the goal is to prevent and guide users at the start.