Gladys Assistant 4.51.0: Zigbee2mqtt, ZWaveJS and MQTT!

News
1

Hello everyone! :tada:

Here is the first release of Gladys for 2025 :partying_face:

This update includes a set of improvements and fixes developed in late 2024 / early 2025, notably:

  • Fix for an MQTT disconnection bug: Thanks to @Terdious for their investigation which helped identify and resolve the unexpected MQTT disconnection issues experienced by some of you. The problem came from custom MQTT topics.
  • ZWaveJS: @Sescandell added support for remote controls, including the noDon Octan Remote CRC-3100 remote.
  • Zigbee2mqtt:
    • @_Will_71 added support for the Heiman smart doorbell.
    • @_Will_71 also developed the integration for the Aqara WXKG15LM double switch.
  • Lixee TIC: @_Will_71 performed a migration of selectors and external_id to fix issues related to a late-2024 migration.
  • Scenes: Updated the axios library by @bertrandda to support chunked responses in “HTTP Request” actions.

A huge thank you to all the developers for these valuable contributions! :folded_hands:

10 Likes
2

Thank you @pierre-gilles , @Terdious , @Sescandell , @_Will_71 and @bertrandda for your commitment :slight_smile:

3 Likes
3

Yes thank you, for your work :clap:

2 Likes
4

Thank you for your work! :grin:

2 Likes
5

Thank you for your work :slight_smile:

2 Likes
6

Many thanks :+1:

2 Likes
7

@_Will_71 Thanks for your commitment.
Can we perform the Lixee TIC update now without any further formalities?
Thank you.

1 Like
8

However, don’t forget that you’ll still have to redo the scenes and/or dashboard where you use the Lixee.

9

OK, thanks @_Will_71

10

Hello,
I noticed this morning that the Lixee, which had been working without any issues for over a year, is no longer displaying any graphs. Could the update be the cause of this problem?
There is no update available for Zigbee2MQTT, and if I remove the Lixee from the device integrations list, I’m sure I’ll lose all the history

11

@Jluc For now, I haven’t installed the update yet; I might wait a little longer — what does @_Will_71 think?

12

Sorry but we have no choice, the migration breaks the dashboards, however the data is preserved.

So you’ll have to redo your dashboards and your scenes, sorry but we couldn’t do both. It was either the data or the dashboards. We chose to keep the data.

The update itself in the z2m integration will bring new features. But of course you should apply the update only after Gladys has been updated to the latest version.

1 Like
13

Thank you, I redid the dashboards and I do indeed have all the data, great

2 Likes
14

Everything’s perfect at my place as well.
Thanks again to @_Will_71 for this great integration.
FYI, for those who might have doubts, my Linky meter is located outside my house about 30 meters away, with a lixee TIC and its external antenna, and I have no problems with Zigbee reception.

3 Likes
15

I applied the proposed update in the zigbee2mqtt integration, and I still have all my data. I adjusted my scenes and dashboard without any issues.
Thanks @_Will_71 :+1:

2 Likes
16

Is it possible that the update installed itself ?
I had been careful not to install it while waiting to have a bit of time and my graphical errors have just confirmed that it is indeed installed ..
Or I’m starting to lose it :face_with_diagonal_mouth:
By the way, when you add a block without specifying devices, all devices appear .. It’s a bit cluttered !

Screenshot 2025-01-22 at 18.15.59
Screenshot 2025-01-22 at 18.15.59292×256 3.19 KB

![Screenshot 2025-01-22 at 18.16.25|66x500](upload://zmvfMb6stFkWD8zLrAWjuhv

1 Like
17

I noticed that yesterday too… it’s odd but I thought, here’s a ready-made dashboard :laughing:

18

It

19

Hello,
I had a power outage on Sunday.
The MQTT broker restarted fine.
However, the one for ZWave JS UI seemed OK (Connected to the MQTT broker successfully!) but no devices were working.

I could see the MQTT devices working, but not the ZWave ones.

By clicking save the configuration everything started working.

20

Great :slight_smile:

Do you have an error in the logs to share? Next time, think about the logs :slight_smile: