I got impatient so I decided to DIY ![]()
I got the Moes 4-button Zigbee scene remote working on Homey and pushed the app source here:
Primordial1/homey-moes-ts0044-remote
Tested device details:
- Model:
TS0044 - Manufacturer:
_TZ3000_kfu8zapd - Product / remote type: Moes 4-button scene remote
- Endpoints:
1-4 - Cluster used for button events:
genOnOff/0x0006
Working actions:
- Button 1 single / double / hold
- Button 2 single / double / hold
- Button 3 single / double / hold
- Button 4 single / double / hold
Important:
This remote needs to be in scene/event mode (default mode) or Homey won’t receive button actions correctly.
To switch mode, hold buttons 2 + 4 for about 6 seconds until the LED indicates the mode change.
Homey Flow trigger exposed by the app:
Button [[button]] was [[action]]
Install instructions
-
Install the Homey CLI:
npm install --global homey -
Log in:
homey login -
Clone the repo:
git clone https://github.com/Primordial1/homey-moes-ts0044-remote.git cd homey-moes-ts0044-remote -
Install dependencies:
npm install -
Install the app to your Homey:
homey app install -
Pair the remote in Homey using the app’s driver:
Moes 4 Button Scene Remote
-
Put the remote into scene/event mode:
- hold buttons
2 + 4for about 6 seconds
- hold buttons
-
Create Flows using:
Button [[button]] was [[action]]
If the device was previously paired as a generic Zigbee device, remove it first and then pair it again using this app.
This was built specifically because this fingerprint was not matched by the TS0044 support I had available:
_TZ3000_kfu8zapd
If the maintainer of an existing Moes / TS0044 Homey app wants to add this fingerprint upstream, the implementation pattern is straightforward:
- bind
genOnOffon endpoints1-4 - handle Tuya action commands
- map action values as:
0 = single1 = double2 = hold
If posting repos is not allowed, let me know. Happy to remove and let the maintainer put it through the app.
P