[Presentation] William

[Will_71]

Hello!

I’m William, I’m 39 years old. I’ve been passionate about computers since childhood and I’m currently an embedded applications developer (C) for mobile equipment…
I started home automation in 2018 after buying my house. After much deliberation, I chose Domoticz on an RPI 3B+.

For a few weeks now, I’ve discovered Gladys and I’ve been seduced by the interface. To not disrupt my current installation, I decided to install Gladys on a VM of my Freebox. I have a RPI 4 on order but the delivery time is very long. I haven’t been able to connect a SONOFF Zigbee dongle, not detected by Gladys but I think it’s a USB detection problem related to Debian 11, and also impossible to make Gladys communicate with Telegram… well, it’s not serious I deleted my VM and I’ll wait for my RPI 4 to install Gladys!

Otherwise, my current configuration that I want to be able to reproduce with Gladys is as follows:

• Heating Management
  I have a NetAtmo Thermostat where I retrieve the schedule, setpoint and temperature information via a Python script and the NetAtmo API. The Domoticz NetAtmo plugin is not suitable because the data refresh time is too long.
  With this thermostat, I control a pellet stove which is my main home heating.
  I have coupled this with electric radiators. The radiators are controlled by Qubino Z-WAVE modules.
  By the way, I see a lot of people talking about the incomplete Z-WAVE integration in Gladys but what can we do or not do currently in Z-WAVE in Gladys?
  For each room, I have a virtual thermostat and a temperature sensor (XIAOMI ZIGBEE), depending on the Netatmo schedule and setpoints, I control my electric radiators via a Domoticz LUA script.

• Linky Info
  I retrieve via a Python plugin in Domoticz the data from my Linky meter

• Pool Management
  I control via a LUA script and a Qubino Z-WAVE module my pool pump depending on the temperature. I currently take the outside temperature but ideally I need a submerged temperature sensor. If anyone has any ideas, I’m interested

• Opening Management
  I have XIAOMI and SONOFF Zigbee sensors to check the opening of doors and windows

• Mailbox
  I check the presence of mail in my mailbox with a Xiaomi Zigbee vibration sensor and an opening sensor. Via a script, I check the vibrations on the mailbox to detect the presence of mail/parcels and the opening sensor on the 2nd door to reset, in order to declare that the mail has been collected.

• Presence
  Via my Freebox, I can retrieve the presence of each person if the phone is connected to WIFI

• Light Management in a Wardrobe
  I installed in a wardrobe a Yeelight LED strip coupled with Xiaomi opening sensors. So the light turns on as soon as you open a door and turns off as soon as the doors are closed.

• Shutter Management
  I control via a Qubino Z-WAVE a wired shutter automatically depending on the sunrise and sunset times
  The rest of my shutters are SOMFY IO that I haven’t automated yet.

• SMS Alert
  With my mobile subscription, I have the possibility to use an API and send SMS via HTTP. So in all my scripts I send messages depending on the state of certain actions (door opening when no one is at home, presence of mail, low battery on sensors…)

• Domoticz Database Backup
  With a shell script, I make daily backups of the Domoticz database on a NAS

Finally, I connect to Domoticz remotely thanks to a VPN.

I still need to add cameras, manage my water heater…

That’s it, I’ve told my life but I have work to do for the transition to Gladys. So see you later with my config under Gladys when I receive my RPI4

[pierre-gilles]

Hello @Will_71 and welcome to Gladys!

Great job on your setup, it’s nice to see such a complete installation

@Will_71

I couldn’t connect a SONOFF Zigbee dongle, not detected by Gladys but I think it’s a USB detection issue related to Debian 11

Indeed, for now Gladys is not compatible with Debian 11 / Ubuntu 21. Max Debian 10 / Ubuntu 20.04. We are working on compatibility.

@Will_71

By the way, I see many people talking about the Z-WAVE integration which is not complete in Gladys but what can we do or not do currently in Z-WAVE in Gladys?

Currently, we use Open-Zwave, a historic open-source library for controlling Z-Wave.

Two things:

• This library is no longer maintained. We are trying to migrate to the new library (ZWaveJS), but it’s a lot of work
• In the meantime, there is little support for the current integration, and some devices are not supported. You have to be patient with these devices

@Will_71

Here I’ve told my life but I have work to do for the transition to Gladys. See you then with my config under Gladys when I receive my RPI4

Awesome! Don’t hesitate if you have feedback or requests for new features. We are listening, and Gladys evolves regularly.

[Will_71]

Thanks for your welcome @pierre-gilles! I hope I can integrate everything I want into Gladys.
I won’t hesitate to come back to this forum if needed.

By the way, I forgot some scripts for weather management, receiving weather alerts (orange, red) by SMS, detecting the presence of frost, useful for my wife to protect her car windshield…

After that, I don’t have any knowledge in JavaScript for development, but I can maybe help test features.

[lmilcent]

Wow, thanks for your presentation, it’s really interesting

Welcome!

@Will_71

With my mobile subscription, I have the possibility to use an API and send SMS via HTTP. So in all my scripts, I send messages based on the status of certain actions (door opening when no one is at home, presence of mail, low battery on sensors…)

That interests me, could you tell us which operator it is? I would like to be able to do this kind of thing, even if ideally it would be via 2G / 3G / 4G to do without the internet in case of a power outage.

[Will_71]

@lmilcent Thanks!

I am with Free Mobile. They have an SMS Notification option. But we need the Internet to execute this command!

Then with an HTTPS request it is possible to send SMS:

https://smsapi.free-mobile.fr/sendmsg?user=XXXXXXXX&pass=XXXXXXXXXXXXXX&msg=Hello%20World%

[pierre-gilles]

@Will_71

Receive weather alerts (orange, red) by SMS

In the case of Gladys, we use Telegram a lot, it might be simpler/more practical, especially since you can reply to Gladys on Telegram!

[Will_71]

@pierre-gilles Yes, with Telegram it seems simpler for two-way discussion!

Currently, I use SMS to notify myself or my wife about certain actions, but my wife doesn’t receive everything.

Can we have multiple Telegram accounts in Gladys? And thus choose which user receives the notification?

[pierre-gilles]

@Will_71

Can we have multiple Telegram accounts in Gladys? And then choose which user receives the notification?

Yes!

In fact, in Gladys you can create an account per user, and then each user can associate their Telegram account.

Then, in the scenes you can select which user you want to send a message to:

[Will_71]

Ok cool! Thanks.

I think I won’t be able to wait for my RPI4 to start testing Gladys.
I must have an old PC that must be gathering dust, so I’ll try to restore it and install a Debian 10 or Ubuntu 20.04 to test all that.

[cce66]

Yes, and even more so, through Node-RED, you can compensate for all the shortcomings of Gladys and adapt scenarios or hardware not yet supported!

[Will_71]

Good evening,

At the request of @lmilcent, I’m coming back here to present my Gladys setup and what I’ve put in place since migrating from Domoticz.

I’ve integrated a number of sensors, actuators, lamps, a Netatmo thermostat, a Sonoff module (Tasmota), Qubino Z-Wave modules, but mostly Zigbee.

Regarding Gladys, I had a bit of trouble getting used to the way scenes work at first because I used to write Python and Lua scripts under Domoticz, but in the end, coupled with Node-RED I was able to handle almost all of my needs.

For Z-Wave, I don’t use Gladys, well not the current integration, but I installed zwavejs2mqtt and thanks to MQTT + Node-RED I can control all my devices as I wish.

In Gladys, I created several dashboards, thanks @jerome for the idea of icons — it definitely looks nicer like this

In the home dashboard, I have basic functions like weather, presence detection, and some functions I’m currently testing.
A box for my mailbox but unlike @lmilcent I use 2 sensors, a Xiaomi vibration sensor and a contact (opening) sensor.
The vibration sensor is fixed to the door with one of the mounting screws located under the flap, so if the door opens for a parcel it generates vibrations and if the postman just leaves mail the flap closing and dropping on the screw also generates enough vibration for the sensor.
The contact sensor I fixed on the second door to know if someone has picked up the mail from the box.
I only have a small problem to solve: the system works quite well but I had to move my mailbox (the location chosen by the previous owners was really inconvenient) and I lost the sensor signal, so I need to add an external relay to improve reception quality.

A second box that may be interesting is for my electric roller shutter.

Here I have a Qubino Z-Wave module to control my roller shutter with physical buttons if needed. I followed @VonOx’s tutorial for position management and I recently modified it following the integration of open/close commands.
But I don’t really use these buttons (physical or in Gladys) because I have a scene to open the shutter at sunrise and another scene to close it at sunset.
Here is the Node-RED flow

In the Batteries dashboard I put a box per room to list all my battery-powered sensors. Thanks @lmilcent I used your display.

Then I created a scene per sensor to send a Telegram message if the battery is below a threshold.
Since the battery value isn’t very reliable I find, I already had a failure under Domoticz while the sensor was still at 100%.
For this in Node-RED I added a Timeout function to measure the time between 2 MQTT messages sent by the sensor. If after 24h I haven’t received another message then I send a Telegram message.
Here is part of the Node-RED flow

In the Temperature and Humidity dashboard, I have the list of all my temperatures and humidities. thanks @cicoub13 I was inspired by your dashboard

In the Heating dashboard, this part is one of the most important in managing my house.
While waiting for @Terdious’s Netatmo integration, I retrieve with Node-RED the info from my Netatmo thermostat which is connected directly to my pellet stove. The Netatmo app is well made and I use it to create my schedules.
The Summer/Winter mode is an MQTT device that I added, not present in Netatmo.

Then I display the house temperature curve + the setpoint curve (red)

Then I have a box per room where I installed an electric radiator (+ Qubino Z-Wave module)

Here all these devices are on MQTT except the temperature sensor and the window contact sensor and are controlled thanks to Node-RED. You can see the new Thermostat module developed by @pierre-gilles which is almost functional for me (some display issues depending on screen resolution).
Here is my Node-RED flow to manage a radiator

The upper part manages all the modes of the Z-Wave module (Frost protection, eco, comfort…) and the lower part I created a thermostat (TPI) to calculate a heating power based on outside temperature, inside temperature, window opening… and I also calculate in this thermostat the consumed power and the price.

I also display temperature/setpoint curves and heating power for each radiator.

In the 1st graph, in red you can see the moments when the setpoint changes but since it’s still warm right now all data are at zero. Thermostat management is handled by scenes. The point of the thermostat I asked @pierre-gilles for is for example if my son comes home earlier from school he can manually increase the temperature of his room.

In the Electricity dashboard, thanks to a Lixee TIC module and Node-RED I display data from my Linky meter.
I also have a SONOFF module (with Tasmota) connected to my water heater to monitor its consumption.

In the Lighting dashboard, nothing special, just controls for my various lamps.
Just a small particularity about my lighting: I added an LED strip in a cupboard in my corridor and I added an opening sensor on each door. So each time a door opens the LED strip lights up and switches off automatically on closing. I have a button in the Gladys dashboard, but I never used it.
The LED strip is from Yeelight and integrated thanks to Node-RED.
One negative point for Yeelight is that it connects to a Chinese server!!! One day I’ll replace it because if there’s no Internet it doesn’t work anymore, except manually.

In the Security dashboard, I display all my opening sensors. I have scenes to alert me if a window opens when I’m not there, or if I forget to close the garage door.

In the last Weather dashboard, I display weather data, temperatures, atmospheric pressure, air quality.
I also have a function where I retrieve the forecasted temperature for the next day at 6AM plus the dew point to calculate the risk of frost. A function much appreciated by my wife who leaves her car outside and receives a notification at 6PM. That way she knows if she needs to protect the windshield in the morning.
The only problem I have is retrieving the dew point data, because I get this info with the DarkSky API that I used in Domoticz, but this API will no longer work in 2023. Bought by Apple and you need an Apple developer account to continue using this API. I saw in OpenWeather used by Gladys that I could retrieve this information but not in the free plan. There is a paid plan (with a number of free requests) which would be sufficient for my use but I’m bothered about registering my credit card for a service that will cost me €0. So on hold for now as long as it works with DarkSky, we’ll see afterwards.

And of course the most important thing for me when I start integrating a system is a backup system.
There I subscribed to Gladys+ to support the project but I still have my backup script which makes nightly backups of Gladys, Zigbee2MQTT and Node-RED.

There you go, I’ve covered my installation, it might give you some ideas. For my part I still have plenty of ideas but I hold back because the budget would explode. One of the next integrations for me will probably be an outdoor surveillance camera. If anyone has a model to recommend I’m interested.

[pierre-gilles]

What a setup! Thanks for this very thorough post @_Will_71

I’ll share it with the community on social media!

[cicoub13]

Thanks for this very comprehensive share. A nice setup with everyone’s ideas that seem to fit your needs well

@_Will_71

The only problem I have is retrieving the dew point data, because I get this info with the DarkSky API that I had in Domoticz, but this API will no longer work in 2023

You can try https://api.open-meteo.com/v1/forecast?latitude=44.84\u0026longitude=-0.59\u0026hourly=dewpoint_2m
I know it’s free, but I don’t know the quality

[Will_71]

Thanks for the info

[jerome]

Thanks @_Will_71 for sharing.

Great setup.

If needed, can we call on you for Node-RED scripts?

Outdoor camera — I’m also interested in any feedback/experiences if there are any?

See ya

[Will_71]

Yes, no problem — if you need anything, don’t hesitate to ask me.

[Einstein8854]

hello, how did you install zwave2mqtt?
I tried to install it under Docker. Apparently everything runs but I can’t reach its home page from a remote browser (ip:8091) even though on my remote PC I opened the port for inbound and outbound.
How do you interface it with Node-RED?

[Will_71]

Hi,

I installed it with Docker but I don’t have the command on hand. I’ll look it up if you want it.
Have you checked the Docker logs to verify that zwavejs2mqtt is working properly?

Then, to interface it with Node-RED, the answer is in its name: MQTT. Once you can access the zwavejs2mqtt web interface, you need to configure the MQTT broker.

[Einstein8854]

hi again,
I also installed it with Docker but I installed zwave-js-ui because it told me that zwavejs2mqtt is deprecated.
when I run docker ps -a it shows as started, but when I look at the logs I get quite a few warnings

2022-10-14 20:53:33.680 INFO APP: Version: 8.2.1.30d0208
2022-10-14 20:53:33.695 INFO APP: Application path:/usr/src/app
  ______  __          __                      _  _____     _    _ _____
 |___  /  \ \        / /                     | |/ ____|   | |  | |_   _|
    / /____\ \  /\  / /_ ___   _____         | | (___     | |  | | | |
   / /______\ \/  \/ / _' \ \ / / _ \    _   | |\___ \    | |  | | | |
  / /__      \  /\  / (_| |\ V /  __/   | |__| |____) |   | |__| |_| |_
 /_____|      \/  \/ \__,_| \_/ \___|    \____/|_____/     \____/|_____|

2022-10-14 20:53:33.758 WARN STORE: settings.json not found
2022-10-14 20:53:33.801 WARN STORE: scenes.json not found
2022-10-14 20:53:33.821 WARN STORE: nodes.json not found
2022-10-14 20:53:34.010 WARN STORE: users.json not found
2022-10-14 20:53:34.216 INFO APP: Listening on port 8091 host 0.0.0.0 protocol HTTP
2022-10-14 20:53:34.628 WARN BACKUP: Store backup is disabled
2022-10-14 20:53:34.643 WARN BACKUP: Nvm backup is disabled
2022-10-14 20:53:34.653 WARN Z-WAVE: Z-Wave driver not inited, no port configured
2022-10-15 17:22:03.643 INFO APP: Version: 8.2.1.30d0208
2022-10-15 17:22:03.707 INFO APP: Application path:/usr/src/app
  ______  __          __                      _  _____     _    _ _____
 |___  /  \ \        / /                     | |/ ____|   | |  | |_   _|
    / /____\ \  /\  / /_ ___   _____         | | (___     | |  | | | |
   / /______\ \/  \/ / _' \ \ / / _ \    _   | |\___ \    | |  | | | |
  / /__      \  /\  / (_| |\ V /  __/   | |__| |____) |   | |__| |_| |_
 /_____|      \/  \/ \__,_| \_/ \___|    \____/|_____/     \____/|_____|

2022-10-15 17:22:04.056 WARN STORE: settings.json not found
2022-10-15 17:22:04.085 WARN STORE: scenes.json not found
2022-10-15 17:22:04.575 INFO APP: Listening on port 8091 host 0.0.0.0 protocol HTTP
2022-10-15 17:22:05.367 WARN BACKUP: Store backup is disabled
2022-10-15 17:22:05.393 WARN BACKUP: Nvm backup is disabled
2022-10-15 17:22:05.453 WARN Z-WAVE: Z-Wave driver not inited, no port configured
2022-10-17 08:51:24.565 INFO APP: Version: 8.2.1.30d0208
2022-10-17 08:51:24.582 INFO APP: Application path:/usr/src/app
  ______  __          __                      _  _____     _    _ _____
 |___  /  \ \        / /                     | |/ ____|   | |  | |_   _|
    / /____\ \  /\  / /_ ___   _____         | | (___     | |  | | | |
   / /______\ \/  \/ / _' \ \ / / _ \    _   | |\___ \    | |  | | | |
  / /__      \  /\  / (_| |\ V /  __/   | |__| |____) |   | |__| |_| |_
 /_____|      \/  \/ \__,_| \_/ \___|    \____/|_____/     \____/|_____|

2022-10-17 08:51:24.651 WARN STORE: settings.json not found
2022-10-17 08:51:24.694 WARN STORE: scenes.json not found
2022-10-17 08:51:25.081 INFO APP: Listening on port 8091 host 0.0.0.0 protocol HTTP
2022-10-17 08:51:25.316 WARN BACKUP: Store backup is disabled
2022-10-17 08:51:25.323 WARN BACKUP: Nvm backup is disabled
2022-10-17 08:51:25.333 WARN Z-WAVE: Z-Wave driver not inited, no port configured
2022-10-19 08:05:57.060 INFO APP: Version: 8.2.1.30d0208
2022-10-19 08:05:57.090 INFO APP: Application path:/usr/src/app
  ______  __          __                      _  _____     _    _ _____
 |___  /  \ \        / /                     | |/ ____|   | |  | |_   _|
    / /____\ \  /\  / /_ ___   _____         | | (___     | |  | | | |
   / /______\ \/  \/ / _' \ \ / / _ \    _   | |\___ \    | |  | | | |
  / /__      \  /\  / (_| |\ V /  __/   | |__| |____) |   | |__| |_| |_
 /_____|      \/  \/ \__,_| \_/ \___|    \____/|_____/     \____/|_____|

2022-10-19 08:05:57.282 WARN STORE: settings.json not found
2022-10-19 08:05:57.409 WARN STORE: scenes.json not found
2022-10-19 08:05:58.032 INFO APP: Listening on port 8091 host 0.0.0.0 protocol HTTP
2022-10-19 08:05:58.476 WARN BACKUP: Store backup is disabled
2022-10-19 08:05:58.481 WARN BACKUP: Nvm backup is disabled
2022-10-19 08:05:58.496 WARN Z-WAVE: Z-Wave driver not inited, no port configured
2022-10-20 08:24:11.342 INFO APP: Version: 8.2.1.30d0208
2022-10-20 08:24:11.376 INFO APP: Application path:/usr/src/app
  ______  __          __                      _  _____     _    _ _____
 |___  /  \ \        / /                     | |/ ____|   | |  | |_   _|
    / /____\ \  /\  / /_ ___   _____         | | (___     | |  | | | |
   / /______\ \/  \/ / _' \ \ / / _ \    _   | |\___ \    | |  | | | |
  / /__      \  /\  / (_| |\ V /  __/   | |__| |____) |   | |__| |_| |_
 /_____|      \/  \/ \__,_| \_/ \___|    \____/|_____/     \____/|_____|

2022-10-20 08:24:11.507 WARN STORE: settings.json not found
2022-10-20 08:24:11.517 WARN STORE: scenes.json not found
2022-10-20 08:24:11.782 INFO APP: Listening on port 8091 host 0.0.0.0 protocol HTTP
2022-10-20 08:24:12.232 WARN BACKUP: Store backup is disabled
2022-10-20 08:24:12.240 WARN BACKUP: Nvm backup is disabled
2022-10-20 08:24:12.264 WARN Z-WAVE: Z-Wave driver not inited, no port configured

[Will_71]

The warnings are probably because you haven’t configured anything yet. Besides, you haven’t set your Z-Wave key.

However, the container — are you sure it’s running? In your logs it restarted several times and nothing since the 20th.
What is the output of the command docker ps -a

Also, from this line 2022-10-20 08:24:11.782 INFO APP: Listening on port 8091 host 0.0.0.0 protocol HTTP you should still be able to access the interface.