Top this overview! As a complement, I made a PR for the milight (Without rflink).
Hello!
Fresh install!
I was waiting for the beta, the alpha was still too « under construction » for a novice like me ^^.
First impression: Damn, it looks great :D!
Even the v3 wasnât ugly, but now itâs even better. Itâs clean, clear and well done.
I have a few questions:
- I just saw the Xiaomi home integration
. Is the gateway mandatory? If so, which model is compatible? (On v3, I think we had to avoid the latest versionsâŠ) - I used Telegram a lot to communicate with Gladys. Is its integration in v4 planned? (Edit: I found it ^^")
Finally, @pierre-gilles, @AlexTrovato I would like to participate in the French translation if itâs not too late! Iâm not good at coding, but English is my thing⊠
Thanks to everyone for this new version!
Hello @Biscotte,
From my side, having done the French translation, Iâm still interested in having you take a look at what weâve done. There are some translations Iâm a bit hesitant about; I sometimes went with my gut on specific things. And then an extra pair of eyes could help find any mistakes that might have slipped through despite multiple reviews.
You can either download @AlexTrovatoâs fork if you have the dev environment, or download the en.json and fr.json files here. If you find better translations, you can repost them as .txt files in issue #634.
Thanks in advance.
Ok, Iâll look at it tomorrow 
Itâs nice to hear that after months of UI development!
Yes, for the current Xiaomi Home integration. A Zigbee2mqtt integration is in progress and will allow you to use a Zigbee dongle instead of the Xiaomi Gateway.
The same models as v3! Iâm not really sure what the « rule » was to determine which ones are compatible and which ones arenât, but I think the ones that are compatible with Homekit and are more recent are not compatible⊠but Iâm really not sure 
Check the forum, thereâs info in other topics!
Hello everyone!
Itâs Monday, a good opportunity to give you an update on this weekâs developments.
Scheduled scenes are now available on the beta! Normally, your instances have been updated, and you should find this kind of triggers in the scenes.
The Philips Hue polling bug is now fixed! See the GitHub PR.
After a debate on the MQTT API, I started working on the specifications + changes to the Gladys 4 MQTT API, as well as developing new features related to MQTT! More information on this topic.
« Stéphane » on GitHub is working on installing the latest version of OpenZWave on the Gladys 4 Docker image. This will allow all recent Z-Wave devices to be compatible and better managed by Gladys. See the discussion on GitHub.
@VonOx is working on the new build process for the Gladys 4 Docker image, to prepare for the beta release of Gladys 4. See the PR on GitHub.
@joeypic is still working on RFLink, with the help of @peb this time to build the Docker image. See the relevant topic.
Iâve started individual calls with Gladys Plus contributors to help beginners get started and gather feedback on this new version Itâs very rewarding to have a phone exchange, it gives me lots of ideas to improve Gladys and I hope it gives a helping hand to novices who want to get into home automation.
This is a small preview of the developments, but there are plenty of other things being done in the background by the entire community.
Itâs great to see so much activity
Hello everyone!
Some news about the ongoing Gladys developments 
This weekend, I mainly worked on Gladys Plus (the offer I propose that allows Gladys users to access their instance remotely with end-to-end encryption), to improve a set of points:
- Gladys Plus will now stay connected much longer on your device, because I understand itâs not fun to type the password + 2FA! In terms of security, if your device is compromised, you can invalidate the session on another device (as is done in most apps, you are rarely or never disconnected, but you can revoke your session remotely).
- I worked on the responsive design of Gladys 4, the manifest.json, and on the app icons so that Gladys and Gladys Plus can be used as a real mobile or desktop app. Read my tutorial to use them on iOS/Android/MacOS/Linux/Windows as a real app. I will probably make a build with Cordova for a real app in the future, but it still requires work and I prefer to dedicate my resources to the missing features of Gladys 4 for now
- I fixed the redirect bug when Gladys Plus disconnects. See the commit.
- @AlexTrovato was on fire this Sunday, as he opened 7 PRs to close 7 GitHub issues, thanks for your support Alex, thanks to you the v4 will be released faster!!
See all his PRs. - @VonOx worked on the Docker image build process for the release, he did an amazing job! Thanks! Setting up the right deployment processes is crucial and itâs not always easy to debug, in short, his help will give the project a great advantage! See his PR.
- As part of the calls I have with the community, I spoke with @link39 this weekend to show me his Gladys 4 installation and discuss his ongoing developments: Milight and Yeelight soon!
Once again, things are moving fast
Feel free to ask if you have any questions/comments
Thatâs great!!! Things are really taking an interesting shape
Hello everyone!
As usual, a quick recap post of recent developments
This week, @AlexTrovato has done an amazing job on a lot of small issues, which allows us to make good progress on the milestone Gladys 4 RC.
1) The « Devices » view of the dashboard allows selecting the room by house
2) It is now possible to edit the name of a room
3) When a motion detector has never received a value, a message indicates it
4) The map is now zoomed in on the different subjects
@VonOx proposed an improvement, which is to center/zoom the map on the different points it displays. For example, on this map there is the userâs house + his position (these are fake data, I am confined donât worry :p)
There may be a good calibration to find the margin between the edge and the points present, after you tell me how it looks on your side, we can fine-tune these settings.
@link39 this should please you!
5) Some internal modifications of the server code
These modifications have no impact for the user, but simplify the developerâs work, and the stability of the software.
Database migrations are now launched automatically at Gladys startup, and not via a different command (which was launched automatically, but it was a separate process). See the PR.
This gives us the advantage of being able to run tests in RAM and thus have continuous integration much faster.
On my side, I spent all day yesterday integrating these changes to Gladys, and fixing small issues here and there, especially with the tool we use on the continuous integration side to check test coverage (CodeCov). It was systematically giving us errors in an unjustified way.
I found the cause of the problem, it wasnât our fault but itâs fixed!
All these modifications are available now in your Gladys 4 Beta, donât hesitate to give me your feedback
Top-notch progress!! Thanks to everyone for your hard work.
Congratulations to you all!
That looks great for the map! Weâll have to test it when we can get out of you, we
And it fixes the server-side test on my GitLab CI, great 
Hello everyone!
Some news about recent developments:
- The bug of creating multiple Z-Wave devices with the same name is now fixed! If devices have the same name multiple times, the user is alerted and can rename the device. The commit in question.
- The « Sonoff » integration has been renamed to « Tasmota », and many improvements have been made. Thanks @AlexTrovato! The commit.
- The bug of a blank page / or a freeze of the UI after going to the Z-Wave service is normally fixed.
- I created a topic for v4 developers on the forum, and published frontend development guidelines to get started!
Looking forward to your feedback on all this
Zwave: Indeed, I confirm the resolution of the bug with devices having the same name 
Regarding zwave, I have encountered several strange behaviors, two contradictory messages in the interface:
I get this with Gladys installed on Synology (Docker).
It should be known that the management of USB keys on Synology (docker) is not great. After each container restart, you need to remove and reinsert the Zwave stick for it to be correctly detected again, otherwise the zwave no longer works. By doing this, you force docker to generate a new virtual com port, and you therefore need to modify the com port in the home automation assistant. Yes, I say home automation assistant, because itâs the same thing on home assistant and co.
And it is at this moment (reboot + remove the key + reinsert the key) that I get the message in the screenshot above. Has anyone else seen this before?
Interesting! Would you have the error logs when this happens?
As luck would have it, I canât reproduce it ^^. Iâll try again later.
This kind of feedback on Gladys Plus Slack makes us happy to see that the work is appreciated Thanks @PhilippeMA for your positive feedback and support 