I love this development!! But I admit it’s a time sink for viewing…^^ And then when you start displaying all your devices and seeing where you could save
Just to compare ^^
What reassures me at home is that it’s the professional one that consumes a lot ^^
Tough break … and it always happens at the worst time!!
Oh but this update is so cool, I totally didn’t see it come out
I only encountered 2 difficulties :
0 devices detected at first, that makes the UI crash for me => you have to read the docs carefully and update the Zigbee devices
The calculation task: on a Pi3 it completely locks up Gladys (no access anymore) => I don’t know yet how to fix that, maybe my calculation period is too large (4 years)
In any case I’m really going to love it when it works
Okay, I know I’ve been publishing a lot of updates this weekend, but it’s to improve Gladys for everyone
I just released Gladys Assistant v4.66.5, which fixes two issues:
On instances with a large DuckDB database, startup could be very slow because of a query calculating the database size. This issue is now fixed.
When Gladys is updated, a message is sent to your configured communication channels (Telegram, WhatsApp, Signal, Nextcloud Talk, etc.). If one of the channels was unavailable, the others weren’t notified. That’s now fixed!
Well, Houston, we’ve got a problem… I don’t agree…
A consumption cannot be ‹ under › a cost; that doesn’t make sense and it’s not real.
That’s why I was against having the visuals « Consumption 30 minutes » and « Cost 30 minutes » directly here. They are « values » intrinsically linked because of this development. But they only depend on their original physical meter.
In your example @prohand the Lixee device should be directly under the Enedis device. And the Socket device directly under the Lixee device. Then each has its own consumption and its cost linked to its consumption. Then it’s the integration that should deduce that each 30-minute consumption is linked to the hierarchy above and the same for costs. But it’s wrong to say that the Lixee device is directly linked to Enedis’s 30-minute cost…
No, in itself in most dwellings there will be only one device at level 0. You could have, for example, 2 meters with a subscription, but that should be
Hmm, okay, but I still don’t understand the logic of the “locking”. Because I had put my 30min consumptions of my outlets under the 30min consumption of the zlinky. But if I reread the doc, the 30min consumption of the outlets should be under the “energy consumed” of the outlet with the same name.
I even have a “cost” that is blocked. In short, I kinda messed up my hierarchy and I don’t feel like I can fix it :frowning
Originally the idea of the lock was precisely to prevent mistakes by preventing modifications of the « 30-minute consumption » and « 30-minute cost » features
In theory, everything is handled by the integrations ^^