[APP][Pro] Nous - Save energy, increase security and comfort of your home and create amazing ambiances

Apps
304

Hello,

“Sorry for the delay but I was very busy these past days.”>>> its ok, we have work !!:wink:

This is indeed the right model.

I ordered a D3Z which I’ll receive today; I’ll try to pair it too and keep you posted.

Regards

20260827_155106
20260827_1551061920×2400 898 KB

20260827_160139
20260827_1601391147×3263 519 KB

20260827_155111
20260827_1551111920×2319 1.03 MB

305

Hi,

Di you try topair it with the new test version ?
It’s the 2.19.5 Nous App version.

Regards,
SoPhos

306

By the way, I’ve released a new test version of the Nous App driver (with cleaned-up bindings) for the Nous DXZ and Nous D5Z Pro models. Could you please test it and let me know how it goes?

I’m giving it a try; the app is working, but I still can’t add the D5Z Pro—I’m still getting the error message. However, there was something new: the relay changed state during the pairing process, right when the error message appeared… so we’re making progress!

Nous test
Nous test558×952 68.4 KB

307

I just tried with DXZ as well, and that didn’t work either.

308

You can forget DXZ device for your D5Z Pro, it’s not the same driver at all.

309

Ok, I will try to unpair and pair again my own D5Z Pro after full restart to control pairing is still working (can’t see why it souldn’t but I must try).
Unfortunately, if it’s working, I won’t be able to do much more than that. And if not, I will find very quickly what’s going on…

Regards,
SoPhos

310

I kind of suspected as much… but I gave it a shot!
What surprises me is that I’ve already added plenty of Zigbee and Z-Wave modules, and I’ve never run into trouble like this before…

311

Thanks, it’s kind of you to go to the trouble.
If it doesn’t work, I’ll try returning them.
I bought five of them at once, since the D3Z worked well and these were cheaper and handled more power…

312

I just received the D3Z; it was easy to add, just like the previous one… I’m going to send back the D5Zs.:wink:

313

Ok, no problem.
I’ll keep my test (unpair and pair again my own D5Z Pro) to confirm there is no problem with driver.

Regards,
SoPhos

314

Okay, anyway, thanks for your help.:wink:

315 
Hello,
I wanted to replace my A1Z sockets with A7Z (16A) sockets.
The data reported by the socket is incorrect...
After being plugged in for 10 minutes: 552 W (fridge) and a voltage of 2372 V (220 V).
The same thing happens with two A7Z sockets.
They work fine with the A1Z socket.
Thanks for your help.
Serge

Nous A7Z
Nous A7Z556×534 25.4 KB

316

Hi Serge,

There is an option on A7Z device settings in Homey to divide Voltage becuase, depending on firmware, some devices need this.
Can you test and tell me if t’s Ok now ?

317

Hello,

thanks for you help … info much better now … :grinning_face:

Tension & Puissance Ok …

Thanks …

Nous A7Z Puissance2
Nous A7Z Puissance2583×664 28.4 KB

318 
Hello,
A comparison between our A1Z and A7Z models...
The last two graphs for the A7Z are incorrect...

Thanks for your help.
Serge

A1Z
A1Z2763×1765 337 KB

A7Z
A7Z2773×1764 183 KB

319

Hi Serge62,

I’m not sure about what you want to say…

Do you mind about A7Z Voltage graph (“Tension” in french)?
If so, it’s normal because you’ve got starting values higher than the normal values (due to 10x multiplicator).
And same for Energy because it seems to be calculated (this is an option in device settings).
You just need to clear all values in Homey graph settings.

To verify, you just need to take shorter delay (last 2 days for example).

Regards,
SoPhos

320

Hello, Thanks for information … :grinning_face:

321

Hi Serge,
I tested the E6 clock issue again on a real TS0601 / _TZE284_wtikaxzs and got it working on Homey.

The missing part is to actively send Tuya MCU time sync, not only wait for the sensor to request time.

Please add this to the E6 driver:

Cluster: 0xEF00
Command: 0x24
Payload length: 8 bytes
Bytes 0–3: UTC Unix timestamp, uint32 BE
Bytes 4–7: local Unix timestamp, uint32 BE
Epoch: 1970-01-01

Best moment to send it is when the E6 has just reported a Tuya datapoint, so it is definitely awake. It can be rate-limited, for example once per hour.

Example:

const now = new Date();
const utc = Math.floor(now.getTime() / 1000);
const timezone = await this.homey.clock.getTimezone();
const offset = getTimezoneOffsetSeconds(now, timezone);
const local = utc + offset;

const payload = Buffer.alloc(8);
payload.writeUInt32BE(utc >>> 0, 0);
payload.writeUInt32BE(local >>> 0, 4);

await tuyaCluster.timeSyncResponse(
  {
    payloadSize: 8,
    payload,
  },
  {
    waitForResponse: false,
  }
);

I tested this today on _TZE284_wtikaxzs and the clock appeared on the display immediately after the command was sent.

So the fix should be simply: send 0xEF00 / 0x24 with UTC + local Unix time, epoch 1970, preferably right after an incoming E6 datapoint.

322

HI Mates1134,

Thank you, I already had to use MCU Time sync (cl 0xEF00) for other Zigbee devices but I hadn’t even thought about trying it on the Nous E6 device!
It’s now in my todo list…

Nice one :1st_place_medal: Thank you very much!

Regards,
SoPhos

323

Hi all,

Following Fred Berger’s request, a new version of Homey Nou App has just been published in test. This new version adds compatibility for a new product :

Smart RGB Bulb GU10 (Nous P8Z)

image
image448×495 47 KB

You can test this new test version on Homey App :

Regards,
SoPhos