Milan Davídek

Same question here, but for Czech support. My login is working in the android app: https://play.google.com/store/apps/details?id=dk.ista.IstaUi

Before updating to 2.0.0 I was running 1.35.x and the problem was present there as well.

updated z2m, issue still present, hold action still not reported Zigbee2MQTT version [2.1.3](https://github.com/Koenkk/zigbee2mqtt/releases/tag/2.1.3) commit: [unknown](https://github.com/Koenkk/zigbee2mqtt/commit/unknown) Coordinator type zStack3x0 Coordinator revision 20240315 got wireless version of the switch [WXKG03LM_rev2](https://www.zigbee2mqtt.io/devices/WXKG03LM_rev2.html#aqara-wxkg03lm-rev2) and it...

physical hold is reported as single: ``` info 2025-03-19 19:43:19z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/VYP ložnice', payload '{"action":"single","consumption":24.21842384338379,"device_temperature":26,"energy":24.22,"last_seen":"2025-03-19T19:43:18+01:00","linkquality":18,"operation_mode":"decoupled","power":21.04,"power_outage_count":24038,"state":"ON","update":{"installed_version":95,"latest_version":95,"state":"idle"}}' info 2025-03-19 19:43:19z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/VYP ložnice/action', payload 'single' ``` @Koenkk do...

QBKG11LM hold (reported wrong as single): ``` [2025-03-21 08:11:13] debug: zh:zstack:unpi:parser: parsed 28 - 2 - 4 - 129 - [0,0,18,0,126,135,5,1,0,105,0,109,167,194,0,0,8,24,72,10,85,0,33,1,0,126,135,29] - 148 [2025-03-21 08:11:13] debug: zh:zstack:znp:

QBKG12LM hold left (reported wrong as single left) ``` [2025-03-21 08:19:58] debug: zh:zstack:unpi:parser: parsed 28 - 2 - 4 - 129 - [0,0,18,0,4,199,5,1,0,116,0,183,80,215,0,0,8,24,24,10,85,0,33,1,0,4,199,29] - 225 [2025-03-21 08:19:58] debug: zh:zstack:znp:

QBKG11LM when hold much longer seems to report unknown key 65520 ``` [2025-03-21 08:31:01] debug: zh:zstack:unpi:parser: parsed 3 - 2 - 5 - 196 - [126,135,0] - 123 [2025-03-21 08:31:01]...

> Thanks for the logs! The Zigbee message send by the device seems to be exactly the same for hold and single, so we cannot distinguish it. So then it...

run into same bug today steps to reproduce: ```bash echo -e "services:\n a:\n image: hello-world" > c.yml podman-compose -f c.yml up #works mkdir subdir mv c.yml subdir/ podman-compose -f subdir/c.yml...

I can confirm that with `v1.1.0` it works, and the line is present there https://github.com/containers/podman-compose/blob/v1.1.0/podman_compose.py#L1685 and has been there long time before so it seems to be introduced by something...