I just came across this article about the new features for Home Assistant.
I’m quite surprised because for Gladys, which is still a very young assistant, we have features that are much more powerful than Home Assistant!! And which have been present since almost the very beginning of its development.
You’re going to laugh, several times I contacted bloggers/YouTubers to tell them about Gladys 4, get their feedback and why not have them post tutorials/articles on their channel.
Several times I was told that Gladys 4 was so simple
Having never used HA, upon reading this article I tell myself « oh dear, I’m not sure I know what I’m doing with editing a file; if it starts like this what will I have to do afterwards. »
The article is dated January 30, 2023, so for me I have no reason to doubt, in principle. It’s not as if it were more than one or two years old.
It’s funny that I come across this topic while researching Gladys for my article because, as you point out and as I’ve been telling myself for the last 10–15 days since I started using Gladys again: There is nothing to say about Gladys — the documentation is super clear and complete, the interface is also very clear and you can see that each integration is meticulously added from back to front.
Automations seem disarmingly simple. So apart from the lack of some integrations, clarifying what is cloud/non-cloud with obligations like Gladys Plus, etc., it’s not obvious to write things.
And unfortunately this strength of Gladys can also be its weakness because if no one talks about it it’s not easy to make this solution known.
Home Assistant has the advantage of being far ahead on integrations and also more customizable, but that poses problems for the complete beginner in home automation.
Another advantage in my eyes is that it has a lot of non-cloud integrations (Tuya/Sonoff/calendar etc.) — so it’s truly local.
But as pierre-gilles says, and as I hope for him, the future will prove him right.
There are a lot of users on Jeedom and Domoticz; it’s those users you should target rather than HA users, because the latter are often tinkerers/geeks — however, that’s exactly the audience that could be interesting from a dev perspective.
For Home Assistant (HA) users, if we make the migration not too complicated (or consider the possibility of having both running in parallel), I’m sure we can introduce HA users to the simplicity of Gladys and capture some of the « tech‑savvy non‑developer » users
Development that would allow connecting Gladys to an external Zigbee2mqtt would be a big help to enable that
I agree with you for users migrating from Domoticz or Jeedom, but less so for « advanced » users
Gladys’s simplicity is a plus for beginners or those with « simple » setups.
We all have different visions of home automation, but here’s mine.
The three important points my home automation must have :
local
security
redundant (buttons and the home automation must work in case of internet outage so no cloud)
Now its purpose :
simplify life (coffee maker from a button or alarm, lighting ambiance, bin notification, appointments, etc)
secure my home (openings, camera, detection/recognition, notification, alarm)
optimization (monitor overall electrical consumption, per device, solar production, monitor well and potable water consumption, manage heating based on presence and off‑peak/peak hours (HC/HP) and Tempo days)
Of course these are just my home automation needs, but from frequenting some home automation groups, these remain the motivations of a large number of users.
Users coming to home automation often already have hardware (Wi‑Fi/Bluetooth) used with manufacturers’ apps. It’s this multitude of apps and the fact that they don’t communicate with each other that brings them to a solution like Gladys or a competitor.
Many of these services are available no‑cloud under Home Assistant (HA); I don’t know if alternatives exist in JavaScript (JS)
I continue exploring Gladys.
Next week I’ll switch my Zigbee hardware to Gladys with z2mqtt to see if HA still recognizes them anyway, which would allow me to really test Gladys in real conditions.
I will also test some functions like TTS without internet on Home Assistant (HA) to know if it’s local or cloud like Gladys.
If you copy-paste your entire configuration like @prohand did here :
You won’t lose anything, and you can switch back to HA once your test is finished if you ever want to go back to HA ^^
Afterwards, it’s a bit more technical but for now there’s no choice as long as we don’t have the feature.
If you encounter any problem when adding devices, don’t hesitate. It happens that some devices are not compatible, we don’t always support everything, but it can be added easily if you ask us
For TTS, if it’s local on HA, that means we could integrate it the same way on Gladys. I proposed a cloud offering so that it would have a very nice voice (generated by an AI — powerful GPU needed), and for ease of use, but I’m not opposed to local options if they exist and are stable and reliable.
Yes, I’ll enter the container just to add my devices YAML into the configuration.yaml.
We’ll see anyway — a simple pairing of the devices will be enough. I’ll test on my test Home Assistant (HA) instance to see if it correctly recognizes the devices from Gladys’ z2mqtt.
Hello, locally, on the CPU, Coqui and Piper are the best. I’ve been a long-time Home Assistant (HA) user, and I have to admit that the difference between using Nabu Casa’s cloud TTS and a local one, even on an RPi5, is unfortunately huge. More information on this blog Mike Gray | TTS Options For OpenVoiceOS otherwise we’re on Matrix https://app.element.io/#/room/#openvoiceos:matrix.org