This is probably the last release of the summer for Gladys. After that, I’ll work behind the scenes on some major topics that I’ll talk about when we return after the break, and I’ll of course take a well-deserved vacation to rest
Fixes in this v4.61.1:
HomeKit: Handling of simple roller shutters Roller shutters in Gladys that don’t have percentage-based control but only a simple control are now correctly handled in the HomeKit integration. Thanks to @bertrandda for this contribution!
CalDAV: Option to ignore SSL certificate verification For users of self-hosted CalDAV servers (self-signed), it is now possible to disable SSL certificate verification. Thanks to @bertrandda for the development.
Netatmo: Support for min, max and average temperature values Netatmo sensors now distinguish between minimum, maximum and average values so as not to pollute the « Room temperature » widget. Thanks to @Terdious for this improvement!
Zigbee2MQTT: Fixed the « Allow pairing » button that stopped working after the upgrade to 2.4.0. Thanks to @Yoann_PUREN for reporting this bug
Hi @pierre-gilles I don’t know why the update is causing my Zigbee2MQTT to crash
I checked the configuration.yaml and mosquitto.conf settings against my backup, everything is identical.
I need to recreate the Docker manually for it to work again.
@bjm Since you’re halfway between a manual installation and an installation managed by Gladys, you’ll have cases like this at every Gladys restart
In my opinion, you need to make a choice:
Either you switch to a fully manual installation with an external Zigbee2mqtt (with a custom container name, not gladys-z2m-zigbee2mqtt)
Or you switch to a fully Gladys-managed installation, with Gladys launching the Zigbee2mqtt container
The problem here is that you’re not launching the container the same way Gladys would, and thus the Zigbee2mqtt configuration you made doesn’t match the information Gladys has to launch the container.
In Gladys, the container is launched like this:
The only thing that’s replaced is the PathOnHost, which becomes the path of the USB port you selected in the Gladys interface
@bjm In that case, you need to stop and remove the Zigbee2mqtt container.
Then, edit the configuration.yaml file that you must have modified when switching to manual. For example, I have this configuration in the serial section for the USB port:
serial:
port: /dev/ttyACM0
adapter: zstack
For the port, I imagine you changed that configuration; you need to switch it back to /dev/ttyACM0.
For the adapter field, I don’t think you changed it.
Normally, if you restart Gladys, it should restart the container with the correct information; otherwise, in the Gladys integration interface, you can restart it.
For the USB port, of course make sure the correct one is selected in the interface