PA-44Z: expose the test property to ring the alarm

[RemyRoux]

This change aims to enable the alarm to be triggered via home assistant.

I'm a new user so I'm not sure whether this would work. Intuitively, the alarm should be able to be triggered by home assistant. The test button rings the alarm so I'd assume that setting the property to True would ring the alarm. It's worth a try.

[Koenkk]

Thanks!

[raveit65]

@RemyRoux @Koenkk
This doesn't work with my PA-44Z.

With zdm-2.1.1 settings looks like this.

With zdm-2.1.3 i have a non working switch in settings.

This happens in log when i try to use the switch.

[2025-03-02 14:42:22] debug: 	zh:zstack:unpi:parser: --- parseNext []
[2025-03-02 14:42:41] debug: 	z2m:mqtt: Received MQTT message on 'zigbee2mqtt_2/RM Küche/set/self_test' with data 'true'
[2025-03-02 14:42:41] debug: 	z2m: Publishing 'set' 'self_test' to 'RM Küche'
[2025-03-02 14:42:41] error: 	z2m: Publish 'set' 'self_test' to 'RM Küche' failed: 'Error: No datapoint defined for 'self_test''
[2025-03-02 14:42:42] debug: 	z2m: Error: No datapoint defined for 'self_test'
    at Object.convertSet (/app/node_modules/.pnpm/[email protected]/node_modules/zigbee-herdsman-converters/src/lib/tuya.ts:1635:27)
    at Publish.onMQTTMessage (/app/lib/extension/publish.ts:252:52)
    at EventEmitter.wrappedCallback (/app/lib/eventBus.ts:204:23)
    at EventEmitter.emit (node:events:536:35)
    at EventBus.emitMQTTMessage (/app/lib/eventBus.ts:137:22)
    at MQTT.onMessage (/app/lib/mqtt.ts:157:27)
    at MqttClient.emit (node:events:524:28)
    at handlePublish (/app/node_modules/.pnpm/[email protected]/node_modules/mqtt/src/lib/handlers/publish.ts:172:11)
    at handle (/app/node_modules/.pnpm/[email protected]/node_modules/mqtt/src/lib/handlers/index.ts:31:17)
    at work (/app/node_modules/.pnpm/[email protected]/node_modules/mqtt/src/lib/client.ts:779:17)
[2025-03-02 14:42:47] debug: 	zh:zstack:unpi:parser: <-- [254,5,69,196,155,98,1,116,244,252,254,29,68,129,0,0,0,5,155,98,1,1,0,87,0,16,168,122,0,0,9,25,62,0]
[2025-03-02 14:42:47] debug: 	zh:zstack:unpi:parser: --- parseNext [254,5,69,196,155,98,1,116,244,252,254,29,68,129,0,0,0,5,155,98,1,1,0,87,0,16,168,122,0,0,9,25,62,0]
[2025-03-02 14:42:47] debug: 	zh:zstack:unpi:parser: --> parsed 5 - 2 - 5 - 196 - [155,98,1,116,244] - 252
[2025-03-02 14:42:47] debug: 	zh:zstack:znp: <-- AREQ: ZDO - srcRtgInd
[2025-03-02 14:42:47] debug: 	zh:zstack:unpi:parser: --- parseNext [254,29,68,129,0,0,0,5,155,98,1,1,0,87,0,16,168,122,0,0,9,25,62,0]
[2025-03-02 14:42:47] debug: 	zh:zstack:unpi:parser: <-- [1,0,0,23,0,0,116,244,28,21]
[2025-03-02 14:42:47] debug: 	zh:zstack:unpi:parser: --- parseNext [254,29,68,129,0,0,0,5,155,98,1,1,0,87,0,16,168,122,0,0,9,25,62,0,1,0,0,23,0,0,116,244,28,21]
[2025-03-02 14:42:47] debug: 	zh:zstack:unpi:parser: --> parsed 29 - 2 - 4 - 129 - [0,0,0,5,155,98,1,1,0,87,0,16,168,122,0,0,9,25,62,0,1,0,0,23,0,0,116,244,28] - 21
[2025-03-02 14:42:47] debug: 	zh:zstack:znp: <-- AREQ: AF - incomingMsg - {"groupid":0,"clusterid":1280,"srcaddr":25243,"srcendpoint":1,"dstendpoint":1,"wasbroadcast":0,"linkquality":87,"securityuse":0,"timestamp":8038416,"transseqnumber":0,"len":9,"data":{"type":"Buffer","data":[25,62,0,1,0,0,23,0,0]}}
[2025-03-02 14:42:47] debug: 	zh:controller: Received payload: clusterID=1280, address=25243, groupID=0, endpoint=1, destinationEndpoint=1, wasBroadcast=false, linkQuality=87, frame={"header":{"frameControl":{"frameType":1,"manufacturerSpecific":false,"direction":1,"disableDefaultResponse":true,"reservedBits":0},"transactionSequenceNumber":62,"commandIdentifier":0},"payload":{"zonestatus":1,"extendedstatus":0},"command":{"ID":0,"parameters":[{"name":"zonestatus","type":33},{"name":"extendedstatus","type":32}],"name":"statusChangeNotification"}}

And the entity binary_sensor.rm_kuche_test is missing at my dashboard.

I am happy to provide more debug infos?
Should i open a new report or is posting the issue here sufficient?

[jswhh]

Same problem here - test property not available any longer

[RemyRoux]

Sorry guys I hadn't tested properly. I'll revert this change.
I contacted the manufacturer who said that the alarm can be triggered from the tuya app when connected via a tuya hub.
So there should be a datapoint that could be used to trigger the alarm. But I don't have a tuya hub handy. If someone could do the datapoint search, it would be much appreciated!

[raveit65]

With lidl gateway and tuya app i don't have an option to trigger a test alarm in tuya app.
There is only an option to enable receiving test alarm events from the device.

When last option is enabled you see this popup when you trigger the test alarm with the button from device.

If this option is disabled than no popup is triggered.