Gladys Assistant 4.19: Air conditioners, Zigbee soil moisture sensor & under-the-hood improvements!

[pierre-gilles]

Hello everyone!

Here we go, another new version of Gladys Assistant

Added air conditioners

It is now possible to manage air conditioners via the MQTT integration:

Thanks @euguuu for the PR

Added soil moisture sensors in the Zigbee integration

In the Zigbee integration, it is possible to integrate soil moisture sensors:

This sensor has been intentionally separated from « room » humidity sensors so as not to skew room humidity calculations.

Thanks @euguuu for the PR

Unification of the search bar and sorting in integrations

All the code for searching / and sorting devices in integrations has been unified into a single component by @AlexTrovato so that the experience is consistent across all integrations.

I think that the more integrations we have in Gladys, the more we’ll be able to unify behaviors and have generalized « UI blocks » across integrations.

A step in the right direction then! Thanks @AlexTrovato

Tasmota/Zigbee: When updating a device, no more loss of name/room

When updating a Zigbee device in the Gladys integration, Gladys used to lose the device’s name and room: this is no longer the case thanks to @AlexTrovato

Under-the-hood improvements / bug fixes

This release brings a set of necessary but less visible changes:

• In the MQTT integration, all Shell script files have been replaced with JavaScript code, which as a result becomes 100% unit-tested (which wasn’t the case for the shell code). I think we really need to stop using these untested Shell files; everything can be done in JS
• Fixed a bug on Gladys Plus: on first login, the error message warning that the user had not accepted their local public/private key was not displayed. It is now displayed:

• Improved the dependency installation code for services during the build. Thanks @Pti_Nico for the work
• Changed the OpenAI integration interface to mention the new quota of 1000 and the ChatGPT API instead of GPT-3 ( L'IA OpenAI GPT-3 disponible dans Gladys Assistant 🤯 - #102 par pierre-gilles )

Ongoing projects

• The private alpha of the Enedis integration is in the hands of users! I’m collecting feedback and making improvements before releasing a public beta (Intégration Enedis-Linky - #87 par pierre-gilles)
• The work on live camera streaming is still ongoing (Afficher l'image en direct d'une caméra en plein écran depuis le dashboard - #14 par pierre-gilles)

Changelog

The full CHANGELOG is available here .

How to update ?

If you installed Gladys with the official Raspberry Pi OS image, your instances will update automatically in the coming hours. It may take up to 24 hours, don’t worry.

If you installed Gladys with Docker, make sure you are using Watchtower (See the documentation )

[guim31]

A lot more work completed! Thank you to everyone who worked for us

[guim31]

Small UI issue on the « clim » device — it appears for me with a horizontal slider:

[Psoy]

Good evening
Since the update, I no longer have a link between Zigbee and Gladys even though everything is correct — both checkboxes are checked in the Zigbee configuration and on the Zigbee dashboard my detectors and sensors respond well to commands. Am I the only one experiencing this?

[Psoy]

I just have to post a message for everything to restart on its own. I’ll put that down to the time it took for the update to be applied. Update 4.19 around 9:00 PM, Gladys fully back up at 12:30 AM. Is that normal?

[pascal_sapin]

hello
same for me, no more information being reported even though everything is correct

[GBoulvin]

Same here…
I unchecked then rechecked the service activation checkbox and everything is working again

Edit: A small snippet of the log :

2023-04-01T13:53:06+0000 \u003cwarn\u003e handleMqttMessage.js:106 () Zigbee2mqtt device PlafonnierSAM1, feature power_on_behavior not configured in Gladys.
2023-04-01T13:53:06+0000 \u003cerror\u003e handleMqttMessage.js:103 () Failed to convert value for device PlafonnierSAM1: Error: Zigbee2mqqt expose not found on device \"PlafonnierSAM1\" with property \"state\".
    at Zigbee2mqttManager.readValue (/src/server/services/zigbee2mqtt/lib/readValue.js:16:11)
    at /src/server/services/zigbee2mqtt/lib/handleMqttMessage.js:99:31
    at Array.forEach (\u003canonymous\u003e)
    at Zigbee2mqttManager.handleMqttMessage (/src/server/services/zigbee2mqtt/lib/handleMqttMessage.js:91:41)
    at MqttClient.\u003canonymous\u003e (/src/server/services/zigbee2mqtt/lib/connect.js:53:12)
    at MqttClient.emit (node:events:513:28)
    at MqttClient._handlePublish (/src/server/services/zigbee2mqtt/node_modules/mqtt/lib/client.js:1277:12)
    at MqttClient._handlePacket (/src/server/services/zigbee2mqtt/node_modules/mqtt/lib/client.js:410:12)
    at work (/src/server/services/zigbee2mqtt/node_modules/mqtt/lib/client.js:321:12)
    at processTicksAndRejections (node:internal/process/task_queues:77:11)
2023-04-01T13:53:06+0000 \u003cwarn\u003e handleMqttMessage.js:106 () Zigbee2mqtt device PlafonnierSAM1, feature switch_type not configured in Gladys.
2023-04-01T13:53:06+0000 \u003cerror\u003e handleMqttMessage.js:103 () Failed to convert value for device PlafonnierSAM1: Error: Zigbee2mqqt expose not found on device \"PlafonnierSAM1\" with property \"linkquality\".
    at Zigbee2mqttManager.readValue (/src/server/services/zigbee2mqtt/lib/readValue.js:16:11)
    at /src/server/services/zigbee2mqtt/lib/handleMqttMessage.js:99:31
    at Array.forEach (\u003canonymous\u003e)
    at Zigbee2mqttManager.handleMqttMessage (/src/server/services/zigbee2mqtt/lib/handleMqttMessage.js:91:41)
    at MqttClient.\u003canonymous\u003e (/src/server/services/zigbee2mqtt/lib/connect.js:53:12)
    at MqttClient.emit (node:events:513:28)
    at MqttClient._handlePublish (/src/server/services/zigbee2mqtt/node_modules/mqtt/lib/client.js:1277:12)
    at MqttClient._handlePacket (/src/server/services/zigbee2mqtt/node_modules/mqtt/lib/client.js:410:12)
    at work (/src/server/services/zigbee2mqtt/node_modules/mqtt/lib/client.js:321:12)
    at processTicksAndRejections (node:internal/process/task_queues:77:11)
2023-04-01T13:53:06+0000 \u003cwarn\u003e handleMqttMessage.js:106 () Zigbee2mqtt device PlafonnierSAM1, feature power_on_behavior not configured in Gladys.
2023-04-01T13:53:06+0000 \u003cerror\u003e handleMqttMessage.js:103 () Failed to convert value for device PlafonnierSAM1: Error: Zigbee2mqqt expose not found on device \"PlafonnierSAM1\" with property \"state\".
    at Zigbee2mqttManager.readValue (/src/server/services/zigbee2mqtt/lib/readValue.js:16:11)
    at /src/server/services/zigbee2mqtt/lib/handleMqttMessage.js:99:31
    at Array.forEach (\u003canonymous\u003e)
    at Zigbee2mqttManager.handleMqttMessage (/src/server/services/zigbee2mqtt/lib/handleMqttMessage.js:91:41)
    at MqttClient.\u003canonymous\u003e (/src/server/services/zigbee2mqtt/lib/connect.js:53:12)
    at MqttClient.emit (node:events:513:28)
    at MqttClient._handlePublish (/src/server/services/zigbee2mqtt/node_modules/mqtt/lib/client.js:1277:12)
    at MqttClient._handlePacket (/src/server/services/zigbee2mqtt/node_modules/mqtt/lib/client.js:410:12)
    at work (/src/server/services/zigbee2mqtt/node_modules/mqtt/lib/client.js:321:12)
    at processTicksAndRejections (node:internal/process/task_queues:77:11)

[bjm]

No problem on my end.
However, yesterday morning Gladys crashed; it seems that it was the Gladys Plus backup that caused the problem.

But that was before the 4.19 update

[gaetanb76]

Nothing for me either.
No status updates, no actions possible.
Disabled then re-enabled the « Enable Zigbee2mqtt » toggle and everything works again.

[Psoy]

@bjm

However, yesterday morning Gladys had crashed

Indeed, before the update, I had a disconnection from the MQTT broker.

[

[gaetanb76]

I saw there was a problem two days ago. It may have dated from earlier.
I have this in System > Containers
/gladys\t21 hours ago\tStarted
/gladys-z2m-mqtt\t2 days ago\tStarted
/eclipse-mosquitto\t2 days ago\tStarted
gladys-z2m-zigbee2mqtt\ta month ago\tStarted
/dozzle\ta month ago\tStopped
/watchtower\t2 months ago\tStarted

This makes me think of these two issues:

ZigBee non disponible au démarrage/BT indisponible

Comme déjà indiqué dans un autre post ton problème vient soit de ta clé ou soit de ton alim. As tu vérifié ces 2 points ?

Bug v4.17.0 Zigbee2MQTT?

Ça fait beauuuucoup de logs, mais ça marche en effet.

[Hizo]

Same here, I had to stop zigbee2mqtt and restart it.

[Psoy]

@gaetanb76

I saw there was an issue 2 days ago

Same here
![image

[Tlse-vins]

I don’t have that problem myself, but I’m encountering another issue.
When I launch Gladys Plus it takes 30 seconds to 1 minute for the page to load. I have to refresh several times.
I checked the logs and there was nothing unusual.

[guim31]

It’s crazy, all these issues…
For me everything’s fine, everything’s running smoothly, locally, on Gladys Plus, on Zigbee2mqtt

[tiboys]

No problems on my end even though I had the same one in the previous update.
Maybe it fixed itself ..

[spenceur]

I had this issue with this update and the previous one.
What worked for me was restarting the service — 10 minutes later everything was fine.
There is a behaviour that seems to repeat with each update; maybe a bug with the service? @pierre-gilles @cicoub13?

[b3n.0]

I’ve also had issues with the last 2 updates…

But more the kind that makes Gladys unavailable …
Script not working, buttons likewise…

With the previous update, a power-cycle restart got the instance running again — no problems until yesterday morning!

But since yesterday it restarts, yet after less than an hour it crashes again…

[pierre-gilles]

Hi everyone! Indeed there is a bug in the Zigbee2mqtt integration for several Gladys versions, but since it’s a bit intermittent it’s hard to know where it comes from.

Intuitively I have the impression the bug appeared in Gladys v4.16: Release v4.16.0 · GladysAssistant/Gladys · GitHub, I think it might be due to this change: Z2m docker limit logs by atrovato · Pull Request #1692 · GladysAssistant/Gladys · GitHub

I created a GitHub issue to track the bug:

Zigbee2mqtt service doesn't reconnect properly on Gladys restart

I’ll investigate it a bit this morning, but I can’t guarantee anything — I’m not an expert on this service

@AlexTrovato I might need your help

@bjm

Par contre hier matin Gladys était planté, il semblerait que c’est la sauvegarde Gladys Plus qui a posé problème.

Did the Gladys container stop?

Background tasks are all independent; if one task fails it doesn’t jeopardize the stability of the instance, so a backup failing is not really a problem — it can happen

However, if your local instance no longer has access to the Gladys Plus servers due to a DNS issue (which is what the error in the message you’re posting is), it’s normal that you no longer have access to Gladys Plus.

If you have more information, maybe we could discuss it in another thread so we don’t mix everything up?

@Tlse-vins

Lorsque je lance Gladys plus cela met 30 secondes à 1 minute le temps que la page se charge. Je suis obligé de rafraîchir plusieurs fois.

Can we discuss this topic somewhere else (or privately) so we don’t mix everything up? In this case it’s probably specific to your installation — we need to determine whether it’s a network issue or a load problem on the machine running Gladys.