Yes, it’s great, if I add an already existing device, it is replaced everywhere in Gladys.
I did the test with my « PriseBureau ».
Old device:
New device, which I renamed for testing:
List of current devices, only the new one has replaced the old one:
In my dashboard, the old device has been replaced by the new one:
Good work in the end, I know we had talked about this kind of feature with @cicoub13 without having the time to implement it.
Thanks for your work 
Isn’t it dangerous to have an On/Off switch on a fridge? 
That was my only way to measure my fridge’s consumption. But coupled with a temperature sensor in the fridge, it’s super interesting!
)Yes you are right, belt and braces 
FINALLY!!
Because the 5MB page that takes forever to load and doesn’t allow filtering had reached its limits!
We’re two in your case
Hello, does anyone know how to connect to the MQTT broker (e.g., the IDs)?
I would like to access it via Node-RED to complete the devices that are in error or not yet integrated.
You can retrieve the credentials in the database (db browser) in the variables table.
Can I assume that device compatibility is improved and that compatibility with older devices is maintained?
(to know if I propose the review of the PR)
For me Yes!
Existing equipment can be added to new and the old ones will then be replaced.
That’s not the question!
If we ever deploy this version to everyone, will everyone be forced to disconnect/reconnect all their devices in Gladys (which we don’t want, as it will break everything: existing scenarios, etc.), or will everything work without any manipulation for anyone?
Will this break scenarios? For example, if you have already created a scenario in Gladys that involves a Zigbee2mqtt device configured in the old integration, if we switch to the new one, will your old scenario continue to work?
I responded incorrectly, but in my tests everything is functional.
I meant to say « It works without breaking the existing system and if the user wants to update their devices, it also does so without breaking compatibility. »
Hello, on my side everything seems okay after removing and re-adding the devices, however, it seems some mappings are missing. I have an LED controller (RGBWW) that allows me, among other things, to control the warmth of the white or the color, but only the whites are managed in Gladys:
The controller is a GL-C-008P.
Thank you for this feedback.
Before adding the new devices, did you check that the old devices were still functional?
I will look into these missing features. Were they present before?
Yes, still functional!
Apologies, I hadn’t seen the second question, no the device was not yet supported by Gladys unfortunately!
As long as there is no regression, it’s fine for me
Haha I found the color, I had done all the code, but I forgot to load the mapping file.
I’m launching a new version of the image tonight (up to date with the latest changes), it should be ready tomorrow
Well, I’m cheating a little, on the new (new) image, I’m adding a 2nd feature (separate PR), the « Update » button on the device discovery page, so that you don’t have to delete the already registered device to add the new one, BUT I haven’t tested it (still no zigbee2mqtt device )
I’m taking the initiative to add this feature in addition to the other one so you don’t have to test twice.
However, if there are any problems, we’ll go back to testing with a smaller scope, step by step.
