[tecnicohome360-dev]

Adds support for Ekaza (Brazilian brand, Tuya OEM) Zigbee wall switches. They currently pair as generic devices, so on the 2- and 3-gang models all gangs toggle together.

Model	modelId	manufacturerName	Driver
1 gang	TS0001	_TZ3000_raytv4q5	wall_switch_1_gang
2 gang	TS0002	_TZ3000_xftvfolu	wall_switch_2_gang
3 gang	TS0003	_TZ3000_kl72oake	wall_switch_3_gang

All three use the standard multi-endpoint layout: one endpoint per gang (1..n), each with the onOff cluster (6) and working attribute reporting. They are mains-powered routers with the same firmware (appVersion 85). The drivers' existing endpoint mapping matches, so only the manufacturerName entries are added to each driver.compose.json (app.json left for the build to regenerate).

Interview – 1 gang (TS0001 / _TZ3000_raytv4q5)

"ids": { "modelId": "TS0001", "manufacturerName": "_TZ3000_raytv4q5" },
"endpointDescriptors": [
  { "endpointId": 1, "applicationProfileId": 260, "applicationDeviceId": 256, "inputClusters": [3, 4, 5, 6, 57344, 57345, 0], "outputClusters": [25, 10] },
  { "endpointId": 242, "applicationProfileId": 41440, "applicationDeviceId": 97, "inputClusters": [], "outputClusters": [33] }
],
"deviceType": "router"

Interview – 2 gang (TS0002 / _TZ3000_xftvfolu)

"ids": { "modelId": "TS0002", "manufacturerName": "_TZ3000_xftvfolu" },
"endpointDescriptors": [
  { "endpointId": 1, "applicationProfileId": 260, "applicationDeviceId": 256, "inputClusters": [3, 4, 5, 6, 57344, 57345, 0], "outputClusters": [25, 10] },
  { "endpointId": 2, "applicationProfileId": 260, "applicationDeviceId": 256, "inputClusters": [4, 5, 6, 57345], "outputClusters": [] },
  { "endpointId": 242, "applicationProfileId": 41440, "applicationDeviceId": 97, "inputClusters": [], "outputClusters": [33] }
],
"deviceType": "router"

Interview – 3 gang (TS0003 / _TZ3000_kl72oake)

"ids": { "modelId": "TS0003", "manufacturerName": "_TZ3000_kl72oake" },
"endpointDescriptors": [
  { "endpointId": 1, "applicationProfileId": 260, "applicationDeviceId": 256, "inputClusters": [3, 4, 5, 6, 57344, 57345, 0], "outputClusters": [25, 10] },
  { "endpointId": 2, "applicationProfileId": 260, "applicationDeviceId": 256, "inputClusters": [4, 5, 6, 57345], "outputClusters": [] },
  { "endpointId": 3, "applicationProfileId": 260, "applicationDeviceId": 256, "inputClusters": [4, 5, 6, 57345], "outputClusters": [] },
  { "endpointId": 242, "applicationProfileId": 41440, "applicationDeviceId": 97, "inputClusters": [], "outputClusters": [33] }
],
"deviceType": "router"

Happy to test a build. Thanks for the great work!

[JohanBendz]

Thanks for this contribution. The three verified Ekaza identities have now been selectively adopted onto modernize-2026-issues as part of the 2026 backlog cleanup. We are not merging older SDK3-based PRs wholesale, but the relevant manifest changes are preserved in the new code line. Tracking: #1469, draft integration PR: #1470.