Looks like this is supported by Zigbee2MQTT: https://www.zigbee2mqtt.io/devices/E2134.html
Back in the days I had to amend /etc/zigbee2mqtt/configuration.yaml, but looks like
the new mode is somewhat different, I need to publish a message:
I first started to watch the logs:
# journalctl -f --unit zigbee2mqtt.service
Then to enable new device to join, I typed:
[matelakat@home01 ~]$ mosquitto_pub -t 'zigbee2mqtt/bridge/request/permit_join' -m '{"time": 254}'
Once I have seen the messages, I disabled auto discovery:
[matelakat@home01 ~]$ mosquitto_pub -t 'zigbee2mqtt/bridge/request/permit_join' -m '{"time": 0}'
After that I renamed the device's friendly name:
$ mosquitto_pub -t 'zigbee2mqtt/bridge/request/device/rename' -m '{"from": "0xf84477fffe7df6d3", "to": "corridor_motion_sensor"}'
Observing the logs, I see these kind of messages:
{
"battery": 100,
"illuminance": 6,
"linkquality": 112,
"occupancy": true,
"update": {
"installed_version": 16777316,
"latest_version": 16777316,
"state": "idle"
},
"voltage": 3200
}
Now it is time to adjust my code to be able to cope with it.