New driver for [Smart Siren NEO] - [_TZE204_t1blo2bj] / [TS0601]

Hi @GD91 ,

I’m trying to implement the same siren to my Homey. As I understand, you have made a custom fork of the Tuya Zigbee app and implemented the siren? I am a bit hesitated to try it since I also use other tuya devices. If I’m going to use this custom Tuya fork, it will probably break all future Tuya devices and updates from the original branch. Have you asked the original Tuya app developer to merge your code in the main app?
Why did you fork the Tuya app and not the NEO app? The package is marked with “NEO Coolcam” branding. Tuya = NEO Coolcam?

Hello,

What I have done about that siren is a new app with only one driver.

So you can install it without any consequence for the others Tuya devices.

NEO coolcam is another kind of device which is working with Z-Wave …

This is the link to what I’ve designed for that siren : https://github.com/GD91a/sirene-NEO-new

I’m using it for several months without any issue

Regards

That is awesome. Thanks, I shall try to install it.

Okay, installed it using the CLI,
It seems to be installed but it keeps crashing immediately:


Tried restarting several times, tried to install the sirene as a unknown Zigbee device first, restarted Homey, and tried using it without the Tuya app (maybe some interference). No luck, keeps crashing immediately.
Maybe I forgot something? Installed Node.js, logged in to my Homey, navigated to the sirene-NEO-new-main folder and did:

>homey app install
? Choose an active Homey: Homey Pro 2023
You have selected `Homey Pro 2023` as your active Homey.
✓ Pre-processing app...
✓ Validating app...
✓ App validated successfully against level `debug`
✓ Packing Homey App...
 — App archive size: 1.68 MB, 209 files
✓ Installing Homey App on `Homey Pro 2023` (https://192-168-178-97.homey.homeylocal.com)...
✓ Homey App `fr.GD.sirene` successfully installed

Ideas?

Run the app using homey app run --remote, that way you’ll see any crash logs when they happen.

Thanks Robert,

This is the crashlog:

CreateClientError: Cannot find module 'zigbee-clusters'
Require stack:
- /app/app.js
- /node_modules/@athombv/homey-apps-sdk-v3/lib/Util.js
- /node_modules/@athombv/homey-apps-sdk-v3/lib/Device.js
- /node_modules/@athombv/homey-apps-sdk-v3/homey.js
- /node_modules/@athombv/homey-apps-sdk-v3/index.js Error: Cannot find module 'zigbee-clusters'
Require stack:
- /app/app.js
- /node_modules/@athombv/homey-apps-sdk-v3/lib/Util.js
- /node_modules/@athombv/homey-apps-sdk-v3/lib/Device.js
- /node_modules/@athombv/homey-apps-sdk-v3/homey.js
- /node_modules/@athombv/homey-apps-sdk-v3/index.js
    at Module._resolveFilename (node:internal/modules/cjs/loader:1140:15)
    at Module._load (node:internal/modules/cjs/loader:981:27)
    at Module.require (node:internal/modules/cjs/loader:1231:19)
    at Module.homeyRequire [as require] (/node_modules/@athombv/homey-apps-sdk-v3/index.js:12:19)
    at require (node:internal/modules/helpers:177:18)
    at Object.<anonymous> (/app/app.js:4:19)
    at Module._compile (node:internal/modules/cjs/loader:1364:14)
    at Module._extensions..js (node:internal/modules/cjs/loader:1422:10)
    at Module.load (node:internal/modules/cjs/loader:1203:32)
    at Module._load (node:internal/modules/cjs/loader:1019:12) {
  code: 'MODULE_NOT_FOUND',
  requireStack: [
    '/app/app.js',
    '/node_modules/@athombv/homey-apps-sdk-v3/lib/Util.js',
    '/node_modules/@athombv/homey-apps-sdk-v3/lib/Device.js',
    '/node_modules/@athombv/homey-apps-sdk-v3/homey.js',
    '/node_modules/@athombv/homey-apps-sdk-v3/index.js'
  ]
}

⚠ The app has crashed.
Exit Code: 1, Exit Signal: null

Apparently it is missing the “zigbee-clusters” module :thinking:
Should I install it like this ?:

You need to run npm install before running/installing the app.

Thanks again Robert… I’m a bit further. I can run the app remotely without crashing. I can add the Zigbee Siren, but when I try to activate it (in with the UI button, or in a flow) I get the error:

“Could not get device by id”

afbeelding

There are also no error messages being published in the remote terminal.

Installing the app and not running it remotely results in the same error. I’m probably still missing something. :thinking:

That sounds like an app bug, can’t help with that.

1 Like