Thanks everyone for your positive feedback on the Ecowatt integration, itâs nice to read 
Thatâs a good idea indeed! I saw the feature request:
For info, in parallel Iâve already been working for a while on an integration with Enedis to see your electricity consumption in Gladys (in kWh and in euros).
Iâm a bit behind because Enedis released a major new version of their API and deprecated the API I had just integrated ( 
), and there are a few bugs in the sandbox of this API for now, which delays my development.
But itâs moving forward, Iâm in regular discussion with the Enedis technical team 
To follow the Enedis topic:
After all, this integration is just the « result » of your consumption afterwards, I agree with you, having the « red/white/blue » days would be great
Darn! Indeed itâs due to the Node.js 18 LTS update.
Ok, the library must have an issue installing on the latest Docker Node 18 Alpine image on some architectures.
Itâs strange because normally during the Docker build if a dependency doesnât install, it should crash the build⊠It slipped through the cracks, we need to understand why. (See: Gladys/server/cli/install_service_dependencies.js at master · GladysAssistant/Gladys · GitHub )
Thanks for the logs 
For info this library (Noble) has always caused us a lot of problems, originally we used this lib for Bluetooth:
Except itâs no longer maintained for 4 years, so someone made a fork that we followed in Gladys:
Except this fork now has 114 GitHub issues, so it also has its share of problems. It is still maintained, but not actively either. The codebase must be old and not pleasant to work with ^^
@VonOx Any idea why the lib no longer installs?
Interesting yes! We need to see if on the Raspberry Pi OS image that we distribute, Gladys has the rights to stop the global system, I donât think so because we donât have access to the system « shutdown » from the container (to test).
For now there are few votes on your request ^^
Not a bad idea, I created an issue, Iâll look at it tomorrow (Monday):