Gladys Assistant 4.2 is available with Zigbee2mqtt compatibility! 🚀

@AlexTrovato I made a PR but I have a Bluetooth test that I couldn’t fix:

The test in question:

If you happen to be in the area :smiley:

I’m trying to understand the test but I’m having trouble understanding what is being tested here, I would avoid modifying it blindly and losing the meaning of the test :slight_smile:

Sorry, not much time at the moment. I’ll look at it as soon as possible.

Don’t worry, I’ll keep investigating on my side :slight_smile:

For information, I continued to investigate on my side this morning before today’s release, but nothing to do, I can’t fix the Bluetooth service tests, and I think it’s a sign that I don’t understand the integration :smiley:

I will therefore not push my changes which will probably do more harm than good, and we will have to wait for @AlexTrovato’s return to have a fix on this bluetooth bug.

Mon Gladys is up and running and since then the service has been working very well.
So I deduce that it is enough to restart the container to temporarily fix the Bluetooth service!
If this can help other users!
Well done for the release @pierre-gilles

It’s really random, which is why it’s quite complicated to reproduce this bug.

The Bluetooth service must not be ready at the moment Gladys starts.

I just activated the Zigbee2Mqtt integration on my new installation and everything started correctly on the first try. Bluetooth is still working so the bug I was talking about earlier did not occur :slight_smile: