It was already possible to create a scene that triggers when a house is empty/not empty, but it was not possible to add a condition in a scene to continue only if the house is empty/not empty.
It's now possible!
With this scene, you can add the presence card on the dashboard:
If you installed Gladys with the official Raspberry Pi OS image, your instance will update automatically in the coming hours. It can take up to 24 hours, don't panic.
If you installed Gladys with Docker, make sure you are using Watchtower. See the documentation.
With Watchtower, Gladys will update automatically.
Today is the release of Gladys Assistant v4.3, a new update that puts the scenes in the spotlight!
Scenes are the backbone of home automation.
Having a connected home is not just to control it remotely: it is also to automate what is done regularly, to bring a share of magic to our home and make our daily lives easier.
Want to be sure everything is off when the last person leaves the house?
It is now possible to make a scene that will be triggered when the last one leaves the house.
In terms of presense detection, the feature is present from Gladys Assistant v4.1, and can work in different ways:
Via bluetooth: There are Bluetooth key fobs like the Nut which are very easily detectable by Gladys. The principle is simple: when you leave your home, Gladys will no longer "see" the bluetooth keychain and will mark you as absent, and when you come back, Gladys will detect the keychain and mark you as present.
In the scenes: it is possible to create a scene which is triggered after a change of state of a sensor for example, which will mark you as present/absent from the house. So you can do more or less what you want to mark yourself as present/absent at home.
Its opposite, "When the house is no longer empty"
Rather, you want to do another scene that will turn on everything when someone comes home and the house was empty before them.
This is possible with the trigger "when the house is no longer empty":
While it is possible to make a scene that is triggered with a certain recurrence (with scheduled scenes), it was not possible until then to add a time-based condition in the scene.
For example, let's say you want to make a scene:
"When the living room temperature is < 20°C"
AND "it is between 9h and 22h"
THEN send me a message "The temperature is too low"
It is possible with the time-based condition!
Example of a scene that will only run between 8 a.m. and 12 p.m. on weekends:
Since Gladys v4.0.3, it is possible to make HTTP requests in the scenes.
Convenient for calling an external API in scenes.
From now on, it is possible to retrieve the response of the HTTP call, and to use the result of the request in the scenes.
For example, let's say you want to do a scene that will call Coinbase's API every morning to retrieve the price of Bitcoin, and send you a message with the price.
It is now possible, and here is an example in video:
Of course this is just one example among many.
You could request a weather API, traffic API, a sensor at home, IFTTT, and many others...
And that's not all! Variables retrieved in the HTTP call can be used in the "continue only if" condition, which allows you to verify that a condition is true.
Example:
Receive a message only if the outside temperature is < 32°F.
Receive an alert if a company stock you follow drops by more than 20%
If you installed Gladys with the official Raspberry Pi OS image, your instance will update automatically in the coming hours. It can take up to 24 hours, don't panic.
If you installed Gladys with Docker, make sure you are using Watchtower. See the documentation.
With Watchtower, Gladys will update automatically.
Once again, thank you to everyone who contributed to this release: whether it's coding, suggesting new ideas on the forum, or testing new features, every help is invaluable and makes the product complete!
Since the launch of Gladys Assistant 4 last November, more and more contributors have made their contribution by offering new features on Gladys Assistant.
Since November, we've released 11 new versions of Gladys. That's almost 3 new releases per month. We're working hard!
It's official, the Zigbee2mqtt integration is now integrated into Gladys 4 🚀
It is therefore now possible to control a wide range of Zigbee peripherals via a Zigbee USB key. Here is the list of supported devices.
This is the result of months of work on the part of many members of the community. Thanks to Reno for the first initial development, thanks to cicoub13 for resuming development, and thanks to lmilcent for testing!
For the moment, all the peripherals are not necessarily perfectly managed, which is normal as we do not have all the unimaginable peripherals on earth. There may be some adjustments to be made that we will discover over the course of the use of this integration.
We've updated the NPM dependency we use in the Philips Hue integration to it's latest version.
Some users had problems with discovering a Philips Hue bridge on their network because we were previously using Philips Hue's N-UpnP scan which is based on their online API.
We changed this function to go through the network UPnP scan, which takes place entirely locally without calls to Philips Hue servers. This should fix the issues some of you were having!
I continued my work on optimizations and performance to improve the speed of access to Gladys Plus!
While researching, I noticed a way to reduce the load on Gladys Plus servers as well as on local instances.
This change drastically improves performances, and I can't wait to see in production what it will look like on larger instances (like Terdious) or instances with slow connections (like Mastho).
We took the opportunity to make major updates to some of the dependencies we use:
From Node 12 -> to Node.js 14 LTS
From Sequelize 4 -> Sequelize 6
We switched to the latest version of node-nlp, the library we use for language recognition in Gladys. According to the tests we did, the language processing model recognizes requests much better! On top of that, new sentences have been added to the weather module for richer discussions with Gladys 😄
Everything was not necessarily easy to do, but we are happy to have done it!
If you installed Gladys with the official Raspberry Pi OS image, your instances will update automatically in the coming hours. It can take up to 24 hours, don't panic.
If you installed Gladys with Docker, make sure you are using Watchtower. See the documentation.
With Watchtower, Gladys will update automatically.
I take this opportunity to announce that we have a new Raspberry Pi OS image, which we build automatically based on the same build process that the Raspberry Pi foundation uses!
This image has several advantages:
It is always up to date. When you install Gladys on a Raspberry Pi, this image will automatically search for the latest version of Gladys during installation. During the first start, you will see a waiting page during the automatic installation of Gladys 🙂
It is more easier for us, because now we can build a new image automatically as soon as the foundation releases a new Raspberry Pi model.
Many thanks to VonOx for the awesome work done. I could not have done better !!
Update: 21/07/2020: Ce tutoriel est destiné à Gladys v3, il ne fonctionne pas avec Gladys v4 !
Salut à tous!
Je le disais dans mon dernier article, mon focus sur l'année 2019 est sur le développement du Gladys Gateway et de Gladys 4.
Aujourd'hui, je suis heureux d'annoncer le lancement de l'Open API du Gladys Gateway, qui permet un ensemble de nouvelles possibilités, notamment la possibilité de contrôler votre instance Gladys via Siri de n'importe où dans le monde.
It’s a tradition: each year, I look back at the year and summarise all the major developments surrounding Gladys. I try to be as transparent as possible, and share all the numbers: download numbers, site visits, and even revenue.
If you missed last year’s summary, the article can be found here (Only in French, sorry!).
