Gladys Assistant v4.26.1: Mosquitto pinned to v2.0.15, Google Home, improved graphs

[pierre-gilles]

Hi everyone!

I hope you had (or are having) a good summer holiday

As for me, I got back to working on Gladys last Friday and I just published an update today with a few fixes.

Mosquitto (MQTT) version pinned to 2.0.15

Mosquitto released a new version of its MQTT broker, and this version suffers from some bugs that, for some of you, prevent the use of the MQTT integration and Zigbee2mqtt.

In Gladys, I decided to pin the version to 2.0.15 for now while the issues persist.

If you are affected by the problems, after the update you may need to go back into the interface and re-register the password on the MQTT integration side, or restart the Zigbee2mqtt integration to properly overwrite your Mosquitto configuration file.

Managing the color temperature of a Zigbee lamp in Google Home

IKEA Tradfri bulbs sometimes come as white bulbs where the white temperature is adjustable (cool or warm).

Google Home handles this temperature in Kelvin, whereas Zigbee handles these temperatures in Mired.

This conversion step didn’t exist in Gladys, so I added it to allow control of these IKEA Tradfri bulbs.

For info, IKEA TRÅDFRI connected LED bulbs are available from €9.99 per bulb at Ikea, (without temperature control), or €12.99 with temperature control — so it’s a great deal; the prices are close to those of standard LED bulbs for very high-quality bulbs.

Charting library update

We use ApexCharts in Gladys, a library that generates charts to display curves on the dashboard:

Several users reported bugs related to this library, and a recent version of this lib has been released that fixes certain bugs. So I updated it!

Some other fixes:

• The chat height is now dynamic and expands according to your screen size. Thanks @cicoub13 for the fix!
• Spelling fixes in the LAN-Manager integration. Thanks @qleg for the PR!
• Stability fix in the NextCloud Talk integration. Thanks @bertrandda for the PR!

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. This can take up to 24 hours, don’t panic.

If you installed Gladys with Docker, check that you are using Watchtower ( See the documentation )

[guim31]

Great update! Well done everyone.

I have a question, maybe I’m not the only one…
I’m having trouble understanding the meaning of the data in a graph. Here’s my dashboard with, on the same graph, the temperature of my pool water and the outside temperature.
Depending on the data range, I have no idea what the numbers are supposed to mean…

Here are a few screenshots:

What’s more, it’s strange that for the 7-day, 30-day and 3-month time ranges, the value in degrees is the same.

Anyway it’s not super clear to me if anyone has any insight to share!

[pierre-gilles]

@guim31

Which is even stranger is that on the time ranges of 7 days, 30 days and 3 months, the value in degrees is the same.

Anyway it’s not super clear to me if anyone has any insight to offer me!

I don’t really get what you don’t understand? ^^

The data for « 7 days »/« 1 month »/« 3 months » are aggregated, so it’s an average We only show precision on the « 1h » and « 24h » views, so it’s normal if it’s smoother on long-term views.

[pascal_sapin]

Great update, however I have a question regarding the IKEA TRÅDFRI modules: I have an E1743 on/off switch — is there any plan to support that one? For now it doesn’t work, which is a shame because the prices are attractive.

Thanks for the work you do

[pierre-gilles]

@pascal_sapin

Great update, however I have a question regarding the IKEA Tradfri modules — I have a switch type E1743 on/off; is it planned to make that one work? For now it doesn’t work, which is a shame because the prices are attractive.

Ah, strange that it doesn’t work, you do mean this one:

IKEA E1743 control via MQTT | Zigbee2MQTT

?

Look in the Zigbee2mqtt documentation, they talk about 2 modes, legacy and new, maybe you need to enable something on the Zigbee2mqtt side for it to work on the Gladys side?

[pascal_sapin]

Yes, that’s the one, Zigbee2MQTT sees it and it responds, Gladys recognized it too, but how can I turn something on or off with it??? In features it says « button click »

[pierre-gilles]

Try to spot the action associated with each click, and then create one scene per click/action

Exemple:

Don’t hesitate to create a dedicated thread if you need help

[pascal_sapin]

OK thanks, I’ve already done it

[pierre-gilles]

Could you create a specific thread on the forum so we can discuss it in more detail? There’s no reason it shouldn’t work.

[Einstein8854]

Beyond 24 hours, aggregation in the form of « average » causes problems, especially for graphs of temperature and rainfall. An approach with two options, min or max, would be more realistic for better monitoring.

[pierre-gilles]

Indeed, there are 2 feature requests (quite redundant) that go in that direction:

Graphiques - Afficher cumul valeur par Jours / Semaine / Mois / Année

Hello Je viens proposer une fonctionnalité pour les graphiques. Le cas le plus concret que j’ai en tête concerne la consommation d’électricité ou eau. Actuellement un capteur récupère toutes les valeurs en temps réel et les transmet à Gladys qui les stocks en base pour générer le graphique. Sauf qu’actuellement si on affiche le graphique en jours, semaines, mois…, on a une moyenne de ce qui est envoyé en temps réel à chaque fois. Le but de ma demande serait que quand on confi…

Pouvoir afficher les graphiques en MAX() ou en SOMME()

bonjour, pour etre en continuité avec l echange avec @pierre-gilles lors du post de lancement de la 4.12.1, sur la restitution des data dans les graphiques : par ailleurs sur les données 7 j , 1mois etc je constate que là où on devrait avoir la data max (ou sommée ?) de la journée concernée on affiche une data lissée(ou moyennée) (ex : 8/11 j ai eu plus de 20mm de pluie, et le graphe sur cette date m affiche 12,96 mm ! pas l attendu !) un petit rajout pour rappeler cette demande ! plutot qu…

Very few votes on these so far

[dahut]

Good evening,

Thank you for the updates.

[guim31]

Thanks for your reply I may not have been very clear about my question.
I understand aggregation, but in these cases I don’t really see why the 7d / 30d / 3mo view display the same value at the top: 29.98°C even if it were an average it’s unlikely to be identical for each time range.

Also, my chart showing 2 temperature values — what does the single displayed value correspond to? An average of the two temperatures? Which in itself doesn’t make much sense for my use.
On my 24h screenshot, we see that the outside temperature is 40.52°, the pool is 28.5° and the displayed value is 34.02°.

In short, it’s a bit unclear to me at that level. But I have the impression that lots of people use charts for many different things: temperatures, the level of a tank, electricity consumption… which means the value calculations aren’t supposed to be the same. Is it possible to « customize » these charts depending on the type of data you want to display?

[pierre-gilles]

@guim31

except that in those cases, I don’t really see why the 7d / 30d / 3-month view displays the same value at the top: 29.98°C even if it was an average there’s little chance it would be identical for each time range.

The value at the top corresponds to the last value of the graph, and if there are multiple curves:

• If the units of the two curves are the same, an average is calculated
• If the unit is different, then only the first curve is taken into account

It’s true that it doesn’t necessarily make sense for everything, you can disable the display of this value if you wish