Yes, works like a charm now, thanks! 
Which brings me to a new question; the power measurements seem highly inaccurate. Is that me or do more people experience this?
Can you take a look at voltage ?
Because of latest firmware, recent Nous A7Z devices have a voltage multiplicated by 10 comparated to previous ones.
So, there is an option on device settings to divide voltage by 10.
And as there is another option on device settings to calculate power instead of getting it from device, try this one too…
Regards,
SoPhos
I have an issue. I ordered 3x Nous A11Z Power Strips from Amazon.They seem to work so far but there is an issue with the device driver. No matter which of the 3 devices I turn on/off, all 3 sockets get activated or deactivated. It seems this has to do with an issue of the cluster mapping for the sockets.
Z2M had the same Issue where all sockets were switched where only one should be. I found an article in french explaining a custom mapper for Z2M to fix the issue. In newer versions the device is now supported natively. So I guess with the information it might be possible you can build a fix for your app?
Device Data:
Here is the link:
Hi Florian_Truck,
Yes, you’re right. Based on my own research, it appears that the latest chipsets and firmware versions used in at least the Nous Power Strip A11Z and the Nous Smart Switch LZ2 are not currently working as expected with the Nous App.
I need to spend some time investigating the issue to understand exactly what is happening. As suspected, it seems to be related to the need for updated converters, such as those provided by zigbee-herdsman-converters.
Please be patient while I work on resolving this issue, as I will have to do it in my spare time.
In the meantime, while waiting for a new release of the Nous App, you could try the Tuya Zigbee App by the excellent johan_bendz.
He is my mentor (he even doesn’t know), and there’s a chance that Tuya Zigbee App may also work with your device.
Regards,
SoPhos
The Tuya app shows the same problem: all three sockets are switching.
With a bit of vibe coding I managed to create my own driver:
My version combines everything in one device. I like this even better because I think 3 different devices make no sense for something that resembles one device.
Has anyone solved the problem of the time not being displayed on the Nous E6 sensor screen?
Hi Florian_Truck,
I wasn’t aware of that, sorry. So I’ll have to fix it sooner than I expected. I think I can make it in July.
Well done! If you want me to integrate your driver code into the Nous app, don’t hesitate to share it. It would save me some precious time.
This is only a design choice, but having only one device for 3 peripherals could be a problem for some users. For example: rapid switching, grouping one of the devices with others, placing devices in different rooms or groups, etc.
Regards,
SoPhos
Another option would be to create a virtual device (e.g. via the Device Capabilities app) that combines the three devices. This way you can also use the original individual devices should you (or other users) need/prefer them.
Thanks for your reply. I appreciate your feedback.
Here is the code:
Feel free to take whatever you need to make it work. As far as I understood it was necessary to have an explicit mapping of the capabilities to the zigbee endpoints. And additionally there is this “magic packet” initialization in onInit of the driver that requests certain clusters in a specific order to “unlock” the device for normal usage. Besides there is not a lot of stuff going on.
Regarding the design choice:
Well, physically it is one device, so it can only be in one room at the same time. I also for myself do subgroups but they remain under the same room. So I understand what you mean. But from an UI perspective there is also the point that you clutter your device overview with “unnecessary” devices additionally. Also: When you have unused sockets, they are also a device but not in use then. So you also have ghost devices that fill up space in your device overview. Plus: you can not hide devices. You can only delete them. But if you delete one of the subdevices all devices get deleted, so you are foreced to keep them.
Plus: The device capabilities app can also used the other way around and you can create single devices that refer to the collecting device 
Forgot to mention: Other apps like for example the Tasmota device app also creates one single device for a power strip, so I assume they had to make the same design choice.
FYI: Check this knowledge base article on how to hide and unhide devices in Homey.
This works great for the app. But not for the desktop website that I mainly use.
You are not blind 
. It seems you are using an older version of the web app. Are you logging in to your Homey via a local user account?
If so, the local web app version is not up to date. I think it is version 1.15.x, while the cloud web app version is currently on 1.18.1. Check the cloud version via my.homey.app.
Correct. The cloud version shows the hidden devices menu.
So in the end there is the decission: Do I create one device with 3 sockets or 3 devices with one socket each where only the first device shows the power monitoring (which I find more odd than a single device).
The implications are:
1 Device variant: I have to create 3 single devices if I want to manage them separately and have to hide 1 device.
3 Device variant: I have to create a single device and have to hide 3 devices. Plus I have to deal with the power values separately.
I honestly don’t know what’s better.
Oh I forgot another implication: Nonetheless of what way is chosen: Users of the local web app will not be able to hide devices unless the new UI is rolled out for them too.
Did you see my earlier post on the option to create an Advanced Virtual Device in addition to the three physical decices created by the app?
Such a virtual device allows you to include all capabilities of all three physical devices in one virtual device. So including 3 on/off buttons, three power/voltage readings etc.
You could then hide the three physical devices or move them in a zone/sub-zone not (directly) displayed on the main screen.
So that might also be an option to consider.
Thats what I described as the 3 devices variant. So instead of hiding one device i need to hide 3 devices. And additionally it is (only for me) not practical since I can not hide them in the local web app anyways. And I need to fiddle with the advanced capability app and figure out how to sync the properties.
