There’s no plug-and-play solution, you need to flash the key at minimum
I mainly need ready-made assembly and don’t want to flash with hardware.
So, I found two on your list that interest me with antennas.
Can they be used as relays?
Like, I connect one to the pi and another to the outlet, will the mesh be created?
Yes yes, there are just several methods apparently depending on the key and I don’t want to buy additional equipment to be able to do it.
Once flashed, is there no maintenance, no updates to be done on this key?
Reflash to update the firmware (I’ve never done it 
)
Once configured, you don’t touch it anymore
A small clarification, however, to make it clear, zigbee2mqtt is not yet integrated into v4. It is in development!
It seems to me that it’s still going well, right?
It will be available for testing soon…
@VonOx, your network display is nice. Do you do it from the Zigbee2mqtt frontend or did you do it yourself via software?
I plan to integrate network recognition and display in Gladys later.
As I have nothing to manage for the moment, I use this + HA:
Regarding unit tests, where are you at? Don’t hesitate to ask any questions here.
And regarding rebase with the current master of Gladys v4, have you done it recently / not yet?
Regarding prettier / eslint, was the PR good?
(Sorry for all these questions, it’s just to get an idea of the progress!)
I agree that publishing a test image is a first step, but I’m really afraid of merging this PR which is based on code almost a year old if I remember correctly?
I know we set the bar high in Gladys Assistant 4 on code quality, but it’s really the only way to have stable software in the long term. I’m always available to help implement best practices if needed
I did the rebase this weekend when I saw that v4 was released. 
I spent a lot of time trying to draw as much inspiration as possible from what had already been done in the other services, so I think it’s not too messy.
Prettier OK. Eslint to do.
My goal is to deliver an image to get test feedback in various configurations.
I will do the unit tests while users test the image.
After that, there will always be back and forth, but I think we’ll get there without too much damage. 
Great news! Phew, that’s reassuring, I was afraid it was older
Ok!
That works. I don’t know how many lines of code there are in your PR, but there will probably be just as much code in the tests, so don’t underestimate the time needed to write them, tests are important and they take time 
For next time, really try to make sure that tests are part of your development flow. Writing all the code at once and then all the tests at once isn’t really the simplest or most motivating, tests should help you develop. Writing tests « just to write tests » isn’t really the point of the operation
I understand the principle well, but I’m an « old-timer » who started with assembly and then C on very small microcontrollers…
At the time, it didn’t exist, and I really struggle to get into it, used to real testing…
It already took me to get into Node…
Just a quick message to those who don’t dare to participate (that was my case at the beginning), that knowing software development and putting in a little effort, you can contribute to Gladys.