Thanks @pierre-gilles it works well for me too.
Yesterday we were in red and today in white (for the Jura) because it seems to me that itâs by sector.
I had been monitoring my dryer for a while, but I ended up adding the smart plug to my NAS.
For my pool pump I have this:
Iâll buy at least one to check the consumption of my air conditioner (itâs a ducted unit so itâs not easy to add a power outlet to make it smart), at least this way itâs directly on the electrical panel!
Not yet, but I think Iâll change next year.
I read somewhere that EDF planned to go from 300k subscribers in 2020 to 5M in 2025 (something like that), that many potential Gladys users notably for automating heating mode changes. You have 16 hours Ă 22 days to manage.
Probably, but on « Tempo » thereâs no room for error â the kWh during peak hours on a red day costs âŹ0.55
No, the day colors are calculated by an algorithm (apparently taking into account mainly Paris and Lyon) and apply at the national level.
At the same time, if itâs like the masks in early 2020 ![]()
The update went really well when done manually and is even more functional.
Iâm still as impressed as ever by these quick integrations â useful or useless, weâll see later.
Great, Pierre-Gilles, I hope I can enjoy all of this soon :sl
I confirm that it would be great to also have information about Tempo days.
I just signed up for it, with the idea of forcing myself to limit my electricity use when itâs most necessary, and I was counting on home automation to turn off my water heater when the kWh is three times more expensive, on red days! There is an EDF trigger in IFTTT, but it doesnât work at all and no response from EDF supportâŠ
So if Gladys can give me the « red/white/blue days » info, that would be awesome!!
I donât know how difficult it is, but thanks in advance for what you can do @pierre-gilles .
Good evening @pierre-gilles
I successfully retrieved the Gladys Assistant v4.13.1 version and the Ecowatt display, but at the same time my Bluetooth is no longer enabled
and I canât restore it by clicking on the Bluetooth action button. Iâm saying this because it corresponds to the Gladys update. Could this come from Node.js 18 LTS? I had just installed it when switching to a 32-bit version ![]()
Indeed,
I hadnât noticed but since the 4.13 update Bluetooth is no longer active and when I look in the services it shows an error!
We need some information to understand whatâs going on and resolve the problem.
docker logs gladys
In general, hardware issues are at the beginning of the log
Hello @VonOx,
Excerpt from my Gladys log:
2022-12-09T19:35:39+0100 \u003cinfo\u003e index.js:15 (Object.start) Starting Bluetooth service
2022-12-09T19:35:39+0100 \u003cwarn\u003e service.start.js:44 (Service.start) Unable to start service bluetooth Error: Cannot find module '@abandonware/bluetooth-hci-socket'
Require stack:
- /src/server/services/bluetooth/node_modules/@abandonware/noble/lib/hci-socket/hci.js
- /src/server/services/bluetooth/node_modules/@abandonware/noble/lib/hci-socket/bindings.js
- /src/server/services/bluetooth/node_modules/@abandonware/noble/lib/resolve-bindings.js
- /src/server/services/bluetooth/node_modules/@abandonware/noble/index.js
- /src/server/services/bluetooth/lib/commands/bluetooth.start.js
- /src/server/services/bluetooth/lib/index.js
- /src/server/services/bluetooth/index.js
- /src/server/services/index.js
- /src/server/lib/index.js
- /src/server/index.js
at Function.Module._resolveFilename (node:internal/modules/cjs/loader:995:15)
at Function.Module._load (node:internal/modules/cjs/loader:841:27)
at Module.require (node:internal/modules/cjs/loader:1061:19)
at require (node:internal/modules/cjs/helpers:103:18)
at Object.\u003canonymous\u003e (/src/server/services/bluetooth/node_modules/@abandonware/noble/lib/hci-socket/hci.js:6:28)
at Module._compile (node:internal/modules/cjs/loader:1159:14)
at Object.Module._extensions..js (node:internal/modules/cjs/loader:1213:10)
at Module.load (node:internal/modules/cjs/loader:1037:32)
at Function.Module._load (node:internal/modules/cjs/loader:878:12)
at Module.require (node:internal/modules/cjs/loader:1061:19)
at require (node:internal/modules/cjs/helpers:103:18)
at Object.\u003canonymous\u003e (/src/server/services/bluetooth/node_modules/@abandonware/noble/lib/hci-socket/bindings.js:7:13)
at Module._compile (node:internal/modules/cjs/loader:1159:14)
at Object.Module._extensions..js (node:internal/modules/cjs/loader:1213:10)
at Module.load (node:internal/modules/cjs/loader:1037:32)
at Function.Module._load (node:internal/modules/cjs/loader:878:12)
at Module.require (node:internal/modules/cjs/loader:1061:19)
at require (node:internal/modules/cjs/helpers:103:18)
at module.exports (/src/server/services/bluetooth/node_modules/@abandonware/noble/lib/resolve-bindings.js:13:12)
at Object.\u003canonymous\u003e (/src/server/services/bluetooth/node_modules/@abandonware/noble/index.js:2:49)
at Module._compile (node:internal/modules/cjs/loader:1159:14)
at Object.Module._extensions..js (node:internal/modules/cjs/loader:1213:10)
at Module.load (node:internal/modules/cjs/loader:1037:32)
at Function.Module._load (node:internal/modules/cjs/loader:878:12)
at Module.require (node:internal/modules/cjs/loader:1061:19)
at require (node:internal/modules/cjs/helpers:103:18)
at BluetoothManager.start (/src/server/services/bluetooth/lib/commands/bluetooth.start.js:16:20)
at Object.start (/src/server/services/bluetooth/index.js:16:28)
at Service.start (/src/server/lib/service/service.start.js:33:21)
at start (/src/server/api/controllers/service.controller.js:22:21) {
code: 'MODULE_NOT_FOUND',
requireStack: [
'/src/server/services/bluetooth/node_modules/@abandonware/noble/lib/hci-socket/hci.js',
'/src/server/services/bluetooth/node_modules/@abandonware/noble/lib/hci-socket/bindings.js',
'/src/server/services/bluetooth/node_modules/@abandonware/noble/lib/resolve-bindings.js',
'/src/server/services/bluetooth/node_modules/@abandonware/noble/index.js',
'/src/server/services/bluetooth/lib/commands/bluetooth.start.js',
'/src/server/services/bluetooth/lib/index.js',
'/src/server/services/bluetooth/index.js',
'/src/server/services/index.js',
'/src/server/lib/index.js',
'/src/server/index.js'
]
}
Ok, thereâs a dependency problem ( the library that handles Bluetooth isnât installed)
Weâll fix that.
Good evening @VonOx
do you want my logs too?
If you donât mind, at least tell me if you have the same error
Here I copied the lines concerning Bluetooth
Require stack:
- /src/server/services/bluetooth/node_modules/@abandonware/noble/lib/hci-socket/hci.js
- /src/server/services/bluetooth/node_modules/@abandonware/noble/lib/hci-socket/bindings.js
- /src/server/services/bluetooth/node_modules/@abandonware/noble/lib/resolve-bindings.js
- /src/server/services/bluetooth/node_modules/@abandonware/noble/index.js
- /src/server/services/bluetooth/lib/commands/bluetooth.start.js
- /src/server/services/bluetooth/lib/index.js
- /src/server/services/bluetooth/index.js
- /src/server/services/index.js
- /src/server/lib/index.js
- /src/server/index.js
at Function.Module._resolveFilename (node:internal/modules/cjs/loader:995:15)
at Function.Module._load (node:internal/modules/cjs/loader:841:27)
at Module.require (node:internal/modules/cjs/loader:1061:19)
at require (node:internal/modules/cjs/helpers:103:18)
at Object.\u003canonymous\u003e (/src/server/services/bluetooth/node_modules/@abandonware/noble/lib/hci-socket/hci.js:6:28)
at Module._compile (node:internal/modules/cjs/loader:1159:14)
at Object.Module._extensions..js (node:internal/modules/cjs/loader:1213:10)
at Module.load (node:internal/modules/cjs/loader:1037:32)
at Function.Module._load (node:internal/modules/cjs/loader:878:12)
at Module.require (node:internal/modules/cjs/loader:1061:19)
at require (node:internal/modules/cjs/helpers:103:18)
at Object.\u003canonymous\u003e (/src/server/services/bluetooth/node_modules/@abandonware/noble/lib/hci-socket/bindings.js:7:13)
at Module._compile (node:internal/modules/cjs/loader:1159:14)
at Object.Module._extensions..js (node:internal/modules/cjs/loader:1213:10)
at Module.load (node:internal/modules/cjs/loader:1037:32)
at Function.Module._load (node:internal/modules/cjs/loader:878:12)
at Module.require (node:internal/modules/cjs/loader:1061:19)
at require (node:internal/modules/cjs/helpers:103:18)
at module.exports (/src/server/services/bluetooth/node_modules/@abandonware/noble/lib/resolve-bindings.js:13:12)
at Object.\u003canonymous\u003e (/src/server/services/bluetooth/node_modules/@abandonware/noble/index.js:2:49)
at Module._compile (node:internal/modules/cjs/loader:1159:14)
at Object.Module._extensions..js (node:internal/modules/cjs/loader:1213:10)
at Module.load (node:internal/modules/cjs/loader:1037:32)
at Function.Module._load (node:internal/modules/cjs/loader:878:12)
at Module.require (node:internal/modules/cjs/loader:1061:19)
at require (node:internal/modules/cjs/helpers:103:18)
at BluetoothManager.start (/src/server/services/bluetooth/lib/commands/bluetooth.start.js:16:20)
at Object.start (/src/server/services/bluetooth/index.js:16:28)
at Service.start (/src/server/lib/service/service.start.js:33:21) {
code: âč MODULE_NOT_FOUND âș,
requireStack: [
âč /src/server/services/bluetooth/node_modules/@abandonware/noble/lib/hci-socket/hci.js âș,
âč /src/server/services/bluetooth/node_modules/@abandonware/noble/lib/hci-socket/bindings.js âș,
âč /src/server/services/bluetooth/node_modules/@abandonware/noble/lib/resolve-bindings.js âș,
âč /src/server/services/bluetooth/node_modules/@abandonware/noble/index.js âș,
âč /src/server/services/bluetooth/lib/commands/bluetooth.start.js âș,
âč /src/server/services/bluetooth/lib/index.js âș,
âč /src/server/services/bluetooth/index.js âș,
âč /src/server/services/index.js âș,
âč /src/server/lib/index.js âș,
âč /src/server/index.js âș
]
}
@bjm what area are you in? Iâm in Dole
Good evening,
This Ecowat integration is very handy. Thank you, Pierre Gilles. But same for me â no Bluetooth anymore.
Thanks for the integration
But in addition to that, and to protect our equipment from outages, being able to shut down the Raspberry Pi might be useful
However, I would also add the ability to stop it via a scene and via Telegram. Since we will know the time of the outage the day before, we wonât always have time, given the scheduled outage hours, to connect to our PC, open PuTTY and cleanly shut down the Raspberry Pi.
While writing I just realized that the ability to stop the Gladys instance and others is also missing for those who are not running Gladys
so in summary it should include
- a button to properly shut down your Raspberry Pi
- the ability to shut down your Raspberry Pi via a scene or via Telegram
- the ability to stop the Gladys container and associated containers (zigbee2mqttâŠ) via a scene or via Telegram.

